OSLC Core Meeting March 9, 2011
Previous meeting
Link to OSLC Core spec:
OslcCoreSpecification
Meeting logistics
How to dial-in to our telecon and login to our screen-sharing session.
Telecon Info
- USA Toll-Free: 888-426-6840
- USA Caller Paid: 215-861-6239
- Participant Code: 6867265#
Online meeting
(when we need it)
- For IBM employees, use the following link:
- For people outside IBM, use the following link:
Agenda
Item: Specification changes
- Delegated UI example change
- Delegated UI resizing change
Item: Community news
- Progress in OSLC Tools
- Progress on OSLC Primer
- Lots of OSLC mentions at IBM's Tivoli conference around "dev-ops" concept, see also:
- Other community news?
Item: Ian Green's Improvements to Vocabulary XSL
Item: Workgroup schedule
- Ready to schedule Baselining come-back
- Ready to schedule Change Log come-back?
- See also the new OslcCoreV3Plan page
- Need to think about OSLC Core v3 schedule
Minutes
Attendees and notes from the meeting
Attendees
Regrets:
- Jim Connallen
- Scott Bosworth
- John Arwe
Attended:
- Dave Johnson
- Steve Speicher
- Bill Higgins
- Nick Crossley
- Frank Budinski
Topics discussed
Dave covered specification changes and community news.
Dave introduced Ian Green's email about our vocabulary XSL
- AI: Dave to notify workgroup leads to regenerate with Ian's new XSL
Tentatively schedule Baselining next meeting, March 23
Schedule: Change Log first, then Baselining on March 23
Nick brought up the topic of SCM and needing to rename it or change it to be more inclusive of Configuration Management. Should we do some renaming now, despite the fact that we are in finalization? Namespaces would have to change
Steve mentioned possibility of shelving the old SCM spec, then copying it to a new spec.
Bill recommended a sprint to investigate suitability of SCM spec for Configuration Management purposes, does it really fit or do we need a new effort. Can we do a two week sprint to figure this out.
Nick: if we can do something in the next month and half we're good. We plan no changes to SCM spec in that timeframe now, as we are still awaiting implementations from some tools before we can finalize.