History   View   Links to this page 2013 January 22 | 08:52 am

Minutes for 2012-08-21

Attending: Nick, David, Mike, Steve S, Sandeep, Gray, CJ Paul, Niklas, Cheryl, Kartik, Peter

  • We first discussed the idea of having alternate meetings at a different time. From the Doodle poll, the best alternative was at 11am US/Pacific on Wednesday, but this was very late for everyone in Europe. After a very brief discussion, the group agreed to leave the current time (Tuesday 6am) for all meetings.
  • CJ Paul and Cheryl from Tivoli introduced themselves as new members of the group.
  • Nick reminded group members to add their names to the Configuration Management home page on the wiki, and to the OSLC SCM mailing list. Nick and Steve will review whether this group will continue to use that SCM mailing list, or create a new one.
  • We then continued the review of configuration management and baseline scenarios, starting with ‘control the use’ - Nick and Mike elaborated the proposal for separate status/workflow objects, trying to keep baselines truly immutable. Steve made the point that with RDF, a provider cannot guarantee true immutability of a resource, since any provider can make new assertions about any resource simply by including a triple with that resource as its subject.
  • Nick agreed to write a draft suggestion for the separate workflow idea, send this to Mike for review, then forward to Config Mgt, PLM, and Change Mgt workgroups for discussion.
  • Nick walked through the ‘high ceremony requirement-driven development’ scenario. Mike commented how again much of this was process / workflow, and effectivity. Nick agreed, but pointed out how there were some important configuration management aspects: the ability to create configurations from scratch, the ability to create configurations that included, referenced, or depended on other configurations, the ability to freeze/snapshot a configuration, and the ability to have links in the context of a configuration.
  • Sandeep suggested we need to define the terminology - and to do so in terms of specific RDF vocabulary definitions, so it would not just be ambiguous English. Nick thought that scenario elaboration and terminology / RDF vocal development had to occur somewhat in conjunction with each other, but agreed that now we had reviewed all the original use cases, it was time for a pass on terminology and vocabulary. Nick undertook to start a draft vocabulary definition on the wiki, and the group would review this draft and the terminology page next week.