It may be helpful for the team to check out what the Eclipse ALF team did when they tried to standardize some web services around SCM. Now, ALF is pretty much dead these days, so we probably don't want to follow their path too closely.
http://wiki.eclipse.org/ALF/SCM_Vocabulary Some key tripping points ALF encountered that we might want to keep in mind (but not get bogged down in right now): 1) Unlike CM systems, many of integration points don't happen "at the SCM system" when we talk about populating some workspace based on SCM configuration, something needs to happen down at the local workspace and in most SCM systems, a local client controls that rather than the central server. 2) Also, we'll need to deal with some different paradigms. For instance, for some SCM systems you ask the central server to populate some view out to some server and all the magic happens. For something like Subversion, a client on the workspace's machine will need to actually retrieve the files. 3) If we get too deep into the vagaries of branching / stream models, we can get into trouble. Warm Regards, Eric Minick Lead Consultant Urbancode Software On Thu, Sep 24, 2009 at 12:46 PM, Nick Crossley <[email protected]>wrote: > The initial meeting of the SCM OSLC working group will be held by > teleconference on Wednesday October 7th at 12 noon - 1 pm Pacific time. > > Agenda: > > - Introduce members > - Go over goals of the group > - Discuss working practices, meeting times, etc. > - Review producers, consumers, and business drivers > - Review initial scenarios > - Set up initial tasks and milestones > > > Details for joining the call can be found on the SCM meeting page, > http://open-services.net/bin/view/Main/ScmMeetings. > > Nick Crossley. > > _______________________________________________ > OSLC-SCM mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-scm_open-services.net > >
