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)

   • Put in action points from last Thursday's meeting.

3. AOCB (<5 mins)

Notes

Attending

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

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

   • Review of last weeks meeting minutes approved

2. Matters Arising (<10 mins)

   • Put in action points from last Thursday's meeting.

3. Continuing with Hudson Green

   • Python builds mostly resolved
   • Java integration tests failing on server, OK locally
     • Test Harness needs to be fixed for some of these tests
   • Integration, server, and cpp should be yellow by Thursday
   • Some tests are obsolete and need to be rewriten at some point
   • Need to decide how to go forward on Thursday (when is 4.2.1 release)

4. Trips

   • Lots of upcoming meeting invites
     • HCS meeting from Carl Kozak (end of Sept)
     • Spencer invite to Paris
     • Pittsburg
     • Curie
     • SPIM meeting in Oct.
       • Propose some stuff for their data structures
     • Cole Spring Harbour in Dec.
     • ASCB in Dec.
     • No-SQL in Frankfurt (Sept 28th)
     • Visit to Lisbin
   • Too much for one human!
     • Need to get planning done soon (Tomorrow!)
   • Road Trips
     • Oxford
     • Cambridge
     • Imperial
     • UEA Crew
     • EBI

5. AOCB (<5 mins)

   • Jason needs to complete his task for Andrew

6. Upcoming work

   • Delete
   • May be a good time for the 'simple API'
     • If we change the API need to give fair warning
     • By 'simple' we mean modular, smaller sub-APIs
     • Allow 'batch' API calls
     • Each service would be completely separate
     • Minimize reliance on the OMERO model objects
     • New service so it doesn't break old API
     • Test the 'simple API' concept with the Delete service
   • Need to decide how to do this to minimize community issues
   • If we go foward, should we get community feedback?
     • Lets go ahead with Delete and see how it is first

Action Items

* Jason: Write contacts about road trips, make list!
* Jason: ASCB 'thing' for Andrew