Date: Wednesday, 14 October 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
• Notice of related OSLC Topic areas:
  • ReportingHome - Currently forming and looking for participants. There is some good overlap that members of this group may be interested.
  • ScmHome - Also forming and looking for participants. One of their initial scenarios is around SCM and CM integrations, see ScmWorkItemIntegrationStory
• Update on outstanding Actions see CmMeetings09302009
• Extended CmChangeRequestV1? definition CmCommonProperties
  • Review product mappings and gaps
  • Start investigation for field types and constraints: length, rich-text, enumeration values, etc
  • Identify which scenarios require which fields
• Update on integration styles writeup
• Proposal for additional scenario: requirements change management
• 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
  • Feedback from implementations CmImplementationReports
  • CmSpecificationIssueTracking

Minutes:

Attendees: SteveSpeicher, SamitMehta, SamLee, AndreWeinand, MikKersten, RobertElves, OlivierBerger, MarkRinger, SteveAbrams, EricSink

Regrets: SusanDuncan, ScottBosworth,

• OlivierBerger gave introduction of himself and effort he's involved in see post on email thread
• Described new topic areas and extended membership to CM members. There were no questions.
• Review of outstanding action items:
  • SteveSpeicher updated milestone plan
  • SteveSpeicher completed updating CmCommonProperties per previous minutes
• Review of updated to CmCommonProperties
  • WG agreed with approach to defining the common properties for a change request
  • ACTION: Each product team to fill-in and validate columns in table in CmCommonProperties once SteveSpeicher makes final editing pass. Additionally, team members should validate current mappings, add proposed new fields and update unmapped fields.
  • Discussed definition of project field and usage:
    • Rational Change has product_name field which is treated as a simple containment value with some metadata
    • Bugzilla has main concept of product for medium size deployments and then some contextual configuration for larger depoyment, according to MikKersten
    • OlivierBerger proposed used of DOAP for definition a project. WG will defer the decision until we have a list of fields that we want to spec, then look at constraints on field types.
• No update on integration styles writeup, previous ACTION on ScottBosworth, SteveAbrams and MarkRinger
• Proposed scenario around requirements change management
  • WG agreed to include within 2.0 effort
  • SteveSpeicher to work on elaboration of the scenario
• SteveSpeicher informed of effort to attempt to produce test suite for OSLC-CM (IBM)
• ACTION: ScottBosworth , SteveSpeicher to investigate contribution of company logos to the site
• Next meeting 28-Oct-2009 12:00 PM ET
  • ACTION: SteveSpeicher to schedule out meetings in 2010 for same day and time