From d6a8557ae6499f246c5feee0af6fc9e6e00e92b3 Mon Sep 17 00:00:00 2001 From: Serge Latyntsev Date: Wed, 27 Jan 2021 10:19:03 +1300 Subject: [PATCH] Update docs/en/05_Contributing/16_Maintainer_Guidelines.md Co-authored-by: Ingo Schommer --- docs/en/05_Contributing/16_Maintainer_Guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/05_Contributing/16_Maintainer_Guidelines.md b/docs/en/05_Contributing/16_Maintainer_Guidelines.md index 2bee6d029..18d226118 100644 --- a/docs/en/05_Contributing/16_Maintainer_Guidelines.md +++ b/docs/en/05_Contributing/16_Maintainer_Guidelines.md @@ -107,7 +107,7 @@ Some of the Supported Modules have their own house rules (usually explained in t ### How to triage -Triaging GitHub issues and pull requests imply responding to issue/pr creators with following closing or labelling. Labelling allows the other maintainers to pick up proper issues/prs accordingly to their dedication or available resources. +Triaging issues and pull requests involves review, applying labels, as well as closing invalid submissions. Applying [labels](./code/#labels) is the main mechanism used to escalate critical and high impact issues, give feedback to the community, or peer review a PR and let other maintainers know it is “good to be merged on green CI tests”.