Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS SDD Minutes 08MAY08"
(Forgot part of the agenda) |
(Undo revision 102348 by Merri.Jensen.sas.com (Talk)) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Logistics == | == Logistics == | ||
| − | * Date: | + | * Date: 08MAY08 |
| − | * Time: | + | * Time: 4PM EST |
| − | * Attendees: Chris Mildebrandt | + | * Attendees: Chris Mildebrandt, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Eric Rose, Jeff Hamm, Robert DeMason, Charles Nemargut |
== Agenda == | == Agenda == | ||
| − | # i11 | + | # i11 work items for SDD |
| − | #* | + | #* http://wiki.eclipse.org/COSMOS/COSMOS_iteration_i11_plan |
| + | #* SDD bug list https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=Cosmos&content=SDD | ||
| + | # Update from Eric/Yan/Chris/Josh/Robert on tools work | ||
| + | # Status of zip extractor contribution | ||
| + | # Status of tool code contribution | ||
| + | # Status of change analyzer code contribution | ||
| + | # Runtime design discussion | ||
# Follow-up on action items | # 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 | + | #* 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 == | == Minutes == | ||
| − | + | # I was late getting on the call, so Jason will have to fill in where I'm missing info. | |
| + | # Drools approval pending, Eric to work out, with an Eclipse mentor's help. | ||
| + | # Using the parallel IP process, Josh can go ahead and get Jason to the code to commit while Drools is being worked out. | ||
| + | # Jason hopes to have zip extractor code committed by next week's call. | ||
| + | # Target for IBM code push - 06/04, all code has to go in at the same time including Change Analyzer. | ||
| + | #* Contigent upon Mark W. hearing back from Eclipse on whether code can go in as is and be updated in the public. | ||
| + | # Use Case Doc going into wiki rather than as a code contribution. Charlie still needs a VP to approve, but he doesn't think it will be a problem. | ||
| + | #* Jason is waiting to move the deployment use cases over into main COSMOS doc until he can see the IBM Use Cases. | ||
| + | # Remaining discussion is on the initial SDD for COSMOS that was created by Mark M., Jeff, and Julia. | ||
== Action Items == | == Action Items == | ||
| − | # Jason to commit SAS zip extractor code | + | # Charlie/Chris/Eric, commit code when legal issues are worked out with Eclipse. |
| + | # Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling. | ||
| + | # Jason to commit SAS zip extractor code. | ||
| + | # Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code) and about in place replacement of Tuscany. | ||
| + | # Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests. | ||
# Continue work on SDD for COSMOS. | # Continue work on SDD for COSMOS. | ||
| + | # 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). | ||
| − | # Charlie to | + | # Charlie to get VP approval for Use Cases and put them on a wiki. |
| − | # | + | # Schedule meetings to discuss Runtime design document that is being worked on and circulated. |
| − | + | ||
Latest revision as of 15:03, 5 June 2008
Contents
Logistics
- Date: 08MAY08
- Time: 4PM EST
- Attendees: Chris Mildebrandt, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Eric Rose, Jeff Hamm, Robert DeMason, Charles Nemargut
Agenda
- i11 work items for SDD
- Update from Eric/Yan/Chris/Josh/Robert on tools work
- Status of zip extractor contribution
- Status of tool code contribution
- Status of change analyzer code contribution
- Runtime design discussion
- 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
- I was late getting on the call, so Jason will have to fill in where I'm missing info.
- Drools approval pending, Eric to work out, with an Eclipse mentor's help.
- Using the parallel IP process, Josh can go ahead and get Jason to the code to commit while Drools is being worked out.
- Jason hopes to have zip extractor code committed by next week's call.
- Target for IBM code push - 06/04, all code has to go in at the same time including Change Analyzer.
- Contigent upon Mark W. hearing back from Eclipse on whether code can go in as is and be updated in the public.
- Use Case Doc going into wiki rather than as a code contribution. Charlie still needs a VP to approve, but he doesn't think it will be a problem.
- Jason is waiting to move the deployment use cases over into main COSMOS doc until he can see the IBM Use Cases.
- Remaining discussion is on the initial SDD for COSMOS that was created by Mark M., Jeff, and Julia.
Action Items
- Charlie/Chris/Eric, commit code when legal issues are worked out with Eclipse.
- Jason to commit SAS SDD Tooling code simultaneous with IBM SDD Tooling.
- Jason to commit SAS zip extractor code.
- Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code) and about in place replacement of Tuscany.
- Jason to start moving use cases and "details" into COSMOS Use Cases and begin entering i11 enhancement requests.
- Continue work on SDD for COSMOS.
- 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).
- Charlie to get VP approval for Use Cases and put them on a wiki.
- Schedule meetings to discuss Runtime design document that is being worked on and circulated.