COSMOS SDD Minutes 01MAY08

Logistics

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

Agenda

1. Update on COSMOS release schedule
   • http://wiki.eclipse.org/COSMOS_Release_Plan_Working_Draft
2. Update to team on third party libraries
   • Question on usage of Tuscany
   • IPzilla needs to be entered
3. Status on runtime code contribution
4. Status on tool code contribution
5. Status on change analyzer code contribution
6. Resource model meeting Tuesdays at 10AM - need regular representation
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. IBM Tooling Update
   • Hope is to push in IBM Tooling code as is, with Tuscany included, and the refactor to remove Tuscany in public. It is estimated to be a 4 week effort. IBM is working with Eclipse on this.
   • One problem, Tuscany requires EMS 2.2, not 2.4 which is buggy.
   • Legal approvals are all in from IBM
2. SAS Code Update
   • SAS code ready for review with Jason
   • Just under 250 lines
   • Initial code is a skelton of a few parts of the framework.
   • We'll start filling in methods and APIs after thumbs up on framework.
3. Use cases still haven't been moved, and the ERs haven't been entered for the Runtime.
4. Mark M., Jeff, and Julia did a WebEx yesterday and were able to get initial COSMOS SDD & supporting docs authored. Need to verify it against the COSMOS reqs.
5. Change Analyzer package names have been updated.
6. SAS BTG Code approx 500 lines of code, so it will need to pushed in pieces.
7. Jason and Jeff have done some whiteboarding on the design of the runtime. Will circulate.
8. Charlie hopes to be able to report that IBM has "something" contributed by next week.

Action Items

1. Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
2. Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.
3. Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code).
4. Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.
5. 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.
6. Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250.
7. Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL).