Date: Wednesday, 16 Feb 2011
Time: 12:00 PM Eastern, 9:00 AM Pacific, 6:00 PM Zurich (contact SteveSpeicher if you'd like to participate)
Previous minutes: CmMeetings20110202
Agenda:
- Reoccurring agenda items:
- Main agenda items:
- 2010 / CM 2.0 Retrospective - review action items from last meeting
- Summary:
- Overall WG considers things worked well
- Would like to see better alignment with something like reference impl / test suite
- Better/more examples around how to adopt the spec
- Continue to be scenario driven
- Proposed actions:
- Encourage contribution and development of RI & test suites from WG participants
- Work on primer, tutorials, articles to help explain how to adopt the spec
- Improve process for out-of-band reviews / decision making
- Improve traceability and background of how specification conclusions were reached.
- Goal is to finalize catalog of scenarios and prioritize for spec work
- Updated scenarios:
- Progress on CmAttachments scenario elaboration
- Identify specification needs/approach to support prioritized scenarios: CmScenarios
- 3.0 Themes CmArchitecturalDirectionV3
- Next meetings:
- [Mar 2] - Reschedule or new host?
Minutes
Attendees: SteveSpeicher, RobertElves, SofiaYeung, BrianSteele, AndreWeinand, DaveJohnson, SamitMehta, ScottBosworth
Regrets: SamLee, SamPadgett
- Reoccurring agenda items:
- Recap of previous meeting CmMeetings20110202
- Community updates
- OSLC talks / demos at IBM Pulse conference in Vegas 2/28-/3/3
- OSLC talks / demos and more expected at IBM Innovate conference in Orlando in June
- Implementation updates
- DaveJohnson gave update on SORI progress on sourceforge
- AndreWeinand gave summary of ongoing progress with RTC 3 fixpack
- Specification Issues Review CmSpecV2Issues
- Main agenda items:
- 2010 / CM 2.0 Retrospective - review action items from last meeting
- Summary:
- Overall WG considers things worked well
- Would like to see better alignment with something like reference impl / test suite
- Better/more examples around how to adopt the spec
- Continue to be scenario driven
- Proposed actions:
- Encourage contribution and development of RI & test suites from WG participants
- Better issue tracker for open-services.net
- Work on primer, tutorials, articles to help explain how to adopt the spec
- Improve process for out-of-band reviews / decision making
- Improve traceability and background of how specification conclusions were reached.
- AndreWeinand - will come back to WG
- ScottBosworth - better examples, practical use of shapes, practical use of state predicates
- Goal is to elaborate catalog of scenarios and prioritize for spec work
- Updated scenarios:
- ScenariosMylyn - elaborate on attachment needs and what did/didn't make 2.0 * Need a way to delete attachments * Not necessarily need a way to modify but maybe replace/update and existing file.
- CmScenariosApplicationAnalysisTools - clarified usage of attachments and minimal properties * Be good if there was a formatting standard for descriptions, rich text fields. Look to create another standard.
- ITOpsToDev - terminology and misc updates
- Progress on CmAttachments scenario elaboration * Outlined out it could work based on current implementation restrictions. Next steps to look at alternative approaches and come up with recommendations.
- ScottBosworth recommended tracking how ChangeLog may expose itself in a domain spec
- Identify specification needs/approach to support prioritized scenarios: CmScenarios
- 3.0 Themes CmArchitecturalDirectionV3
- Next meetings:
- Mar 9 - Elaborate on scenarios, identify specification needs (rescheduled from 3/2)
- Mar 16 - Elaborate on scenarios, identify specification needs