The document was accepted in the 2021-11-02 TSC meeting. The document was moved to Anuket Project Operations and Procedures .
Overview
Content Tools
The document was accepted in the 2021-11-02 TSC meeting. The document was moved to Anuket Project Operations and Procedures .
9 Comments
Beth Cohen
I have a couple of comments. I think it is VERY important to pin down our definition of committers here. It should be a broader definition than is stated to include people who contribute to the overall project, not just code. Another point we should dig into is how sub projects are started, who gets to start them and their overall lifecycle. The reality is that projects usually have a sponsor – individual or organization that is willing to contribute resources – in whatever form that takes – to the work. It is up to the TSC to determine if that proposal/project fits into the Anuket charter. Does that belong in this document, or in the TSC doc?
Should we include language about how and when a project should be retired? There are many zombie projects out there.
Except for Contributors and Reviewers, the other roles require that participants be affiliated with an Anuket member organization. – What does this mean?
Gergely Csatari AUTHOR
We have a definition of contributors in 2.1.1 with the definition of contribution " Contributions can take the form of requirements, specifications, code, or other artifacts ". Beth Cohen do you think that this is a) not broad enough or b) does not include specification work?
The proposed Charter-s 3.3.b and 3.3.c points define that it is the TSC-s responsibility to approve and remove sub-projects and point 2.1.3.1 of this document defines that the TSC should add committers. Do you think that we need to request resources from the ones who propose the projects?
Can you add your comments as inline comments to the relevant places of the document? It is more easy to review them like that.
Pankaj Goyal
Rewrite of 2.1.4.1
2.1.4.1. PTL/WSL Election Procedures
General -- PTL/WSL Election:
In case of a vacancy for a PTL/WSL position or 30-days prior to the end of the term of the current position holder:
An invitation to the project/workstream active membership shall be sent for nominations.
A candidate maybe nominated or may self-nominate.
The election shall be administered electronically by Anuket staff and the results shall be communicated to the Anuket TSC for ratification. The TSC ratification shall be pro-forma exercise.
Eligible Voting Members:
The eligible voting members shall be:
Interim PTL/WSL Appointment
In the case where an election of the eligible voters ends up in a tie then the TSC shall appoint an Interim PTL/WSL until new elections can be held:
(i) ask the current PTL/WSL to continue as interim lead for a period of three (3) months, or
(ii) if (i) is not feasible then elect one of the TSC members to be the interim PTL/WSL
PTL/WSL Appointment
The Anuket TSC shall vote to elect PTL/WSL at the time of the creation of a project/workstream, or at time of reactivation of a moribund project/workstream. The TSC shall also vote to elect an interim PTL/WSL in the case where the project/workstream active contributors are unable to elect a PTL/WSL.
An election for Project Technical Leader or Workstream Leader shall occur when any of the following are true:
Gergely Csatari AUTHOR
In case you have any comments to the proposal from Pankaj to chapter 2.1.4.1 please add it to the comment 14 of 18.
Al Morton
Hi Gergely Csatari ,
We have "sub-project deletion" on the agenda for the Technical Discussion on .
I believe what we need is a complete section on Sub-Project Life-cycle, including creation, archiving (replaces deletion), and reactivation.
Please allow me to suggest some text for this purpose as a starting point for Anuket discussions. It might save us some time.
Pankaj Goyal
Al,
the write-up works for non-specification projects but not the specification projects. Actually in the description ("development of upstream code, integration of platform components, support functions to create and maintain the infrastructure and the development and maintenance of the toolchains we use.").
Gergely Csatari AUTHOR
We incorporated the original text in the meanwhile and adopted it to Anuket. Please check section 2.3.
Gergely Csatari AUTHOR
Meeting notes :
Beth Cohen
Make a recommendation that there be a minimum of 3 contributors, rather than up to 3. Those are very different statements.