Skip to main content

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.

Jump to: navigation, search

COSMOS SDD Minutes 15APR08

Revision as of 18:02, 15 April 2008 by Unnamed Poltroon (Talk) (Initial content)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Logistics

Agenda

  1. Logistics for new call time
  2. Update from the summit call on Friday
  3. Status on runtime code contribution
  4. Status on tool code contribution
    • Question on usage of Tuscany
    • IPzilla needs to be entered
  5. Status on change analyzer code contribution
  6. Create an SML profile of the COSMOS install
  7. Review minutes from last week
  8. 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.
    • Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
    • 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.
    • Jason to contact Ruth for alternate meeting time so as not to conflict with the RE meeting.
    • Chris to find someone to update package names for Change Analyzer before code is committed.


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. Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
  6. 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.
  7. Mark M. and Jeff to continue working on code for zip extraction.
  8. Jason to contact Ruth for alternate meeting time so as not to conflict with the RE meeting.
  9. Chris to find someone to update package names for Change Analyzer before code is committed.

Back to the top