From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 62246@debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#62246] [PATCH] doc: Add a reference to a page explaining consensus decision making.
Date: Fri, 17 Mar 2023 16:22:34 -0400 [thread overview]
Message-ID: <20230317202234.25156-1-maxim.cournoyer@gmail.com> (raw)
This is to make explicit something which until now had always been implicit.
* doc/contributing.texi (Commit Access): Mention that committers are expected
to employ consensus decision making.
---
doc/contributing.texi | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 911c3a7bbf..4db0fdc76e 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1728,7 +1728,11 @@ project for at least 6 months. This ensures enough interactions with
the contributor, which is essential for mentoring and assessing whether
they are ready to become a committer. Commit access should not be
thought of as a ``badge of honor'' but rather as a responsibility a
-contributor is willing to take to help the project.
+contributor is willing to take to help the project. It is expected from
+all contributors, and even more so from committers, to collaborate in a
+consensus decision making fashion. To learn what consensus decision
+making means and understand its finer details, you are encouraged to
+read @url{https://www.seedsforchange.org.uk/consensus}.
The following sections explain how to get commit access, how to be ready
to push commits, and the policies and community expectations for commits
base-commit: 933051281fbed0ae71bd40c24a701faf2a02791c
--
2.39.1
next reply other threads:[~2023-03-17 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 20:22 Maxim Cournoyer [this message]
2023-03-26 21:35 ` [bug#62246] [PATCH] doc: Add a reference to a page explaining consensus decision making Ludovic Courtès
2023-03-28 15:15 ` Maxim Cournoyer
[not found] ` <87ttxwd9a4.fsf_-_@gmail.com>
2023-04-09 17:39 ` pelzflorian (Florian Pelz)
2023-04-11 15:58 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230317202234.25156-1-maxim.cournoyer@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=62246@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).