-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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: @CleanMachine1 #6123
Labels
community
Issues/PRs dealing with role changes and community organization.
Comments
bl-ue
added
the
community
Issues/PRs dealing with role changes and community organization.
label
Jun 14, 2021
of course! |
Invitation sent! |
Where do I accept? Am I missing something? |
@CleanMachine1 in your email I guess, maybe notifications. |
Ah I found it, it wasn't in my notifications, it was here github.com/orgs/tldr-pages |
Im just about start a PR to change the contributor file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, @CleanMachine1! After joining as a collaborator in the repository, you have been regularly performing maintenance tasks (#6122, #6101, #6100, #6099, #6097, #6095, #6093, #6092, #6083, #6065, #6064, #6058, #6057, #6047, #6044, #6042, and many more!).
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?
The text was updated successfully, but these errors were encountered: