Please consider defining what a "maintainer" is, perhaps using a different word, and document any cap on the number.
Maintainers usually reply within 1 day
@rarjun7777 is already working on this.
Since Aug 31, 2023.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Read maintainers-election-policy.md alongside the linked TAG Contributor Strategy Maintainer Circle documentation, then compare the role definitions in Istio's ROLES.md and the maintainers CSV process described in the issue. Clarify the intended meaning of “maintainer,” whether a different CNCF role name is needed, and whether a listing or voting cap applies; done means the policy and process are unambiguous.
Written by the indexing model from the issue text.
Description
As part of onboarding Istio into the CNCF, we were asked to list our maintainers. I mentioned we have 87, and sought clarity if I should add them all; @amye said "no", and @dims commented to say
LOL no to 87 :)
As projects and communities evolve, there is inevitable drift between intentions and realities. I'm always keen to use moments like this as an opportunity to make sure that tribal knowledge can be written down for the benefit of everyone to come.
I take from the maintainer election policy the intention that all maintainers of all CNCF projects all get to vote for GB and TOC seats.
Looking at TAG Contributor Strategy's Maintainer Circle documentation points out the differing meanings of the word. It further states:
"CNCF has a pool of listed maintainers for each project that vote on behalf of their project in TOC elections"
This suggests that not all project maintainers are necessarily "part of the pool of listed maintainers".
Istio is an "old" (mature?) and "large" project; it's not of the scale of Kubernetes, of course, but I imagine it's going to be in the top 5 by most metrics. At the time of writing, we have 87 maintainers, defined here as people who have earned approval access to a part of the project, and have earned voting rights within the working groups.
We've been told that this is too many people to list on https://maintainers.cncf.io/, or to put it another way, grant voting rights to.
By comparison, gRPC has 49 maintainers listed in this file, and Cilium has 42. Given the large community of developers and breadth of companies that contribute to Istio, it's fair to assume that ratio of maintainers between Istio and those projects is roughly accurate. (I would assume that these projects all use "maintainer" in a similar fashion to how Kubernetes uses "owner". )
Conversely, there are only 17 people listed on behalf of Kubernetes on https://maintainers.cncf.io/, with 10 of them listed as non-voting. There are many sandbox projects that have a higher number of maintainers listed, and if I have this right, a higher influence on voting for the TOC seat? (This is less relevant for the GB seats, one of which I understand is chosen by the Kubernetes steering committee, the other from the maintainers of all other projects.)
It would be useful to understand the intention of this policy before we proceed with adding some or all of our maintainers. Some things that might make it more clear, depending on the intention:
- using a different word for the CNCF role: it sounds like you're asking for a number of "project liaisons" or "leads"?
- capping the number in some fashion: assuming the intention is treat all projects like US states
(I'm going to give Amye the e-mail addresses of a few project leads to proceed with the transition, and await clarification here before updating the CSV.)
- Dominant language
- Rich Text Format
- Stars
- 696
- Forks
- 869
- Avg merge
- 12h 6m
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cncf/foundation
-
code-of-conduct.md: version number is not bumped up since v1.3 (2023-06-09)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cncf/foundation#1109 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cncf/foundation#1552 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cncf/foundation#1542 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
cncf/foundation#1541 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cncf/foundation#1539 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
uniswap-python/uniswap-python#487 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
area: server enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
scs0209/laya-guard#52 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days