Agenda

Remember: Agenda must be complete (with estimated times) on the day before the meeting. Any additions after that must go at the bottom (AOCB)

1. Accepting minutes from last meeting

2. Matters Arising (<10 mins)

   • Jason: don't use omero-team for personal contact (it's for computer spam)
   • Josh: talk to Jason about calendaring.
   • Josh: move emails to omero-team.

3. Milestone suggestion (josh/jean-marie)

   • current (4.3.2)
   • next (5.0)
   • WIP
   • usability backlog
   • team backlog ("Unscheduled")
   • Promotion of OMERO?

4. Any other business (<5 mins)

   • OME Schema License Discussion - Wed 31st at 9am Central time (3pm UK time)

In Attendance

• Brian, Melissa, Colin, Josh, Carlos, Jean-Marie, Littewood, Simon, Andrew, Scott, Curtis at 14:45, Jason 14:48

Notes

1. Accepting minutes from last meeting

   • Approved
   • JMB: File format tests happened yesterday, a few bugs reported.
   • Josh: Multiuser import is slow, it probably needs some more optimizations
     • We should track the problems because others could experience the same thing.
     • Hopefully this will go away with pre-importing the test data
     • JMB: This makes it hard to know if its a file format or a performance issue
     • Elwood: seemed inconsistent. Able to delete from one client but not the other
       • Josh: This problem should be tracked. L'Wood: This resolved itself
         • Josh: We should still probably track these sorts of issues.
   • Melissa got what she needed?
     • Should be ok. Not that many actual bugs.

2. Matters Arising (<10 mins)

   • Jason: don't use omero-team for personal contact (it's for computer spam)
     • Jason needs to sync with Josh. Josh: Will talk to him.
   • Josh: talk to Jason about calendaring. (Google groups maybe)
   • Josh: move emails to omero-team. DONE
     • Streamlined reporting: should be getting less emails now
   • Discussion:
     • Reminder: Josh is arriving Monday morning (arriving in Dundee Sunday night)

3. Milestone suggestion (josh/jean-marie/scott loynton) Starting at 14:45

   • Proposal
     • current (4.3.2)
     • next (5.0)
     • WIP
     • usability backlog
     • team backlog ("Unscheduled")
     • Promotion of OMERO?
   • Why we're discussing this?
     • JMB and Scott met and talked about where tickets go
     • Josh: We have been fighting against trac, this is another attempt to get it working better
   • Scott: usability backlog as a template
     • ticket 3545 - lots of things, hard to manage.
     • change to 2818, requirement at the top, with user stories in each particular area
     • below that, collection of tasks.
   • Andrew: this is where bugs are going?
     • JMB: not really. collection of stories in a requirement
     • Josh: http://trac.openmicroscopy.org.uk/ome/wiki/DevelopmentGenericProcess
     • Andrew: problem is it goes against idea of open ended tickets.
   • Josh:
     • When we are working on things under investigation, we only move one item at a time into working milestone to avoid spam
   • Jason: obvservation, wanting tools to do things that they can't do.
     • e.g. Josh's example of "I want to see when we're done"
     • e.g. whiteboard gets a ton of things on it.
     • Is the answer to do use queries?
     • Observation: Things that depend on strict behaviour will probably not work ideally, might run into problems
   • Andrew:
     • don't have a problem with the proposal
     • but had decided to use keywords (ever-living) rather than requirements/stories.
   • Elwood (opinion of a new start)
     • Used punchcards with box of stories.
     • Took stories at the front and put them on the wall.
   • Around the room
     • Simon:
       • happy to work with the story
       • made more complicated by learning trac & the process at the same time
       • "put things into current milestone, make new story in next milestone, etc."
       • working within limitations
       • not clear (yet) of the limitations of the backlog, i.e. unclear of what needs to be done
     • Elwood:
       • What's this trying to address?
       • JMB: difficult for someone external to know when we will have addressed what.
     • Curtis
       • Your trac gives more information than most projects (small comfort)
       • Probably not too far off from giving the information that satellites need.
       • 4.3.2 deliverables is really useful for future milestones as well.
       • Look at https://wiki.mozilla.org/Features/Release_Tracking
       • Higher level, though
       • Josh: right, maybe we manage some tickets only in spreadsheet form (i.e. drop the backlog)
       • Scott: issue with the milestones that they are only discussed periodically
         • JMB: more than one year.
         • Andrew: when else? as a group not so often.
         • Scott: day like one after in Paris more consistently.

4. Any other business (<5 mins) Started at 15:35.

   • HIC meeting (Tues, 10-12), and steering meeting possibly.
   • OME Schema License Discussion - Wed 31st at 9am Central time (3pm UK time)
     • Review emails if you want to ahead of time

Action Items

• Elwood: capture issue with concurrent import / delete