[oslc-cm] OSLC Change Management Working Group Minutes February 16, 2011
Steve K Speicher
sspeiche at us.ibm.com
Wed Feb 16 13:18:06 EST 2011
Minutes: http://open-services.net/bin/view/Main/CmMeetings20110216
Attendees: SteveSpeicher, RobertElves, SofiaYeung, BrianSteele,
AndreWeinand, DaveJohnson, SamitMehta, ScottBosworth
Regrets: SamLee, SamPadgett
* Reoccurring agenda items:
o Recap of previous meeting CmMeetings20110202
o 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
o Implementation updates
+ DaveJohnson gave update on SORI progress on sourceforge
+ AndreWeinand gave summary of ongoing progress with RTC 3
fixpack
o Specification Issues Review CmSpecV2Issues
* Main agenda items:
o 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
o Goal is to elaborate catalog of scenarios and prioritize for
spec work
o 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
o 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.
o ScottBosworth recommended tracking how ChangeLog may expose
itself in a domain spec
o Identify specification needs/approach to support prioritized
scenarios: CmScenarios
o 3.0 Themes CmArchitecturalDirectionV3
* Next meetings:
o Mar 9 - Elaborate on scenarios, identify specification needs
(rescheduled from 3/2)
o Mar 16 - Elaborate on scenarios, identify specification needs
Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645
More information about the Oslc-Cm
mailing list