RE: [alf-dev] ALF Source Code Mangement Vocabulary Meeting+1-303-928-323

["Tim Buss" <TBuss@xxxxxxxxxx>]

There will be a ALF Source Code Management Vocabulary Meeting tomorrow,
Wednesday May 31th at 10:00AM PDT

The call in number is

+1-303-928-3232 id 6053141#

as usual

Agenda
0. Last week's minutes (below)

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

2. Use Cases 

3. Workspace discussion 

4. Any other business

Tim Buss - Serena.  

-----Original Message-----
From: Tim Buss 
Sent: Thursday, May 25, 2006 9:56 AM
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 May 24th at 10:00AM PDT 

Agenda
0. Last week's minutes (below)

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

2. Use Cases 

3. Workspace discussion 

4. Any other business


Attendees:
Tim Buss - Serena
Adam Simantel - Serena
Eric Minick - Urban Code
Richard Title - Accurev
Mark Phippard - SoftLanding

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

1. Status on tasks

Todo
T3. Pick a couple of use cases to fully flesh out as examples. 

We received some integration based use cases from Kelly Shaw (see her
email) and have decided to pursue her first case from an ALF perspective
Eric Minick and Richard title "volunteered" to have go at this.

T7. Discuss "Workspace" -
We started the discussion on the all (see below)

T9. Add SCM product equivalent terms to concepts - due May 24
	Adam Simantel added some

T11. Integration based use cases
We need to capture a set of typical SCM integration use cases to ground
the ALF vocab effort
	Adam Simantel
	Eric Minick
	All
Eric created a Wikki page which was discussed (see below) It was
suggested that we need to have some scenario based use cases (see Use
Cases Below) We decided to continue this task in a separate Mail thread.
This appears to be close to the idea of T3 (above) which somehow I
missed in the task review

The email thread gathered some useful perspective.

T12. Review and Discuss Data Model - All - due May 31 Postponed due to
Brian' absence

T13. Review and
Discuss "Component" concept - All - due May 31 Postponed due to Brian'
absence

T14. Wikki pictures -
This has been figured out and while a bit convoluted seems to be fairly
easy.  When you are editing a section thre is a tab at the top that
allows you to insert an image tag   eg. [[Image:Example.jpg]] at the
cursor.  If you save the change and exit the edit mode you can click on
the image tag to upload the image.

New Tasks
T15.
Expand "primitive" use cases to include more detail (eg datatypes,
method signatures) I volunteered to ask Adam and Jamey to take a look at
this

2. Use cases
Basic point - While the it's true that primitive can be used to create
any SCM scenario we want to ALF focused integration scenarios to
prioritize primitives.  The goal is not to create the "best SCM ever".
We decided to pursue primitives and scenarios in tandem.  
Eric and Richard will break down Kelly Shaw's Scenario to illustrate how
that might get implmented using ALF.
Adam and Jamey (too be determined) will expand the primitive use cases
to start including the datatypes and method signatures (see tasks T3 and
T15)

3.  Workspaces
Basic point - SCM usually involves a client that controls some local
storage.  Tools operate on this local storage.  In ALF, the service flow
may iniate a get (fex) but it doesn't control any local storage and we
do not want to stream file content through BPEL.  We need a "workspace
service" that can provide storage for the get (fex) that the SCM can be
instructed to get to and tools can be instructed to access to obtain the
file content. The ALF purpose is to avoid the tool having in integrate
with every SCM client individually.  There are a number of models for
this.  This will be discussed in a separate thread.

4. Other business
No other business was noted.

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.