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

Add organization member: @MasterOdin #5473

Closed
bl-ue opened this issue Mar 18, 2021 · 4 comments · Fixed by #5660
Closed

Add organization member: @MasterOdin #5473

bl-ue opened this issue Mar 18, 2021 · 4 comments · Fixed by #5660
Labels
community Issues/PRs dealing with role changes and community organization.

Comments

@bl-ue
Copy link
Contributor

bl-ue commented Mar 18, 2021

Hi, @MasterOdin! After joining as a collaborator in the repository, you have been regularly performing maintenance tasks.
Thank you for that!
According to our community roles documentation, you've now met the thresholds to be effectively considered an active maintainer of the project.
To publicly acknowledge that fact, we'd like to add you to the tldr-pages organization.

If you accept the invitation, we ask you to make your membership public, and (in case you don't already) start hanging out in our Gitter chat room.
Additionally, consider subscribing to the notifications from the various repositories under the tldr-pages organization.
As one of the public faces of the tldr-pages project, it's also especially important that you follow and encourage the project
governance principles
.

How does that sound? Are you up for it?

@bl-ue bl-ue added the community Issues/PRs dealing with role changes and community organization. label Mar 18, 2021
@MasterOdin
Copy link
Collaborator

I'd point out that I have not merged 10 PRs or provided 5 non-trivial reviews to PRs within the main tldr-pages/tldr repo which the COMMUNITY-ROLES.md file seems to indicate. I do not have an interest in really reviewing PRs here, having more interest in working on clients and surrounding infrastructure stuff.

@bl-ue
Copy link
Contributor Author

bl-ue commented Mar 18, 2021

That's a good point, and if you'd like to close this issue I'd be happy to do so. But I have noticed that you contribute a lot some of the repos, such as tldr-lint and tldr-node-client, and among other things, being an organization member (to my knowledge) extends your collaborator's permissions to all repositories under the organization.

Also, we should discuss with @waldyrious if the other repos should count at all towards these "promotions." 🤔

@sbrl
Copy link
Member

sbrl commented Mar 25, 2021

Yeah, it does extend privileges to all repos. The community roles we have in this repo are really tailored towards the tldr repo here, and they don't specifically talk about other repos. With that in mind, I'd suggest that the process for regular contributors of other repos is much more of a case-by-case ad-hoc basis.

If @MasterOdin would like to be an org member to remove barriers in other repos, that's fine by me :-)

@sbrl
Copy link
Member

sbrl commented Apr 1, 2021

I assume that by opening that PR @MasterOdin you're accepting the offer? Sending invite!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues/PRs dealing with role changes and community organization.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants