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.

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.

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.

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