[oslc-scm] Update about status of OSLC SCM, and discussion about the way forward

[Steve K Speicher]

Nick Crossley/Irvine/IBM wrote on 05/11/2012 01:13:53 AM:

> From: Nick Crossley/Irvine/IBM
> To: "OSLC SCM" <oslc-scm at open-services.net>, Darcy Wiborg Weber/Irvine/
> IBM at IBMUS, Gray Bachelor/UK/IBM at IBMGB, michael.loeffler at gm.com, 
> Cc: Kartik Kanakasabesan/Durham/IBM at IBMUS, Steve K Speicher/Raleigh/
> IBM at IBMUS, rainer.ersch at siemens.com, John Kellerman/Raleigh/IBM at IBMUS
> Date: 05/11/2012 01:13 AM
> Subject: Update about status of OSLC SCM, and discussion about the way 
forward
> 
> OSLC SCM workgroup members:
> 
> It has been a long time since our last workgroup meeting, and while the 
spec
> has still not been finalized, there have been several developments in 
the 
> configuration management space and some new requirements from other OSLC 

> domain including the PLM-ALM workgroup.
> 
> I would like to explain to the workgroup why the spec has not progressed 
to 
> finalization, some of the reasons for the lack of adoption, and how we 
might
> address those issues by broadening the potential audience while at the 
same 
> time lowering the cost of adoption by simplifying the spec.
> 
> Two possible times for this review meeting are:
> Tuesday May 22nd at 6am US/Pacific, 9am US/Eastern, 2pm in the UK.
-1

> Thursday May 24th at 9am US/Pacific, 12 noon US/Eastern, 5pm in the UK.
+1

> Please let me know which of these times you could attend; if you are 
unable 
> to attend either but you are still interested in the future of OSLC SCM, 

> please nominate a substitute.
I don't think I'm a required attendee but would like to be part of it.  I 
know we are well connected on this and therefore I do not need a 
substitute.

> After this initial discussion, it is my hope that we will commence a new 

> stage in the life of the workgroup, resuming regular meetings as we work 
on 
> a revised spec.  For this reason, please also consider what times would 
work
> for you in the future.

I'll work with whatever schedule works for other key required workgroup 
members.

- Steve