Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2011 2011-08-16 Tuesday Meeting

2011-08-16 Tuesday Meeting

Attending: Brian, Chris, Scott, Andrew, Jean-Marie, Simon, Littlewood, Ola, Josh (10:40), Jason (11:05)

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)

    • Brian: Move over client memory doc to om.org, DONE
      • Let Jason know so he can send email
    • Chris: Look over PSLID codde and provide feedback. Ola can review with you on Tuesday.
    • Andrew: add git, etc. points to Tuesday meetings.
    • Chris: upgrade nightshade to 4.3.1 - done
    • Everyone: tomorrow (Friday) is ticket review!!! - done
  3. OMERO Training:Part 1 (<15 mins)

    • I shall give some extra background to the OMERO Training schedule and questions related for this.
  4. 4.3.2 status. (30mins)

    • Round table following last Friday ticket review
  5. Any other business (<5 mins)

In Attendance

  • Brian, Chris, Scott, Andrew, Jean-Marie, Simon, Littlewood, Ola, Josh (10:40), Jason (11:05)

  • Accepting minutes from last meeting

    • Accepted
  • Matters Arising (<10 mins)

    • Brian: Move over client memory doc to om.org, DONE
      • Let Jason know so he can send email - PENDING
    • Chris: Look over PSLID codde and provide feedback. Ola can review with you on Tuesday. - DONE
    • Andrew: add git, etc. points to Tuesday meetings. - DONE
    • Chris: upgrade nightshade to 4.3.1 - DONE
    • Everyone: tomorrow (Friday) is ticket review!!! - DONE
  • OMERO Training: Part 1 (<15 mins)

    • I shall give some extra background to the OMERO Training schedule and questions related for this.
      • Scott: Everyone please have a look through the day 2 developer topics for OMERO.admin/Devs training
        • Are there other topics that would be better?
        • Martin is very flexible about what we show, he wants a "scripting day"
        • Idea is that they go away with a good understanding of how sripts can be written and run
        • Day 1 is for new omero users (scientists), Day 2 is for developers
          • Chris: Day 1 is two different grounds of scientists (CRUK and Imperial), with different views of OMERO
          • JMB: We need to give them a proposal for what to present
          • CRUK already has a lot of matlab scripts, so they will have advanced questions
          • Andrew: Soundsl like they need a hackathon
          • Simon: Need to get insight from Martin? Probably doesn't know what CRUK requirements are
            • JMB: Anatol perhaps would be the person to talk to at CRUK - lots of matlab
            • JMB: Need to solidify the developer pages with examples, etc.
        • Chris: timescale? 3-4 of October.
          • CellProfiler is not possible
        • Ola: Who can handle the matlab work? JMB recently reworked the matlab code, he can do it.
          • Josh: If its a matlab fest he can also come over
  • 4.3.2 status. (30mins)

    • Round table following last Friday ticket review
      • JMB: Reduced tickets from 124 to 75 with 36 bugs (probably a few more in QA).
        • Are we pushing tickets forward?
        • Josh: Too much stuff for 31st of August
        • JMB: Can we move to mid-September release?
          • Josh: Moving up means delaying some of the blockers
          • Ola: 1 extra week would be nice, I'm away 24th to 31st of August, Chris also away till 31st
          • Chris: We are about a week behind at this time. Most tickets in Bio-formats and web, those are important
          • If SPW + Tree in web, plus BF is our goal for this release, then we should delay
          • Josh: Are the things we're looking at too big for 4.3.2?
          • Chris/Ola: Tree is almost fixed now
          • Josh: If we have too many things in develop now we can cherry pick some of it for release
          • JMB: So we add one more sprint from 1st to 15th to wrap up
          • Josh: After August, no new features then
          • Testing can begin on Ola's features on the 25th, the rest after the 1st
          • Jason: This gives Josh time for changegrp fixes? Josh: Yes should be OK.
            • Some of the changes may not go into 4.3.2, and will go in separately
          • Josh: Had more LDAP syncronization forum posts. Do we want to fix LDAP group syncronization or push it?
            • Ola: Should probably push it. We should first gather more information and how they want to syncronize
            • Josh: Admins want users who are removed from LDAP group to be removed from OMERO group, users consider this a bug
            • Jason: This probably is a bug, with people away maybe we should fix this in a 4.3.3 release
            • Alternatively we just let them know its going to be release when we get to it
            • Chris: We could possibly get it in 4.3.2 and have Josh/other team member test it
            • Chris: This is all getting pretty involved at this point for 4.3.2 release
            • Ola: What about making a script they can use to manually synrcronize
            • Josh: Thought of this but its complicated with Java involved
            • Chris: Would rather not hack a script, do it properly. Lets branch, test it, and see if its ready for Sept 15th
            • Chris: Major bug is fixed right now and will got into 4.3.2, still some other things to fix though
      • Chris: Still have investiation stories in 4.3.2. These have been moved out of the sprint
        • Important for HIC, VM, Scott, Andrew that the right stuff is assigned here so they can be moved/filtered before release
  • Any other business (<5 mins)

    • Andrew: Re proposed changes for N-dimensions, the goal here is to minimize application stack changes
      • JMB: Will have a schedule for these changes and proposal coming out in the next few days
      • Can be talked about after meeting if needed

Action Items

  • Scott: Clairify what requirements are needed for dev training in London
  • Jason: Send forum post about client memory allocation
Document Actions