-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
policy: add github org membership section #171
Conversation
Signed-off-by: Jordan Harband <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though it isn't very relevant in this case could you please add the signoff to fix the DCO issue?
@lehors whoops, thanks, done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me; thanks!
I plan to merge this tomorrow if there’s no objections. |
Followup from #155 and #155 (comment)
There are currently no dangerous permissions inherently granted by being a member of the github org, and I don't foresee anyone changing that (at all, let alone without broad discussion and TAC approval).
Note: the wording here is "should", intentionally - this paragraph in no way obligates OpenSSF to add anyone to the github org. However, once someone is in the org, they can be freely added to and removed from teams - prior to being in the org, they have to accept an invitation that expires in 7 days, so it's harder to use teams as a self-documenting structure when you have to wait on invitation acceptance.