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

proposal: Separating Leaders #26

Closed
Xuanwo opened this issue Jul 27, 2021 · 2 comments · Fixed by #34
Closed

proposal: Separating Leaders #26

Xuanwo opened this issue Jul 27, 2021 · 2 comments · Fixed by #34

Comments

@Xuanwo
Copy link
Contributor

Xuanwo commented Jul 27, 2021

Now we have leader groups for all projects which are not needed, maybe we can merge them into one which responsible for the whole BeyondStorage community.

Inside these changes, we will

  • Remove all leaders groups include go-storage-leaders, beyond-tp-leaders, community-leaders
  • Add new group leaders which will have admin permissions on all BeyondStorage repos.
  • Remove separate community teams
  • All team members will have the same permissions on site
@Xuanwo
Copy link
Contributor Author

Xuanwo commented Jul 27, 2021

ping all maintainer, committer and reviewers for advice.

@beyondstorage/beyond-tp-maintainer
@beyondstorage/beyond-tp-committer
@beyondstorage/beyond-tp-reviewer
@beyondstorage/go-storage-maintainer
@beyondstorage/go-storage-committer
@beyondstorage/go-storage-reviewer
@beyondstorage/community-maintainer
@beyondstorage/community-committer
@beyondstorage/community-reviewer

@Prnyself
Copy link
Member

I agree.
In some aspects, leader's permission is overlaped with maintainer. So, with the existence of maintainer, we may not need a higher permission role in each project.

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

Successfully merging a pull request may close this issue.

2 participants