summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorMaxim Cournoyer <maxim.cournoyer@gmail.com>2023-03-17 16:07:52 -0400
committerMaxim Cournoyer <maxim.cournoyer@gmail.com>2023-04-03 15:41:41 -0400
commit52d373dfef7ddd93c67bd615e74057af90c189ac (patch)
treec55783c821795faddd537a77138fbdd9fd04003d /doc
parentf3424ada316a9962818b60ae22236efce8bd9fb7 (diff)
downloadguix-52d373dfef7ddd93c67bd615e74057af90c189ac.tar.gz
doc: Add a reference to a page explaining consensus decision making.
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.

Co-authored-by: Ludovic Courtès <ludo@gnu.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing.texi7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index e03d888bd1..73d1cd2648 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1727,7 +1727,12 @@ 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 help build
+consensus and make decisions based on consensus.  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