OSLC Steering Committee (SC) Meeting 1512 - December 15, 2015

Agenda

Attendees:

  • SC Voting Members:
  • Amit Fisher [], Andreas Keis [], Bill Chown [], Bola Robiti [], Mark Schulte [], Martin Sarabura [], Mats Berglund [], Rainer Ersch [], Wesley Coelho []
  • SC Staff Members: Nelson Jean [x], Jim Amsden []
  • OASIS Staff: Jane Harnad [], Scott McGrath []
  • Additional Attendees: Ginny Ghezzo []

# / Area / Topics
1 / General Business
(10mins) / A. SC governance during specification release process (10 mins) -- Rainer
Discussion:
  • There are no specific governance activities defined for the SC in either the MS policies or OASIS specification lifecycle.
  • Prior to OSLC moving to OASIS, the Steering Committee at that time approved specifications after the Workgroup approved it (Participation FAQ on open-services.net)
  • For our future standards/specifications, what role should the SC play in the OASIS Specification Lifecycle?
  • OSLC MS and SC involvement in the forming and guiding of TCs is a valuable aspect of the process
  • Initial ideas on possible options (not mutually exclusive):
  • A recommendation to the OASIS organizational members to release a "Technical Committee work product" as an OASIS standard, after the Committee Specification stage is achieved in the specification lifecycle.
  • SC approval as an OASIS-OSLC specific extension to the "Prerequisites" for starting the OASIS Standard process.
  • SC members are part of the MS, which can participate in the public review process. SC members can also review working draft documents and vote to submit for public review.
  • Others?
  • Comments from previous meeting:
  • Unclear what problem we are trying to solve.
  • Should business challenges/objectives be part of an approval process for technical specifications?
  • Higher-level awareness for the SC in areas like compatibility would be beneficial.
  • OSLC RoP section "e. Provisions that Apply to Affiliated Technical Committees":
  • OASIS Technical Committees may seek to affiliate with the Member Section as provided in the OASIS Member Section Policy.
Technical Committees affiliated with this Member Section will operate under the RF Limited IPR terms unless otherwise approved by a Member Section Steering Committee Special Majority Vote. Technical Committees affiliated with this Member Section should have charters that define coordination points with other TCs in the Member Section to ensure that related specifications and deliverables are consistent and can be used with each other.
Technical Committees affiliated with this Member Section must obtain approval from the Steering Committee prior to submitting any deliverable to the OASIS Technical Committee Administration for OASIS Membership vote and prior to submitting any deliverable to de jure standards organizations. Approval by the Steering Committee will be by a simple majority vote.
2 / Financial
(0 mins) / A. OSLC-SC BudgetLead ( Deferred to future meeting ) -- Mark
Discussion:
  • Mark working with Communications WG.
  • Priorities and proposals for budget use in 2016.

3 / OSLC Initiatives and Partnerships
(30 mins) / A. OSLC Initiatives & Partnerships (30 mins) -- Rainer
  • Navigation: SC wiki Front Page -> Working Documents -> OSLC Initiatives and Partnerships
Discussion:
  • Rainer will provide background and what the objectives and desired outcomes are in the establishment and execution of these partnerships.
  • Review status of all partnerships:list andstatus of partnerships and initiatives

4 / TCs / WGs / UGs
(10 mins) / A. OSLC Communications WG (10 mins) -- Bill, Ginny
Discussion:
  • OSLC Communications Scorecard:
  • Conferences:
  • Conference calendar: SC wiki Front Page -> Working Documents -> Conferences and Events
  • 2016 calendar
B. Lifecycle Integration Patterns UG (Deferred to future) -- Dave West
Discussion
  • Overview by Dave; dependent on his availability.

5 / Other
(35 mins) / A. Eclipse Lyo as general project (10 mins) -- Rainer, Mats
Background:
  • What is the position of StC regarding Lyo
  • We have no formal governance
  • Do we want to influence what’s happening there?
  • Feedback from the community
  • Unclear who to contact for questions
  • Would like to see more activity / content
  • Willing to contribute, but don’t know how
  • What’s the formal relationship to OASIS OSLC?
  • Need for a marketplace for OSLC related assets
  • There are some ideas for an interoperability marketplace
    with the following questions:
  • Should Lyo be this marketplace?
  • What needs to be added to Lyo for that purpose?
  • Is a market place a business opportunity for a small company?
  • there is some interest and venture capital accessible
  • What could be a funding model for a market place?
  • based on sponsorship, membership fee, crowed funding
    other ?
Discussion:
  • Lyo is an external independent entity that has a strong brand in OSLC. As an SC, we support it but don't have control or governance. Contributors to the project are the ones that influence direction.
  • SC generally supportive of the concept of a marketplace and exploring building a closer relationship with Lyo and the community.
  • Rainer/Mats to think about the next level of detail on these concepts and bring back to SC for further discussion.
B. Participation in open source OSLC-related projects (10 mins) -- Jim
Discussion:
  • Overview of projects, participation and how they could help lower barrier of adoption.
C. CIMdata assessment of OSLC (15 mins) -- Andreas
Discussion:
  • OSLCSWOT analysis - accuracies and inaccuracies
  • Next steps
D. OSLC Vision ( Defer to January 2016 ) -- Rainer
Discussion:
  • Need to define and document the OSLC vision.
  • SC members: to provide input to Nelson prior to January meeting.
  • John Wiegand is also planning to provide his perspective as input.
  • May have a dedicated separate meeting to discuss.

6 / Planning for Next SC meeting /
  • Week of January 18th?

7 / RoundTable