2011-06-21 Tuesday Meeting

Brian, Ola, Will, Andrew, Scott, Simon, Josh, Melissa, Carlos, Colin, Jason, Curtis

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)

Accepting minutes from last meeting
Matters Arising (<10 mins)
- Chris: find out how any files lack copyright
- Chris: Add copyright templates
- Feedback on XLS for users? (see google docs)
Release TODOs
- Close 4.3.0 milestone
  - 4.3.0 top-level: less than 20; get to 0
  - 4.3.1 top-level: already more than 150
  - 5.0 top-level: already more than 50
- Merge into master
- Schedule next testing scenarios : Scott
  - Updates of existing scenario will be done. (Limited)
  - A deadline of next tuesday 28th June to account for any adjustments made for 4.3.1.
  - Set the time available for the next set of test scenarios?
  - Is there a need for internal pre-testing if so set the internal date for release.
- Prepare/discuss branches (git, hudson, etc)
- Features page
- Other documentation
- Scott: Outline future milestones for #3476/#4494 Web UI review
OMERO/HIC: Simon Wells (45 mins)
- Tickets: which sprint/milestone?
Any other business (<5 mins)
- FAQ entry: http://lists.openmicroscopy.org.uk/pipermail/ome-users/2011-June/002639.html

In Attendance

Brian, Ola, Will, Andrew, Scott, Simon, Josh, Melissa, Carlos, Colin, Jason, Curtis

Notes

Accepting minutes from last meeting
- Accepted
Matters Arising (<10 mins)
- Chris: find out how any files lack copyright - DONE
- Chris: Add copyright templates - DONE
  - Anyone who creates new files should copy their template from here
  - Still need to change some files
  - Josh: Can enable an ant task to fail on non-agreement
  - Jason: timeline for getting webmobile cleaned?
    - Will: for next release (4.3.1)
- Feedback on XLS for users? (see google docs)
  - Josh: Anyone have feedback on email crafted, otherwise will sent it
    - Andrew: Would be nice to have an html version
      - Josh: Will look into it
Release TODOs
- Close 4.3.0 milestone
  - 4.3.0 top-level: less than 20; get to 0
  - 4.3.1 top-level: already more than 150
  - 5.0 top-level: already more than 50
  - Notes
    - Scott: issue of having a place for all remaining tickets
    - Josh: At this point it may be time to move these to 4.3.1. But 4.3.1 list is huge
    - Josh: Working to clean things up in 4.3.1
    - Jason: how can we help to figure out where we put the 4.3.0 usability/testing tickets?
      - Should Start to become a process for release
      - Scott: Hesitant to put everything in one big bucket for me to filter - can miss things
      - Scott: Working on alternatives
      - Andrew: also need to track the history of requirements/requests as they arise.
      - Josh: one possibility is to have Scott prepare milestones ahead of time.
      - Jason: To be concrete: Move some of these to testing scenarios and clients 'milestones'
        
        Them move as appropriate
        
        Jason: Can we script templates that generate milestone tickets for testing?
        
        Josh: Yes
        
        Jason: OK move stories to new testing scenario milestone template (important that this is not just a script)
        
        NB: So the script would now copy all tickets in a template milestone and add them to a real milestone
        
        Add a scripted useability milestone as well (works in a similar way). All client consistency tickets go here
- Merge into master - DONE
  - Josh renamed and merged master as appropriate
  - New tag name is: v.4.3.0 (signed with Josh's key)
- Schedule next testing scenarios : Scott
  - Updates of existing scenario will be done. (Limited)
  - A deadline of next tuesday 28th June to account for any adjustments made for 4.3.1.
  - Set the time available for the next set of test scenarios?
  - Is there a need for internal pre-testing if so set the internal date for release.
  - Notes:
    - Scott: Dates? Josh: Thinking of sprint from the 23rd to the 7th - Testing could start on the 11th
- Prepare/discuss branches (git, hudson, etc) - TABLED FOR THURSDAY
- Features page
  - Anything to do?
  - Will: Adding movies is about all that's left
  - About page needs a few more links - all minor
- Other documentation - TABLED FOR THURSDAY
  - Josh: need to get 4.3.0 out of the door ASAP so 4.3.1 doesn't start getting mixed together.
- Scott: Outline future milestones for #3476/#4494 Web UI review
  - Already discussed
OMERO/HIC: Simon Wells (45 mins)
- Notes
  - Pilot project: major point - data aquisition and management of non-image data
  - Loss of information on data preparation / provenance over time.
  - Jason: currently using flat files from R, stata, plink, ...
    - Statement by July 11th: "with a few months work, have replicated what they do already"
    - Added value: auditing, security model
  - Gianluigi: next step, select individual and see what is available for them.
    - second field in ped file is the key
  - Josh: silo is a combination of OMERO.tables, repositories, auditing, and eventually scripting & indexing
  - Andrew: previously read attempts weren't recorded and now it's important? Good way of putting it.
  - Andrew: is this a specialized install or can it work together?
    - Josh: auditing is server-side, and a silo would look like an FS repository, so should be able to work together
  - Jason to Gianluigi: changes to the model is what you've already done?
    - 3 things
      - Handle health related data
        
        Basically static
        
        Not computation but selection.
        
        i2b2 uses large EAV tables.
        
        also possible to use OpenEHR to describe clinical data.
        
        currently using EAV since not easily mapped to OpenEHR
        
        only data acquired directly from hospitals (i.e. better control on details) is in OpenEHR.
        
        i.e. laboratory results.
      - Handle experimental measurements (geno-typing)
        
        do you want to do processing server side?
        
        allows for providing transparent movement of data
      - easily integrated with available data sources.
- Discussion
  - Tickets: which sprint/milestone?
Any other business (<5 mins)
- FAQ entry: http://lists.openmicroscopy.org.uk/pipermail/ome-users/2011-June/002639.html
  - Jason: Should be make into an FAQ