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.
Anuket Project Operations and Procedures
The Anuket Technical Community consists of multiple sub-projects, workstreams and a Technical Steering Committee (TSC) that oversees all sub-projects and workstreams.
The Anuket Project will at any given time consist of a set of sub-projects and workstreams.
A sub-project is created by the Anuket TSC as a development (e.g., code) work item, and has a defined scope beginning, end and resources. In this document, Anuket Project will be used for the LFN project while, hereafter, project, without the qualifier Anuket, will be used to refer to a sub-project.
A workstream (WS) is created around certain defined technical areas where the specified work, related to specifications of models and architectures, is continuous with intermediate deliveries. Workstreams are created for creating of specifications such as in the Reference Model and Reference Architectures.
The success of a project or workstream shall require several active participants drawn for a variety of organisations. Participants can be personnel affiliated with an Anuket member organization or individuals with no such affiliations. Participants can have specific roles on the project/workstream. Except for Contributors and Reviewers, the other roles require that participants be affiliated with an Anuket member organization.
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 organisation.
A Contributor is someone who contributes to a project or workstream (WS). Contributions can take the form of requirements, specifications, code, or other artifacts (collectively hereafter artifacts).
For each project/workstream, Reviewers review, ask for changes and approve the artifacts. Anyone can review, comment and approve the artifacts.
An artifact is considered to have been “Approved” for committing if it has been reviewed and approved by a minimum of 3 (three) reviewers where these 3 (three) reviewers are:
Please note that while unaffiliated participants or participants affiliated with the author’s organization can approve an artifact, their approval doesn’t count towards the three approvals required for committing the artifact.
Project Committers
For each project, there is a set of Contributors approved for the right to commit code to the source code management system (the “Committers”) for that project.
Workstream Committers
Workstream leads (WSL) are the Committer for their workstream. WSLs can commit an approved artifact for their workstream if they are not the author and the author does not belong to their organization. For an approved artifact that cannot be committed by a WSL, either of the Anuket TSC Co-Chairs shall commit that artifact.
The Anuket TSC is responsible for adding Contributors to new or a reactivated moribund project.
A Committer may voluntarily resign from a project by making a request to the project team lead (PTL) to resign (via anuket-tsc@lists.anuket.io mail list).
A Committer for a project who is disruptive or has been inactive on that project for at least six months may have their Committer status revoked by a vote of the project’s committers.
The PTL shall inform the Anuket TSC of any committers who reign or are removed, including the reason for removal, via the anuket-tsc@lists.anuket.io mail list.
A Committer voted to be removed for cause shall have the right to petition the Anuket TSC to reject their removal. In case of such a petition, the Anuket TSC shall vote on accepting or rejecting the removal. The Anuket TSC may invite the PTL and the aggrieved person to oppose/defend the decision.
The project PTL and the workstream WSL are the leaders and de facto spokesperson for the project/workstream. As leaders, PTLs and WSLs are responsible for:
The Anuket TSC shall vote to elect PTLs and WSLs at the time of the creation of a project or workstream, or in the case of a vacancy, or at the end of the PTL/WSL term.
An election for Project Technical Leader or Workstream Leader occurs when any of the following are true:
All members of the Anuket TSC shall be invited to vote in the election of the PTLs/WSLs. The election shall be administered by Anuket staff and the results shall be communicated to the Anuket community.
Candidates for PTL/WSL:
A PTL/WSL can be removed by a 2/3rd vote of all TSC members if the TSC has received reports that the PTL/WSL:
Project/workstream technical and release decisions shall be made by consensus of the Reviewers and Committers of that project/workstream participating in meetings organized for that purpose. If consensus cannot be reached, the issues are escalated for discussion at the Anuket TSC Technical Discussions call. If all fails, the issues are escalated to the Anuket TSC for decision.
The Anuket TSC decided on the bi-annual release dates. Projects and Workstreams shall publish a Release Plan at the beginning of a release cycle. The Release Plan shall have certain common tasks whose duration shall be fixed by the Anuket TSC:
Other elements of the Release Plan may contain the following sections:
Amendments to this Anuket Project Operations and Procedures document can only be made by a majority vote of all TSC members, except that changes to any voting mechanism and requirements shall require a two-thirds (2/3rd) vote of the entire TSC members.