From: "Ludovic Courtès" <ludo@gnu.org>
To: 73803@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#73803] [PATCH 1/2] doc: Add “Making Decisions” section.
Date: Mon, 14 Oct 2024 19:30:36 +0200 [thread overview]
Message-ID: <af70c561796ff70ef0422c818a2f5d7b1bdd365a.1728926815.git.ludo@gnu.org> (raw)
In-Reply-To: <cover.1728926815.git.ludo@gnu.org>
Suggested by Simon Tournier <zimon.toutoune@gmail.com>.
* doc/contributing.texi (Making Decisions): New section, with paragraphs
moved from…
(Commit Access): … here. Cross-reference it.
(Teams): Likewise.
Change-Id: Ib276242e0ec7598a1b60dacdde8647bd3d3b85d3
---
doc/contributing.texi | 45 +++++++++++++++++++++++++++----------------
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index acdc303be6..cc6e84013a 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -31,6 +31,7 @@ Contributing
* Coding Style:: Hygiene of the contributor.
* Submitting Patches:: Share your work.
* Tracking Bugs and Changes:: Keeping it all organized.
+* Making Decisions:: Collectively choosing the way forward.
* Commit Access:: Pushing to the official repository.
* Reviewing the Work of Others:: Some guidelines for sharing reviews.
* Updating the Guix Package:: Updating the Guix package definition.
@@ -2233,10 +2234,8 @@ Teams
and review the work of individuals in its scope (@pxref{Reviewing the
Work of Others}); it can make decisions within its scope, in agreement
with other teams whenever there is overlap or a close connection, and in
-accordance with other project rules such as seeking consensus.
-@c TODO: Currently ``consensus-based decision making'' is discussed
-@c under ``Commit Access''. Move that elsewhere and refer to it from
-@c here.
+accordance with other project rules such as seeking consensus
+(@pxref{Making Decisions}).
As an example, the Python team is responsible for core Python packaging
matters; it can decide to upgrade core Python packages in a dedicated
@@ -2706,6 +2705,25 @@ Cuirass Build Notifications
where each RSS entry contains a link to the Cuirass build details page
of the associated build.
+@node Making Decisions
+@section Making Decisions
+
+@cindex decision making
+@cindex consensus seeking
+It is expected from all contributors, and even more so from committers,
+to help build consensus and make decisions based on consensus. By using
+consensus, we are committed to finding solutions that everyone can live
+with. It implies that no decision is made against significant concerns
+and these concerns are actively resolved with proposals that work for
+everyone.
+
+A contributor (who may or may not have commit access) wishing to block
+a proposal bears a special responsibility for finding alternatives,
+proposing ideas/code or explain the rationale for the status quo to
+resolve the deadlock. To learn what consensus decision making means and
+understand its finer details, you are encouraged to read
+@url{https://www.seedsforchange.org.uk/consensus}.
+
@node Commit Access
@section Commit Access
@@ -2721,19 +2739,10 @@ Commit Access
thought of as a ``badge of honor'' but rather as a responsibility a
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. By using
-consensus, we are committed to finding solutions that everyone can live
-with. It implies that no decision is made against significant concerns
-and these concerns are actively resolved with proposals that work for
-everyone.
-
-A contributor (who may or may not have commit access) wishing to block
-a proposal bears a special responsibility for finding alternatives,
-proposing ideas/code or explain the rationale for the status quo to
-resolve the deadlock. To learn what consensus decision making means and
-understand its finer details, you are encouraged to read
-@url{https://www.seedsforchange.org.uk/consensus}.
+Committers are in a position where they enact technical decisions. Such
+decisions must be made by @emph{actively building consensus} among
+interested parties and stakeholders. @ref{Making Decisions}, for more
+on that.
The following sections explain how to get commit access, how to be ready
to push commits, and the policies and community expectations for commits
@@ -3006,6 +3015,8 @@ Reviewing the Work of Others
the project to keep bikes dry.}. As a reviewer, try hard to explain the
rationale for suggestions you make, and to understand and take into
account the submitter's motivation for doing things in a certain way.
+In other words, build consensus with everyone involved (@pxref{Making
+Decisions}).
@end enumerate
@cindex LGTM, Looks Good To Me
--
2.46.0
next prev parent reply other threads:[~2024-10-14 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 17:28 [bug#73803] [PATCH 0/2] Add "Decision Making" section Ludovic Courtès
2024-10-14 17:30 ` Ludovic Courtès [this message]
2024-10-14 17:30 ` [bug#73803] [PATCH 2/2] doc: Promote “Teams” section Ludovic Courtès
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=af70c561796ff70ef0422c818a2f5d7b1bdd365a.1728926815.git.ludo@gnu.org \
--to=ludo@gnu.org \
--cc=73803@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).