Per [0] OVN has been a Linux Foundation Collaborative Project since November 4th, 2019. The OVN charter is linked in the same email thread [1]. For better visibility also add it to the OVN repository.
NOTE: The charter.rst file now contains the exact text copied from the linked OVN charter [1] with the exception of the '"MAINTAINERS" file' and 'committer-grant-revocation.rst' references that have been changed to link to the actual MAINTAINERS.rst and committer-grant-revocation.rst files in the repository. [0] https://mail.openvswitch.org/pipermail/ovs-discuss/2020-January/049702.html [1] https://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20200116/c648d433/attachment-0001.pdf Signed-off-by: Dumitru Ceara <[email protected]> --- Documentation/automake.mk | 1 + Documentation/index.rst | 3 +- Documentation/internals/charter.rst | 253 ++++++++++++++++++++++++++++ Documentation/internals/index.rst | 1 + 4 files changed, 257 insertions(+), 1 deletion(-) create mode 100644 Documentation/internals/charter.rst diff --git a/Documentation/automake.mk b/Documentation/automake.mk index 5f7500fb76..a70c294b95 100644 --- a/Documentation/automake.mk +++ b/Documentation/automake.mk @@ -44,6 +44,7 @@ DOC_SOURCE = \ Documentation/internals/index.rst \ Documentation/internals/authors.rst \ Documentation/internals/bugs.rst \ + Documentation/internals/charter.rst \ Documentation/internals/committer-emeritus-status.rst \ Documentation/internals/committer-grant-revocation.rst \ Documentation/internals/committer-responsibilities.rst \ diff --git a/Documentation/index.rst b/Documentation/index.rst index 9fb298c283..36fabb2cca 100644 --- a/Documentation/index.rst +++ b/Documentation/index.rst @@ -84,7 +84,8 @@ Learn more about the Open Virtual Network (OVN) project and about how you can co :doc:`internals/contributing/inclusive-language` | :doc:`internals/contributing/coding-style` -- **Maintaining:** :doc:`internals/maintainers` | +- **Maintaining:** :doc:`internals/charter` | + :doc:`internals/maintainers` | :doc:`internals/committer-responsibilities` | :doc:`internals/committer-grant-revocation` | :doc:`internals/committer-emeritus-status` diff --git a/Documentation/internals/charter.rst b/Documentation/internals/charter.rst new file mode 100644 index 0000000000..f7484f2a34 --- /dev/null +++ b/Documentation/internals/charter.rst @@ -0,0 +1,253 @@ +The Linux Foundation Open Virtual Network Charter +================================================= + +Effective November 4, 2019 + +This Charter sets forth the responsibilities and procedures for +technical contribution to, and oversight of, the Open Virtual Network +("OVN") open collaboration project, which has been established as OVN +a Series of LF Projects, LLC (the "Project"). LF Projects, LLC +("LF Projects") is a Delaware series limited liability company. All +contributors (including committers, maintainers, and other technical +positions) and other participants in the Project (collectively, +"Collaborators") must comply with the terms of this Charter. + +1. Mission and Scope of the Project + + a. The mission of the Project is to develop an open source system to + support native virtual network abstractions, such as virtual L2 + and L3 overlays and security groups for production-quality + implementations that can operate at significant scale. + + b. The scope of the Project includes collaborative development under + the Project License (as defined herein) supporting the mission, + including documentation, testing, integration and the creation of + other artifacts that aid the development, deployment, operation or + adoption of the open source project. + +2. Technical Steering Committee ("TSC") + + a. The Technical Steering Committee (the "TSC") will be responsible + for all technical oversight of the open source Project. + + b. The TSC voting members are initially the Project's Committers. + At the inception of the project, the Committers of the Project + will be as set forth within the :doc:`/internals/maintainers` file + within the Project's code repository. The TSC may choose an + alternative approach for determining the voting members of the + TSC, and any such alternative approach will be documented in the + CONTRIBUTING file. Any meetings of the Technical Steering + Committee are intended to be open to the public, and can be + conducted electronically, via teleconference, or in person. + + c. TSC projects generally will involve Contributors and Committers. + The TSC may adopt or modify roles so long as the roles are + documented in the CONTRIBUTING file and other files that it + references. Unless otherwise documented: + + i. Contributors include anyone in the technical community that + contributes code, documentation, or other technical artifacts + to the Project; + + ii. Committers are Contributors who have earned the ability to + modify ("commit") source code, documentation or other + technical artifacts in a project's repository; and + + iii. A Contributor may become a Committer following the guidelines + set out by the TSC, currently available at + :doc:`/internals/committer-grant-revocation`. + A Committer may be removed per the same guidelines + provided by the TSC. + + d. Participation in the Project through becoming a Contributor and + Committer is open to anyone so long as they abide by the terms of + this Charter. + + e. The TSC may (1) establish work flow procedures for the submission, + approval, and closure/archiving of projects, (2) set requirements + for the promotion of Contributors to Committer status, as + applicable, and (3) amend, adjust, refine and/or eliminate the + roles of Contributors, and Committers, and create new roles, + and publicly document any TSC roles, as it sees fit. + + f. The TSC may elect a TSC Chair, who will preside over meetings of + the TSC and will serve until their resignation or replacement by + the TSC. + + g. Responsibilities: The TSC will be responsible for all aspects of + oversight relating to the Project, which may include: + + i. coordinating the technical direction of the Project; + + ii. approving project or system proposals (including, but not + limited to, incubation, deprecation, and changes to a + sub-project's scope); + + iii. organizing sub-projects and removing sub-projects; + + iv. creating sub-committees or working groups to focus on + cross-project technical issues and requirements; + + v. appointing representatives to work with other open source or + open standards communities; + + vi. establishing community norms, workflows, issuing releases, + and security issue reporting policies; + + vii. approving and implementing policies and processes for + contributing (to be published in the CONTRIBUTING file) and + coordinating with the series manager of the Project (as + provided for in the Series Agreement, the "Series Manager") + to resolve matters or concerns that may arise as set + forth in Section 7 of this Charter; + + viii. discussions, seeking consensus, and where necessary, voting + on technical matters relating to the code base that affect + multiple projects; and + + ix. coordinating any marketing, events, or communications + regarding the Project. + +3. TSC Voting + + a. While the Project aims to operate as a consensus-based community, + if any TSC decision requires a vote to move the Project forward, + the voting members of the TSC will vote on a one vote per voting + member basis. + + b. Quorum for TSC meetings requires at least fifty percent of all + voting members of the TSC to be present. The TSC may continue to + meet if quorum is not met but will be prevented from making any + decisions at the meeting. + + c. Except as provided in Section 7.c. and 8.a, decisions by vote at + a meeting require a majority vote of those in attendance, + provided quorum is met. Decisions made by electronic vote without + a meeting require a majority vote of all voting members of the + TSC. + + d. In the event a vote cannot be resolved by the TSC, any voting + member of the TSC may refer the matter to the Series Manager for + assistance in reaching a resolution. + +4. Compliance with Policies + + a. This Charter is subject to the Series Agreement for the Project + and the Operating Agreement of LF Projects. Contributors will + comply with the policies of LF Projects as may be adopted and + amended by LF Projects, including, without limitation the policies + listed at https://lfprojects.org/policies/. + + b. The TSC may adopt a code of conduct ("CoC") for the Project, which + is subject to approval by the Series Manager. In the event that a + Project-specific CoC has not been approved, the LF Projects Code + of Conduct listed at https://lfprojects.org/policies will apply + for all Collaborators in the Project. + + c. When amending or adopting any policy applicable to the Project, + LF Projects will publish such policy, as to be amended or adopted, + on its web site at least 30 days prior to such policy taking + effect; provided, however, that in the case of any amendment of + the Trademark Policy or Terms of Use of LF Projects, any such + amendment is effective upon publication on LF Project's web site. + + d. All Collaborators must allow open participation from any + individual or organization meeting the requirements for contributing + under this Charter and any policies adopted for all Collaborators by + the TSC, regardless of competitive interests. Put another way, the + Project community must not seek to exclude any participant based on + any criteria, requirement, or reason other than those that are + reasonable and applied on a non-discriminatory basis to all + Collaborators in the Project community. + + e. The Project will operate in a transparent, open, collaborative, + and ethical manner at all times. The output of all Project + discussions, proposals, timelines, decisions, and status should + be made open and easily visible to all. Any potential violations + of this requirement should be reported immediately to the Series + Manager. + +5. Community Assets + + a. LF Projects will hold title to all trade or service marks used by + the Project ("Project Trademarks"), whether based on common law + or registered rights. Project Trademarks will be transferred and + assigned to LF Projects to hold on behalf of the Project. Any use + of any Project Trademarks by Collaborators in the Project will be + in accordance with the license from LF Projects and inure to the + benefit of LF Projects. + + b. The Project will, as permitted and in accordance with such license + from LF Projects, develop and own all Project GitHub and social + media accounts, and domain name registrations created by the + Project community. + + c. Under no circumstances will LF Projects be expected or required to + undertake any action on behalf of the Project that is inconsistent + with the tax-exempt status or purpose, as applicable, of LFP, Inc. + or LF Projects, LLC. + +6. General Rules and Operations. + + a. The Project will: + + i. engage in the work of the Project in a professional manner + consistent with maintaining a cohesive community, while also + maintaining the goodwill and esteem of LF Projects, LFP, Inc. + and other partner organizations in the open source community; + and + + ii. respect the rights of all trademark owners, including any + branding and trademark usage guidelines. + +7. Intellectual Property Policy + + a. Collaborators acknowledge that the copyright in all new + contributions will be retained by the copyright holder as + independent works of authorship and that no contributor or + copyright holder will be required to assign copyrights to the + Project. + + b. Except as described in Section 7.c., all contributions to the + Project are subject to the following: + + i. All new inbound code contributions to the Project must be made + using the Apache License, Version 2.0, available at + https://www.apache.org/licenses/LICENSE-2.0 (the "Project + License"). + + ii. All new inbound code contributions must also be accompanied + by a Developer Certificate of Origin + (http://developercertificate.org) sign-off in the source code + system that is submitted through a TSC-approved contribution + process which will bind the authorized contributor and, if not + self-employed, their employer to the applicable license; + + iii. All outbound code will be made available under the Project + License. + + iv. The Project may seek to integrate and contribute back to other + open source projects ("Upstream Projects"). In such cases, the + Project will conform to all license requirements of the + Upstream Projects, including dependencies, leveraged by the + Project. Upstream Project code contributions not stored + within the Project's main code repository will comply with the + contribution process and license terms for the applicable + Upstream Project. + + c. The TSC may approve the use of an alternative license or licenses + for inbound or outbound contributions on an exception basis. To + request an exception, please describe the contribution, the + alternative open source license(s), and the justification for + using an alternative open source license for the Project. License + exceptions must be approved by a two-thirds vote of the entire + TSC. + + d. Contributed files should contain license information, such as + SPDX short form identifiers, indicating the open source license or + licenses pertaining to the file. + +8. Amendments + + a. This charter may be amended by a two-thirds vote of the entire TSC + and is subject to approval by LF Projects. diff --git a/Documentation/internals/index.rst b/Documentation/internals/index.rst index 446b35e3db..edbeaddfc7 100644 --- a/Documentation/internals/index.rst +++ b/Documentation/internals/index.rst @@ -39,6 +39,7 @@ itself and how they might involved. release-process bugs security + charter committer-emeritus-status committer-responsibilities committer-grant-revocation -- 2.45.2 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
