ref: #1330 (comment)
The additional role makes the contributor ladder more complicated. It's also just as much if not more effort to administer the role, and more difficult to audit across repos and orgs.
The only real benefit the additional role adds is constraining people's ability to use certain commands to specific repos instead of all repos in the org they're a member of (eg: /lgtm, /close, /assign).
When discussed during a sig-contribex meeting, there was agreement on simplifying and cutting the role. Unfortunately, this agreement didn't land in meeting notes, and I haven't seen the video recording hit youtube yet.
I think we could benefit from a survey of where and how extensively the role is used today across kubernetes/* and kubernetes-incubator/* repos. This is something only people with... write? admin? access to said repos can do. But IMO anyone is free to tackle modifying community-membership.md and I'm happy to review PR's to that effect.
FYI @kubernetes/sig-contributor-experience-proposals
ref: #1330 (comment)
The additional role makes the contributor ladder more complicated. It's also just as much if not more effort to administer the role, and more difficult to audit across repos and orgs.
The only real benefit the additional role adds is constraining people's ability to use certain commands to specific repos instead of all repos in the org they're a member of (eg: /lgtm, /close, /assign).
When discussed during a sig-contribex meeting, there was agreement on simplifying and cutting the role. Unfortunately, this agreement didn't land in meeting notes, and I haven't seen the video recording hit youtube yet.
I think we could benefit from a survey of where and how extensively the role is used today across kubernetes/* and kubernetes-incubator/* repos. This is something only people with... write? admin? access to said repos can do. But IMO anyone is free to tackle modifying community-membership.md and I'm happy to review PR's to that effect.
FYI @kubernetes/sig-contributor-experience-proposals