This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
CmHome
>
CmMeetings
>
CmMeetings10132010
(13 Oct 2010,
SteveSpeicher
)
(raw view)
---++ Date: Wednesday, 13 Oct 2010 Time: *12:00 PM* Eastern, 9:00 AM Pacific, 6:00 PM Zurich (contact SteveSpeicher if you'd like to participate) ---+++ Agenda: * Progress on 2.0 spec finalization * Promoting usage URIs to be allowed values for rdf:type of a oslc_cm:ChangeRequest * Clarifying what should be returned from queries when requesting application/xml: atom or rdf-subset? * Review any new CmImplementationReports * Review and resolve any CmSpecV2Issues on CmSpecificationV2 * Will declare 2.0 final when: * 2 Provider implementation reports received (4 received as of 13-Sept) * 1 Consumer implementation report received (4 received as of 13-Sept) * Looking for more feedback on shapes, limited feedback to date * WG will review impl reports and make decision on whether specs are considered implementable and interoperable * Continue to leave open for feedback * Community updates * Implementation progress * Review and prioritize scenarios for further consideration * [[http://open-services.net/pipermail/oslc-cm_open-services.net/2010-October/000223.html][Possible OSLC priorities and themes for 2011]] * [[CmScenarios][Scenario Backlog]] * [[CmTechnicalPrioritiesV2][V2 Technical Priorities and backlog]] * [[CmExperimental][Experimental Specification and feedback]] * [[CmArchitecturalDirectionV2][V2 Architectural Direction and Backlog]] * Next meetings: * 27-Oct-2010 Scoping of scenarios and content for post-2.0 specs. ---+++ Minutes: Attendees: SteveSpeicher, RobertElves, AndreWeinand, SamPadgett, SofiaYeung, DaveJohnson, ScottBosworth Regrets: MikKersten, SamitMehta, * Call for additional agenda items, none. * Progress on 2.0 spec finalization * Promoting usage URIs to be allowed values for rdf:type of a oslc_cm:ChangeRequest * agreement to make change * Clarifying what should be returned from queries when requesting application/xml: atom or rdf-subset? * Steve will clarify what should be returned with appl/xml, abbrev RDF/XML form of XML * Steve will clarify to use rdf/xml within atom+xml as recommended content type for entries * Review any new CmImplementationReports * no new updates * Review and resolve any CmSpecV2Issues on CmSpecificationV2 * no new issues logged * Will declare 2.0 final when: * 2 Provider implementation reports received (4 received as of 13-Sept) * 1 Consumer implementation report received (4 received as of 13-Sept) * Looking for more feedback on shapes, limited feedback to date * WG will review impl reports and make decision on whether specs are considered implementable and interoperable * Continue to leave open for feedback * will vote on the Oct 27th and target as finalization as CM and Core clarifications are finalized * Community updates * Implementation progress * SteveSpeicher attended Open World Forum and presented on OSLC. Also many good discussions during the conference on OSLC * RobertElves Eclipse Mylyn announcement that it has been elevated to top-level Eclipse project and OSLC is part of it * SteveSpeicher reiterated mailing list announcements on early access support for CM 2.0 by Rational's CM products: Team Concert, Change and ClearQuest * Review and prioritize scenarios for further consideration * Feedback on [[http://open-services.net/pipermail/oslc-cm_open-services.net/2010-October/000223.html][Possible OSLC priorities and themes for 2011]] * RobertElves standard way to get embeddable/delegated ChangeRequest Web UI editor * RobertElves way to know which properties' allow values are dependent on another property's current value * SofiaYeung similar to Robert's needs on providing more information on property dependencies * AndreWeinand similar request for delegated CR editors * AndreWeinand comprehensive test suites are needed to help ensure complete coverage, esp of areas of spec that aren't used in own team's integration testing. * SamPadgett ability to tie state changes across resources, for example defect being fixed unblocking test case * SamPadgett mechanism similar to delegated editor UI but possibly for action based or state change scenarios * SamLee Action based integration with abstract levels of state models, completing state predicate and actions works from before * Need for way for common ways of initiating and performing approvals/reviews. * Other material referenced and will discuss in future meetings: * [[CmScenarios][Scenario Backlog]] * [[CmTechnicalPrioritiesV2][V2 Technical Priorities and backlog]] * [[CmExperimental][Experimental Specification and feedback]] * [[CmArchitecturalDirectionV2][V2 Architectural Direction and Backlog]] * Next meetings: * [[CmMeetings10272010][27-Oct-2010 Finalize 2.0, Scoping of scenarios and content for post-2.0 specs.]] * 10-Nov-2010 Continue post-2.0 work _updated as needed with corrections_
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r6
<
r5
<
r4
<
r3
<
r2
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r6 - 13 Oct 2010 - 17:56:32 -
SteveSpeicher
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback