-
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
Create access management policies for github.com/ossf #164
Comments
I'd be happy to find time to attend a TAC meeting if either of these points receive pushback, to argue in favor :-) |
I agree that permission should be managed through roles/groups and not via individual entitlements. Can we get some folks to donate some time in assisting with the repo review and implementation of changes if the TAC approves? |
Is there any downsides to this (other than requiring some work to implement it)? |
This was brought up in the TAC with @steiza @AevaOnline volunteering to help. |
I suggest separating these two tasks. The former (manage github access for maintainers by roles / groups) seems well supported by other procedural improvements that are in flight; the latter (allow open membership) would facilitate improvements in voting and representation of the contributor community, but may require more time to flesh out. Key terms to capture definitions of, as we proceed with this:
|
I'm also able to help; I've already spent a bunch of time doing this auditing. |
I made the first pass of this for all the repositories in ossf. All individuals have been put on a team with similar access. If there are any problems with this you can ping me on slack or email us at [email protected] I decided to remove individuals from the repo rather than wait for them to join the team so that we can move this more quickly. Some contributors are no longer active and I did not want the process held up. |
SGTM. Thanks Amanda! |
This work was in-flight before the new TAC was seated, see #155.
There's essentially two parts:
The text was updated successfully, but these errors were encountered: