Skip to content
This repository was archived by the owner on Jan 2, 2024. It is now read-only.

charter: Add a section on OCI Projects #2

Closed
wking wants to merge 2 commits into from
Closed

charter: Add a section on OCI Projects #2

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b26ca65
charter: Fix "The OCI shall" formatting for LF rules
wking Aug 6, 2015
ac72ae7
charter: Add a section on OCI Projects
wking Aug 6, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 24 additions & 19 deletions content/charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,15 +22,19 @@ The Open Container Initiative does not seek to be a marketing organization, defi
* ii. identify their company as a member or participant in the OCI;
* iii. vote in all decisions of the OCI Trademark Board.

**3. Trademark Board**
**3. OCI Projects**

The OCI maintains a collection of projects around open containers. For example, specifications, runtime implementations, certification tooling, and certification application are all possible projects.

**4. Trademark Board**

* a. The Trademark Board shall be composed of one representative appointed by each OCI Member. A member may appoint an alternative representative for any meeting.
* b. Trademark Board meetings may be held in-person or via electronic conferencing.
* c. Quorum for holding meetings shall be established when a simple majority of Trademark Board representatives are present.
* d. Voting at meetings shall be based on a one vote per Active Member basis, requiring a simple majority of votes to pass. An Active Member is defined as any Trademark Board member who has participated in at least one of the last four Trademark Board meetings. An alternative representative’s attendance counts as participation for determining whether a member is an Active Member.
* e. At any time a vote may be conducted via email or electronic voting service and pass with a simple majority of OCI Members voting in favor.
* f. The Trademark Board is intended to provide a minimalist governance structure around the development and use of the OCI trademarks and shall only be responsible for:
* i. creating the OCI trademarks associated with OCI Specifications, OCI Projects, the Open Container Format (OCF) or OCI Certified Solution.
* i. creating the OCI trademarks associated with OCI Projects.
* ii. establishing and executing a certification program defining the terms for using any OCI trademark(s) for an OCI Certified Solution;
* iii. approving the use of OCI funds for specific trademark enforcement actions, if any, that may arise;
* iv. approving a budget directing the use of funds raised from all sources of revenue;
Expand All @@ -39,34 +43,34 @@ The Open Container Initiative does not seek to be a marketing organization, defi
* g. Any issues that cannot be resolved by the Trademark Board shall be referred to The Linux Foundation for resolution.
* h. For avoidance of doubt, OCI membership does not convey any rights to directly influence the technical direction of the project. That influence will come through code contribution.

**4. Technical Developer Community (“TDC”)**
**5. Technical Developer Community (“TDC”)**

* a. The OCI has established a technical project for an open source Technical Developer Community. The TDC shall be open to any developer, end user or subject matter expert that chooses to participate in the activities of OCI, regardless of whether the participant is employed by an OCI Member company.
* b. The TDC has an established scope of work focused on:
* i. Creating and maintaining formal specifications (“OCI Specifications”) for container image formats and runtime, which will allow a compliant container to be portable across all major, compliant operating systems and platforms without artificial technical barriers;
* ii. Ensuring OCI Specifications incorporate and align to the OCI Values;
* iii. Accepting, maintaining and advancing the projects associated with the OCI Specifications (“OCI Projects”), which shall initially be the container runtime (runc);
* ii. Ensuring OCI Projects incorporate and align to the OCI Values;
* iii. Accepting, maintaining and advancing OCI Projects;
* 1. The TDC will look to agree on a standard set of container actions (e.g. start, exec, pause) as well as runtime environment associated with the container runtime;
* iv. Creating and maintaining test cases that shall serve as the testing functions for achieving certification as an OCI Certified Solution.
* v. Engaging end users for feedback or input on OCI Projects, including, but not limited to, usability;
* vi. Ensuring all OCI Specification and OCI Projects follow and adhere to the OCI IP Policy;
* vii. Approving releases of OCI Specifications or OCI Projects;
* vi. Ensuring all OCI Projects follow and adhere to the OCI IP Policy;
* vii. Approving releases of OCI Projects;
* viii. Creating, maintaining and following governance guidelines for the TDC, including:
* 1. the establishment of roles (e.g. Maintainer, Contributor) and each role’s responsibilities,
* 2. the process or requirements to take on a role in the TDC (e.g. how to become a Contributor, or how to become a Maintainer),
* 3. the process by which participants in the TDC may give up or be revoked of their roles (e.g. how to remove Maintainers);
* 4. the rules for decision making in the TDC; and
* 5. any workflow or processes participants are expected to follow in making or merging contributions.
* ix. Attempting to harmonize the OCI Specifications with other proposed standards, including, but not limited to, the appc specification;
* x. Ensuring that the scope of technologies promulgated and proposed as standard elements of OCI Specifications of OCI Projects are those that are sufficiently widespread and sufficiently mature and stable so as to warrant establishment as a standard;
* xi. Referring any issues to the Technical Oversight Board that deal with failure to follow established technical governance, impact multiple OCI Projects or Specifications, or conflicts that cannot be resolved within the TDC.
* x. Ensuring that the scope of technologies promulgated and proposed as standard elements of OCI Projects are those that are sufficiently widespread and sufficiently mature and stable so as to warrant establishment as a standard;
* xi. Referring any issues to the Technical Oversight Board that deal with failure to follow established technical governance, impact multiple OCI Projects, or conflicts that cannot be resolved within the TDC.
* c. The maintainers and contributors shall set the technical direction of the OCI Projects, with minimal interference by the Technical Oversight Board.
* d. The TDC will only accept influence through contribution. The primary means for any organization to influence the technical direction of the OCI Projects is via contribution or service as maintainers. OCI Members specifically disclaim any right to influence technical direction either on the basis of their financial contributions or their existence as OCI Members.
* e. The initial leadership of the TDC shall be Michael Crosby (chief maintainer, Docker, @crosbymichael), Rohit Jnagal (google,@rgnagal), Victor Marmol (google, @vmarmol), Mrunal Patel (redhat, @mrunalp), Alexandr Morozov (docker, @LK4D4), Daniel Minh (@dqminh), Tianon Gravi (@tianon), Vincent Batts (redhat, @vbatts), Brandon Philipps (CoreOS, @philips)

**5. Technical Oversight Board (TOB)**
**6. Technical Oversight Board (TOB)**

* a. The TOB is responsible for managing conflicts and any cross-project or high-level issues that cannot be resolved in the TDC for OCI Specifications or OCI Projects.
* a. The TOB is responsible for managing conflicts and any cross-project or high-level issues that cannot be resolved in the TDC for OCI Projects.
* b. The TOB shall be composed of individuals elected for their expertise and contribution to the advancement of container technologies. Anyone may be elected to the TOB, regardless of whether the individual is an OCI Member or OCI TDC participant. It is intended that TOB members shall be technical experts that are considered thought leaders in the ecosystem. An elected TOB member is elected as an individual and not as a representative of their employer. TOB members may not designate alternative representatives.
* c. TOB members shall be split into two groups, serving for a term of two years on a staggered basis, where one group is elected each year. The initial TOB will have four (4) TOB members who will only serve for a term of one year and three TOB members that serve for a term of two years.
* d. The initial TOB shall be established through a nomination and election process. The first group of four (4) TOB members shall be nominated and elected by the current TDC maintainers and serve for a period of one (1) year. The second group of three (3) TOB members shall be nominated and elected by the OCI Members and serve for a period of two (2) years.
Expand All @@ -78,37 +82,38 @@ The Open Container Initiative does not seek to be a marketing organization, defi
* j. At any time a vote may be conducted via email or electronic voting service and pass with a simple majority of all TOB members voting in favor.
* k. Any issues that cannot be resolved by the TOB shall be referred to The Linux Foundation Executive Director for resolution with The Linux Foundation Board of Directors.

**6. OCI Values. The TDC and TOB shall reflect and adhere to the following values for OCI Specifications and OCI Projects:**
**7. OCI Values. The TDC and TOB shall reflect and adhere to the following values for OCI Projects:**

* a. Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable. A container runtime should not be bound to clients, to higher-level frameworks, etc.
* b. Portable. The runtime standard should be usable across different hardware, operating systems, and cloud environments.
* c. Secure. Isolation should be pluggable, and the cryptographic primitives for strong trust, image auditing and application identity should be solid
* d. Decentralized. Discovery of container images should be simple and facilitate a federated namespace and distributed retrieval.
* e. Open. The format and runtime should be well-specified and developed by a community. OCI encourages independent implementations of tools to be able to run the same container consistently. Within the OCI community, code development leads specification development, rather than vice-versa. The OCI community seeks rough consensus and running code.
* f. Minimalist. The OCI Specifications should aim to do a few things well, be minimal and stable, and enable innovation and experimentation above and around it.
* g. Backward compatible. OCI Specifications and OCI Projects should strive to be as backward compatible as possible with the prior releases of the OCI Specification and OCI Project (“runc”).
* f. Minimalist. The OCI Projects should aim to do a few things well, be minimal and stable, and enable innovation and experimentation above and around it.
* g. Backward compatible. OCI Projects should strive to be as backward compatible as possible with the prior releases of OCI Projects.

**7. OCI IP Policy.**
**8. OCI IP Policy.**

* a. All new inbound code contributions to OCI shall be made under the Apache License, Version 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0) accompanied by a Developer Certificate of Origin sign-off (http://developercertificate.org);
* b. All outbound code will be made available under the Apache License, Version 2.0.
* c. All documentation will be received and made available by OCI under the Creative Commons Attribution 4.0 International License.
* d. If an alternative inbound or outbound license is required for compliance with the license for a leveraged open source project or is otherwise required to achieve OCI’s mission, the TOB may approve the use of an alternative license for inbound or outbound contributions on an exception basis. Please email [email address] to obtain exception approval.

**8. Antitrust Guidelines**
**9. Antitrust Guidelines**

* a. All members shall abide by The Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy.
* b. All members shall encourage open participation from any organization able to meet the membership requirements, regardless of competitive interests. Put another way, the OCI shall not seek to exclude OCI membership based on any criteria, requirements or reasons other than those established as required of all members.

**9. Budget**
**10. Budget**

* a. The Trademark Board shall approve an annual budget and never commit to spend in excess of funds raised. The budget shall be consistent with the non-profit mission of The Linux Foundation.
* b. The OCI Budget shall include funds for a part-time program manager, or at the OCI’s discretion, an Executive Director, to assist OCI with project management, organizing meetings and assisting in driving initiatives of the Trademark Board, TDC or TOB.
* c. The Linux Foundation shall provide regular reports of spend levels against the budget.
* d. The Linux Foundation shall have custody of and final authority over the usage of any fees, funds and other cash receipts.

**10. Linux Foundation General Rules and Operations.
The OCI shall:**
**11. Linux Foundation General Rules and Operations.

The OCI shall:

* a. demonstrate plans and the means to coordinate with the open source project’s developer community, including on topics such as branding, logos, and other collateral that will represent the community;
* b. engage in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of The Linux Foundation in the open source software community;
Expand Down