COSMOS SDD Minutes 08MAY08

Logistics

• Date: 08MAY08
• Time: 4PM EST
• Attendees: Chris Mildebrandt, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Eric Rose, Jeff Hamm, Robert DeMason, Charles Nemargut

Agenda

1. i11 work items for SDD
   • http://wiki.eclipse.org/COSMOS/COSMOS_iteration_i11_plan
   • SDD bug list https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=Cosmos&content=SDD
2. Update from Eric/Yan/Chris/Josh/Robert on tools work
3. Status of zip extractor contribution
4. Status of tool code contribution
5. Status of change analyzer code contribution
6. Runtime design discussion
7. Follow-up on action items
   • Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
   • Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.
   • Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code).
   • Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.
   • Julia to work with Jeff and Mark M. to create CL1 SDD for COSMOS and work with Chris to run it through the Change Analyzer.
   • Mark M. and Jeff to continue working on code for zip extraction.
   • Chris to update package names for Change Analyzer before code is committed.
   • Charlie to find someone to update the Change Analyzer code to remove the dependency on Tuscany and replace it with DOM.
   • Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250.
   • Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL).

Minutes

1. I was late getting on the call, so Jason will have to fill in where I'm missing info.
2. Drools approval pending, Eric to work out, with an Eclipse mentor's help.
3. Using the parallel IP process, Josh can go ahead and get Jason to the code to commit while Drools is being worked out.
4. Jason hopes to have zip extractor code committed by next week's call.
5. Target for IBM code push - 06/04, all code has to go in at the same time including Change Analyzer.
   • Contigent upon Mark W. hearing back from Eclipse on whether code can go in as is and be updated in the public.
6. Use Case Doc going into wiki rather than as a code contribution. Charlie still needs a VP to approve, but he doesn't think it will be a problem.
   • Jason is waiting to move the deployment use cases over into main COSMOS doc until he can see the IBM Use Cases.
7. Remaining discussion is on the initial SDD for COSMOS that was created by Mark M., Jeff, and Julia.

Action Items

1. Charlie/Chris/Eric, commit code when legal issues are worked out with Eclipse.
2. Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.
3. Jason to commit SAS zip extractor code.
4. Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code) and about in place replacement of Tuscany.
5. Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.
6. Continue work on SDD for COSMOS.
7. Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250.
8. Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL).
9. Charlie to get VP approval for Use Cases and put them on a wiki.
10. Schedule meetings to discuss Runtime design document that is being worked on and circulated.