Jump to: navigation, search

Difference between revisions of "Governance/InteropWG"

(Current Committee Participants)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.
 
This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.
  
''DefCore sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled "OpenStack."''
+
''Interop Working Group sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled "OpenStack."''
  
 
Our mission is to define "OpenStack Core" as chartered by the by-laws.
 
Our mission is to define "OpenStack Core" as chartered by the by-laws.
  
 
== Important Artifacts ==
 
== Important Artifacts ==
# [https://github.com/openstack/defcore/blob/master/doc/source/process/Lexicon.rst Terms Definition]
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/Lexicon.rst Terms Definition]
# [https://github.com/openstack/defcore/blob/master/doc/source/process/CoreDefinition.rst 10 Core Principles]  (board approved Hong Kong Summit)
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/CoreDefinition.rst 10 Core Principles]  (board approved Hong Kong Summit)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/PlatformCap.rst Capability Levels: Component and Platform]  (board approved October 2014)
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/PlatformCap.rst Capability Levels: Component and Platform]  (board approved October 2014)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/CoreCriteria.rst 12 Scoring Criteria]  (board approved Atlanta Summit)
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/CoreCriteria.rst 12 Scoring Criteria]  (board approved Atlanta Summit)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/DesignatedSections.rst 10 Designed Sections Principles]  (board approved December 2014)
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/DesignatedSections.rst 10 Designed Sections Principles]  (board approved December 2014)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/GovernanceProcess.rst  DefCore Governance:]
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/GovernanceProcess.rst  Interop Working Group Governance:]
# [https://github.com/openstack/defcore/blob/master/doc/source/process/2015A.rst DefCore Process]
+
# [https://github.com/openstack/interop/blob/master/doc/source/process/2015A.rst Interop Working Group Process]
 
# Capabilities & Sections
 
# Capabilities & Sections
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.03.rst 2015.03] (review [https://github.com/openstack/defcore/blob/master/2015.03.json JSON] for details)
+
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2015.03.rst 2015.03] (review [https://github.com/openstack/interop/blob/master/2015.03.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.04.rst 2015.04] (review [https://github.com/openstack/defcore/blob/master/2015.04.json JSON] for details)
+
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2015.04.rst 2015.04] (review [https://github.com/openstack/interop/blob/master/2015.04.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.05.rst 2015.05] (review [https://github.com/openstack/defcore/blob/master/2015.05.json JSON] for details)
+
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2015.05.rst 2015.05] (review [https://github.com/openstack/interop/blob/master/2015.05.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.07.rst 2015.07] (review [https://github.com/openstack/defcore/blob/master/2015.07.json JSON] for details)
+
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2015.07.rst 2015.07] (review [https://github.com/openstack/interop/blob/master/2015.07.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2016.01.rst 2016.01] (review [https://github.com/openstack/defcore/blob/master/2016.01.json JSON] for details)
+
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2016.01.rst 2016.01] (review [https://github.com/openstack/interop/blob/master/2016.01.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/next.json next.json (current draft of next Guideline) ]
+
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2016.08.rst 2016.08] (review [https://github.com/openstack/interop/blob/master/2016.08.json JSON] for details)
 +
## [https://github.com/openstack/interop/blob/master/doc/source/guidelines/2017.01.rst 2017.01] (review [https://github.com/openstack/interop/blob/master/2017.01.json JSON] for details)
 +
## [https://github.com/openstack/interop/blob/master/next.json next.json (current draft of next Guideline) ]
  
 
== Objective / Scope ==
 
== Objective / Scope ==
  
The DefCore charter is around how the OpenStack brand is applied for commercial uses. Initially, this focus is on "what is core" and sustaining that definition over time.  The scope will likely expand since brand is an ongoing concern related to specialized marks and other use cases.
+
The Interop Working Group is around how the OpenStack brand is applied for commercial uses. Initially, this focus is on "what is core" and sustaining that definition over time.  The scope will likely expand since brand is an ongoing concern related to specialized marks and other use cases.
  
 
There are three ways in which the community uses the OpenStack brand including referring to projects.
 
There are three ways in which the community uses the OpenStack brand including referring to projects.
 
# General community use of the mark
 
# General community use of the mark
 
# Project-specific use associated with development activity
 
# Project-specific use associated with development activity
# DefCore-governed commercial use
+
# Governed commercial use
  
While the top two of these uses are out of scope for DefCore, the committee has a need to participate in the discussion to ensure consistent and clear use.
+
While the top two of these uses are out of scope for Interop Working Group, the committee has a need to participate in the discussion to ensure consistent and clear use.
  
 
== How to Engage? ==
 
== How to Engage? ==
  
* Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee defcore-committee] list
+
* Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg Interop Working Group] list
* Join #openstack-defcore on Freenode IRC
+
* Join #openstack-interop on Freenode IRC
* Follow the code at https://github.com/openstack/defcore
+
* Follow the code at https://github.com/openstack/interop
* Join our weekly [[Governance/DefCoreCommittee#Meetings|meetings]]
+
* Join our weekly [[Governance/InteropWG#Meetings|meetings]]
* Learn the [https://github.com/openstack/defcore/blob/master/HACKING.rst rules for submitting changes]
+
* Learn the [https://github.com/openstack/interop/blob/master/HACKING.rst rules for submitting changes]
  
 
== Meetings ==
 
== Meetings ==
Meeting times and channels can be found on the [http://eavesdrop.openstack.org/#DefCore_Committee_Meeting official OpenStack IRC meeting list].  An [http://eavesdrop.openstack.org/irc-meetings.ical ICS file] of all OpenStack meetings is also available.  Logs of past meetings [http://eavesdrop.openstack.org/meetings/defcore/ can be found here].
+
Meeting times and channels can be found on the [http://eavesdrop.openstack.org/#Interop_Working_Group_Meeting official OpenStack IRC meeting list].  An [http://eavesdrop.openstack.org/irc-meetings.ical ICS file] of all OpenStack meetings is also available.  Logs of past meetings [http://eavesdrop.openstack.org/meetings/interopwg/ can be found here]. Old meetings [http://eavesdrop.openstack.org/meetings/defcore/ DefCore].
  
 
== Process Cycles ==
 
== Process Cycles ==
  
Defining OpenStack Core is a long term process and we are doing the work in progressive cycles.  For reference, we have named the cycles.  This helps describe concrete deliverables for a cycle while allowing discussion of the broader long term issues.  For example, we may say that "item X is important to DefCore but out of scope for Elephant."  We have found that this approach to breaking down the problem is necessary to maintain community consensus because we are taking smaller bites of the larger challenge (aka eating the elephant).  
+
Defining OpenStack Core is a long term process and we are doing the work in progressive cycles.  For reference, we have named the cycles.  This helps describe concrete deliverables for a cycle while allowing discussion of the broader long term issues.  For example, we may say that "item X is important to Interop Working Group but out of scope for Elephant."  We have found that this approach to breaking down the problem is necessary to maintain community consensus because we are taking smaller bites of the larger challenge (aka eating the elephant).  
  
See [https://github.com/openstack/defcore/blob/master/doc/source/process/ProcessCycles.rst Process Cycles]
+
See [https://github.com/openstack/interop/blob/master/doc/source/process/ProcessCycles.rst Process Cycles]
  
 
The current cycle is named the '''''Scale Cycle'''''.
 
The current cycle is named the '''''Scale Cycle'''''.
Line 57: Line 59:
 
* [http://www.openstack.org/community/members/profile/10331 Chris Hoge] (Foundation staff)
 
* [http://www.openstack.org/community/members/profile/10331 Chris Hoge] (Foundation staff)
  
You can also find information about who is contributing to DefCore [http://stackalytics.com/?release=all&metric=commits&project_type=all&module=defcore here].
+
You can also find information about who is contributing to Interop Working Group [http://stackalytics.com/?release=all&metric=commits&project_type=all&module=defcore here].
  
[[category: defcore]]
+
[[category: InteropWG]]
 
[[Category: Working_Groups]]
 
[[Category: Working_Groups]]

Latest revision as of 21:19, 21 April 2017

This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.

Interop Working Group sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled "OpenStack."

Our mission is to define "OpenStack Core" as chartered by the by-laws.

Important Artifacts

  1. Terms Definition
  2. 10 Core Principles (board approved Hong Kong Summit)
  3. Capability Levels: Component and Platform (board approved October 2014)
  4. 12 Scoring Criteria (board approved Atlanta Summit)
  5. 10 Designed Sections Principles (board approved December 2014)
  6. Interop Working Group Governance:
  7. Interop Working Group Process
  8. Capabilities & Sections
    1. 2015.03 (review JSON for details)
    2. 2015.04 (review JSON for details)
    3. 2015.05 (review JSON for details)
    4. 2015.07 (review JSON for details)
    5. 2016.01 (review JSON for details)
    6. 2016.08 (review JSON for details)
    7. 2017.01 (review JSON for details)
    8. next.json (current draft of next Guideline)

Objective / Scope

The Interop Working Group is around how the OpenStack brand is applied for commercial uses. Initially, this focus is on "what is core" and sustaining that definition over time. The scope will likely expand since brand is an ongoing concern related to specialized marks and other use cases.

There are three ways in which the community uses the OpenStack brand including referring to projects.

  1. General community use of the mark
  2. Project-specific use associated with development activity
  3. Governed commercial use

While the top two of these uses are out of scope for Interop Working Group, the committee has a need to participate in the discussion to ensure consistent and clear use.

How to Engage?

Meetings

Meeting times and channels can be found on the official OpenStack IRC meeting list. An ICS file of all OpenStack meetings is also available. Logs of past meetings can be found here. Old meetings DefCore.

Process Cycles

Defining OpenStack Core is a long term process and we are doing the work in progressive cycles. For reference, we have named the cycles. This helps describe concrete deliverables for a cycle while allowing discussion of the broader long term issues. For example, we may say that "item X is important to Interop Working Group but out of scope for Elephant." We have found that this approach to breaking down the problem is necessary to maintain community consensus because we are taking smaller bites of the larger challenge (aka eating the elephant).

See Process Cycles

The current cycle is named the Scale Cycle.

Current Committee Leaders

Current Leaders:

You can also find information about who is contributing to Interop Working Group here.