all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 66430@debbugs.gnu.org
Subject: [bug#66430] [PATCH v2] doc: Mention the responsibilities that blocking comes with.
Date: Sat, 14 Oct 2023 09:05:06 -0400	[thread overview]
Message-ID: <87r0lx4anx.fsf@gmail.com> (raw)
In-Reply-To: <87pm1isgm8.fsf@gmail.com> (Simon Tournier's message of "Fri, 13 Oct 2023 17:10:23 +0200")

Hello,

Simon Tournier <zimon.toutoune@gmail.com> writes:

> Hi Maxim,
>
> On Fri, 13 Oct 2023 at 10:38, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> +                                                                       A
>> +participant wishing to block a proposal bears a special responsibility
>
> The term “participant” could appear unclear when reading the complete
> section «Commit Access».  Instead, I propose:
>
>     contributor, without or with commit access,
>
> IMHO, it makes clearer what are the expectations on both sides:
> reviewer and submitter.
>
> Aside this comment, it is LGTM.  But it is better to wait more
> comments. :-)

I've reworded it like so:

--8<---------------cut here---------------start------------->8---
modified   doc/contributing.texi
@@ -2036,11 +2036,12 @@ Commit Access
 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
-participant 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>.
+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>.
 
 The following sections explain how to get commit access, how to be ready
 to push commits, and the policies and community expectations for commits
--8<---------------cut here---------------end--------------->8---

I'll push a v3 shortly and let it sit there to let enough time for
others to chime in if they wish

-- 
Thanks,
Maxim




  reply	other threads:[~2023-10-14 13:05 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 [this message]
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=87r0lx4anx.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=66430@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@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.