all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Maxime Devos <maximedevos@telenet.be>,
	 Nicolas Graves <ngraves@ngraves.fr>,
	guix-devel@gnu.org
Subject: Re: rust-build-system from antioxidant
Date: Mon, 12 Jun 2023 09:34:28 -0700	[thread overview]
Message-ID: <CAFHYt55A=nSA4Op-Sx-HLrpQVAKFF9uaC6txpWDv8h46JKGeMA@mail.gmail.com> (raw)
In-Reply-To: <87y1kobtw3.fsf@wireframe>

Hi Vagrant,

On Mon, Jun 12, 2023 at 8:09 AM Vagrant Cascadian <vagrant@debian.org> wrote:
>
> everything kind of has a social component!

Thank you for pointing that out! Many technical discussions about
project governance claim high moral ground but remain incomplete.

Maxime possibly felt some righteous indignation because Maxim's
well-intended reference to consensus does not actually apply in Guix
that often. (I have to be careful to keep both your names in order.)
It would be ignorant to claim that there are no power structures.

Not all of them are official, but they are there. [1] Hierarchies are
human, and they are not always bad.

During the past year, I made some ambitious proposals that did not
resonate with the general public or any of the folks in power. (I am a
member of the general public.) Some committers told me privately that
nothing big happens without the maintainer collective.

Someone in the maintainer collective told me that nothing truly
important (like legal stuff) happens without Ludo'.

Of course, that expectation places an extraordinary burden on Ludo',
who already works very hard. I don't think he (or maybe "they") even
wants all that responsibility. Personally, I find Ludo' measured and
generous.

That being said, everyone makes mistakes. Sometimes, words are
misunderstood. At other times, the merit of an argument is overlooked.
Maybe that's what happened in the bug Maxime cited. Or maybe Maxime
made a mistake with that narrow, unfavorable and critical assessment.
Either way, it's important to have goodwill toward one another.

I know a little bit about how large groups can work together. For the
past nine years, I have been a minor city official in a bustling
community of 230,000 immigrants—mostly from India and China, with 158
languages spoken at home. The key is to keep solving the community's
problems and also, to solve other people's problems in addition to my
own.

In Jewish mysticism, there is an old story about a giant vessel that
once existed when the world was made. Unfortunately, it broke into a
gazillion pieces, and we each ended up with a little shard. We spend
the remainder of our lives looking for other pieces that fit.

Let's be proud of our large and diverse community. Let's focus on the
pieces that fit together. Thank you all for being here!

Kind regards
Felix

[1] https://guix.gnu.org/blog/2022/gnu-guix-maintainer-rotation/


  reply	other threads:[~2023-06-13  4:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 18:02 rust-build-system from antioxidant Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-08 17:55 ` Maxime Devos
2023-06-12  1:17   ` Maxim Cournoyer
2023-06-12 10:10     ` Maxime Devos
2023-06-12 13:05       ` Maxim Cournoyer
2023-06-14 13:02         ` Maxime Devos
2023-07-02 20:12       ` Overruling and blocking Ludovic Courtès
2023-06-12 15:08     ` rust-build-system from antioxidant Vagrant Cascadian
2023-06-12 16:34       ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-06-16 13:53         ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-17  0:51           ` Maxim Cournoyer

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='CAFHYt55A=nSA4Op-Sx-HLrpQVAKFF9uaC6txpWDv8h46JKGeMA@mail.gmail.com' \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=maximedevos@telenet.be \
    --cc=ngraves@ngraves.fr \
    --cc=vagrant@debian.org \
    /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.