Page History

...

• 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:

...

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 will operateoperates, 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 Project or system sub-project proposals (including, but not limited to incubationcreation, 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 workstreamworkstreams
   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.

...

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 GitHub 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.

...

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 new inbound code contributions must also be accompanied by the Anuket Contributors 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.

...