[Oslc-steeringcommittee] Follow up action on SCM charter clarification

[Ersch, Rainer]

That was pretty much my understanding, too.
Based on this, I still would recommend to create a new workgroup called "CM" and put "SCM" on hold.
On the SCM home page it should be clearly described what the status of the workgroup is and what issues the workgroup did run into. In addition, there should be link to the CM workgroup and an outlook to the future of SCM: either continue the exiting which is on hold or move it to the CM as subtopic.
To some extent, that's what the current SCM Home Page says anyway.

Bye and have a nice day
Rainer



From: oslc-steeringcommittee-bounces at open-services.net [mailto:oslc-steeringcommittee-bounces at open-services.net] On Behalf Of Steve K Speicher
Sent: Monday, July 23, 2012 10:20 PM
To: oslc-steeringcommittee at open-services.net
Subject: [Oslc-steeringcommittee] Follow up action on SCM charter clarification

>From our July 19, 2012 meeting [1], we discussed the proposed SCM rechartering and I took the action [2]:
  "Action item for Steve S.: connect with Nick Crossley to get more clarification for the StC"

I have talked to Nick about this.  He has updated the charter to clarify what was intended to be initially within scope for the delivery of a first set of specifications compared to the scope of the workgroup.  Some aspects of SCM will be covered but in the context of a cross-domain view of the concepts, which include SCM scenarios and tools.

Please let me know if this does not cover the action.  If there is still clarity needed, please let me know what sections have an issue and what you would like to be done with it, this will help expedite the resolution.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645

[1] - http://open-services.net/wiki/120719-StC-Meeting/#minutes
[2] - http://open-services.net/wiki/120719-StC-Meeting/#action-items
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20120724/55a587a2/attachment-0003.html>