Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2011 2011-01-27 Thursday Meeting

2011-01-27 Thursday Meeting

Attending: Brian, Colin, Scott, Jason, Chris, Jean-Marie, Donald, Will, Ola, Carlos, Josh, Melissa, Andrew

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)

    • Everyone: move tickets to next sprint
    • Everyone: keep reviewing
    • Josh: send out actual/estimated ticket times
    • Chris: update developer pages on OME.org site for new GIT urls
    • Curtis: send email about when conference times are good.
    • Scott: get all web unification reqs/stories/tasks documented.
    • Brian: Get involved with Scott for synchronizing documentation with clients.
    • Chris: replies to forum, or pings individuals to reply.
    • FLIM: update
  3. Generating sprint # (45 mins)

    • What New Tasks were added to old sprint
    • What Tasks are left in old sprint
    • Make new sprint
    • Estimates
    • Close old sprint and move other tasks into new sprint
    • Are we getting better?
    • 4.3 bugs
  4. Email and Forum Review - checked at 13:45 (5 mins)

  5. Any other business (<5 mins)

In Attendance

Brian, Colin, Scott, Jason, Chris, Jean-Marie, Donald, Will, Ola, Carlos, Josh, Melissa, Andrew

Notes

  1. Meeting notes? Nothing

  2. Matters Arising

    • Josh: send out actual/estimated ticket times (DONE)
      • Some discussion about multiple people on one ticket or multiple tickets in progress
      • Best thing to do (without another tool) is to only have your work in the middle column.
      • Chris: need to make better use of the requirements
        • Difficult to split up some tickets if everything is started at the story level
        • Ola: Now we can also link stories to stories
        • Chris: documentation story is a good example.
        • Tickets are a lot bigger than 0.5 to 1.0 days work
        • Chris: was trying to pull things from the backlog
        • but it's insane (many)
        • Need organization.
      • Andrew: to use in-progress as above,
        • There should only be 10 in-progress at a time? Yes. In theory.
        • If you move something back from in-progress, just adjust the estimate down
        • In theory should have tasks we do and just bugs add on to this
        • Josh's script is good now we can see what's dragging on between sprints
        • Will: does the script ignore things with no time estimates? Yes, think so. Can add something for that.
    • Chris: update developer pages on OME.org site for new GIT urls
      • Done to a certain extent. Everyone check the download page to make sure its ok for you (opinions welcome)
      • Jason: either someone understands or they don't. Chris: Just might need more links - we have to decide
      • Josh: git clone -b SHA1 ... is the one-liner
    • Curtis: send email about when conference times are good (not sure - waiting on Curtis)
    • Scott: get all web unification reqs/stories/tasks documented.
      • User story opened + ticket. Doing breakdown (in general requirement of web at this point)
        • Ola: Can help move things to a more sane spot
        • Jean-Marie: something available before Scott leaves?
    • Brian: Get involved with Scott for synchronizing documentation with clients.
      • Working on it with Scott
    • Chris: replies to forum, or pings individuals to reply.
      • Done. Chris/Will will to talk to users about OME-XML and when it should be used.
    • FLIM: update
      • Jean-Marie: Pieta contacted JMB yesterday, keen on moving FRAP work forward.
        • No feedback from David yet.
        • Waiting on feedback from others.
        • JMB is organizing a meeting with everyone next week (Jason will join in)
        • Where to put machine? how to integrate?
        • Jason: Do Angus' people have access to this FLIM?
          • JMB: No access to Edinburgh currently, could if set up for them
  3. Generating sprint # (45 mins)

    • What New Tasks were added to old sprint
    • What Tasks are left in old sprint
    • Make new sprint
    • Estimates
    • Close old sprint and move other tasks into new sprint
    • Are we getting better?
    • 4.3 bugs
      • Josh: We have gotten better on adding estimates to tickets. Only 8 now without
        • We need to do something with tickets assigned to no-one (with no estimates)
        • Better with fewer tickets over 1 day, number in progress
        • Take away: Keep estimates in place, times down! in progress accurate!
        • Trivial tickets should be .1 time?
      • JMB: Some bugs not not touched, we still need to tackle these!
      • Josh: 4.3 bugs done
        • Only 4 of the 26 are older than 2 weeks .
      • Jason: Goal is reminder next Tuesday, close by mid-sprint
    • From above
      • Everyone: move tickets to next sprint
      • Everyone: keep reviewing
    • Chris: The tickets closed are much more granular. We are getting better at recording these things
    • JMB: Will create sprint 6
    • Jason: Next sprint runs until Feb 10th then Feb 24th. Cover all of Feb.
      • Where are we?
      • Keeping upcoming events in mind - OMERO in Action, Paris, ...
      • May not far away
      • Do we want to start focusing on testing with lots of lead time before May?
        • Lots of big functionality coming
        • 2-3 sprints in the future do we want ot start working with testers?
          • Chris: Too early to tell when
          • Jean-Marie: Previously we had said, at the end of an iteration we should be able to show something.
          • Also useful for Scott to take our code and show it to users.
          • Jason: Still need to look at the calendar and make some guestimates
            • JMB: Give it a bit of time for things to become clearer, then deside
          • Chris: Mid-this sprint we need to look at where we are at, get some estimates
            • By next Thursday we should be able to have a better idea
          • Jason: Some folks away next week. Perhaps table this for the week after?
            • End of sprint 5, we decide
  4. Email and Forum Review - checked at 13:45 (5 mins)

    • Email -
      • Jerome Avondo [ome-devel] Python Scripts: downloadPlane( ) in script_utils.py
        • Will responded to this (privately)
        • Josh: doesn't look responded to.
    • Forums -
    • QA -
      link * 3148 new tanjh@bii.a-... Insight 4.2.0 2011 01 17 - - java.lang.Exception: org.... (WAITING FOR REPLY - CLOSING) * 2659 new avgise@ender... Insight 4.2.0 2010 08 25 - - java.lang.Exception: org.... (WAITING FOR REPLY - CLOSING) * Some issues with QA itself.
  5. Any other business (<5 mins)

    • Jason: Discussion about layout for new building.
      • Should be able to see something for the floorplan soon
      • 16 slots allocated
    • Jason: Still reviewing applicants for 3 new positions
    • Josh coming to Dundee? Around March 10ths

Actions

  1. Everyone: review/update "4.3+ Priorities" i.e. list of "big things" for next sprint review
  2. Will: forward to list Jerome emails.
  3. Ola: Work with Scott on web unification docs.
  4. Donald: Talk to Jos about getting access (1/2 Doz. test accounts for Angus' lab)
  5. Everyone: look at download pages from chris.
  6. Everyone: week from Thursday, have "Bug:" tickets below 10!
    • Move them to stories with estimates
    • Or do the work.
    • Everyone: Sort out bugs that are too long / mislabled
  7. Brian: Help forum "Scripting movie error'" (see above)
  8. Jason: respond to forum "beginners and baby beginners"
  9. Andrew: Send Jason some floorplan ideas
Document Actions