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.

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

Closed
yurishkuro opened this issue Oct 23, 2019 · 14 comments
Closed

Decentralize membership lists #233

yurishkuro opened this issue Oct 23, 2019 · 14 comments
Assignees

Comments

@yurishkuro
Copy link
Member

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.

SergeyKanzhelev added a commit to open-telemetry/opentelemetry-dotnet that referenced this issue Oct 23, 2019
SergeyKanzhelev added a commit to open-telemetry/opentelemetry-dotnet that referenced this issue Oct 23, 2019
@SergeyKanzhelev
Copy link
Member

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.

@SergeyKanzhelev SergeyKanzhelev changed the title [proposal] Decentralize membership lists Decentralize membership lists Oct 23, 2019
@mayurkale22
Copy link
Member

I like the idea, but who is responsible for adding a new member to respective team (ex: @open-telemetry/xxx-approvers or @open-telemetry/xxx-maintainers)?

@yurishkuro
Copy link
Member Author

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?

@SergeyKanzhelev
Copy link
Member

Yes: https://github.com/open-telemetry/community/blob/master/docs/how-to-configure-new-repository.md#permissions:

Even though the members of foo-maintainers are included in foo-approvers transitively, every member of foo-maintainers should be included in foo-approvers explicitly, and with the "Maintainer" GitHub privileges. So repository maintainers can invite new approvers to the team.

@SergeyKanzhelev
Copy link
Member

node teams seems to be broken. I can fix permissions right away. Also do you want them to be renamed to JavaScript?

@mayurkale22
Copy link
Member

node teams seems to be broken. I can fix permissions right away. Also do you want them to be renamed to JavaScript?

Sure, thanks 👍

@SergeyKanzhelev
Copy link
Member

approvers are fixed:

image

@SergeyKanzhelev
Copy link
Member

Maintainers are fixed:

image

@tedsuo
Copy link
Contributor

tedsuo commented Oct 25, 2019

Great to see this!

@lizthegrey
Copy link
Member

This is now done.

@SergeyKanzhelev
Copy link
Member

@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?

@lizthegrey
Copy link
Member

Sure, I can sort that out.

@lizthegrey lizthegrey self-assigned this Mar 5, 2020
@bogdandrutu
Copy link
Member

There are some special sigs that are cross repos (like TC) I would suggest for this we keep track here.

SergeyKanzhelev added a commit that referenced this issue Aug 21, 2020
@SergeyKanzhelev
Copy link
Member

I believe this is done for all, except website. Let's track decentralization of website sig membership file in this issue #427

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants