Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add community membership requirement #3564
If sig leaders are not community members, this prevents us from putting them in OWNERS files, assigning issues/PRs to them, and other common community administration tasks. Requiring folks to go through this process also ensures that leaders are established members of the community and have had their work reviewed/sponsored by others.
1 similar comment
@mrbobbytables Perhaps, but working groups have a different place in our ecosystem. I could see it making sense for a sig to sponsor a working group organizer who is new to the community.
I personally don't feel strongly either way, but am happy to amend my PR if there are opinions supporting adding that requirement for other groups like working groups, committees, or user groups.
I'll add my +1 as a steering member. And yes, I think this should apply to more than just SIGs:
At a minimum, these folks need to be able to review and approve docs that describe what their group is and how it operates. Thus, must be org members.
+1 to what Aaron said…
On Wed, Apr 10, 2019 at 4:00 PM Aaron Crickenberger < ***@***.***> wrote: I'll add my +1 as a steering member. And yes, I think this should apply to more than just SIGs: - SIG chairs and tech leads - UG chairs - WG organizers - Committee members At a minimum, these folks need to be able to review and approve docs that describe what their group is and how it operates. Thus, must be org members. — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#3564 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABbCH9qp2CqUBgVGVuy2hIZgBW84v1Dks5vfkLFgaJpZM4ci_Q0> .
-- Davanum Srinivas :: https://twitter.com/dims
2 times, most recently
Apr 12, 2019
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dims
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing