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 Management Enablement meetings"

(Updated action items)
(Agenda)
Line 28: Line 28:
  
 
== Agenda ==
 
== Agenda ==
 
+
# Logistics for new call time
 +
# Update from the summit call on Friday
 +
# Status on runtime code contribution
 +
# Status on tool code contribution
 +
#* Question on usage of Tuscany
 +
#* IPzilla needs to be entered
 +
# Status on change analyzer code contribution
 +
# Create an SML profile of the COSMOS install
 
# Review minutes from last week
 
# Review minutes from last week
# Cover using SDD to install COSMOS possibilities
 
#* Create an SDD for installing COSMOS -- community members to be on the call to articulate COSMOS install requirements.  How formal do we want requirements gathering to be?
 
#* Marry change analyzer code to SAS extraction code and UI
 
#* Create an SML profile of the COSMOS install
 
#* Status update on the above items
 
# Deployment runtime use case review -- need these moved to COSMOS use case section
 
 
# 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.
 
#* 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.
 
#* 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).
 
#* Mark W to contact Eclipse about adding SDD Tooling code (since contributions are over 200 lines of code).
#* Mark W to review Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements.
 
#* Continue looking into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08.
 
 
#* 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.
 
#* Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.
 
#* Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS.

Revision as of 08:53, 15 April 2008

SDD Meetings

Meeting Title: COSMOS SDD Weekly Meeting
Link to information on Wiki:
Date & Time: Tuesday at 9:00 EDT / 9:00am EDT
Toll-free Dial-in number: 1-877-641-0660
Primary International Dial-in: + 1-919-531-0660 (Requires International prefix first)
Passcode: 107017

Contact

Email [Jason Losh] Phone


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 of prior meetings

Back to the top