COSMOS SDD Minutes 15APR08

Logistics

• Date: 15APR08
• Time: 9AM EST
• Attendees: Chris Mildebrandt, Charlie Halloran, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Julia McCarthy, Eric Rose, Jeff Hamm, Robert DeMason
• STARTING NEXT WEEK, SDD CALL WILL BE HELD ON THURSDAY AT 4:00 PM EST

Agenda

1. Logistics for new call time
2. Update from the summit call on Friday
3. Status on runtime code contribution
4. Status on tool code contribution
   • Question on usage of Tuscany
   • IPzilla needs to be entered
5. Status on change analyzer code contribution
6. Create an SML profile of the COSMOS install
7. Review minutes from last week
8. 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.
   • 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.
   • Jason to contact Ruth for alternate meeting time so as not to conflict with the RE meeting.
   • Chris to find someone to update package names for Change Analyzer before code is committed.

Minutes

1. In order not to overlap with the Release Engineering Meeting, we have decided to change the SDD call from Tuesdays at 9:00 AM EST, to Thursdays at 4:00 PM EST. We also checked to make sure there we no other COSMOS calls at this time.
2. We won't be using the terminology "install program" since this implies a GUI. For COSMOS, we will be providing an SDD based runtime and a command line interface. Will need to make sure that runtime can interact with any interfaces that might be developed for it though.
3. COSMOS Summit Notes:
   • June 1.0 release date moved to November.
   • Gives us a little more wiggle room, but we still need to be working towards end of June
4. Discussion about Feature selection support:
   • We definitely will not be supporting CL2 functionality, but COSMOS has a need for some minimal feature selection
   • Possible options are to utilize monolithic artifacts (which were CL1/CL1.5ish)
   • Monolithic artifacts imply some sort of inner feature selection, and uses parameters to pass selection info into artifact
   • Zips don't fit this model well, they don't have inner feature selection ability (SAS intends to submit Zip Extractor code for runtime)
     • Alternatives: Multiple zips (use AdditionalContent) or provide multiple SDDs/packages.
5. Zip Extractor needs to take into account the monolithic discussion results, so will probably be ready for commitment later this week.
6. Use Cases/Change Analyzer/IBM Tooling all have been sent to IBM Legal. Waiting to hear back.
   • Charlie may split them out so that Use Cases can be submitted since they don't include any code that needs to be committed.
   • Change Analyzer package names still need to be updated. Chris doesn't think that the code will have to be rescanned if the package names are changed.
7. Jason asked that the weekly call that is scheduled for Tooling between IBM and SAS should be moved into COSMOS schedule once all the tooling code has been committed so it is public.
8. Discussion about contributing Tuscany with SAS Tooling. Has been approved by SAS Legal, but Mark W. wanted to know what it was used for because it seemed rather large. Basically, it is used to convert xml/xsd to java objects (or to model the SDD in javascript).
9. Our SML research is still in the research phase.
10. Jason wants to hold off on entering Enhancement Requests for i11, now that the schedule is in flux. He still needs to move runtime use cases over to the main use cases page.

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. Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
6. 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.
7. Mark M. and Jeff to continue working on code for zip extraction.
8. Chris to find someone to update package names for Change Analyzer before code is committed.