Hi, @Proscream! You seem to be enjoying contributing to the tldr-pages project.
You now have had five distinct pull requests merged (#3549, #3553, #3560, #3577, #3578, #3579, #3582, #3585, and #3586)!
That qualifies you to become a collaborator in this repository, as explained in our community roles documentation.
As a collaborator, you will have commit access to the repository.
That means you can merge pull requests, label and close issues, and perform various other maintenance tasks that are needed here and there.
Of course, all of this is voluntary — you're welcome to contribute to the project in whatever ways suit your liking.
If you do decide to start performing maintenance tasks, though, we only ask you to get familiar with the maintainer's guide.
So, what do you say? Can we add you as a collaborator?
Either way, thanks for all your work so far!
sbrl
All 13 comments
Hi @sbrl First of all, thank you for the offer. I'm really enjoying the work of translating. I'm thinking of continuing to translate Korean. It would be great if you could add me as a collabulator.
Have a nice day!
Proscream
on 19 Nov 2019
Hi @Proscream
Thank you for your contribution to the project.
Welcome aboard :rocket:
andrik
on 20 Nov 2019
@andrik Thank you for your hospitality. :)
Proscream
on 20 Nov 2019
Invite sent :D
You should have privileges to close this issue when you accept the invite, @Proscream :D
sbrl
on 22 Nov 2019
@sbrl Thanks! I will close this issue.
Proscream
on 22 Nov 2019
@sbrl these issues should not be closed manually, but rather with the PR adding the new collaborator name to the MAINTAINERS.md document. 😉
waldyrious
on 22 Nov 2019
@waldyrious Thank you for your advice!
Proscream
on 22 Nov 2019
No problem @Proscream. Please make sure to read the maintainer's guide, which contains guidelines for performing the main maintenance tasks, and COMMUNITY-ROLES.md, which has instructions specifically about when and how to perform role changes like this one. 🙂
waldyrious
on 22 Nov 2019
@waldyrious Of course. I'll be well-informed of it as soon as I can. :)
Proscream
on 22 Nov 2019
Welcome @Proscream !
einverne
on 23 Nov 2019
Oops, I totally forgot about that step @waldyrious! I'll do that now.
sbrl
on 24 Nov 2019
@sbrl Do older PRs count too? I had 17 PRs merged back in 2016. Source :medal_military:
zlatanvasovic
on 28 Nov 2019
@zdroid definitely! Ideally we should collect statistics across the entire repo history so that we can recognize contributions older than the adoption of this policy, but as always, manpower has been limited 😅 (if it's something you'd like to do, please go ahead!)
In your case in particular, we can just go ahead and make the change, sure. Can you open a separate issue similar to this one for yourself, so we can keep a better record of these additions? Then @sbrl can include your name in #3617 as well :)
waldyrious
on 28 Nov 2019
Related issues
Wesalius
·
3Comments
schneiderl
·
3Comments
taki
·
3Comments
pascaliske
·
3Comments
GabLeRoux
·
3Comments
Most helpful comment
@zdroid definitely! Ideally we should collect statistics across the entire repo history so that we can recognize contributions older than the adoption of this policy, but as always, manpower has been limited 😅 (if it's something you'd like to do, please go ahead!)
In your case in particular, we can just go ahead and make the change, sure. Can you open a separate issue similar to this one for yourself, so we can keep a better record of these additions? Then @sbrl can include your name in #3617 as well :)