Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Force Requirement to Accept Github Invitation For All #74

Open
hblankenship opened this issue Feb 11, 2022 · 0 comments
Open

Force Requirement to Accept Github Invitation For All #74

hblankenship opened this issue Feb 11, 2022 · 0 comments
Labels
chapter-policy-2022.2 Link to document - https://github.com/OWASP/www-policy/blob/master/draft-prepublish/chapters.md regional-operational

Comments

@hblankenship
Copy link
Contributor

From: Lisa Jones @latf6711

`At least one leader, but preferably all leaders, must accept the GitHub invite before it expires. A leader with chapter repository admin rights can grant other leaders admin access.

This statement is creating a single point of failure. This is why we ask for a minimum of 2 leaders. This contradicts the requirements in the request ticket and the statement in Share Services.
@hblankenship hblankenship added the chapter-policy-2022.2 Link to document - https://github.com/OWASP/www-policy/blob/master/draft-prepublish/chapters.md label Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chapter-policy-2022.2 Link to document - https://github.com/OWASP/www-policy/blob/master/draft-prepublish/chapters.md regional-operational
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vanderaj @hblankenship