@@ -230,7 +230,7 @@ We strive for the following in our public projects:
1. Uphold our [Community Code of Conduct](https://about.gitlab.com/community/contribute/code-of-conduct/).
1. Enable [GitLab's mission that everyone can contribute.](/handbook/company/mission/#mission).
1. Show our work in [public](#public-by-default).
1.[Recognize and thank](/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#recognition-for-contributors) contributors for their work.
1.[Recognize and thank](/handbook/marketing/developer-relations/engineering/community-contributors-workflows/#recognition-for-contributors) contributors for their work.
1. Respect contributors donated time by providing [a timely review turnaround time](/handbook/engineering/workflow/code-review/#review-turnaround-time).
@@ -239,7 +239,7 @@ In Distribution we strive for the following in our public projects:
1. Uphold our [Community Code of Conduct](https://about.gitlab.com/community/contribute/code-of-conduct/).
1. Enable [GitLab's mission that everyone can contribute.](/handbook/company/mission/#mission).
1. Show our work in [public](#public-by-default).
1.[Recognize and thank](/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#recognition-for-contributors) contributors for their work.
1.[Recognize and thank](/handbook/marketing/developer-relations/engineering/community-contributors-workflows/#recognition-for-contributors) contributors for their work.
1. Respect contributors donated time by providing [a timely review turnaround time](/handbook/engineering/workflow/code-review/#review-turnaround-time).
@@ -145,7 +145,7 @@ We strive for the following in our public projects:
1. Uphold our [Community Code of Conduct](https://about.gitlab.com/community/contribute/code-of-conduct/).
1. Enable [GitLab's mission that everyone can contribute.](/handbook/company/mission/#mission).
1. Show our work in [public](#public-by-default).
1.[Recognize and thank](/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#recognition-for-contributors) contributors for their work.
1.[Recognize and thank](/handbook/marketing/developer-relations/engineering/community-contributors-workflows/#recognition-for-contributors) contributors for their work.
1. Respect contributors donated time by providing [a timely review turnaround time](/handbook/engineering/workflow/code-review/#review-turnaround-time).
@@ -7,7 +7,7 @@ At GitLab, our mission is to change all creative work from read-only to read-wri
Any GitLab team-member can triage merge requests. Keeping the number of un-triaged merge requests low is essential for maintainability, and is our collective responsibility. Consider triaging a few merge requests around your other responsibilities, or scheduling some time for it on a regular basis.
Triaging incoming wider community merge requests is divided between several departments. Quality Department maintains triage automation, [Merge Request Coaches](/handbook/marketing/developer-relations/contributor-success/merge-request-coach-lifecycle) take on a partial merge request triage, and finally triage automation helps completing the triage process. Additionally, [Contributor Success](/handbook/marketing/developer-relations/contributor-success/) drives the community collaboration efforts and works with our community to ensure they receive support and recognition for contributing to GitLab.
Triaging incoming wider community merge requests is divided between several departments. Quality Department maintains triage automation, [Merge Request Coaches](/handbook/marketing/developer-relations/engineering/merge-request-coach-lifecycle) take on a partial merge request triage, and finally triage automation helps completing the triage process. Additionally, [Contributor Success](/handbook/marketing/developer-relations/engineering/) drives the community collaboration efforts and works with our community to ensure they receive support and recognition for contributing to GitLab.
## Merge request triage for the `gitlab-org` group
@@ -22,7 +22,7 @@ A merge request is considered initially triaged when it has a:
-`~"Community contribution"` label applied
- "Thank you" message posted by [`@gitlab-bot`](https://gitlab.com/gitlab-bot) with more details on the process
The initial triage is automated by the [Contributor Success team](/handbook/marketing/developer-relations/contributor-success/) via the [Community contribution thank you note](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#community-contribution-thank-you-note) reactive triage automation.
The initial triage is automated by the [Contributor Success team](/handbook/marketing/developer-relations/engineering/) via the [Community contribution thank you note](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#community-contribution-thank-you-note) reactive triage automation.
#### Partial triage (`gitlab-org`)
@@ -33,7 +33,7 @@ A merge request is considered partially triaged when it has a:
-[group label](https://docs.gitlab.com/ee/development/labels/index.html#group-labels) applied (e.g. `~"group:editor"`). If no group label exists, the stage label is enough.
The partial triage is completed by [Merge Request Coaches](/handbook/marketing/developer-relations/contributor-success/merge-request-coach-lifecycle) via the [Newly created community merge requests](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#newly-created-community-merge-requests) triage report.
The partial triage is completed by [Merge Request Coaches](/handbook/marketing/developer-relations/engineering/merge-request-coach-lifecycle) via the [Newly created community merge requests](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#newly-created-community-merge-requests) triage report.
For MRs related to issues, partial triage can be completed by using the following quick action and confirming proper metadata:
@@ -58,7 +58,7 @@ A merge request is considered completely triaged when it has a:
- milestone set if the merge request with the `~"Community contribution"` label is merged.
This triage process is automated by the [Contributor Success team](/handbook/marketing/developer-relations/contributor-success/) via the [Add milestone to community contributions on Triage Operations](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#add-milestone-to-community-merge-requests) scheduled triage automation.
This triage process is automated by the [Contributor Success team](/handbook/marketing/developer-relations/engineering/) via the [Add milestone to community contributions on Triage Operations](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#add-milestone-to-community-merge-requests) scheduled triage automation.
@@ -79,7 +79,7 @@ Community contributions are valuable, and we should handle them as effectively a
| [Complete Triage for Merged Merge Requests](#complete-triage-for-merged-merge-requests-gitlab-org) | 1 day ([this is automated for `gitlab-org/gitlab`](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#add-milestone-to-community-merge-requests)) |
| [Time to assign reviewer](#complete-triage-for-open-merge-requests-gitlab-org) | 2 hours ([this is automated](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#automated-review-request)) |
If an SLO isn't met, reach out to the [Contributor Success team](/handbook/marketing/developer-relations/contributor-success/).
If an SLO isn't met, reach out to the [Contributor Success team](/handbook/marketing/developer-relations/engineering/).
## Merge request triage for the `gitlab-com/www-gitlab-com` project
