From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 62246@debbugs.gnu.org
Subject: [bug#62246] [PATCH] doc: Add a reference to a page explaining consensus decision making.
Date: Tue, 11 Apr 2023 11:58:54 -0400 [thread overview]
Message-ID: <87fs96mmv5.fsf@gmail.com> (raw)
In-Reply-To: <87cz4d7y6b.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Sun, 09 Apr 2023 19:39:08 +0200")
Hi Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Hi Maxim and all.
>
> Maxim added to doc/contributing.texi:
>> It is expected from all contributors, and even more so from
>> committers, to collaborate in a consensus decision making
>> fashion. To learn what consensus decision making means and
>> understand its finer details, you are encouraged to read
>> @url{https://www.seedsforchange.org.uk/consensus}.
>
> Only now, that it is already pushed, have I taken the time to read
> (or, at some point, skim) the link.
>
> I just want to acclaim:
>
> * I agree with the addition of this kind of writing.
>
> * Seeds for Change is more politically left than I first expected, and
> the consensus sub-page uses not only examples that chime well with
> free software and Outreachy, but also one-sided views on issues like
> housing. Perhaps such examples will prompt dissent in the future.
>
> It would have been an option (a worse option) to add consensus
> decision making to the manual without linking to such an extensive
> text.
>
> Nonetheless, the way it is written, the manual asks for agreement
> with consensus decision making, not with Seeds for Change or the
> examples on the consensus page. I still agree with making people
> learn from the link.
>
> * It is good that, when there is little feedback, you have pushed it.
> Seeds for Change say: take “sufficient time”, but IMHO you did and
> more time would not have helped. Also you had already taken steps
> like writing to guix-devel and generally applied the Seeds’
> recommendations.
Glad you found it pertinent. I had read the whole thing for the first
time, and found it had useful tricks or suggestions, and was good at
clearing any misunderstandings I had about consensus decision making.
I hope others find it useful too!
--
Thanks,
Maxim
prev parent reply other threads:[~2023-04-11 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 20:22 [bug#62246] [PATCH] doc: Add a reference to a page explaining consensus decision making Maxim Cournoyer
2023-03-26 21:35 ` Ludovic Courtès
2023-03-28 15:15 ` Maxim Cournoyer
2023-04-03 20:02 ` bug#62246: " Maxim Cournoyer
2023-04-09 17:39 ` [bug#62246] " pelzflorian (Florian Pelz)
2023-04-11 15:58 ` Maxim Cournoyer [this message]
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=87fs96mmv5.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=62246@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.