Some of you may already be aware of Open Services for Lifecycle
Collaboration (OSLC), an open initiative being developed at
OSLC is a community developing specifications for a set of REST
services for linked data in product and software delivery teams.
One such specification is that for Software Configuration Management,
and I lead the workgroup for that team (my name is Nick Crossley,
and I work for IBM).
I'm hoping that some of you would be interested in contributing to
OSLC in any of several ways.
First, we have a draft first version of the SCM specification, defining
read-only services to access resources in an SCM system, and of course
it would be good if we could produce an implementation of those services
for Subversion. The first step in this direction would be for us to
review the draft spec and see how the services could be mapped to
Subversion; if there are problems in the spec making it unclear how to
do this, we can clarify or fix defects in the spec.
Second, we will soon start work on version 2 of the SCM spec, adding
new services. I would very much like to have some input from this
community on what those services should be, and how they should work.
This input can be provided informally, or you are welcome to join the
Third, you are of course not limited to reviewing or contributing to the
SCM spec. If you have interest in the other groups, such as change
management (defect tracking, etc.), asset management, quality/test
management, requirements management, etc., then your input to those
domains would also be welcome.
To review the specs for any of these groups, and to comment on those
specs or contribute new idea, look at the wiki at
http://open-services.net/bin/view/Main/WebHome. Each workgroup has an
email list, and there's also a community email list for general OSLC
For your comments on OSLC SCM, you can use the OSLC SCM email list (see
or respond to this thread, or mail me directly at ncrossley_at_us.ibm.com.
Received on 2011-03-17 19:21:41 CET