COMMUNITY-ROLES.md: add role transition procedures

COMMUNITY-ROLES.md

@@ -72,6 +72,125 @@ exceptions can always be considered, via open community discussion.)
   they should be added back to the organization, to reflect that fact.
 
 
+## How to change roles
+
+*Note: this section is aimed at owners in the tldr-pages organization
+(i.e. the group of people who are able to perform these changes).*
+
+If you notice a contributor being particularly active,
+review their recent contributions to check whether a role transition is due,
+according to the criteria defined in the previous section.
+If a role change is warranted, **open a new issue proposing that role change**,
+using one of the template messages below as a base.
+
+### For adding new collaborators
+
+Open an issue with the following message:
+
+```
+Hi, @username(s)! You seem to be enjoying contributing to the tldr-pages project.
+You now have had five distinct pull requests merged ([LINKS TO THE RELEVANT PRs]),
+which qualifies you to become a collaborator in this repository,
+as explained in our
+[governance guidelines](https://github.com/tldr-pages/tldr/blob/master/GOVERNANCE.md).
+
+As a collaborator, you will have commit access
+and can therefore merge pull requests from others, 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](https://github.com/tldr-pages/tldr/blob/master/contributing-guides/maintainers-guide.md).
+
+Thanks for all your work so far!
+```
+
+Once they acknowledge the message,
+go to https://github.com/tldr-pages/tldr/settings/collaboration
+and add them to the repository as collaborator with write permissions.
+
+### For adding new organization members
+
+Open an issue with the following message:
+
+```
+Hi, @username(s)! After joining as a collaborator in the repository,
+you have been regularly performing maintenance tasks. Thank you for that!
+According to
+[GOVERNANCE.md](https://github.com/tldr-pages/tldr/blob/master/GOVERNANCE.md),
+you've now met the thresholds to be effectively considered
+an active maintainer of the project ([LINKS TO THE RELEVANT PRs]).
+To publicly acknowledge that fact, we'll 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.
+You'll now be one of the public faces of the tldr-pages project.
+Welcome aboard!
+```
+
+Once they acknowledge the message,
+go to https://github.com/orgs/tldr-pages/people
+and add them to the organization as a member.
+
+### For adding new organization owners:
+
+Open an issue with the following message:
+
+```
+Hi, @username(s)! You've been an active tldr-pages org member for over 6 months.
+Thanks for sticking around this far and helping out!
+According to
+[GOVERNANCE.md](https://github.com/tldr-pages/tldr/blob/master/GOVERNANCE.md),
+you're now eligible for becoming an owner of the organization.
+
+That means you will, from now on, be part of the team
+responsible for performing role changes (like this one!) in the community.
+Before performing such role transitions, make sure to review the
+[COMMUNITY-ROLES.md](https://github.com/tldr-pages/tldr/blob/master/COMMUNITY-ROLES.md)
+document.
+
+Thanks for all the work you've done so far. You rock!
+```
+
+Once they acknowledge the message,
+go to https://github.com/orgs/tldr-pages/people
+and change their role from "member" to "owner".
+
+Afterwards, add their name to the list of current organization owners below.
+
+### For removing inactive organization members:
+
+Open an issue with the following message:
+
+```
+Hi, @username(s)! As you know, our
+[governance guidelines](https://github.com/tldr-pages/tldr/blob/master/GOVERNANCE.md)
+define processes for keeping the list of organization members
+in sync with the actual maintenance team.
+Since you haven't been active in the project for a while now,
+we'll be moving you to the status of former maintainer.
+
+In practice, not much will change on your side,
+since you'll remain a collaborator in the repos you have been active in,
+so **you will keep the ability to commit, merge PRs, label and close issues, etc.**,
+if you feel so inclined. But even if you don't,
+keep in mind that every bit of work you already did for the tldr-pages project
+was a voluntary gift of your time to this community.
+Your efforts have contributed to a project
+which helps hundreds of people every day — be proud of it!
+
+And of course, you're welcome back anytime as a maintainer, if you so choose
+— in which case we'll re-add you to the organization,
+as is also described in the guidelines.
+In any case, we wish you the best of luck in your new endeavors!
+```
+
+Once the role change is completed,
+make sure to update the lists below accordingly.
+
+
 ## Who can change roles
 
 ### Current owners