RE: [alf-dev] RE: ALF Source Code Mangement Vocabulary Meeting meetingmi

["Richard Title" <rtitle@xxxxxxxxxxx>]

Great, looks good!

Also, I just added an "Introduction" section and a "Architecture" section to
the ALF SCM Vocabulary Wiki, based on my earlier Word doc. The Architecture
section is the one Tim was going to re-do, but in the meantime I filled in
some text based on my earlier write-up and our subsequent discussions.

http://wiki.eclipse.org/index.php/ALF/SCM_Vocabulary 

[I also re-did the "Concepts/Objects" section in the Wiki, based on my
earlier Word doc, but those edits were lost when my Wiki login expired
before I saved them. I'll do it again tonight if I have the energy :-(. A
word to the wise: Save early and often when editing Wiki's.]

Question: How do I insert pictures into the Wiki?

Thanks,

- Richard Title

-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Eric Minick
Sent: Tuesday, May 16, 2006 6:16 PM
To: ALF Developer Mailing List
Subject: Re: [alf-dev] RE: ALF Source Code Mangement Vocabulary Meeting
meetingminutes

SCM Vocab Team and all,

I've put together a quick overview of the SCM integration use cases from 
the perspective of build management tools. Comments and suggestions from 
those who are familar with these tools would be most welcome.

It's currently up on the wiki here: 
http://wiki.eclipse.org/index.php/ALF/Build_Server_Use_Case .

As we discussed, this is a fairly coarse grained set of use cases. On 
further reflection though, I'm not sure that's the right direction. As 
we move have added more customizable workflow oriented behavior in our 
commercial app, we found it helpful to expose more low level and scm 
dependent concepts directly to the user - particularly the advanced 
user. In the open source tool, the coarse grained approach does simplify 
development.

In a tool like ALF that is primarily geared towards users scripting 
interactions in service flows, finer grained use cases might be more 
appropriate, if only in the context of the more coarse.

Cheers,

Eric Minick
Urbancode, Inc.
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev