Agenda

1. JimConallen will update workgroup of OSLC Core status.
2. Begin listing the critical use case scenarios we want to address for the 2.0 spec.

Minutes

Atendees: Dave Johnson, Tom Picolli, Jonathan Harclerode, Derry Davis, Jim Conallen

1. We started the discussion with the essential use cases. Jim C. proposed four areas of interest: baselines, impact analysis, MDA (automation), and review and approve. Derry also added testing, and in particular relationships to testing resources.

2. Since baselines are generic concept, not AM specific we checked with Dave J. to see if it made sense for our workgroup to discuss it, since it would most likely be a core concepts in the long run. Dave said that it would be useful for us to discuss here, and present later our thoughts to the core.

3. The concept of a baseline should be a first class resource and represents a combination of configuration + version information. Determining configuration is interesting, as it could be determined with a single timestamp, and all resources that exist at that time, and their current versions at that time are what defined the baseline. Configuration could also be determined manually, or with a query. It is useful to be able to subset the active resources for inclusion into a baseline.

4. We concluded that baselines are immutable.

5. We discussed if baselines could be cloned. If they are then the clone would be expected to be editble for at least a little while.

6. The idea of working in a baseline (where the resources are editable) was discussed. We decided that this was really just working in a stream (another concept) and that baselines should remain immutable.

7. The question of whether a baseline was a noun or a verb popped up.

8. Jim C. asked what is it that we expect a baseline to be used for? We came up with two quick uses; compare (Tom P), and compliance checking (Derry D.). Both of which could be done with a combination of automation and manual work.

9. In order to support these two uses of baselines, the service provider is expected to be able to render resources in a baseline.