-
Notifications
You must be signed in to change notification settings - Fork 240
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
Decentralize membership lists #233
Comments
We actually discussed it while back and @bogdandrutu @sarahnovotny and @bhs we onboard. It is a good idea to make it in stages. Removing the "proposal" from title. |
I like the idea, but who is responsible for adding a new member to respective team (ex: |
I see that the teams allow Member vs. Maintainer roles, which exist outside of a specific repository. Do Maintainers have rights to add people to the team? |
|
node teams seems to be broken. I can fix permissions right away. Also do you want them to be renamed to JavaScript? |
Sure, thanks 👍 |
Great to see this! |
This is now done. |
@lizthegrey we still have docs, erlang, cpp, and a few others not migrated out: https://github.com/open-telemetry/community/blob/master/community-members.md#docs-and-website Let's keep it open. Would you mind following up with these SIGs? |
Sure, I can sort that out. |
There are some special sigs that are cross repos (like TC) I would suggest for this we keep track here. |
I believe this is done for all, except website. Let's track decentralization of website sig membership file in this issue #427 |
At the moment we list approvers/maintainers of all SIGs in the central file
community-members.md
in this repo. That means adding/editing those lists requires the attention of the admins/TC, while the decisions to promote member are actually made locally in the SIGs.I suggest replacing the explicit lists with links to the respective repo and maintaining the lists there, to better scale up the process.
Similarly, the SIG information (schedule of meetings, etc.) can be also moved from the README in this repo to the READMEs in the respective repos. This repo will only have the links to information.
To avoid creating a bunch of refactoring work right now (unless someone wants to take it on), I suggest we do it incrementally as new requests (like #230) to change membership arrive.
The text was updated successfully, but these errors were encountered: