...
The Anuket Project Operations and Procedures document (<link>https://wiki.anuket.io/display/HOME/Anuket+Project+Operations+and+Procedures) specifies how the Anuket Project Community and work teams will be organized and operate. It defines
...
The Anuket Project Technical Steering Committee (TSC) Operations and Procedures document (https://wiki.anuket.io/display/HOME/Anuket+TSC+Operations+and+Procedures) 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
...
- The Technical Steering Committee (the “TSC”) will be responsible for the technical oversight of the open source Anuket Project.
- 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.
- Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Anuket Project which include but are not limited to:
- coordinating the technical direction of the Anuket Project
- approving sub-project proposals (including, but not limited to creation, deprecation, and changes to the scope of a sub-project or workstream)the creation, re-organization and closure of sub-projects and workstreams
- approving system proposals (e.g: lab equipment)
- organizing and removing sub-projects and workstreams
- creating reating sub-committees or working groups to focus on cross-project technical issues and requirements
- appointing representatives to work with other open source or open standards communities
- establishing community norms, workflows, issuing releases, and security issue reporting policies
- approving and implementing policies and processes for contributing, outcomes publications 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
- discussions, seeking consensus, and where necessary, voting on technical matters relating to an artifact that affects multiple sub-projects
- coordinating any marketing, events, or communications regarding the Project
- approving license exceptions under Section 7, and
- 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.
...
1 TSC Meetings and Decision Making
- 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.
- The TSC shall follow the decision-making process specified in Section 1.2 of the Anuket Technical Steering Committee Operations and Procedures document.
- Quorum for TSC meetings requires at least half (1/2) of all members of the TSC to be present.
- The TSC may continue to meet if quorum is not met but the TSC may not make any decisions at the meeting.
- The TSC may continue to meet after quorum stops to be met but the TSC may not make any further decisions at the meeting.
- 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.
...
- 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.
- Except as described in Section 7.c., all contributions to the Anuket Project are subject to the following:
- 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”)
- 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
- all code contributors will undertake the obligations set forth in the Anuket contributor license agreement (CLAthe Anuket corporate contributors license agreement (CCLA) (https://wiki.anuket.io/display/HOME/Anuket+ICLA+and+CCLA#AnuketICLAandCCLA-AnuketCCLA) or the Anuket individual contributors license agreement (ICLA) (https://wiki.anuket.io/display/HOME/Anuket+ICLA+and+CCLA#AnuketICLAandCCLA-AnuketICLA)
- All outbound code will be made available under the Anuket Project License.
- 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/).
- 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.
- 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.
- 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.
- 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.
...