Conversation
Added and defined the "outside collaborator" role to the table.
|
cc @kubernetes/sig-contributor-experience-pr-reviews |
|
|
||
| | Role | Responsibilities | Requirements | Defined by | | ||
| | -----| ---------------- | ------------ | -------| | ||
| | outside collaborator | new active contributor to the community | sponsored by 1 member. existing contributions to the project. | Kubernetes GitHub org member. | |
There was a problem hiding this comment.
defined by: read-only collaborator on a repository in the kubernetes org
|
How many people do we have that are collaborators vs. members? My concern with putting this in the table is it might imply to someone that this is a required step in the ladder. I would much prefer people just jump straight to member, than think they have to go through this first. Managing collaborators is noisier. |
|
+1 to @spiffxp's comments. What does being an outside collaborator get you? Assigned issues, sure. Do we know which bot commands are gated by collaborators and which ones use |
|
Collaborators can do all the things a member can do... but only for the repos they're specifically collaborators on, vs repos in the entire org. This means you could eg: give someone /lgtm privileges on kubernetes/charts without giving them /lgtm privileges on kubernetes/kubernetes |
|
@spiffxp the reason why I've added this role to the table - as we already have this role defined below - https://github.com/kubernetes/community/blob/58a1ba55effe150b4f5f1e2d770f86ef3041ffd8/community-membership.md#new-contributors. If you feel that we shouldn't define the "collaborator" role in a table, I'd remove it from the entire document/reformat the document to follow the consistency. |
|
This PR hasn't been active in 30 days. It will be closed in 59 days (Feb 11, 2018). cc @calebamiles @grodrigues3 @idvoretskyi You can add 'keep-open' label to prevent this from happening, or add a comment to keep it open another 90 days |
|
@spiffxp @calebamiles any final decision on this? I'd like to have it merged or closed, whatever will be decided (but not to keep it open forever). |
|
IIRC, this was talked about briefly at the last contribex meeting, and most who commented were not in favour of introducing another level. |
|
Closing this since no decision for almost 60 days. |
|
Argh my bad, I meant to open an issue for this. I made noises about removing this to steering@kubernetes.io, and didn't hear a wild no. It's low on my list right now though. I'd like to survey which repos are using collaborators to understand the scope of the role today. |
Added and defined the "outside collaborator" role.