[news.eclipse.technology.alf] ALF Source Code Mangement Vocabulary Meeti

["Tim Buss" <t b u s s @ S e r e n a . c o m>]

Meeting minutes for ALF Source Code Management Vocabulary Meeting, Wednesday
May 31th at 10:00AM PDT

0. Last week's minutes

1. Status on tasks (see list in minutes below)

2. Component and Data Model discussion

3. Use Cases

4. Workspace discussion

5. Any other business

Attendees:

Brian Carrol

Tim Buss

Richard Title

Mark Phippard

Jamey Clark

Adam Simantel

Eric Minick

0. Last weeks minutes were accepted. Not additional comments were noted

1. Status on tasks

Done:

T12. Review and Discuss Data Model (see item below) T13. Review and Discuss
"Component" - Due to the complications it raises we decided to drop the
notion of Component for now (see item below)

Todo

T7. Discuss "Workspace" -

The discussion continued in Email. There are two points of view.

1. That ALF should just specify an "API" with which to wrap the SCM client
allowing it to be installed in the same locality as a tool much as an SCM
client would normallybe but be controled by ALF to materialize files
"locally" to the tool.

2. That ALF should specify an API that and SCM server would implement that
would allow for a "common client" to be implemented. This would allow for
more sophisticated interactions such a pushing the file to the tool. ( not
sure I've really captured this one)

We still have to resolve this. I propose that 2 may be considered an
extension of 1 and if we decide it is necessary we can build on 1 to create
2. They are not mutally exclusive. I would like to get agreement on this so
we can mke an initial proposal.

T11. Integration based use cases

We think that most build use cases are a variant of the K Shaw use case.
(see Use Case Discussion below)

T15.

Expand "primitive" use cases to include more detail (eg datatypes, method
signatures) Adam and Jamey are taking a look at this

T16.

Update Data model based on ALF meeting feedback. Brian took notes and will
do this

T17.

Create a schema from the data model. Sicne the data model is in visio this m
ay need to be done by hand. Looking for volunteers otherwise Tim Buss may
take this on.

T18

SCM metadata difference report schema. We should capture some use cases for
this. To make it worthwhile to define a machine readable schema there needs
to be some compelling mainstream use cases that need to leverage the report
results in an automated way. - All

2. Component and Data Model discussion

Brian presented v3 of the data model (attached). There was general consensus
that it made sense. Some modifications were suggested.

It was suggested that maybe the notion of an ALF define meta-data difference
report should be captured. There was some concern that this may be beyond
the scope of ALF but it was generally agree that this may depend on what use
cases we consider core and what are edge and that this was worth some
further analysis. It seem likely that such a report would be based on the
same types defined by the data model and thus this may not the that onorous
to define if we think that is workwhile. It was noted that the is already a
semi-standard differnce format for file content.

Three action items were noted (T16, T17, T18)

On the idea of "component" (see attached) it was generally agreed that this
was an abstract notion that was not universally supported by SCMs. It was
suggested that it might be useful as a concept across stores. For now we
decided to drop it and perhaps re-visit it later once the core is defined.

3. Use Cases - not discussed due to time

4. Workspaces - not discussed due to time (see T7 above) There has been some
discussion in the mailing list on this

5. Other business - none raised



Tim Buss,

Serena