[news.eclipse.technology.alf] Meeting minutes for the ALF Source Code Ma

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

Meeting minutes for the ALF Source Code Management Vocabulary Meeting on
Wednesday July 28th at 10:00AM PDT

Agenda

0. Last meetings's minutes (below)

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

2. Data model and Schema (see attached)

3. Events

4. Any other business

Attendees

Richard Title

Mark Phippard

Eric Minick

Tim Buss

0. Last weeks minutes were accepted. No additional comments were noted
except I had the date wrong.

1. Tasks

Completed

T20 Add the notion of User to the concepts User is an important concept to
SCM since a primary function is to attribute changes to particular authors

Eric added some "user stuff"

Todo

T15.

Expand "primitive" use cases to include more detail (eg datatypes, method
signatures) Richard made some updates. Adam committed to update the items he
signed up for and resend the email soliciting for volunteers to address the
remaining items

T17.

Create a schema from the data model.

Tim has create a set of type defintions from the main data model.

Workspace still needs to be addressed. Revision Specification need more
discussion (see T21)

T19

Wikki pictures. There are some placeholders for pictures in the Wikki.

These need to be populated. In particular it would be good to get the
updated data model into the Wikki



T21. Refine the idea of "Revision Specification". Define the common use
cases.

There are several ways this could be expressed. For example:

A) as an opaque string to ALF

B) as a formal set of "objects" that can be related in some formal way

C) as an ALF defined "language string

D) some combination of above.

It seems that there are some common use cases (eg get "latest" from

branch) that should be defined explicitly by ALF but there are many other
cases. It seems unwise for ALF to attempt to define a fully generalized
approach. For this cases ALF should just allow the underlying tool to extend
the ALF services or provide tool specific services. We need to decide what
cases make sense for ALF to formally define.

This should be an agenda item for next week.

T22. Create WSDL for operations and events

2. Data model and Schema

The schema was given a quick review.

It was noted that two spellings of Label were used.

Some of last meetings discussion may not be reflected in the schema and that
should be reviewed.

It was noted that timestamp is currently a string and since time is
important to SCM it was thought better if the schema datetime type was used.

3. Events

We walked through the various proposed operations and discussed the events
that might result. My notes are not good on this CreateWorkspace

no event needed?

ModifyWorkspace

no event needed?

RemoveWorkspace

no event needed?

AddAssets

Seems similar to CreateNewVersions

a NewElementVersion event seems useful. An issue would be if there 100s at
once as a project gets checked it.

RemoveAssets

ElementRemoved seems reasonable. Probably not a core ALF scenario
IntentToModify

Not clear what the ALF scneario would be. An issue would be if there are
100s of locks at once if a project gets locked. May need an event it it
could be slow.

CreateNewVersions

(see AddAssets)

CreateStream

NewStream event seems reasonable. Probably not a core ALF scenario. May need
an event if it could be slow.

CreateBaseline

NewBaseline event seems reasonable. Might be connected with a build. May
need an event if it could be slow.

UpdateWorkset

WorksetUpdated (Workspace surely?) Probably the trigger to start the build
CompareElementVersions

CompareComplete event seems reasonable. Might be connected with a build. May
need an event if it could be slow.

Merge

Merge does not seem like a good candidate for ALF since it can fail in ways
that cannot be detected. If it is useful then it may need an event if it
could be slow.

Promote

ElementVersionPromoted seem a bit to granular.

ElementVersionsPromoted seems more useful

3. Any other business

A point was raise that perhaps raising an ALF Event for every asynchronous
action completion may be too heavyweight. An alternative using a dynamic
callback service passed with the operation was suggested. This would
probably tale the form of an ALF event in defintion but would connect back
to the calling instance of the service flow directly. The removes the need
to create new service flow instance and simplifies data correlation in some
cases.

Tim Buss - Serena.