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 "COSMOSF2F-08-May-07"
(→Logistics) |
(→Minutes) |
||
| (18 intermediate revisions by 4 users not shown) | |||
| Line 13: | Line 13: | ||
Thornhill, Ontario, Canada, L3T 7W4 | Thornhill, Ontario, Canada, L3T 7W4 | ||
| − | |||
* Need to have regular updates at the end of each day | * Need to have regular updates at the end of each day | ||
=== Requirements === | === Requirements === | ||
| − | + | * Requirements for [[COSMOSPersisteceFrameworks|Persistence Framework]] | |
* Requirements for additional framework features | * Requirements for additional framework features | ||
** Out of box experience | ** Out of box experience | ||
| + | *** Initial user experience | ||
*** Install/packaging | *** Install/packaging | ||
* Requirements for additional components | * Requirements for additional components | ||
* Add detail to all requirements to facilitate planning and design | * Add detail to all requirements to facilitate planning and design | ||
| + | * Resource Modeling | ||
| + | ** Review design for repository API | ||
| + | |||
| + | * Data Visualization | ||
| + | ** Discussion around the deployment and programming models for the user interface. | ||
=== Architecture === | === Architecture === | ||
| Line 30: | Line 35: | ||
* High level design of exemplary components | * High level design of exemplary components | ||
* Alignment of query interface with TPTP and Data Reporting | * Alignment of query interface with TPTP and Data Reporting | ||
| + | * Review of the SML definitions for Data Collection and Managed Component resources ( RM project, requested by Valentina ) | ||
=== Planning === | === Planning === | ||
| Line 35: | Line 41: | ||
* Prioritization of component and feature delivery | * Prioritization of component and feature delivery | ||
* Tentative assignment of resources to deliverables | * Tentative assignment of resources to deliverables | ||
| + | * Discuss features for post 1.0 releases | ||
| + | |||
| + | === Process === | ||
| + | |||
| + | * Planning for the next release. Define schedule and project direction for COSMOS 1.1 ( or 2.0 ? ) | ||
| + | * Release engineering/build - clarify who is responsible for leading this component. I understand Hubert is just helping with setting up the build until a replacement is made available. Do we have any plans moving forward? | ||
| + | * Define an iteration testing process. During the test pass cycle executed at the end of every iteration all projects are expected to run testcases and report results. We should clearly describe the process and the iteration test pass exiting criteria. At what point can a project declare that the testpass has been completed? (Is it when all testcases are run and execution is logged in CVS? Or when all testcases are marked as pass? ) | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | === Minutes === | ||
| + | |||
| + | A first pass of the detailed minutes has been posted. | ||
| + | [[Image:COSMOS F2F-May 8-10 2007-minutes.zip]] | ||
| + | |||
| + | |||
| + | ---- | ||
| + | [[Category:COSMOS Summits]] | ||
Latest revision as of 09:38, 28 January 2008
Contents
The focus will be on refining the design of the data collection framework and prioritizing its delivery.
Here are a few agenda items to get us started - please add your own
Logistics
May 8 - 10, 2007
Computer Associates has been kind enough to host this meeting
Training Room,
8th floor, 125 Commerce Valley Dr. West,
Thornhill, Ontario, Canada, L3T 7W4
- Need to have regular updates at the end of each day
Requirements
- Requirements for Persistence Framework
- Requirements for additional framework features
- Out of box experience
- Initial user experience
- Install/packaging
- Out of box experience
- Requirements for additional components
- Add detail to all requirements to facilitate planning and design
- Resource Modeling
- Review design for repository API
- Data Visualization
- Discussion around the deployment and programming models for the user interface.
Architecture
- High level design of functional enhancements
- High level design of exemplary components
- Alignment of query interface with TPTP and Data Reporting
- Review of the SML definitions for Data Collection and Managed Component resources ( RM project, requested by Valentina )
Planning
- Prioritization of component and feature delivery
- Tentative assignment of resources to deliverables
- Discuss features for post 1.0 releases
Process
- Planning for the next release. Define schedule and project direction for COSMOS 1.1 ( or 2.0 ? )
- Release engineering/build - clarify who is responsible for leading this component. I understand Hubert is just helping with setting up the build until a replacement is made available. Do we have any plans moving forward?
- Define an iteration testing process. During the test pass cycle executed at the end of every iteration all projects are expected to run testcases and report results. We should clearly describe the process and the iteration test pass exiting criteria. At what point can a project declare that the testpass has been completed? (Is it when all testcases are run and execution is logged in CVS? Or when all testcases are marked as pass? )
Minutes
A first pass of the detailed minutes has been posted. File:COSMOS F2F-May 8-10 2007-minutes.zip