-
Notifications
You must be signed in to change notification settings - Fork 44
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
Permissions and ownership of this repo #5
Comments
I gave build admin access, I don't think anyone will abuse that, and since that means you have admin access, I guess you can now rearrange perms as you see fit, @rvagg |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I forgot to set up permissions properly before I resigned from the TSC, so I no longer have write or admin access here. I'm just not sure exactly what structure to request.
My name is on the README as the only maintainer and so far I've not managed to attract any other maintainer interest. #1 suggests that it might get closed down if it doesn't get any more help. Maintenance burden has been much less than I expected, I've had to do nothing with this since I set it up and it seems to be running fine. We'll see what happens when it breaks though.
So the options are:
Option 2 would be simpler but it has a side effect of putting this more into Build's field of responsibility than was intended. But maybe that's not a big deal? After all, node-gyp is in a similar category, although it does have a team of its own that largely overlaps with Build.
The text was updated successfully, but these errors were encountered: