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 01APR08"
(Initial content) |
(Updated minutes and action items) |
||
| Line 9: | Line 9: | ||
# Review minutes from last week | # Review minutes from last week | ||
# Cover using SDD to install COSMOS possibilities | # Cover using SDD to install COSMOS possibilities | ||
| − | #* Create an SDD for installing COSMOS | + | #* 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 | #* Marry change analyzer code to SAS extraction code and UI | ||
#* Create an SML profile of the COSMOS install | #* 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 | # 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. | ||
| − | #* Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements. | + | #* Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements. - Update from Jason |
| − | #* Look into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08. | + | #* Look into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08. |
| − | #* | + | #* Jason to move forward with vote for Eric as code committer with COSMOS. - DONE |
#* Charlie to ask Mark W. about whether package name changes will be needed for Change Analyzer code. | #* Charlie to ask Mark W. about whether package name changes will be needed for Change Analyzer code. | ||
| − | #* | + | #* Everyone review the new deployment use cases by tomorrow, then move use cases and "details" into COSMOS Use Cases by end of week. |
| − | #* | + | #* Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS. - Julia has done some exploration here. Jason/Julia to provide update. |
| − | #* | + | #* 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. | ||
== Minutes == | == Minutes == | ||
| − | # | + | # Feedback for deployment use cases was due last week, so we can go ahead and start moving them over to the main COSMOS use case wiki now. Jason will start this effort and work on getting the i11 enhancement requests entered. |
| − | # | + | # Charlie submitted COO to Ruth for Use Cases last week, and she was supposed to meet with IBM Legal last Friday, but the meeting was moved to today instead. |
| − | # | + | # Vote for Eric as committer has begun. Hopefully it will be finished by the time he returns. |
| − | # | + | # Decided that we should change our meeting time since it is at the same time as the Release Engineering meeting, and we're going to need to start working with them soon. |
| − | + | # Mark W. has action to contact Eclipse about all our code contributions that are ready for submission and needs to get Charlie the appropriate package names for the Change Analyzer. Mark has at least responded and indicated that he knows he needs to do this ;-) | |
| − | + | # Jason met with SAS Legal and has the okay to proceed with our code contribution. Code will need to be scanned. | |
| − | # | + | # Jason has created the Decision Matrix, but would like Mark W. to review. Jason felt that he skewed more towards Java because he thinks that would be the best technology to use longer term (it allows for easy extensibility), however since the TPM group had some objections to using Java it would be best to have others review. |
| − | + | # Jeff is continuing to look into P2. | |
| − | # | + | # Jason has conference call at 10:00 AM with Mark W. and Julia M. to go over the resource model for the MDR registration for a COSMOS SDD implementation. |
| − | # | + | # Jimmy summarizes the requirements and problem areas he has encountered when deploying COSMOS. This is to help us with creating an SDD and runtime for i11. |
| − | + | #* Identifying Pre-reqs: JRE, JDK, Tomcat, Muse | |
| − | + | #** Main issue is with detecting pre-reqs and versions and what to do when you have conflicting versions. | |
| − | # | + | #** SDD supports Range of versions and supported vs. certified versions |
| − | # | + | #* Sequencing issues - there are a lot of pieces that need to be installed, and sometimes sequencing does matter. |
| − | # | + | #* Version issues with other products |
| − | # | + | #** SDD provides for including pre-reqs with install with requisites (but this is a CL2 feature, so I'm not sure how we'll be able to use this functionality). |
| − | #* | + | #* Jason to set up a meeting later this week to discuss in more detail. |
| − | #* | + | |
| − | #* | + | |
| − | #* Jason | + | |
| − | + | ||
| − | + | ||
| Line 53: | Line 50: | ||
# 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. | ||
| + | # 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. | ||
# 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. | ||
Latest revision as of 14:57, 1 April 2008
Contents
Logistics
- Date: 01APR08
- Time: 9AM EST
- Attendees: Chris Mildebrandt, Charlie Halloran, Mark McCraw, Merri Jensen, Josh Hester, Jason Losh, Robert DeMason, Jimmy Mohsin, Tania Makins
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.
- Create Decision Matrix wiki page for implementation technology and for CL1 vs CL2 non-functional requirements. - Update from Jason
- Look into additional projects that Michael mentioned, links are provided in the Minutes section from 19FEB08.
- Jason to move forward with vote for Eric as code committer with COSMOS. - DONE
- Charlie to ask Mark W. about whether package name changes will be needed for Change Analyzer code.
- Everyone review the new deployment use cases by tomorrow, then move use cases and "details" into COSMOS Use Cases by end of week.
- Merri & Jason to get up with COSMOS SML experts to create SML for COSMOS. - Julia has done some exploration here. Jason/Julia to provide update.
- 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.
Minutes
- Feedback for deployment use cases was due last week, so we can go ahead and start moving them over to the main COSMOS use case wiki now. Jason will start this effort and work on getting the i11 enhancement requests entered.
- Charlie submitted COO to Ruth for Use Cases last week, and she was supposed to meet with IBM Legal last Friday, but the meeting was moved to today instead.
- Vote for Eric as committer has begun. Hopefully it will be finished by the time he returns.
- Decided that we should change our meeting time since it is at the same time as the Release Engineering meeting, and we're going to need to start working with them soon.
- Mark W. has action to contact Eclipse about all our code contributions that are ready for submission and needs to get Charlie the appropriate package names for the Change Analyzer. Mark has at least responded and indicated that he knows he needs to do this ;-)
- Jason met with SAS Legal and has the okay to proceed with our code contribution. Code will need to be scanned.
- Jason has created the Decision Matrix, but would like Mark W. to review. Jason felt that he skewed more towards Java because he thinks that would be the best technology to use longer term (it allows for easy extensibility), however since the TPM group had some objections to using Java it would be best to have others review.
- Jeff is continuing to look into P2.
- Jason has conference call at 10:00 AM with Mark W. and Julia M. to go over the resource model for the MDR registration for a COSMOS SDD implementation.
- Jimmy summarizes the requirements and problem areas he has encountered when deploying COSMOS. This is to help us with creating an SDD and runtime for i11.
- Identifying Pre-reqs: JRE, JDK, Tomcat, Muse
- Main issue is with detecting pre-reqs and versions and what to do when you have conflicting versions.
- SDD supports Range of versions and supported vs. certified versions
- Sequencing issues - there are a lot of pieces that need to be installed, and sometimes sequencing does matter.
- Version issues with other products
- SDD provides for including pre-reqs with install with requisites (but this is a CL2 feature, so I'm not sure how we'll be able to use this functionality).
- Jason to set up a meeting later this week to discuss in more detail.
- Identifying Pre-reqs: JRE, JDK, Tomcat, Muse
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.