| | 1 | = Triage & Review Team = |
| | 2 | |
| | 3 | This page is used to document helpful information regarding the [https://www.djangoproject.com/foundation/teams/#triage-review-team Triage & Review Team]. |
| | 4 | |
| | 5 | == Team definition == |
| | 6 | |
| | 7 | Current definition of the Triage & Review Team exists in [https://github.com/django/deps/blob/main/final/0010-new-governance.rst#new-role-triage-review-team DEP-10]. |
| | 8 | |
| | 9 | > The Triage & Review Team allows current, regular contributors additional permissions on GitHub, in order to assist with the processing of pull requests. |
| | 10 | > |
| | 11 | > The objective of the team is to help spread work beyond the Mergers and into the wider contributor community. |
| | 12 | > |
| | 13 | > * There will be a GitHub Team with GitHub's Triage Permission to allow members to help manage pull requests directly. |
| | 14 | > * A pull request approval from a member of the Triage and Review team will be sufficient to allow a Merger to merge a minor change they themselves have proposed. |
| | 15 | > * Subject to both the Django Code of Conduct, and to Technical Board oversight, the Triage and Review Team will be self-managing. |
| | 16 | > * Anyone actively engaging in discussions on GitHub and django-developers will be eligible to join the Triage and Review Team. Membership is not meant to be bureaucratic: folks who are active should be invited by a team member or Merger, or quietly mention that they've been overlooked and would like to join if this fails to happen. A simple seconding from an existing member should be enough for approval. |
| | 17 | > * Team membership will be reviewed with each major release. Members will be asked if they wish to continue. For self-care, those needing a break are advised to take it. Former members will be welcome back in the future. |
| | 18 | |
| | 19 | |
| | 20 | == How to add a member to the Triage & Review Team == |
| | 21 | |
| | 22 | Once there is agreement from the team that the new member is suitable to join, they can be added to the Triage & Review Team. |
| | 23 | |
| | 24 | You will need: |
| | 25 | * Their preferred email address |
| | 26 | * Their Trac username |
| | 27 | * Their GitHub username |
| | 28 | * Their Discord username (if they have one) |
| | 29 | |
| | 30 | If you do not have permissions to do any of the below, email ops@djangoproject.com |
| | 31 | * Add the Trac user to the "supertriagers" permission group. |
| | 32 | * Add their GitHub account to the [https://github.com/orgs/django/teams/triage-review Triage & Review Team] on GitHub. |
| | 33 | * Add them to the [https://groups.google.com/a/djangoproject.com/g/triage-review/members Triage & Review Team] Google group. |
| | 34 | * Add them to the #triage-review private Discord channel within the [https://chat.djangoproject.com/ Django Discord] |
| | 35 | * Add them to the Triage & Review Team on the [https://www.djangoproject.com/admin/members/team/ Django website]. Before they can be officially added on the website as a member of the team, they will need DSF membership. [https://docs.google.com/forms/d/e/1FAIpQLSd5lbWxAO-sylEEjHVKBNIpmHlhdJRf0_LCo8glnLUWd-Q2Sw/viewform Nominate them for DSF membership] if they are not already a member. |
| | 36 | |
| | 37 | Finally send a welcome email to the new member with triage-review@djangoproject.com in cc. |
| | 38 | |
| | 39 | === Welcome email === |
| | 40 | |
| | 41 | Hello [Name], |
| | 42 | |
| | 43 | Welcome to Django's Triage & Review Team! https://www.djangoproject.com/foundation/teams/#triage-review-team 🎉 |
| | 44 | |
| | 45 | You have been added to this team in recognition of your contributions to Django. Thank you for all your support with the Django project! |
| | 46 | |
| | 47 | By being a member, we wish to recognize your contributions and to encourage your further involvement in the triaging of tickets and reviewing of PRs. |
| | 48 | |
| | 49 | As a member of the Triage & Review Team, you have the following new permissions/rights: |
| | 50 | * You are a member of Trac's "supertriagers" permission group. This gives you greater editor rights on tickets, such as being able to add folks on cc in a ticket. |
| | 51 | * As a member of the Triage & Review Team on GitHub, you can add labels to PRs on GitHub. Your approval is also sufficient that a Merger can merge a PR. You may notice that fellows often ask for a Triage & Review Team review (as no one can merge their own PR without an approval). |
| | 52 | |
| | 53 | We have a couple of modes of communication within the team: |
| | 54 | * The Triage & Review google group which receives emails sent to triage-review@djangoproject.com |
| | 55 | * The #triage-review private Discord channel (this may not have all members as not all members are active on Discord) |
| | 56 | These are often used to communicate about holiday periods and to discuss new members joining the team. You may also use these to ask for advice of a sensitive nature about a difficult contributor. Otherwise, most discussions around Django should be held in public. |
| | 57 | |
| | 58 | Django has some professional PyCharm licenses that we can share with our contributors. PyCharm (hopefully) renew these each year. If you wish to have a free Professional PyCharm license, please email fellows@djangoproject.com and we will share one with you. |
| | 59 | |
| | 60 | Thank you for your work contributing to Django and welcome to the team! |
| | 61 | |
| | 62 | Kind Regards |
| | 63 | |
| | 64 | [Name] |