Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS SDD Minutes 01MAY08"
(Initial content) |
(Updated to include minutes.) |
||
Line 29: | Line 29: | ||
== Minutes == | == Minutes == | ||
+ | # 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 | ||
+ | # 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. | ||
+ | # Use cases still haven't been moved, and the ERs haven't been entered for the Runtime. | ||
+ | # 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. | ||
+ | # Change Analyzer package names have been updated. | ||
+ | # SAS BTG Code approx 500 lines of code, so it will need to pushed in pieces. | ||
+ | # Jason and Jeff have done some whiteboarding on the design of the runtime. Will circulate. | ||
+ | # Charlie hopes to be able to report that IBM has "something" contributed by next week. | ||
== Action Items == | == Action Items == | ||
Line 37: | Line 52: | ||
# Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests. | # 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. | # 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. | ||
− | |||
− | |||
− | |||
# Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250. | # 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). | # Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL). |
Latest revision as of 11:44, 9 May 2008
Contents
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
- Update on COSMOS release schedule
- Update to team on third party libraries
- Question on usage of Tuscany
- IPzilla needs to be entered
- Status on runtime code contribution
- Status on tool code contribution
- Status on change analyzer code contribution
- Resource model meeting Tuesdays at 10AM - need regular representation
- 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
- 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
- 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.
- Use cases still haven't been moved, and the ERs haven't been entered for the Runtime.
- 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.
- Change Analyzer package names have been updated.
- SAS BTG Code approx 500 lines of code, so it will need to pushed in pieces.
- Jason and Jeff have done some whiteboarding on the design of the runtime. Will circulate.
- Charlie hopes to be able to report that IBM has "something" contributed by next week.
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.
- 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).