From e5426867423140c6fe3c9dd7715678083bfebf55 Mon Sep 17 00:00:00 2001 From: Gireesh Punathil Date: Mon, 11 Nov 2024 03:45:13 +0530 Subject: [PATCH] doc: clarify triager role MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit highlight additional points around triager role Co-authored-by: Antoine du Hamel PR-URL: https://github.com/nodejs/node/pull/55775 Reviewed-By: Chengzhong Wu Reviewed-By: Antoine du Hamel Reviewed-By: Ulises Gascón Reviewed-By: Rafael Gonzaga Reviewed-By: Moshe Atlow --- doc/contributing/issues.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/contributing/issues.md b/doc/contributing/issues.md index 7cd043148ff..e9bbc4de28e 100644 --- a/doc/contributing/issues.md +++ b/doc/contributing/issues.md @@ -60,5 +60,17 @@ activities, such as applying labels and closing/reopening/assigning issues. For more information on the roles and permissions, see ["Permission levels for repositories owned by an organization"](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization). +When triagging issues and PRs: + +* Show patience and empathy, especially to first-time contributors. +* Show no patience towards spam or troll, close the issue without interacting with it and + report the user to the moderation repository. +* If you're not able to reproduce an issue, leave a comment asking for more info and + add the `needs more info` label. +* Ideally issues should be closed only when they have been fixed or answered (and + merged for pull requests). Closing an issue (or PR) earlier can be seen as + dismissive from the point of view of the reporter/author. + Always try to communicate the reason for closing the issue/PR. + [Node.js help repository]: https://github.com/nodejs/help/issues [Technical Steering Committee (TSC) repository]: https://github.com/nodejs/TSC/issues