https://wiki.eclipse.org/index.php?title=COSMOS_SDD_Minutes_24APR08&feed=atom&action=historyCOSMOS SDD Minutes 24APR08 - Revision history2024-03-29T07:29:20ZRevision history for this page on the wikiMediaWiki 1.26.4https://wiki.eclipse.org/index.php?title=COSMOS_SDD_Minutes_24APR08&diff=94452&oldid=prevMerri.Jensen.sas.com: Initial content2008-04-25T00:37:42Z<p>Initial content</p>
<p><b>New page</b></p><div>== Logistics ==<br />
* Date: 24APR08<br />
* Time: 4PM EST<br />
* Attendees: Chris Mildebrandt, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Julia McCarthy, Eric Rose, Jeff Hamm, Robert DeMason, Charles Nemargut<br />
<br />
== Agenda ==<br />
<br />
# Update on COSMOS release schedule<br />
#* http://wiki.eclipse.org/COSMOS_Release_Plan_Working_Draft<br />
# Update to team on third party libraries<br />
#* Question on usage of Tuscany<br />
#* IPzilla needs to be entered<br />
# Status on runtime code contribution<br />
# Status on tool code contribution<br />
# Status on change analyzer code contribution<br />
# Resource model meeting Tuesdays at 10AM - need regular representation<br />
# Follow-up on action items<br />
#* Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.<br />
#* Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.<br />
#* Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.<br />
#* 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.<br />
#* Mark M. and Jeff to continue working on code for zip extraction.<br />
#* Chris to find someone to update package names for Change Analyzer before code is committed.<br />
<br />
== Minutes ==<br />
<br />
# Third Party Libraries<br />
#* Build Time Generator requires Tuscany and Drools. Have to get ipzilla approval for these. Holding up code contributions.<br />
#* Change Analyzer requires Tuscany also, but can possibly be replaced with DOM to read the xml instead.<br />
#* Charlie will need to find someone to make these changes, otherwise we may have to go through ipzilla for Tuscany.<br />
#* 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.<br />
# IBM Legal Status<br />
#* COO for tooling has been approved by IBM Legal, now waiting on Eclipse approval.<br />
#* Use cases are approved by IBM Legal pending VP approval.<br />
# SAS Legal Status<br />
#* 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.<br />
#* Josh to check on exact LOC for BTG from SAS<br />
# Resource Modeling call on Tuesday's at 10:00 EST<br />
#* Jason and Merri to participate regularly<br />
#* Encourage others to attend as well, especially folks from other member companies so that expertise is spread out.<br />
# Code contributions coming together, need to turn to documentation<br />
#* Jason to start fleshing out more details and to refine high level architecture diagram that was started earlier.<br />
#* BTG and other tooling already documented on Wiki (need URL)<br />
#* Jason to use the tooling pages as a starting point for the runtime documentation.<br />
<br />
== Action Items ==<br />
<br />
# Charlie/Chris/Eric, continue working w/ IBM legal on committing BTG code & Change Analyzer code, Charlie to send status.<br />
# Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.<br />
# Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code).<br />
# Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.<br />
# 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.<br />
# Mark M. and Jeff to continue working on code for zip extraction.<br />
# Chris to update package names for Change Analyzer before code is committed.<br />
# Charlie to find someone to update the Change Analyzer code to remove the dependency on Tuscany and replace it with DOM.\<br />
# Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250.<br />
# Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL).</div>Merri.Jensen.sas.com