From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 66430@debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#66430] [PATCH] doc: Mention the responsibilities that blocking comes with.
Date: Mon, 9 Oct 2023 22:01:56 -0400 [thread overview]
Message-ID: <5760a46dfc1b97312d1d5512ebf1bd21da6707f5.1696903067.git.maxim.cournoyer@gmail.com> (raw)
* doc/contributing.texi (Commit Access): Mention that blocking comes with
extra responsibilities.
Change-Id: I27cafcb351f68057b7882198e72e9bf66ccc1262
---
doc/contributing.texi | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 864190b119..082a288704 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -2030,7 +2030,11 @@ Commit Access
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}.
+@url{https://www.seedsforchange.org.uk/consensus}. The project uses the
+@samp{Requiring people who block to help find solutions} block variant,
+which means a participant wishing to block a proposal bears a
+special responsibility for finding alternatives and proposing ideas/code
+to resolve the deadlock.
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: 7937c8827b8d23347a3159b4696335bd19fc17aa
--
2.41.0
next reply other threads:[~2023-10-10 2:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 2:01 Maxim Cournoyer [this message]
2023-10-10 3:49 ` [PATCH] doc: Mention the responsibilities that blocking comes with Maxim Cournoyer
2023-10-11 9:30 ` [bug#66430] " Simon Tournier
2023-10-11 21:10 ` Ludovic Courtès
2023-10-12 17:08 ` Maxim Cournoyer
2023-11-05 17:19 ` Ludovic Courtès
2023-11-07 18:05 ` Maxim Cournoyer
2023-10-12 19:17 ` Simon Tournier
2023-10-12 20:18 ` [bug#66430] Wording v2 (was Re: [bug#66430] [PATCH] doc: Mention the responsibilities that blocking comes with.) Simon Tournier
2023-10-13 4:02 ` Maxim Cournoyer
2023-10-13 6:51 ` Simon Tournier
2023-10-13 4:02 ` Maxim Cournoyer
2023-10-13 14:38 ` [bug#66430] [PATCH v2] doc: Mention the responsibilities that blocking comes with Maxim Cournoyer
2023-10-13 15:10 ` Simon Tournier
2023-10-14 13:05 ` Maxim Cournoyer
2023-10-14 13:06 ` [bug#66430] [PATCH v3] " Maxim Cournoyer
2023-10-31 9:34 ` Simon Tournier
2023-10-31 13:30 ` Maxim Cournoyer
2024-02-02 21:55 ` André Batista
2024-02-03 9:32 ` bug#66430: " Simon Tournier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5760a46dfc1b97312d1d5512ebf1bd21da6707f5.1696903067.git.maxim.cournoyer@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=66430@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.