Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "COSMOS SDD Minutes 08MAY08"

(Initial content)
(No difference)

Revision as of 11:27, 9 May 2008

Logistics

  • Date: 08MAY08
  • 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

  1. i11 work items for SDD
  2. Update from Eric/Yan/Chris/Josh/Robert on tools work
  3. Status of zip extractor contribution
  4. Status of tool code contribution
  5. Status of change analyzer code contribution
  6. Runtime design discussion
  7. 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

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. 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.
  6. Mark M. and Jeff to continue working on code for zip extraction.
  7. Chris to update package names for Change Analyzer before code is committed.
  8. Charlie to find someone to update the Change Analyzer code to remove the dependency on Tuscany and replace it with DOM.\
  9. Josh to determine the exact number of lines that SAS has for BTG code since it is close to 250.
  10. Jason to start documenting the Runtime similar to doc Chris has created for SDD Tooling (need URL).

Back to the top