From 59bced0a6ecd6bb132760dc0c5f5c84b677be919 Mon Sep 17 00:00:00 2001 From: tobtoht Date: Wed, 29 Jan 2025 02:10:06 +0100 Subject: [PATCH] CoC: allow maintainers to make 'value judgments' on correct patches --- docs/CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 606c28fe4..a8af915d6 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -145,7 +145,6 @@ C4 is meant to provide a reusable optimal collaboration model for open source so - 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. - Maintainers SHOULD NOT merge their own patches except in exceptional cases, such as non-responsiveness from other Maintainers for an extended period (more than 30 days) 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 people from the Monero Maintainer Team. - The Contributor MAY tag an issue as "Ready" after making a pull request for the issue. - The user who created an issue SHOULD close the issue after checking the patch is successful.