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.

Date: Wednesday, 25 November 2009

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

Agenda:

  • Call for last minute agenda changes
  • Update on outstanding Actions see CmMeetingsActions
  • Review contributed scenario CmOfRequirements
  • Discussion around OAuth
    • What solutions are used today for cross-system authentication and authorization?
    • What are the current issues with today's solutions?
    • Do any of your tools support OAuth today? If not, any plans. If no plans, reasons for not adopting?
    • If you support or plan to, would you be a consumer or service provider?
  • 1.0 spec comments
  • Review of CmCommonProperties
    • Review product mappings and gaps
    • Identify which properties should be considered for 2.0
  • Discussion on schema/meta-data requirements
  • Progress on 2.0 specs
    • Prioritize scenarios
    • Define scope - CmArchitecturalDirectionV2
    • Milestone plans
    • Progress on extending participation - both as WG participants and implementations
  • 1.0 spec maintenance items
  • Next meetings: 9-Dec, 16-Dec ? update with additional items

Minutes:

Attendees: SteveSpeicher, SofiaYeung, AndreWeinand, RobertElves, MikKersten, MatsGothe, MarkRinger, SusanDuncan,

Regrets: ScottBosworth, OlivierBerger, SamLee, DenisTyrell, SamitMehta

  • Last minute agenda items
  • Review on outstanding Actions see CmMeetingsActions
    • Reiterating need for ALL to review scenarios and needs on certain properties, see CmCommonProperties
  • Mylyn OSLC Java API contribution has been made by Tasktop: RobertElves, MikKersten
  • Review of CmOfRequirements
    • Discussed the difference with scenario of implementing a requirement, creation of change request and linking.
    • Initial read shows these potential gaps in CM: determining completeness of CR and presence of changeset (as a resource and a property of CR)
    • WG concensus that this scenario will be included in CM 2.0 scope
    • Concern was raised with coordination RmHome (working with topic lead on this)
  • OAuth discussion
    • MikKersten, RobertElves have not encountered OAuth in the many connectors they support, prominant one is HTTP-basic
    • ACTION: RobertElves to produce survey of what type of auth model they've encountered (kind and frequency).
    • Noted that their may be classes of integrations to may require OAuth (3-legged), while other scenarios (2-legged) can rely on HTTP-Basic
  • Review of 1.0 spec comments
  • Review of CmCommonProperties mapping effort
    • GoogleDocs? spreadsheet updated with "Frequency" column (B) and color coded to highlight commonality. Many WG members found this format to be very useful
    • Discussion around need to carefully define Project and Component: suggestions were around defining them in generic terms as "context" (Project) and "subtext" (Component) for hierarchal systems, though there may be a need for tagged-based model (Google code). Will queue up for a future WG topic.
    • ACTION: All WG participants to validate entries
    • Next Steps:
      • WG participants to validate entries and scenarios involved
      • SteveSpeicher to propose an CR 2.0 definition based on frequency of use + scenario needs
  • Next meetings:
    • 9-Dec 12:00 PM Eastern
    • 16-Dec 12:00 PM Eastern (added)

Update with any corrections

Topic revision: r5 - 25 Nov 2009 - 18:58:24 - SteveSpeicher
 
This site is powered by the TWiki collaboration platform 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