2010-01-26 Tuesday Meeting
Agenda
- Goal of meeting
-
Proj. Mgmt.
- No estimates for proj. mgmt. tasks, not on graffle (Josh)
-
Proto-Checklist: http://spreadsheets.google.com/ccc?key=0AnDHwaZ2QLBSdDlJeDFBYmV4emVrT3FjRWtNWEE2ZWc&hl=en
- What is it? The goal?
- Anonymous?
- Something we want to move forward with? If not, what format?
- Timeline ok?
- (Mgmt questions?)
Notes
Agenda (addenda)
- Estimates
- Google docs
- Tools
Estimates
- Think they are on all items
-
Discussion
- Model: 5 days for X people needs to be broken down
- need to be able to see how the workload is balanced
WorkPlan
- https://trac.openmicroscopy.org.uk/omero/wiki/WorkPlan
Google Docs / checklist
- Did everyone have a look? Apparently yes.
- Find our goals
- Needs to be something we can agree on
-
Jean-Marie
- -5 to 5, no parts
- hard finish deadline: Monday night
- Process them for Tuesday
-
Empty answers: question mark is unclear, blank is no opinion
- non-numerical means
- 0 is no opinion
- empty is don't understand
-
strong disagreements
- this is just a plan/survey
- need to work towards consensus
- will look for workarounds, etc.
-
Scott: adding mgmt questions?
- Jean-Marie: later step
- anonymity?
-
Jason
- we've spent more time on scoping 4.2
- hopefully in a few months we're saying "that was worth it"
- is this survey appropriate now? or in 6 weeks? probably both
-
Jean-Marie: another survey, don't combine too many things
- the question at the moment is process/tool for the majority
Tools (Mingle & Jira)
-
Donald
- Jira seems complicated (UI), fewer display options
- Mingle, more stream-lined, easier to define views
- Mingle, SVN integration with mingle wasn't as complete
- Mingle, neater, more pretty, more slick
-
Chris
-
Jira setup was a pig. (JaveEE app)
- powerful, tons of features
- multiple way to describe linkages between 2 tickets
- might take a couple of weeks to get setup
- we have to share the proj mgmt load
-
neither of the 2 has as good source integration (display/tools)
- no display in Jira
-
neither does everything out of the box
- need fiddling
- possibly sacrifices
-
neither will import trac data
- will probably have to write tools to import
-
Jira setup was a pig. (JaveEE app)
-
the trac-based ones didn't support dependencies
- Josh: I think agilo does
- Chris: will try to get that setup.
-
Donald
- mingle is more reliable ($$ and company's using it); has training
- Andrew: is that also an argument for Windows?
-
Jason
- turning it around, are these an improvement?
- Chris: both will certainly track more knowledge of the process ---- exchange, visualize, encourage us to put the info in ---- (trac discourages all that)
-
Donald: agree. both give an overview of the whole system
- google-map style zooming in and out
- Jason: coming from a different background, this feels alien
-
Ola
- mingle is powerful in terms of progress
- how much of the process should be automatic (v. by-hand)
- Chris: jira/mingle takes text from commit into issue/card
- Jean-Marie: a best practice
- Chris: we'll have to be militant about the commit formats! (mingle)
-
Chris: mingle has nice chat integration (automatic devteam!)
- i.e. collaboration environment (different philosophy)
- Jira is more focused on issue tracking
-
Jason: does one have more traction?
- both are moving
- Jira is huge, lots of opensource up-take
- Mingle is a bit more fragile
-
Jean-Marie: as we get more QA tickets need something to handle it
- Chris: not designed to satisfy open-source workflow (public is extra)
-
Andrew: any problem being open?
- Chris: No. Just have to configure/pay.
-
Jason: what do the public URLs look like?
- chris: mingle ones look nicer
-
Donald
Jason (misc)
- trips; meetings in the US
- JCB would like UI updates to page
-
ASCB: thinking about experimental ontology
- cF. ontology-lookup-service
- on-going (in planning)
- Bio team funding deadline April 1, waiting
-
kinetchore tracking is acceptied in JCB
- production mode
- Big day: June 26th
-
growing team, and not exclusively in Dundee
- lifetime, hcs, etc.
- also people for istalling/evangelizing