unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 66430@debbugs.gnu.org
Subject: [bug#66430] [PATCH] doc: Mention the responsibilities that blocking comes with.
Date: Wed, 11 Oct 2023 23:10:13 +0200	[thread overview]
Message-ID: <87h6mwrhl6.fsf@gnu.org> (raw)
In-Reply-To: <5760a46dfc1b97312d1d5512ebf1bd21da6707f5.1696903067.git.maxim.cournoyer@gmail.com> (Maxim Cournoyer's message of "Mon, 9 Oct 2023 22:01:56 -0400")

Hi!

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> * doc/contributing.texi (Commit Access): Mention that blocking comes with
> extra responsibilities.
>
> Change-Id: I27cafcb351f68057b7882198e72e9bf66ccc1262

(Oh, what does this line mean?)

> +@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.

I’m unsure about this.  A situation I have in mind is this: a volunteer
writes a review describing issues with a proposed change that have no
obvious solution, or rejecting the change altogether (for instance
because it’s deemed outside the scope of the project or tool).

How would one interpret the reviewer’s responsibility in this case?

Thanks,
Ludo’.

PS: We really need a process for changes to our collective rules.




  parent reply	other threads:[~2023-10-11 21:11 UTC|newest]

Thread overview: 19+ 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-11  9:30 ` Simon Tournier
2023-10-11 21:10 ` Ludovic Courtès [this message]
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

  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=87h6mwrhl6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=66430@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).