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, 13 May 2009

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

Agenda:

  • 1.0 spec finalization items (if any) see CmSpecificationIssueTracking
  • demonstration of sample application from Rational
  • retrospective of 1.0 iteration:
    • each WG member should be prepared with feedback on what worked and what didn't (and how we can do to improve)
  • 2.0 milestone date discussion
  • Next meeting May 27, 12 ET
  • Continue with bi-weekly meetings at same time?

Minutes:

Attendees: SteveSpeicher, SteveAbrams, AndreWeinand, RobertElves, MikKersten, ScottBosworth, GaryDang, SamitMehta, CarolynPampino

  • 1.0 Spec issues
    • May 22nd, final day to lock spec. We'll continue with minor updates regarding introductory text, clarfication and consistency (polish), as well as any late-breaking implementation discoveries.
    • Reviewed latest "higher impact" changes:
      • attended factory dropped, form factory (POST on creationDialog)
      • usage of ETags/If-Match parameter on PUT
  • SteveSpeicher demonstrated TeamConcert? and ClearQuest? support from single test application: deep dive on service discovery, delegated UI interactions
  • 2.0 Milestone Plan / Roadmap:
    • July - First focus on scope (scenarios supported)
    • 4Q - target for finalization specs
  • Tabled retrospective until 27 May
  • Next meeting May 27, 12 ET, agenda topics:
    • Tasktop to demonstrate their efforts, looking for WG feedback on approach
    • Retrospective on 1.0 efforts
Topic revision: r4 - 13 May 2009 - 19:12:45 - 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