all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Juliana Sims <juli@incana.org>
Cc: guix-devel@gnu.org, suhailsingh247@gmail.com
Subject: Re: Guix (and Guile's) promise, and how to (hopefully) get there
Date: Sun, 27 Oct 2024 02:01:20 +0100	[thread overview]
Message-ID: <02559f63-35e6-4159-9d4c-e1d423aad3be@elenq.tech> (raw)
In-Reply-To: <J8HZLS.QBAJ7DPOPKFR@incana.org>

Hi Juliana,

I like some of the points you do here: we should encourage committers to 
review patches, and give commit access to those that are focused on that.

On the other hand, I disagree with your message about GNU and the FSF.

First, I don't think the sentiment you describe about GNU and the FSF is 
universal. It's probably biased by the people you interact with and the 
country you live in. That's not something for me to criticize,  you have 
your views and they are valid, the problem with your argument is the 
same I find with the "let's use a Git forge, that'll give use many new 
contributors!".

It's just really hard to measure.

I wish being a GNU project was the only problem Guix had. The sad truth 
is we'd probably had the same conversation if the project was just Guix, 
with no GNU and no FSF support involved. Furthermore, we'd probably be 
in a worse position, at least economically speaking.

I understand the recent news make us be a little bit heated about the 
FSF and so on, but I don't think it's a central matter of this discussion.

It's probably going to encourage a division in the community as many 
members are here **because** this is a FSF endorsed distribution. Being 
a GNU/FSF project still means a lot to many, and when it comes to the 
free software purism, those acronyms still have some credibility.

Maybe without those we'd be just empty. We don't know. So I prefer to be 
more cautious with the arguments.

Thanks for highlighting the work of these community members and for your 
thoughts.

Ekaitz



  reply	other threads:[~2024-10-27  1:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 22:02 Guix (and Guile's) promise, and how to (hopefully) get there Juliana Sims
2024-10-27  1:01 ` Ekaitz Zarraga [this message]
2024-10-27 10:00   ` indieterminacy
2024-10-27 10:47     ` Ekaitz Zarraga
2024-10-27 11:39       ` indieterminacy
2024-10-28  9:43         ` Ricardo Wurmus
2024-10-27 18:12       ` paul
2024-10-27 19:13         ` Ekaitz Zarraga
2024-10-27 21:31           ` Thompson, David
2024-10-27 22:19             ` Ekaitz Zarraga
2024-10-27 22:22             ` Suhail Singh
2024-10-28 10:12               ` Efraim Flashner
2024-10-28 14:07                 ` Suhail Singh
2024-10-28 10:07             ` Ricardo Wurmus
2024-10-27 23:42           ` paul
2024-10-28  9:53           ` Ricardo Wurmus
2024-10-28 10:01             ` Ekaitz Zarraga
  -- strict thread matches above, loose matches on Subject: below --
2024-10-28 16:33 spacecadet
2024-10-30 23:43 ` Tomas Volf
     [not found] <mailman.1757.1729980481.21403.guix-devel@gnu.org>
2024-10-27  0:05 ` Andy Tai
2024-10-24 22:08 Discussion on Guix funding // future Ekaitz Zarraga
2024-10-25 12:58 ` Thompson, David
2024-10-26 13:48   ` Guix (and Guile's) promise, and how to (hopefully) get there Christine Lemmer-Webber
2024-10-26 14:49     ` Ekaitz Zarraga
2024-10-26 20:22       ` Ludovic Courtès
2024-10-27  0:38         ` Ekaitz Zarraga
2024-10-29 23:04           ` Ludovic Courtès
2024-10-28 10:09         ` Andreas Enge
2024-10-28 10:20         ` Andreas Enge
2024-10-26 16:40     ` Suhail Singh
2024-10-26 22:07       ` Ludovic Courtès
2024-10-27  1:33         ` Suhail Singh
2024-10-26 22:28       ` indieterminacy
2024-10-26 21:12     ` Ludovic Courtès

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=02559f63-35e6-4159-9d4c-e1d423aad3be@elenq.tech \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=juli@incana.org \
    --cc=suhailsingh247@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.