all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 66430@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#66430] [PATCH v3] doc: Mention the responsibilities that blocking comes with.
Date: Tue, 31 Oct 2023 10:34:06 +0100	[thread overview]
Message-ID: <87pm0vyw35.fsf@gmail.com> (raw)
In-Reply-To: <651c8c1faba688a5ac0dff1edc25c02cea249634.1697288813.git.maxim.cournoyer@gmail.com>

Hi,

On sam., 14 oct. 2023 at 09:06, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> * doc/contributing.texi (Commit Access): Mention that blocking comes with
> extra responsibilities.

[...]

>  doc/contributing.texi | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)

[...]

> +@url{https://www.seedsforchange.org.uk/consensus}.  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 (which 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
> +<https://www.seedsforchange.org.uk/consensus>.

I will push this change soon if there is no more comment.

Cheers,
simon




  reply	other threads:[~2023-10-31 11:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  2:01 [bug#66430] [PATCH] doc: Mention the responsibilities that blocking comes with Maxim Cournoyer
2023-10-10  3:49 ` 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 [this message]
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=87pm0vyw35.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=66430@debbugs.gnu.org \
    --cc=ludo@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 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.