Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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 current Anuket TSC Operational Guidelines document.

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 document for commenting

1.   Technical Steering Committee Operational Procedures

1.1 General

The Technical Steering Committee (TSC) shall operate as per the terms and conditions specified by the Anuket Project Charter (https://wiki.anuket.io/display/HOME/Anuket+Charter). In case of any conflict between the procedures specified in the current document and the Charter, the Charter shall prevail.

The Definitions of the terms used here are as per the Charter.

1.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:
    • any TSC member
    • any sub-project or workstream lead
    • any member of a sub-project or workstream
    • others with the prior permission of either of the TSC Co-Chairs
  • Transparency. The TSC meetings and all decision making shall be open
  • Quorum. A majority of TSC members need to be present for a TSC meeting to make decisions. If at any time a quorum ceases to exist, then no decisions can be made past that time.

1.3. TSC Decision Making Process

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

  1. The intent is for the TSC to find a path to consensus within the TSC and community.
  2. 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.
  3. Decisions by the TSC are made after a review of the opinions, optional virtual discussion/debate options are identified, consensus sought, and, if necessary, a vote of the TSC members taken.
  4. TSC member's can madate a proxy to participate on TSC meetings instead of them
    1. In order to maintain the objective that the TSC should consist of active contributors, a proxy must be an active contributor, as identified in the last annual community election. An exception may be made if approved by the TSC.

    2. A proxy may only be designated by an active TSC member.  Also, a proxy is only valid as long as the TSC member that appointed the proxy remains on the TSC. In addition, proxies may not designate another proxy.

    3. A TSC member may not be a proxy for another TSC member, unless approved by the TSC.
    4. A proxy for one TSC member may not also serve as the proxy for another TSC member, concurrently.
    5. 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. A proxy may not "self-announce". That is, attend the TSC meeting and announce that they are the proxy for a TSC member, with no previous notification from the TSC member.
    6. 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 (typ 1 year), unless approved by the TSC. If a TSC member anticipates being unavailable for longer than that, then they should offer to step down. An exception may be made by approval of the TSC.
  5. Simple TSC issues may be resolved by a short discussion and simple majority vote of the TSC members in attendance.
    1. TSC discussions associated with simple issues may be over email or at a meeting of the TSC.
    2. 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, Anuket Technical Steering Committee Operations and Procedures or Anuket Project Operations and Procedures clauses that have a different voting criterion specified within the respective documents.
    3. TSC decisions may be made by an electronic vote without a meeting require a majority vote of all members of the TSC.
    4. 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.
  6. Major TSC issues may only be resolved at a TSC meeting except that the voting shall be electronically.
    1. 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.
    2. Any two (2) TSC members may ask that an issue be classified as a major issue.
    3. The TSC may form a sub-committee to recommend options that may or may not be accepted by the TSC.
    4. 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.
  7. Changes to the Charter are subject to the Charter clauses 7.c and 8.

2. TSC Membership and Composition

2.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: <add_link>

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

2.2.     TSC Membership

Only active community members can be Anuket TSC members. Only TSC members can vote on TSC decisions, electing TSC co-chairs, sub-project leads, workstream leads, and sub-project committers.

2.2.1.TSC Member Elections

Candidate and Voter Eligibility

  • Any active community member is eligible to be a candidate for a TSC seat.
  • Only active community members are eligible to vote in a TSC membership election.
  • Only one (1) active community member from any organisation can vote in any election. Where a company/organisation has multiple active members, then these members shall meet and decide who amongst them shall be eligible to vote and communicate the decision to the person in charge of conducting the 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 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:
    • the move places the member in conflict with the TSC composition rules, or
    • 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:
    • 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.

2.3.     TSC Composition

The Anuket TSC shall consist of fifteen (15) members of which at least seven (7) will 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.
  • Only one (1) member per company/organisation
    • 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 one (1) individual to be the member

2.4.     TSC Chair

The TSC will elect from amongst the TSC voting members two (2) co-chairs, each for a term of one (1) year according to the Anuket Technical Charter. A TSC co-chair serves until their resignation or replacement by the TSC.

The TSC shall hold elections to elect the TSC Co-Chairs annually or whenever a vacancy occurs. There are no limits on the number of terms a TSC Co-Chair may serve.

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

2.4.2.TSC Chair Candidates

  • Candidates for TSC Co-Chair must be TSC Members.
  • Acceptance of a nomination, or self-nomination (anyone may nominate, anyone may be nominated)

2.4.3.TSC Chair Election Mechanics

  • Only TSC Members are eligible to vote for TSC Co-Chairs. Responsibilities of the TSC.

3.   TSC Responsibilities

Subject to the Technical Charter, the TSC is responsible for:

  • Defining Anuket release vehicles (such as a Coordinated Release) that align with the Project’s mission,
  • Fostering cross-project collaboration,
  • Serving as Anukets’s primary technical liaison body with other consortiums and groups,
  • Developing an architecture,
  • Setting simultaneous release dates,
  • Defining release quality standards,
  • Defining technical best practices and community norms (including the establishment and maintenance of a Development Process),
  • Monitoring technical progress,
  • Mediating technical conflicts between Committers and PTLs,
  • Organizing inter-project collaboration,
  • Coordinating technical community engagement with the end-user community.

4.   Amendments

Amendments to this Anuket TSC Operations and Procedures document can only be made by a two-thirds (2/3rd) vote of the entire TSC members.







  • No labels