Date: Wednesday, 14 September 2011

Time: 12:00 PM Eastern, 9:00 AM Pacific, 6:00 PM Zurich (contact SteveSpeicher if you'd like to participate)

Previous minutes: CmMeetings20110831

Agenda

• Reoccurring agenda items:
  • Recap of previous meeting CmMeetings20110831
  • Community & Implementation updates
  • Specification Issues Review CmSpecV2Issues (6 open as of 5/26)
• Main agenda items:
  • Progress on 3.0 items
    • Proposed: state transition - AndreWeinand (review proposal)
    • Proposed: priority/severity - RobertElves (review proposal)
    • Awaiting progress on state transitions CmScenariosMultiStateQuery - BrianSteele
  • Assigned scenario owners:
    • ITOpsToDev - VijayAggarwal, SteveSpeicher
    • ScenariosMylyn - RobertElves
    • CmScenariosMultiStateQuery - BrianSteele
    • CmScenariosApplicationAnalysisTools - SteveSpeicher
    • CmTaskTracking - AndreWeinand
  • Assigned specification owners
    • attachments - SteveSpeicher DaveSteinberg
    • need for OR in query - BrianSteele
    • state transition - AndreWeinand
    • priority/severity - RobertElves
• Previous Action Items:
  • VijayAggarwal to complete list of ITOpsToDev scenarios and prioritize
  • SteveSpeicher - take feedback from Andre around implementation guidance wiki page, etc
  • SteveSpeicher - 2010 / CM 2.0 Retrospective - review action items from last meeting
• Next meetings:
  • Sept 28
    • Continue with multi-state query, state transition and pri/sev

Minutes

Attendees: SteveSpeicher, SofiaYeung, SamPadgett, RobertElves, AndreWeinand, SamitMehta, BrianSteele

Regrets: VijayAggarwal

Reoccurring agenda items:

• Recap of previous meeting CmMeetings20110831
• Community & Implementation updates
  • EclipseCon? Europe Nov 2-4 - SteveSpeicher - giving mini-OSLC workshop
• Specification Issues Review CmSpecV2Issues (6 open as of 5/26)

• Progress on 3.0 items
• Review timetable for 3.0 spec
  • Propose to move CM 3.0 finalization until 2H2012
• Proposed: state transition - AndreWeinand (review proposal)
  • Need to define well-known state transitions (actions)
  • What would happen when required fields are missing? Case 2: Delegated UI, Case 1: perhaps have a simpler model for integrations
    • simplified state model preferred
    • an advanced option would be to have shapes for actions
  • ACTION: Need an agreement on right RESTful action model to use
  • How does the user know the right state/action flow to get to desired state? TBD
• Proposed: priority/severity - RobertElves (review proposal)
• Awaiting progress on state transitions CmScenariosMultiStateQuery - BrianSteele

• ITOpsToDev - VijayAggarwal, SteveSpeicher
• ScenariosMylyn - RobertElves
• CmScenariosMultiStateQuery - BrianSteele
• CmScenariosApplicationAnalysisTools - SteveSpeicher
• CmTaskTracking - AndreWeinand

• attachments - SteveSpeicher, DaveSteinberg
• need for OR in query - BrianSteele
• state transition - AndreWeinand
• priority/severity - RobertElves, SteveSpeicher

• VijayAggarwal to complete list of ITOpsToDev scenarios and prioritize
• SteveSpeicher - take feedback from Andre around implementation guidance wiki page, etc
• SteveSpeicher - 2010 / CM 2.0 Retrospective - review action items from last meeting

• Sept 28
  • Continue with multi-state query, state transition and pri/sev

update with additional items