GNU bug report logs - #66430
[PATCH] doc: Mention the responsibilities that blocking comes with.

Previous Next

Full log

Message #29 received at 66430 <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 66430 <at> debbugs.gnu.org
Subject: Re: [bug#66430] Wording v2 (was Re: [bug#66430] [PATCH] doc: Mention
 the responsibilities that blocking comes with.)
Date: Fri, 13 Oct 2023 08:51:26 +0200

Hi,

On Fri, 13 Oct 2023 at 06:02, Maxim Cournoyer <maxim.cournoyer <at> gmail.com> wrote:

> > 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, without or with commit access, wishing to
> > block a proposal bears a special responsibility for finding
> > alternatives, proposing ideas/code or detailing 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 like it, but I admit I wasn't sure what "detailing the status quo"
> meant until I read your examples below.  Perhaps it could be reworded to
> "explain the rationale for the status quo" ?

Yes, that's better. :-)

Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.