Proposed agenda for this meeting

1. Announcements from the project
2. Brief overview of bi-weekly Jira report (process, content)
3. Impediments for Iteration 1 completion
4. Development Environment update
   1. latest investigations: Calendar, ?
   2. challenges: Git?
5. Brainstorming: Ideas for getting through next 6 days gracefully

Minutes

Announcements from the project

tshirts "Ci09", Words of Matt on the back – reserve with Rita to save yourself one

Brief overview of bi-weekly Jira report (process, content)

Impediments for Iteration 1 completion

• carry over of a day all right for new if confident of completion
• want a package of completed tasks at the end of the iteration
• verification team review
• what should be the due dates? subsystem IPT choose, end of iteration by default.
• what happens at beginning of wrap week?

Pens down at end of 5 weeks, the leads review this work to identify the most important elements to summarize/analyze/adopt for future work. (Step back and consider next iteration, other context.) Developers can work on integration and packaging: additional documentation, wrapping into binary packages, putting into Confluence, deleting deprecated material. (But should be ready for review after the 5 weeks. Also provide comments as to remaining or future tasks.) Also should be able to find issues with the work – suggests a peer review activity (inspection, running unit tests, etc.), testing integration scenarios. (Knowledge should be tracked in Jira defects or other common location.) Summary of peer review should go to subsystem leads for evaluation. Goal is to be completely done at the end of wrap-up.

Development Environment update

Development environment team list has been set up at cidevenvironment, get us to add you to the Confluence group if you want to be a member. (Don't go directly to the email group, that will get out of sync.) Press the request button on the Group, Rita will typically approve that.

– latest investigations:

Calendar, ?

looking at integrated mail and calendar solution, has other features: Kerio. Syncs with Google and Apple iCal. So far it's very positive. Very inexpensive. Looking at it for our own mail server, and has nice Exchange compatibiliity and web interface.

Git?

ok now. Are new GIT repositories listed on the OOI server? Unless chosen otherwise. (Semantic prototype chose otherwise to make sure the password files are removed before public posting.) It's at the discretion of developers when to push and make public; important thing is to make sure versions are on server, so we have access. Should document this in the development environment page.

(Dorian-Michael – document the use of AMQP by developers)

PSI, other chat

Jabber XMPP protocol. Features include chat room (login on instant messaging server at UCSD), can we create new rooms? So far just one room, everyone joins that one to talk. Other rooms can be created. How to create history? Doesn't keep entire history. Possible to configure duration, logs a few days worth. Do we want more? As a matter of practice, copy good chats into Confluence where they fit.

Campfire has chat, probably not compatible with Jabber.

Confluence also has chat.

Vertebra also mentioned.

Brainstorming: Ideas for getting through next 6 days gracefully

Note Jack K, Alan C will be here

Think about how to make this period as effective for developers as possible.

Monthly reports

Matt: Like to see 2 to 4 sentences per subsystem on monthly report. Uses link to reflect bi-weekly reports for more detail. Overview statement (success, failure, challenges) with specific work referenced. Not a deep expose of technologies in the monthly report.

Agreed for this time to do monthlies the same as last time, reports to Rita if you have something on a particular subsystem.

2nd iteration: ends with LCO

By the end of the second design period week, we should be able to describe the LCO and our approach to holding it. Think of 3-4 days to review the Objectives.

LCO is not just words and diagram, but about showing some real progress in prototypes and technologies. Focus is how to show end to end architecture, critical requirements and risk addressed, identifying all technologies in subsystems/respective services. Next 2 months of iteration 2 are targeting that review.