COSMOS SDD Minutes 24APR08

Logistics

• Date: 24APR08
• 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.
   • Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
   • 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 find someone to update package names for Change Analyzer before code is committed.

Minutes

1. Third Party Libraries
   • Build Time Generator requires Tuscany and Drools. Have to get ipzilla approval for these. Holding up code contributions.
   • Change Analyzer requires Tuscany also, but can possibly be replaced with DOM to read the xml instead.
   • Charlie will need to find someone to make these changes, otherwise we may have to go through ipzilla for Tuscany.
   • We need to all be aware of our third party usage and make sure that it is already approved through ipzilla. Code committers can check via Committer Portal.
2. IBM Legal Status
   • COO for tooling has been approved by IBM Legal, now waiting on Eclipse approval.
   • Use cases are approved by IBM Legal pending VP approval.
3. SAS Legal Status
   • SAS intends to submit code in appropriately sized chunks starting with a core framework and build on that. This is true for the Extractor and the BTG code.
   • Josh to check on exact LOC for BTG from SAS
4. Resource Modeling call on Tuesday's at 10:00 EST
   • Jason and Merri to participate regularly
   • Encourage others to attend as well, especially folks from other member companies so that expertise is spread out.
5. Code contributions coming together, need to turn to documentation
   • Jason to start fleshing out more details and to refine high level architecture diagram that was started earlier.
   • BTG and other tooling already documented on Wiki (need URL)
   • Jason to use the tooling pages as a starting point for the runtime documentation.

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. Mark M. and Jeff to continue working on code for zip extraction.
7. Chris to update package names for Change Analyzer before code is committed.
8. Charlie to find someone to update the Change Analyzer code to remove the dependency on Tuscany and replace it with DOM.\
9. Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250.
10. Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL).