From 89bbdf0aa0f1f11b6738e4b69b33e9bfcfeb55d6 Mon Sep 17 00:00:00 2001 From: tobtoht Date: Sun, 26 Jan 2025 14:56:36 +0100 Subject: [PATCH] docs: clarify who can approve and how --- docs/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 03f2aea5f..ad6049a87 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -123,7 +123,7 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S - To submit a patch, a Contributor MUST create a Platform pull request back to the project. - Patches MUST NOT be committed directly to the project. - To discuss a patch, people MAY comment on the Platform pull request, on the commit, or elsewhere. -- To accept or reject a patch, a Maintainer MUST use the Platform interface. +- To approve or reject a patch, Contributors MUST use the Platform interface. - Maintainers SHOULD NOT merge their own patches unless they were added to the merge queue on irc and have at least 2 approvals from contributors OR unless urgent as defined by the Monero Maintainers Team. - Maintainers MUST NOT make value judgments on correct patches unless the Maintainer (as may happen in rare circumstances) is a core code developer. - Maintainers MUST NOT merge pull requests in less than 168 hours (1 week) unless deemed urgent by at least 2 Maintainers.