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)

   • J-M: send email to Curtis for scheduling discussion. DONE Discussion 25/09
   • J-M: assign remaining video tickets DONE. Everyone finish them for Tuesday.
   • Josh: create/organize a 4.3.3 milestone (BUGS-ONLY!) DONE see the milestone page
   • Ola: look at the Leon K. email thread. DONE ticket #6863

3. Git/github/branching policies

   • See "Coding (exerpt)"

4. Data Model Discussion: Modulo and Pyramids - Curtis/Andrew/Chris (10 mins)

   • Modulo - See : file-formats/6d-and-7d-storage
     • meeting 25/09: Adjust the proposal see ticket #6485 and notify the list.
   • Pyramids - See : 2011.09.23-big-images-ome-tiff-pyramid
     • meeting 25/09: Minor B-F changes (add method) and e-mail list about OME-XML see ticket #6858.

5. Any other business (<5 mins)

   • Scott: A deadline for training day material Wednesday night (28th Sept) to be sent to London on Thursday morning.

Notes

1. Accepting minutes from last meeting

   • DONE

2. Matters Arising (<10 mins)

   • J-M: send email to Curtis for scheduling discussion. DONE Discussion 25/09
   • J-M: assign remaining video tickets DONE. Everyone finish them for Tuesday.
   • Josh: create/organize a 4.3.3 milestone (BUGS-ONLY!) DONE see the milestone page
     • We can table it for Thursday, is the anything else we want to add?
     • Andrew: When this expect to run until?
     • Josh: Maximally 2 sprints
     • We will finalize it on Thursday.
   • Ola: look at the Leon K. email thread. DONE ticket #6863

3. Git/github/branching policies (14:35)

   • See "Coding (exerpt)"
     • Josh: For people what wants to read it. Josh pieced together policies how to work with git hub. Do we want to use git hub for 4.3.3. It shouldn't be so hard, people should be able to use it quite easily. We will try to get as much as instruction to be done before we start. It will be good way to test github before we take it to the full release.
     • Scott: Outline the process more clear. How to clarify the investigation step and the move to the development..
     • Josh: Write the suggestion down, put them in doc or email. We will summarize the process. This is really to take the process to the person who is new. They will be happy to have any spec written down. Should be as detailed as much as possible, and we can improve anything that’s too painful over time.
     • Josh: Introduction, command to much of the github workflow.

4. Data Model Discussion: Modulo and Pyramids - Curtis/Andrew/Chris (10 mins) (14:43)

   • Modulo - See : file-formats/6d-and-7d-storage
     • Andre: Melisa Curtis Kevin and Andrew had a chat about it yesterday. The items that came out:
       • minor changes to c, z, t, If people want to use the API the same way, then can use annotation instead.
       • generally need to fix the export of annotations.
         
       • Will: whats the timetable of that support, do we release across the whole stack at once?
       • Andrew: we got one more email to send to the list ”here is how do we are going to store it”.
         
         
       • Will: no plans to support modulo across the stack in any other way?
         • Curtis/Andrew: some sample code that will be written.
         • Andrew: There is no idea to make change across the stack
         • Curtis: changes to the Bioformat’s TiffReader, maybe some change to insight
           • Andrew: UI tweaks, identify when you have additional structures, changing: channel scroller, the detection code. This can be changed once we got data in. First thing is to allow people to write data in and process.
       • Melissa: currently don’t have a better understanding of changes Chriss mentioned.
     • Will: we put the model out there and get people to write it? Yes.
     • Andrew: providing you’re only putting one extra dimension in C, support is essentially there already.
       • Bio-Formats importer needs to be tweaked to add the annotation.
   • meeting 25/09: Adjust the proposal see ticket #6485 and notify the list.
   • Pyramids - See : 2011.09.23-big-images-ome-tiff-pyramid (14:52)
     • Andrew: decision was to get documentation out for how to store pyramids and get feedback.
     • Andrew: can we get rid of binary data. Can we deprecate ome-xml as a storage format, and replace by metadata storage format? No one is writing it that way.
     • Josh: Someone see the sample file and get confused: “Why would I base64 encode my data?!?”
     • Will: Alternatively if I can have tool, where i could edit ome-tiff file.
     • Andrew: I got little script to do it
     • Curtis: tiffcomment -edit.
     • Jason: It will be a big change for the community. Write to the community, asking if anyone has a problem with deprecating it.
     • meeting 25/09: Minor B-F changes (add method) and e-mail list about OME-XML see ticket #6858.

5. Any other business (<5 mins) (14:59)

   • Scott: A deadline for training day material Wednesday night (28th Sept) to be sent to London on Thursday morning.
   • Scott:just general comment
     • Might be better to post training materials, because it will be heavy. Will send it on Thursday morning.
     • Andrew: there are printer materials, t-shirts, etc. After Thursday 12pm (or 2pm) is to late to post it.
     • Will: Training material for second day are only few sheets, we can put in luggage.
     • Josh: Whats the official starting point for training, wiki page, google doc?
     • Will: There is life google doc; we are updating.
     • Andrew: if you put in OMEDocs folder it will automatically share with others.
   • Andrew: We are finalizing movies. Please remember about details, codecs, sizes, etc.
     • Colin: People needs to keep the application to fill the whole screen.
     • Andrew: record an initial bit and check your microphone settings.
     • Andrew: If you need any help Colin is the movie master, ask him about advices.
   • Will: we need more feedback about training material, anything is missed
     • Josh: do we want sit down and review it all together.
     • Will: if there are any problems issues, send an email, or ask person directly.
     • Josh: will be good to have a instruction how to review, spelling mistakes, etc.
   • Kevin: meeting dates?
     • 8-9th Nov does not work, Jason is not here
     • 14-15th Nov Kevin is on the big meeting (neuroscience)
     • next weekend Colin is on Holiday (Thanksgiving)
     • Jason: suggest survey the list of people who will be coming. May not be necessary for Jason to be there.
     • Jason: December is too close to the fiji hackathon. May not work to change it.
     • Andrew: Invite people for 8-9th Nov, if to many people reject, we will change it after.
     • Curtis: if it were right next (before/after) the hackathon, then it increases the changes of attending.
     • Andrew: dates? Dec 10 - 17 hackathon.
     • Jason: also a few people at ASCB at that time.
     • Kevin: I will put the poster in.
     • Kevin: also a meeting on the 9th (Bob as well) so it may be rough. Like the idea of having the PIs there, but developers are more important.
     • Jason: Will be nice to have all PI’s and developers together.
     • Jason: We are back to: 8-9th Nov or 7-10th Dec. Melisa can make them, but not the 1st of Nov.
     • Jason: Later date will bring more delays.
     • Summary: Nov/8-9th or Dec/7-8th (or 9-10th - this might be to close to the hackathon)
   • Jason is setting up appointment with RAS about data protection issue.

6. Done at 15:17

Actions

* Everyone: review 4.3.3 milestone and github instructions since we’re planning on using it
* Andrew: write to the community about model changes.
* Scott: send list of all training materials to nitpick