all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Tai <atai@atai.org>
To: guix-devel@gnu.org, Juliana Sims <juli@incana.org>
Subject: Re: Guix (and Guile's) promise, and how to (hopefully) get there
Date: Sat, 26 Oct 2024 17:05:11 -0700	[thread overview]
Message-ID: <CAJsg1E_Tf0Ec5VwgXDBak=8jdx0eurUUdmLEr7o-2wPikmiucQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.1757.1729980481.21403.guix-devel@gnu.org>

With due respect, I disagree with that.

Guix recent years has seen growing interests and contributions, so
many patches that the they are not reviewed or processed in a timely
manner.   This is with affiliation with GNU.  I contributed to Guix
because it is GNU.

In fact I just contact the FSF about contribution to Guix with small
donations periodically. I am in the US and financially contribution to
the FSF is tax deductible and the FSF has a better track record of
efficient use of contributions than most other non profits (as
regulated by the US Government Internal Revenue Service).  Financially
many free software nonproifts are having issues (per recent article in
lwn.net) and the FSF is in better shape than these (with questions on
their abilities to raise income and expenses) in that article.  So it
is not clear where the FSF lost its financial capital.

So my observation is inconsistent with what Juliana wrote in this part.

On Sat, Oct 26, 2024 Juliana Sims wrote:
>
> ...Guix should break with GNU and the FSF. Moreso the FSF, but the two
> are irrevocably intertwined in the public conscious -- which is the
> primary reason Guix needs to break away. To avoid relitigating what has
> been litigated more than sufficiently already, the FSF made a bad
> political move that has destroyed its social capital and, as a
> side-effect, its financial capital as well. Even if it can help us with
> funding, it shouldn't.
>
> I think so. As I noted above, if we break with GNU, I am highly
> confident we will see an uptick in new contributors, at least some of
> whom can help there.


       reply	other threads:[~2024-10-27  0:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1757.1729980481.21403.guix-devel@gnu.org>
2024-10-27  0:05 ` Andy Tai [this message]
2024-10-28 16:33 Guix (and Guile's) promise, and how to (hopefully) get there spacecadet
2024-10-30 23:43 ` Tomas Volf
  -- strict thread matches above, loose matches on Subject: below --
2024-10-26 22:02 Juliana Sims
2024-10-27  1:01 ` Ekaitz Zarraga
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
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='CAJsg1E_Tf0Ec5VwgXDBak=8jdx0eurUUdmLEr7o-2wPikmiucQ@mail.gmail.com' \
    --to=atai@atai.org \
    --cc=guix-devel@gnu.org \
    --cc=juli@incana.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.