From 3c4b3c5406cd9f75e8904a0e649cd31045f57e54 Mon Sep 17 00:00:00 2001 From: Steve Myers Date: Wed, 29 Jul 2026 14:28:34 -0500 Subject: [PATCH] docs: add maintainers section to CONTRIBUTING.md --- CONTRIBUTING.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9cd11e0a..3d41dc97 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -95,7 +95,22 @@ well as test out the patch set and opine on the technical merits of the patch. PR should be reviewed first on the conceptual level before focusing on code style or grammar fixes. -To merge a PR we require all CI tests to pass, the PR has at least one approving review by a maintainer with write access, and reasonable criticisms have been addressed. +Repository maintainers +---------------------- + +Like all open source projects our maintainers are busy. Please take it easy on +them and only ping them if you get no response for a week or two. Maintainers must ensure +that there is "rough consenus" that a PR is needed and correctly implemented. +Maintainers are not required to review and test your PR. A maintainer may ACK and +merge (or NACK and close) a PR based on the reviews of any competent project contributors. + +Minimum pull request merge requirements: + +- all CI tests pass. +- at least two "accepts"/ACK from a repository maintainer (other than the author). +- no reasonable "rejects"/NACK from anybody who reviewed the code. + +See the .github/CODEOWNERS file for a current list of the project maintainers. Coding Conventions ------------------