...
The Anuket Technical Community consists of multiple sub-projects , workstreams and a Technical Steering Committee (TSC) that oversees all sub-projects and workstreams.
2.
...
Sub-project Management
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 or specification (e.g., code, Reference Model or Reference Architectures) 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.
2.1. Project
...
Roles
The success of a project or workstream shall require several active participants drawn for from 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.
2.1.1. Contributor
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).
2.1.2. Reviewers
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:
- Affiliated with three different Anuket member organisations, and
- are note affiliated with the artifact author
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 artifactthe artifact has been review-ed according to the rules of its sub-project.
2.1.3. Committers
Project Committers
For each project, there is a set of Contributors Comitters approved for the right to commit code to the source code management system (the “Committers”) for that project.
- Committer rights are per project; being a Committer on one project does not give an individual committer rights on any other project.
- The Committers will be the decision makers on all matters for a project including design, code, patches, and releases for a project.
- Committers are the best available individuals, but usually work on components in active development.Each project is encouraged to have at least three Committers from different organisations (subject to meritocracy) while preserving meritocracy in the selection of 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.
2.1.3.1. Adding Project Committers
...
- If the PTL or any Committer for that project is a voting member of the Anuket TSC then they shall recuse themselves from voting in the Anuket TSC.
- A simple majority of the Anuket TSC members in attendance, if there is a quorum, is required to overturn the decision of the project’s Committers.
2.1.4. Project Technical Leader
...
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:
- steering the work towards a successful conclusion
- ensuring that the work benefits from a wide spectrum of views
- ensuring a consensus-based approach, as much as is possible, in achieving decision
- organizing and conducting meetings with the objective of furthering the project /workstream objectives
- ensuring quality of deliverables
2.1.4.1. PTL
...
Election Mechanics
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.
- If there is only one candidate for a position, then the person is elected to the position by default.
- To be elected to the position requires a simple majority of the Anuket TSC members (not those voting)
- In case no candidate secures a majority (see clause above),
- if the election was contested by more than two (2) candidates, another vote shall be conducted amongst the two candidates to get the highest number of votes
- if the election was contested by only 2 candidates and after the election none of the two withdraws/concedes in favour of the other candidate, then the TSC shall (i) ask the current PTL /WSL to continue as interim leads for another three (3) months, and (ii) after waiting for 30 days, restart the process starting with the solicitation of candidates.
- In case no candidate secures a majority (see clause above),
An election for Project Technical Leader or Workstream Leader occurs when any of the following are true:
- The project or workstream is initially created or reactivated
- The PTL or WSL resigns
- First week of December
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.
2.1.4.2. PTL
...
Term
- The term for a PTL /WSL shall end on the first Sunday of January.
2.1.4.3. PTL
...
Candidates
Candidates for PTL/WSL:
- may self-nominate or be nominated by any Anuket participant.
- Must demonstrate an advanced level of professional experience in the scope of the project/workstream
- are expected to have demonstrable leadership skills
- must commit that they have the available bandwidth to make the time to invest in the success of the project/workstream
- must operate neutrally in discussions and put the goals and success of project /workstream above any of their employer
2.1.4.4. PTL
...
removal
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:
- is absent without notification to the TSC and the project /workstream for more than 2 weeks
- has been ignoring their responsibilities including not holding a project /workstream meeting for more than 4 weeks
- favours or ignores certain views, opinions, voices, etc.
- is in violation of the LFN Code of Conduct
2.2. Decision Making Process
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:
...