-
Notifications
You must be signed in to change notification settings - Fork 0
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
Additional org owner(s) #3
Comments
I had thought that setting up the team would achieve this, but apparently not. I am happy to add all members of the team as owners of the org (making the team redundant, I suppose), or specific people as nominated here. In addition, we should consider who should hold rights to pypi, conda-forge and RTD. |
Looks like conda-forge has a bunch of owners as well https://github.com/orgs/conda-forge/people?query=role%3Aowner, including
Still very useful for mentioning and for, well, adding people to maintainers and not org owners 🙂 I think we should create
All org owners (aka admins) need to be added to those, I believe. For the same reasons as having multiple owners of this org. This might become a security concern at a certain number of people though, so we should find a balance. Whichever way we go, I think I should nominate myself to be added , as I'm pretty much directly or indirectly managing all of the fsspec-related work at iterative (sshfs, ossfs, pydrive2, gitfs etc) and I'm happy to serve as an emergency backup for other repos. 🙂 |
I added all the maintainers team as owners (I think!). |
@martindurant Thanks! Closing since this is resolved. Created #4 for pypi/conda/rtd discussion. |
Currently, there is only one owner https://github.com/orgs/fsspec/people , which means that if @martindurant for some reason becomes unavailable, no one else will be able to do org-level actions (e.g. inviting people, changing teams, granting permissions to repositories, adopting new repos that are being transfered from elsewhere, etc), which is a problem. I think we should have at least one more owner for everyone's security.
From fsspec/sshfs#13
The text was updated successfully, but these errors were encountered: