Introduction

This page is created to provide a framework for the modifications of the proposed Anuket Charter. The baseline document was created by Pankaj Goyal based on the XGVela and CNCF and on the comments collected to the current Anuket charter.

Ways of working

• A copy of the proposed documents added to this page
• Please comment the text in the documents using the inline commenting feature of Confluence in a way that the whole text to be replaced is marked for commenting
• Propose a modified text in your comment if possible
• Once there is a consensus on the text to be modified it will be edited to the text

The proposed charter for commenting

Technical Charter (the “Charter”)

for

Anuket Project a Series of LF Projects, LLC

This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the Anuket Project, which has been established as Anuket Project a Series of LF Projects, LLC (the “Anuket 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 Anuket Project (collectively, “Collaborators”) must comply with the terms of this Charter.

1. Mission and Scope of the Project

1. The mission of the Anuket Project is to empower the global communications community by creating and developing reference cloud infrastructure models, architectures, conformance programs and tools to deliver network services faster, more reliably, and securely.
2.  The Anuket Project develops open reference models and architectures for cloud infrastructures, tools, and programs.
3. The scope of the Anuket Project includes collaborative development under the Anuket 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. The scope of the Anuket Project includes but is not limited to:
   1. Enabling member communities to align on model, architecture and implementation requirements and specifications for cloud-based infrastructure for telecommunication workloads,
   2. Supporting open source and open standards communities in the ecosystem,
   3. Developing an integrated, tested, and validated open software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,
   4. Helping design a conformance framework and validation programs,
   5. Contributing to and influencing upstream projects leveraging the reference infrastructure,
   6. Creating new open source components within the reference infrastructure where needed,
   7. Supporting ongoing strategic activities and evaluating emerging technologies to foster continued deployment success.

2. Anuket Project Operations

The Anuket Project Operations and Procedures document (<link>) specifies how the Anuket Project Community and work teams will be organized and operate. It defines

• The structure of the Anuket community
• Sub-project and workstream management including Roles & Responsibilities, and Decision-making process

The Anuket Project Technical Steering Committee (TSC) Operations and Procedures document defines:

• How TSC will operate
• TSC membership and composition including
  • Community membership
  • TSC membership including eligibility and voting procedures
  • Co-Chair election and responsibilities
• TSC Responsibilities subject to this Charter  

3. Technical Steering Committee

1. The Technical Steering Committee (the “TSC”) will be responsible for the technical oversight of the open source Anuket Project.
2. TSC Operations and Procedures (link) specifies the how the TSC operates, its composition, election of its members, responsibilities, etc. The document specifies how amendments to the document can be made by the TSC.
3. Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Anuket Project which include but are not limited to:
   1. coordinating the technical direction of the Anuket Project
   2. approving sub-project proposals (including, but not limited to creation, deprecation, and changes to the scope of a sub-project or workstream)
   3. approving system proposals (e.g: lab equipment)
   4. organizing and removing sub-projects and workstreams
   5. creating sub-committees or working groups to focus on cross-project technical issues and requirements
   6. appointing representatives to work with other open source or open standards communities
   7. establishing community norms, workflows, issuing releases, and security issue reporting policies
   8. approving and implementing policies and processes for contributing 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
   9. discussions, seeking consensus, and where necessary, voting on technical matters relating to an artifact that affects multiple sub-projects
   10. coordinating any marketing, events, or communications regarding the Project
   11. approving license exceptions under Section 7, and
   12. amending the Anuket Project Operations and Procedures and the Technical Steering Committee Operations and Procedures documents and other policies and documents of the TSC as per the procedures defined in these documents.

3. TSC Voting

1. The Anuket Project aims to operate as a consensus-based community, but if a TSC decision requires a vote, the members of the TSC will vote on a one vote per member basis.
2. The TSC shall follow the decision-making process specified in Section 1.2 of the Anuket Technical Steering Committee Operations and Procedures document.
3. Quorum for TSC meetings requires at least half (1/2) of all members of the TSC to be present.
   1. The TSC may continue to meet if quorum is not met but the TSC may not make any decisions at the meeting.
   2. The TSC may continue to meet after quorum stops to be met but the TSC may not make any further decisions at the meeting.
4. In the event a vote by the TSC cannot resolve an issue, any member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution.

4. Compliance with Policies

1. 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/.
2. The TSC may adopt a code of conduct (“CoC”) for the Project, which is subject to approval by the Series Manager. If 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.
3. When amending or adopting a policy applicable to the Project, LF Projects will publish such a 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.
4. 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.
5. The Anuket 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

1. LF Projects will hold title to all trade or service marks used by the Anuket Project (“Project Trademarks”), whether based on common law or registered rights.
2. Anuket Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Anuket Project. Any use of any Anuket Project Trademarks by Collaborators in the Anuket Project will be in accordance with the license from LF Projects and inure to the benefit of LF Projects.
3. The Anuket Project will, as permitted and in accordance with such license from LF Projects, develop and own all Anuket Project tools and social media accounts, and domain name registrations created by the Anuket Project community.
4. Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Anuket 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.

The Project will:

1. engage in the work of the Anuket 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
2. respect the rights of all trademark owners, including any branding and trademark usage guidelines.

7. Intellectual Property Policy

1. 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.
2. Except as described in Section 7.c., all contributions to the Anuket Project are subject to the following:
   1. All new inbound code contributions to the Anuket Project must be made using the Apache License, Version 2.0, available at https://www.apache.org/licenses/LICENSE-2.0 (the “Project License”)
   2. 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
   3. all code contributors will undertake the obligations set forth in the Anuket contributor license agreement (CLA)
   4. All outbound code will be made available under the Anuket Project License.
   5. Documentation will be received and made available by the Anuket Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/).
   6. To the extent a contribution includes or consists of data, any rights in such data shall be made available under the CDLA-Permissive 1.0 License.
   7. The Anuket Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”). In such cases, the Anuket Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Anuket Project. Upstream Project code contributions not stored within the Anuket Project’s main code repository will comply with the contribution process and license terms for the applicable Upstream Project.
3. 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 Anuket Project. License exceptions must be approved by a two-thirds vote of the entire TSC.
4. Contributed files should contain license and copyright information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.

8. Amendments

1. This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects.
2. The Anuket Project Operations and Procedures and the Technical Steering Committee Operations and Procedures documents may be amended as provided in the respective documents.