Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2011 2011-02-22 Tuesday Meeting

2011-02-22 Tuesday Meeting

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

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

    • Melissa should be added to attendee list
  2. Matters Arising (<10 mins)

    • Josh: Add minigroup notes to plone DONE
    • JMB & Josh: breakdown milestones page with more details + tickets
    • Donald: commit jpeg2000 code to a branch, commit processing code to a branch
    • Donald: possibly committing alternative storage investigations
    • Ola: commit paneljs code to a branch (or a mainline)
    • Will: commit to webfigure, but still turned off.
    • Ola: Look at QA 3201
    • Will: create ticket about rawFromOriginalFile
    • JMB & Scott: Start documentation for QA and what client they are using
    • Jason: Update 'omero in production' page
    • Andrew: submit poster to CRS
  3. Backporting (10 mins)

  4. Usage and the Stats We Collect (30 mins)

    • What we collect now
    • What questions do we need to ask
      • Server uptime
    • How can we collect data differently to answer the new questions
  5. Any other business (<5 mins)

Attending

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

Notes

  1. Accepting minutes from last meeting

    • Melissa should be added to attendee list - FIXED
  2. Matters Arising (<10 mins)

    • Josh: Add minigroup notes to plone DONE
    • JMB & Josh: breakdown milestones page with more details + tickets
      • Some stuff done, more to add
    • Donald: commit jpeg2000 code to a branch, commit processing code to a branch
      • Still needs to be comitted
    • Donald: possibly committing alternative storage investigations
      • working, needs to be committed
    • Ola: commit paneljs code to a branch (or a mainline)
      • DONE, commited to trunk
    • Will: commit to webfigure, but still turned off.
      • PENDING (created ticket to move to webtest)
    • Ola: Look at QA 3201
      • PENDING
    • Will: create ticket about rawFromOriginalFile
      • DONE. Assigned to Donald.
    • JMB & Scott: Start documentation for QA and what client they are using
      • Ticket Created
      • Discussed today
      • Scott will share via google docs
    • Jason: Update 'omero in production' page
      • UNKNOWN
    • Andrew: submit poster to CRS
      • Abstract mailed to Alison, need a presenter!
      • Poster still needs to be put together, but in progress
  3. Backporting (10 mins)

    • See docs/backporst/README.txt. "BackPorts" wiki page to follow
      • Josh: Email sent out with a list of backporting commits (about 70-80). Thanks all for help
        • May have missed some things, will have to see
        • Big pain, lets try to avoid in the future
        • process should be: git pull branches, cherry pick commits, and then commit git.ome to commit all 3 branches
        • Important to update all 3 branches with changes
        • If something can't be backported, create a ticket for it
        • Try to apply branch patches right away while fresh in your mind!
        • Josh will be checking periodically for what needs backporting and email problems, fix + reply ASAP!
        • Some things clearly don't backport (new featurs) like insight importer and big images
      • Carlos: use to have to keep 4.1 to 4.3 web gateway in full sync
        • now I can probably cherrypick but should I?
          • Josh: Caveat is that we have to know which features are where, test, etc.
            • In Python can do a full backport and use defines to seperate branch code inline
            • Need to be very careful about splitting up commits, must keep code atomic and on topic (applies to everyone!)\
      • Jean-Marie: if we can agree that backporting immediately, that will make our lives easier
        • Andrew: branch 4.2 is server only? No. Specification needs to be kept inline where possible.
        • Josh: Happy to let Andrew manage the branches so they look as he wants them too
      • Josh: We haven't done the cherry pick tutorial, perhaps when Josh arrives on the 6th we can do that
        • If you need help in the meantime, ask in dev team
  4. Usage and the Stats We Collect (30 mins)

    • What we collect now

      • Andrew and Ola collected some data yesterday
        • would be nice to organize the data so we can ask specific questions
        • get OMERO.server starts & importer starts (CLI or GUI) or when OMERO.web is login
        • Ola: not convinced about importer hits.
        • May not consistent across clients (some before login, some after)
        • Importer hits higher (could be drop box imports starting for each file)
        • Importer should be split into CLI, Dropbox, and GUI to refine results (insight importer should be ignored)
      • Figures we get: starts per application
        • Makes sense for web, insight, and importer
        • Doesn't make sense for server; need up-time
        • Josh: this is getting us into "opt-in" rather than "opt-out" options
        • Andrew: using a heart-beat?
        • Will: do we need this information?
        • Brian: it's what's being asked.
          • would be good: uptime along with how many clients attached
      • Also, session recreation makes things very difficult.
      • Will: Need to keep things in perspective, some things we can't ethically collect w/o permission
        • Other think we can do is have people fill out a form before they download client
      • Curtis: prompt on initial startup asking about "optional anonymous statistics"
    • What questions do we need to ask -

      • Server uptime
      • Ticket has been created, need to put options there, review with Jason
    • Josh: bio-formats stats work really well, reloads library every time

      • Curtis: This has changed to 'check once a day'
      • Andrew: Can this be changed back?
        • Curtis: it was slowing things down, could optionally put in separate thread
        • Melissa: its not in the released version just now
    • How can we collect data differently to answer the new questions

      • Development team should be able to 'opt out' or note 'developer'
      • Josh: May need to put some special file for or config option for 'dev' that won't affect repo
  5. Any other business (<5 mins)

    • Will: A couple of posts awaiting answers (everyone please look)
    • Edinburgh guys coming on Thursday. Dmac will find out when (hopefully 10:30)

Action Items

  • Jean-Marie: look at milestone page
  • Donald: commit jpeg2000 branch today (Tuesday)
  • Ola: create ticket for QA 3201
  • Everyone: Think about going to Crief, need a presenter (Friday 25th to Monday 27th)
    • Someone could just go for the presentation (a few hours not the whole day)
  • Need to split CLI/GUI/DROPBOX importer application
  • Need to unify when upgrade ccheck happens
  • Brian: Create page about what anonymous data is being collected (for future setup of 'opt in' dialog)
  • Andrew: Will update stat collection ticket with questions to ask
  • Add tickets for checking to cellprofiler, etc.
Document Actions