RE: [alf-dev] ALF Source Code Mangement VocabularyMeeting+1-303-928-3232

["Tim Buss" <TBuss@xxxxxxxxxx>]

No SCM vocabulary call this week.  A number of people said they were
unable to make this week's call due to the holiday so we will not have a
call this week.  If there is something pressing please send email to the
mailing list or to me directly.

Thanks
Tim Buss
Serena Software Inc.

-----Original Message-----
From: Tim Buss 
Sent: Wednesday, June 28, 2006 11:43 AM
To: 'ALF Developer Mailing List'
Subject: RE: [alf-dev] ALF Source Code Mangement
VocabularyMeeting+1-303-928-3232 id 6053141# Wednesday 10:00AM PDT -
meeting minutes

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

Agenda
0. Last week's minutes (below)

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

2. Data model and Schema

3. Any other business

Attendees
Tim Buss
Eric Minick
Richard Title
Scott McGrath

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

1. Tasks

Completed
T7. Discuss "Workspace"

T18
SCM metadata difference report schema.  
We agreed to defer this for now as it does not seem to be a critical use
case.  We will re-visit it in the future.

Todo

T11. Integration based use cases
We decided that this was being discussed extensively as part of the
build use case and that we can piggy back off that discussion.  This
will become important once we have the proposed schema/WSDL since we
will need to apply the use case filter to determine if we have a
reasonable definition (ie useful but not overreaching)

T15.
Expand "primitive" use cases to include more detail (eg datatypes,
method signatures) Richard made some updates.  Tim will check with Adam.

T16.
Update Data model based on ALF meeting feedback.
Brian sent out the updates.  No one has had a chance to review to see of
the changes reflected our discussion.

T17.
Create a schema from the data model. Since the data model is in visio
this may need to be done by hand.
Tim started this.  Various issues became evident (see discussion in "2.
Data Model and Schema" below) Tim will attempt to refine sufficiently to
provide an object for discussion by next week.

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

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

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.

2. Data model and Schema
In attempting to convert the Data model to a schema, some issues came up
and were discussed
A) objects vs ids.  The data model currently implies a ser of nested
instances.  In reality is seems more likely that the object instances
will be related by an ID and that unless we needed the object details we
would always refer to the object by ID.  It seems likely that all SCM
providers can provide a form of ID for the objects the expose to ALF.
It also seems likely that we can assume that these IDs can be passed a
strings and that the actual content of the ID can be opaque to ALF.  It
was suggested that all exposed objects should present a "display name"
and a "unique identifier".  For some providers the value of these fields
may be identical for any particular instance.  The assumption is that
the "display name" is printable and the that "unique identifier" can be
used to identify and retrieve an object instance.
B) Revision Specification (see discussion in T21 above)

3. Any other business - no other business was discussed

Tim Buss - Serena.   

-----Original Message-----
From: Tim Buss
Sent: Tuesday, June 27, 2006 8:31 PM
To: 'ALF Developer Mailing List'
Subject: RE: [alf-dev] ALF Source Code Mangement Vocabulary
Meeting+1-303-928-3232 id 6053141# Wednesday 10:00AM PDT - meeting
minutes

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

Agenda
0. Last week's minutes (below)

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

2. Workspace discussion 

3. SCM Events 

4. Use Cases

5. Any other business

Attendees
Richard Title
Adam Simatel
Brian Carroll
Scott McGrath
Tim Buss

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

1. Tasks

Todo

T7. Discuss "Workspace" -
The problem was re-stated, a discussion ensued in email and it appears
that we have general agreement.

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)

Eric has updated the Wikki description of this based on our discussion.
We need to decide if we need more.  Please review the Wikki.

T15.
Expand "primitive" use cases to include more detail (eg datatypes,
method signatures) Adam has entered some content.  It was agreed that
Adam and Richard would divide up the work and continue this

T16.
Update Data model based on ALF meeting feedback.  Brian committed to
complete the update this week

T17.
Create a schema from the data model. Since the data model is in visio
this may need to be done by hand.  Tim committed to starting this, this
week.

T18
SCM metadata difference report schema.  
We agreed to defer this for now as it does not seem to be a critical use
case.  We will re-visit it in the future.

For some use cases we have identified that some concept of "user" is
necessary to make machine readable report useful.

It is still unclear what the use case is for a more detailed machine
readable report and wha the priority for specifying this is.  It is
possible that most of what we need will come from the schema types we
might define from the data model.

T19
Wikki pictures.  There are some placeholders for pictures in the Wikki.
These need to be poulated.  In particulare it would be good to get the
updated data model into the Wikki

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

2. Workspace discussion
It was agreed that we had general agreement on the workspace concept.
The basic notion is that it is a potentially seperable SCM service that
may run on the same machine as the consuming tool.

3. SCM Events
This item was not discussed in detail 

4. Use cases
File Selection abd Version Selection were mentioned.  To be discussed
later

5. No other business was raised

Tim Buss - Serena.  

**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.