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 Management Enablement meetings"
(Added this week's minutes as a link) |
(Updated action items) |
||
Line 38: | Line 38: | ||
# 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. |
− | #* | + | #* 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. | |
− | #* | + | #* Mark W to determine package names for Change Analyzer code. |
− | #* Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS | + | #* 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. | #* 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 COSMOS install. | #* Mark M. and Jeff to continue working on code for COSMOS install. | ||
+ | #* Jason to schedule meeting for futher discussion of SDD for COSMOS. | ||
+ | #* Jason to determine alternate meeting time so as not to conflict with the RE meeting. | ||
== Minutes of prior meetings == | == Minutes of prior meetings == |
Revision as of 14:58, 1 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: | |
Passcode: | 107017 |
Contact
Email [Jason Losh] Phone
Agenda
- 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
- 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).
- 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.
- Mark W to determine package names for Change Analyzer 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 COSMOS install.
- Jason to schedule meeting for futher discussion of SDD for COSMOS.
- Jason to determine alternate meeting time so as not to conflict with the RE meeting.