COMMUNITY-ROLES: discourage SMS 2FA, add reply comment templates (#19505)

Signed-off-by: Dharun Krishna K B <[email protected]>
Co-authored-by: Lena Pastwa <[email protected]>
Co-authored-by: Waldir Pimenta <[email protected]>
Co-authored-by: Managor <[email protected]>

Author: 4 people

COMMUNITY-ROLES.md

@@ -21,7 +21,13 @@ the metrics used are objective, easy to check, and explicitly described below. (
 exceptions can always be considered through open community discussion.)
 
 > [!IMPORTANT]
-> It is required to have [two-factor authentication](https://github.com/settings/security) (2FA) enabled for your GitHub account to be added as an outside collaborator or a member of the tldr-pages organization.
+> It is required to have a secure [two-factor authentication (2FA)](https://github.com/settings/security) method (Authenticator app/Security Keys/GitHub mobile) enabled for your GitHub account
+> to be added as an outside collaborator or a member of the tldr-pages organization.
+
+> [!WARNING]
+> SMS-based 2FA methods pose a higher risk of being compromised,
+> so **we require all maintainers to disable SMS-based 2FA**
+> and use more secure methods.
 
 ## When to change roles
 
@@ -109,7 +115,8 @@ using one of the template messages below as a base.
    Either way, thanks for all your work so far!
 
    > [!NOTE]
-   > It is required to have [two-factor authentication](https://github.com/settings/security) (2FA) enabled for your GitHub account to be added as a collaborator to the tldr-pages/tldr repository.
+   > It is required to have a secure [two-factor authentication (2FA)](https://github.com/settings/security) method (Authenticator app/Security Keys/GitHub mobile) enabled for your
+   > GitHub account to be added as a collaborator to the tldr-pages/tldr repository.
    ```
 
 2. Once they acknowledge the message and if they accept the invitation,
@@ -121,6 +128,18 @@ using one of the template messages below as a base.
    Make sure to include `Closes #<issue number>` in the PR description.
    The issue will then be automatically closed once the PR gets merged.
 
+   Feel free to use this reply comment template:
+
+   ```md
+   Welcome to tldr! I've sent you an invitation to become a collaborator in this repository. 
+   
+   Feel free to close this issue with a pull request, updating the [MAINTAINERS.md](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md#repository-collaborators) file's active collaborator section with a new entry.
+
+   Also add yourself to the [CODEOWNERS](https://github.com/tldr-pages/tldr/blob/main/.github/CODEOWNERS) file if you wish to take responsibility for reviewing PRs for a language's translations or a specific directory.
+
+   We also have a [Matrix chat room](https://matrix.to/#/#tldr-pages:matrix.org), which we recommend as a way to stay in touch with community discussions and other maintainers.
+   ```
+
 ### Adding new organization members
 
 1. Open an issue with the following message template (edit it as appropriate):
@@ -153,6 +172,18 @@ using one of the template messages below as a base.
    Make sure to include `Closes #<issue number>` in the PR description.
    The issue will then be automatically closed once the PR gets merged.
 
+   Feel free to use this reply comment template:
+
+   ```md
+   Welcome to tldr-pages! I've sent you an invitation to become a member of the organization. Once you accept it, don't forget to set your membership to ["Public" visibility](https://github.com/orgs/tldr-pages/people).
+   
+   Feel free to close this issue with a pull request, updating the [MAINTAINERS.md](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md#organization-members) file's active organization members section with a new entry.
+
+   Make sure to update your existing [repository collaborator](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md#repository-collaborators) entry in [MAINTAINERS.md](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md) file and move it to the bottom of the collaborators list.
+
+   Additionally, if you haven't already, add yourself to the [CODEOWNERS](https://github.com/tldr-pages/tldr/blob/main/.github/CODEOWNERS) file if you wish to take responsibility for reviewing PRs for a language's translations or a specific directory.
+   ```
+
 ### Adding new organization owners
 
 1. Open an issue with the following message template (edit it as appropriate):
@@ -181,6 +212,18 @@ using one of the template messages below as a base.
    Make sure to include `Closes #<issue number>` in the PR description.
    The issue will then be automatically closed once the PR gets merged.
 
+   Feel free to use this reply comment template:
+
+   ```md
+   Welcome to administering tldr-pages! I've converted your role to an Organization Owner.
+   
+   Feel free to close this issue with a pull request, updating the [MAINTAINERS.md](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md#organization-owners) file's active organization owners section with a new entry.
+
+   Make sure to update your existing [organization member](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md#organization-members) entry in [MAINTAINERS.md](https://github.com/tldr-pages/tldr/blob/main/MAINTAINERS.md) file and move it to the bottom of the members list.
+
+   As an owner, you will be able to perform role changes and also manage the organization's settings. I request you to be extra careful to avoid any accidental misconfigurations and also discuss any changes beforehand with other maintainers before implementing them.
+   ```
+
 ### Removing inactive organization members
 
 1. Open an issue with the following message template (edit it as appropriate):