Attendees: Julia McCarthy, Chris Mildebrandt, Charlie Halloran, Mark McCraw, Merri Jensen, Josh Hester, Jeff Hamm, Eric Rose, Jimmy Mohsin
Agenda
Review minutes from last week
Update on tooling use case entry
Enhancement requests entered
P2 Deep Dive Meeting Summary
Jason, Mark, Charlie to summarize P2 runtime meeting
Identify SDD deliverables for COSMOS 1.0
Tools
Runtime
Repository
Tentative: continue use case review
Focus on deployment end user use cases
Follow-up on action items
Charlie/Chris/Julie, continue working w/ IBM legal on committing BTG code, Charlie to send status.
Josh to link Enhancement Requests to Use Cases.
Mark M., Jeff, & Jason to create wiki page for P2 findings.
Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements. (Owner?)
Look into additional projects that Michael mentioned, links are provided in the Minutes section above.
Julia to send Charlie Change Analyzer design doc, Charlie to engage IBM legal about contributing code.
Charlie to prepare analysis of our deployment use cases and fill in the holes that are provided in IBM's end user use cases.
Mark W. to answer outstanding questions on generated code for BTG and proposed repo structure and package naming conventions.
Mark W. to move forward with vote for Julie as code committer with COSMOS. Jason has already been approved.
Minutes
Jason is in Europe so Jeff Hamm from SAS runs the call (and very effectively I might add - Julia didn't even realize it wasn't Jason ;-)
Charlie's Update:
Use Cases - got the green light from IBM to submit use cases, so all that needs to be done now is to get a Certificate of Originality from Tania, and then it can be posted. Charlie is going to go through them with Julia this week to "re-write" them from a runtime perspective, since they are geared more toward a user going through a GUI. We should be able to start going through these next week.
Tooling & Change Analyzer - Charlie wants to go through the code with Julia and send it through some IBM tool, the Certificate of Originality has been completed before sending it over to IBM legal.
Tooling Update:
Julie Halloway has been reassigned, so she will not be participating any more. For the time being Eric Rose and Yan (I didn't catch his last name) will be the main tooling contributers from IBM.
Chris M. will still participate in the COSMOS calls and he'll let us know the transition plans when they are figured out since he is still moving up.
Eric Rose will need to be approved as the IBM code contributer instead of Julie.
Eric and Yan will both be taking extended vacations in April, Eric for 2 weeks and Yan for 4 weeks, so IBM's tooling output will be significantly impacted during this time. Chris and/or Eric will let us know closer to the time what the impact is likely to be.
Chris said that they might be getting an additional resource in the May/June time frame.
The tooling code is ready for submission, it has been separated from the SAS code, and the package names have been updated to match the approved COSMOS naming convention. All that is left is for the code to be scoured by IBM legal.
Charlie is going to check with Mark W. to find out what the expectation is for the Change Analyzer package names, whether they need to be changed to COSMOS naming conventions or not.
Runtime Update:
Mark M. and Jeff at SAS have been able to get P2 compiled and running with the latest batch of updates. They are going through the code and the doc to determine if it works as advertised and to determine its potential as a starting point for an SDD runtime over the next two weeks.
The result of their work would be a mapping if you will between SDD concepts and the P2 code, as well as where the gaping holes are.
Julia gave an overview of the Change Analyzer - basically it was a proof of concept/reference implementation, that was created to process CL1 SDD's for deployment planning purposes. It is a command line interface that creates HTML pages.
Three phases:
Flatten the SDD
Analyze the SDD
Report results
The next step would be to make it actually resolve the SDD, which would just require plugging in XML inputs and outputs.
Jimmy Mohsin one of the contributers for COSMOS proper was asked to inquire with us regarding what the expectation was for using the SDD Runtime for the June deliverables for COSMOS. Right now they just have zip/tar and there is nothing pretty about their deployment process. Charlie and Merri indicated that we didn't think that the SDD Runtime would be available at that time some of the tooling might be, but that Mark W. and Jason would probably need to be the ones to answer his question definitively.
Action Items
Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.
Mark M., Jeff, & Jason to create wiki page for P2 findings.
Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements. (Owner?)
Look into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08.
Charlie to prepare analysis of our deployment use cases and fill in the holes that are provided in IBM's end user use cases.
Mark W. to move forward with vote for Eric as code committer with COSMOS. Jason has already been approved.
Charlie to ask Mark W. about whether package name changes will be needed for Change Analyzer code.
Mark W. and Jason to determine what SDD deliverables will be available for COSMOS release in June and communicate back to Jimmy.
