Jump to: navigation, search

Difference between revisions of "Governance/InteropWG"

(How to Engage?)
Line 37: Line 37:
  
 
* Join #openstack-interop and #refstack on OFTC IRC
 
* Join #openstack-interop and #refstack on OFTC IRC
* Follow the [https://opendev.org/osf/interop Interop code] and associated repositories: [https://opendev.org/osf/refstack Refstack] and [https://opendev.org/osf/refstack-client Refstack-client]
+
* Follow the [https://opendev.org/osf/interop Interop code] and associated repositories: [https://opendev.org/osf/refstack Refstack], [https://opendev.org/osf/refstack-client Refstack-client] and [https://opendev.org/x/ansible-role-refstack-client ansible-role-refstack-client]
 
* Join our weekly [[Governance/InteropWG#Meetings|meetings]]
 
* Join our weekly [[Governance/InteropWG#Meetings|meetings]]
 
* Learn the [https://opendev.org/osf/interop/src/master/HACKING.rst rules for submitting changes]
 
* Learn the [https://opendev.org/osf/interop/src/master/HACKING.rst rules for submitting changes]

Revision as of 08:46, 14 June 2021

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. Draft Interop Working Group Process (current 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

Since April 30 2021, the Interop WG meetings have been held on meetpad on https://meetpad.opendev.org/interop at 4pm UTC every Friday Convert time to your timezone: https://mytime.io/16pm/UTC

If you cannot use Meetpad, you can ping the #openstack-interop channel at 4pm UTC on Friday. Latest meetings notes/minutes are posted on the Etherpad: https://etherpad.opendev.org/p/interop. Agenda is also posted to Etherpad: https://etherpad.opendev.org/p/interop and hashed at the start of the meeting.

Logs of past IRC meetings can be found here. Much Older meetings logs from when the interop group was called "Defcore" are here.

Current Committee Leaders

Current Leaders:

The interop WG is assisted by the "refstack" core group who help maintain various code repositories.