Technical Charter (the “Charter”) for Anuket Project a Series of LF Projects, LLC

This charter (the “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 Anuket Project

a. The mission of the Anuket Project is to empower the global communications community by creating and developing reference infrastructure models, architectures, conformance programs and tools to deliver network services faster, more reliably, and securely.
b. The Anuket Project develops open reference models and architectures for cloud infrastructures, tools, and programs. Open source software developed within the project will use OSI-approved licenses, while documentation, including specifications, will use open licenses.
c. 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:

i. Enabling member communities to align on model, architecture and implementation requirements and specifications for cloud-based infrastructure for telecommunication workloads,
ii. Supporting open source and open standards communities in the ecosystem,
iii. 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,
iv. Helping design a conformance framework and validation programs,
v. Contributing to and influencing upstream projects leveraging the reference infrastructure,
vi. Creating new open source components within the reference infrastructure where needed,
vii. Supporting ongoing strategic activities and evaluating emerging technologies to foster continued deployment success.

2. Anuket Project Operations
The Anuket Project Operations and Procedures document (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

3. Technical Steering Committee

a. The Technical Steering Committee (the “TSC”) will be responsible for the technical
oversight of the open source Anuket Project.
b. Responsibilities: The TSC will be responsible for all aspects of oversight relating to
the Anuket Project which include but are not limited to:

i. coordinating the technical direction of the Anuket Project including the
approval the technical scope of the Anuket Assured program
ii. approving the creation, re-organization and closure of sub-projects and
workstreams
iii. approving system proposals (e.g: lab equipment)
iv. creating sub-committees or working groups to focus on cross-project technical
issues and requirements
v. establishing community norms, workflows, issuing releases, and security issue
reporting policies
vi. approving and implementing policies and processes for contributing, outcomes
publications and coordinating with the series manager of the Anuket 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
vii. seeking consensus, and where necessary, voting on technical matters relating
to an artifact that affects multiple sub-projects
viii. coordinating any marketing, events, or communications regarding the Anuket
Project
ix. approving license exceptions under Section 7, and
x. amending the Anuket Project Operations and Procedures document and other
policies and documents of the TSC as per the procedures defined in these
documents.
xi. coordinating with other communities

3.1 TSC Meetings and Decision Making

a. 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.
b. The TSC shall follow the decision-making process specified in Section 3.2.3

c. TSC members can appoint proxies to participate on TSC meeting instead of
them as per the procedures defined in Section 3.3.2.2.
d. Quorum for TSC meetings requires at least half (1/2) of all members of the TSC to be
present. 

i. The TSC may continue to meet if quorum is not met but the TSC may not
make any decisions at the meeting.
ii. The TSC may continue to meet after quorum stops to be met but the TSC may
not make any further decisions at the meeting.
iii. TSC members can appoint proxies to participate on TSC meeting instead of
them as per the procedures defined in Section 3.3.2.2

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

3.2 Technical Steering Committee Operational Procedures
3.2.1 General
The Technical Steering Committee (TSC) shall operate as per the terms and conditions specified by the this Charter.
3.2.2 Operating Model

• The Technical Steering Committee (TSC) is expected to meet regularly to discuss key topical issues.
• The TSC may meet as needed to discuss emerging issues. Issues may be raised for TSC consideration by:

o any TSC member
o any sub-project or workstream lead
o any member of a sub-project or workstream
o others with the prior permission of either of the TSC Co-Chairs

• Transparency. The TSC meetings and all decision making shall be open

3.2.3. TSC Decision Making Process
All decisions shall be made in the TSC meetings, on a public mailing list, or on publicized electronic polling.

a. The intent is for the TSC to find a path to consensus within the TSC and community.
b. TSC meetings shall require a quorum (defined in the Anuket Project Charter) to make any decision. If a TSC meeting fails to meet the quorum requirement, discussions may proceed, however there shall be no voting or decisions made.
c. Decisions by the TSC are made after a review of the opinions, virtual discussions/debate, options identified, consensus sought, and, if necessary, a vote of the TSC members taken.

i. Simple TSC issues may be resolved by a short discussion and simple majority vote of the TSC members in attendance.
ii. TSC discussions associated with simple issues may be over email or at a meeting of the TSC.
iii. TSC decisions at meetings satisfying the quorum requirements shall pass with a majority vote of the TSC members present, except if the decision affects the Anuket Charter or Anuket Project Operations and Procedures clauses that have a different voting criterion specified within the respective documents.
iv. TSC decisions may be made by an electronic vote without a meeting and require a majority vote of all members of the TSC.
v. During an electronic vote, if any two (2) TSC members request a meeting to discuss the decision, the electronic vote in process shall end without effect, and a new vote may be initiated after the meeting to discuss the decision has completed.

d. Major TSC issues may only be resolved at a TSC meeting except that the voting shall be electronically.

i. Major issues are of a fundamental nature or those with wide ranging impact on the community or operation of the Project or operation of the TSC.
ii. Any two (2) TSC members may ask that an issue be classified as a major issue.
iii. The TSC may form a sub-committee to recommend options that may or may not be accepted by the TSC.
iv. Decisions can only be made by a two-thirds (2/3rd) vote of the entire TSC members conducted electronically ten (10) business days after the TSC makes a recommendation.

e. Changes to the Charter are subject to the Charter clauses 7.c and 8.

3.3 TSC Membership and Composition
3.3.1 Anuket Community Membership
Community Member: Any person, regardless of LFN membership, that has joined Anuket or one of the sub-projects or workstreams or teams. Anyone can join the Anuket community by subscribing to one of the Anuket lists https://lists.anuket.io.
Active Community Members: A community member with at least twenty (20) measurable contributions during the previous 12-month period to the Anuket Project or the predecessor OPNFV and CNTT groups. Only active members can vote in an Anuket election and hold positions within the Anuket community. Measurable contributions are Gerrit changes, GitHub pr-s, edits to the Anuket Confluence and other contributions that benefit to the success of the project, like whitepapers and blog posts. Other contributions must be are approved by the TSC and recorded in here:
https://wiki.anuket.io/display/HOME/Other+contributions+that+benefit+to+the+success+of+the+project+approved+by+the+TSC
Participants affiliated with a Company that is a fully- or partially owned by another Company or a group of Related Companies are considered to be affiliated with the same organization (company).
3.3.2 TSC Membership
Only active Anuket community members can be Anuket TSC members.
3.3.2.1. TSC Member Elections
Candidate and Voter Eligibility

• Any Only active community members is are eligible to be a candidate for a TSC seat.
• Only active community members are eligible to vote in a TSC membership election.
• Eligibility is effective as of the date and time the nomination process starts.

TSC Member Candidates

• There are no limitations on the number of candidates that can run for a TSC seat
• There is no limit to the number of candidates from any organisation that can run in a TSC election
• Acceptance of a nomination, or self-nomination (anyone may nominate, anyone may be nominated)

TSC Member Resignation

• If a TSC member is no longer able to perform the TSC duties, the TSC member may inform the TSC via an email to the TSC email list.
• If a TSC member moves companies, that member must notify the TSC via an email to the TSC email list. That TSC member may remain a member unless:

o the move places the member in conflict with the TSC composition rules, or
o the TSC member (at his/her determination) will no longer be able to perform their TSC duties.

Replacement of a TSC member

• In the event of a TSC member resignation:

o an election for the position is held within 30 days of notification to resign. The conditions of the election are the same as for any TSC election.

• If the said position was of that of a TSC co-chair, then the TSC co-chair position will undergo re-election after the successful appointment or election of the new TSC member.
• When the next General TSC election is held, any seat filled by a Replacement of a TSC Member (per above) will also be included in the general TSC election.

TSC Member election mechanics

• The nominations period shall be open for two (2) weeks
• The TSC member elections shall be conducted electronically by LFN staff among the Active Community Members
• The elections are held by using electronic voting tool based on the Condorcet method

TSC Member and Position Holder term

The TSC is elected for an one (1) year term. TSC members elected later (e.g. as a replacement) will end their TSC membership when the term of the TSC ends. The regular term for TSC member or any Position Holder shall begin on the first Sunday of the year and end on the first Saturday of the following year. In case of a vacancy, or an election or appointment during the regular term of the TSC, the term of the member shall begin on the day specified as the start of the term and shall end as of the regular term, viz. the first Saturday of the following year.

3.3.2.2 TSC Member Proxy
TSC members can appoint a proxy for their substitution on TSC meetings

a. In order to maintain the objective that the TSC should consist of active contributors, a
proxy must be an active contributor. An exception may be made if approved by the
TSC.
b. A proxy may only be designated by a TSC member.
c. A TSC member may not be a proxy for another TSC member.
d. A proxy for one TSC member may not also serve as the proxy for another TSC member, concurrently. In addition, proxies may not designate another proxy.
e. The proxy is not subject to the limitations on organizational membership of TSC members, i.e. a proxy may belong to an organization which is already presented by a regular TSC member.
f. A TSC member must notify the TSC of a proxy designation by sending email to the TSC mailing list, or by announcing a proxy in a regular TSC meeting and having the designation recorded in the minutes. The notification shall consist of the full name, proxy duration, email-id and id(s) for the contribution tools used by Anuket Project.
g. A person may not self-nominate, either at a TSC meeting or email, that they are the proxy for a certain TSC member.
h. In general, a proxy should not serve for more than 6 consecutive meetings, unless approved by the TSC. In addition, a TSC member may not designate a proxy for more than 25% of the meetings in a TSC term (typically 1 year), unless approved by the TSC.

3.3.3 TSC Composition
The Anuket TSC shall consist of a minimum of seven (7) and a maximum of fifteen (15) members of which up to half would represent Telco Operators.

• Any changes to the membership shall maintain the 7 to 15 ratio of the minimum number of Telco Operator members to the total number of TSC members.
• Maximum of two members per company/organisation

o If more than two (2) TSC members would be from the same group of Related Companies, either at the time of election or from a later job change or changes to company ownership, they will jointly decide on the two (2) individual to be the TSC members

3.3.4. TSC Co-Chair
The TSC will elect from amongst the TSC members two (2) co-chairs. A TSC co-chair serves
until the end of the TSC-s term, their resignation or replacement by the TSC.
The TSC shall hold elections to elect the TSC Co-Chairs annually, 4 weeks after the TSC
elections or whenever a vacancy occurs. There are no limits on the number of terms a TSC
Co-Chair may serve.

3.3.4.1 TSC Chair Responsibilities
A TSC Co-Chair is responsible for:

• Organising and presiding over TSC meetings
• Serve as the Anuket representative to the Technical Advisory Committee (“TAC”) of
the LF Networking Fund of The Linux Foundation (“LFN”)
• Serve as the primary communication contact between the Project and the LFN
• Provide inputs on Anuket resource requirements to the TAC

3.3.4.2 TSC Co-Chair Candidates

• Candidates for TSC Co-Chair must be TSC Members.
• TSC Co-Chair candidates can be nominated only by TSC Members.
• Nominations must be accepted

3.3.4.3 TSC Co-Chair Election Mechanics

• Only TSC Members are eligible to vote for TSC Co-Chairs.
• The nominations period shall be open for two (2) weeks
• The newly elected or the current TSC members are the "TSC Co-chair Electors" for
annual or vacancy elections respectively
• The TSC Co-chair elections shall be conducted electronically by LFN staff among the
TSC Chair Electors
• At least two-thirds of the TSC Chair Electors are required to have voted for a valid
election
• The TSC Co-chair elections shall be conducted electronically, using the Condorcet method, by LFN staff among the TSC Chair Electors

4. Compliance with Policies
a. This Charter is subject to the Series Agreement for the Anuket Project and the
Operating Agreement of LF Projects. Collaborators 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 Anuket Project, which is
subject to approval by the Series Manager. If an Anuket 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 Anuket Project.
c. When amending or adopting a policy applicable to the Anuket 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.
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 Anuket 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 Anuket Project will operate in a transparent, open, collaborative, and ethical
manner at all times. The output of all Anuket 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 Anuket Project
(“Project Trademarks”), whether based on common law or registered rights.
b. 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.
c. 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.
d. 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 Anuket Project will:
a. 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
b. 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 Anuket Project.
b. Except as described in Section 7.c., all contributions to the Anuket Project are subject
to the following:
i. 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”)
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 code contributors will undertake the obligations set forth in the Anuket
corporate contributors license agreement (CCLA)
(https://wiki.anuket.io/display/HOME/Anuket+ICLA+and+CCLA#AnuketICL
AandCCLA-AnuketCCLA) or the Anuket individual contributors license
agreement (ICLA)
(https://wiki.anuket.io/display/HOME/Anuket+ICLA+and+CCLA#AnuketICL
AandCCLA-AnuketICLA)
iv. All outbound code will be made available under the Anuket Project License.
v. 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/).
vi. 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.
vii. 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.
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 Anuket Project. License exceptions must be
approved by a two-thirds vote of the entire TSC.
d. 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
a. This charter may be amended by a two-thirds vote of the entire TSC and is subject to
approval by LF Projects.
b. The Anuket Project Operations and Procedures document may be amended as
provided in the respective document.