OSLC Change Management October 10 2013

OSLC Change Management October 10, 2013

Previous Meeting

Meeting logistics

Included in Meeting agendas and minutes

Agenda

• Recurring agenda items:

  • Community & Implementation updates
  • Specification Issues

• Main agenda items:

  • Follow-up on actions proposal from Automation workgroup.
  • Evolving new CM resources types

• OSLC CM 3.0 Draft Specification

• Assigned scenario owners:

  • IT Operations Linked with Development - VijayAggarwal, SteveSpeicher
  • Mylyn - RobertElves
  • Query For Change Requests matching multiple states - BrianSteele
  • Report problems for application analysis tools - SteveSpeicher
  • Tracking progress of change requests

• Assigned specification owners

  • Attachments - SteveSpeicher, DaveSteinberg
  • Multi state query - BrianSteele
  • State Transitions - SteveSpeicher, SamPadgett
  • Priority / Severity - RobertElves, SteveSpeicher
  • Change Management Types - SteveSpeicher, SamPadgett

Next meeting:

• October 24, 2013

Minutes

Community Updates

Steve: Working on OASIS CCM charter (Change Management, Configuration Management, Asset Management). Trying to find co-proposers (5 people from 2 organizations needed).

Specification Issues

No open CM issues.

Main Agenda

Actions

Sam and Steve gave summary of meeting with John and Martin from Automation workgroup.

Discussion on what this means for CM. Thinking is that the current CM actions proposal fits in with the generic actions proposal from Automation. CM workgroup can limit the meaning of an oslc_cm:Action (e.g., actions must always be POST) in the CM spec. The CM workgroup will then monitor the general actions proposal as it is evolves in Core.

Action Item: Sam will update CM actions wiki to give an example of POST body content and add a separate section showing how CM action should look with the proposed Core actions vocabulary.

We will discuss CM types in a future meeting.

Attendees: Sam Padgett, Steve Speicher, Brian Steele.

Category:Meetings