From: "Ludovic Courtès" <ludo@gnu.org>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: Christine Lemmer-Webber <cwebber@dustycloud.org>,
"Thompson, David" <dthompson2@worcester.edu>,
guix-devel@gnu.org
Subject: Re: Guix (and Guile's) promise, and how to (hopefully) get there
Date: Wed, 30 Oct 2024 00:04:42 +0100 [thread overview]
Message-ID: <87bjz2mrxx.fsf@gnu.org> (raw)
In-Reply-To: <af782a87-9ecc-4088-8a58-834ca4e59a3d@elenq.tech> (Ekaitz Zarraga's message of "Sun, 27 Oct 2024 02:38:36 +0200")
Hi,
Ekaitz Zarraga <ekaitz@elenq.tech> skribis:
> On 2024-10-26 22:22, Ludovic Courtès wrote:
>
>> We have enough money, about 50k€ currently at the FSF plus a couple
>> thousand € at Guix Foundation⁰.
>
> So we rely on the FSF for the funding, mostly.
To be clear, the FSF is not sponsoring Guix or funding its development;
it is acting as a fiscal sponsor (read: a bank) here.
[...]
>>> - Is the Guix Foundation the way to do it?
>> It is one way to do it, yes.
>
> Should we invest on making it **The Way**?
My personal take: yes, we should do that.
> 0. Is the donate page in guix.gnu.org up to date? Maybe we should make
> sure it is, and maybe include the Guix Foundation?
>
> 1. Adopt an RFC process. I think it's valuable.
>
> 2. Decide if we want to invest on the Guix Foundation:
> - What is the status of it? Is it a fully functional organization?
> - Can we use the Guix Foundation for, for example, Tax exempt
> donations in the EU? And the US? Maybe some famous streamer could
> use their platform to make fundraisers for the Guix
> Foundation. (see what the Zig Software Foundation does)
> - Could we use the Guix Foundation to make a minimal Business (I
> hate that word) model to make a Guix-based product to get funds to
> improve Guix itself? Say, make a Guix hosting service? Currently
> most of us are throwing money to corporations for our small
> servers and would be happy to redirect that to something we love,
> while also having a great Guix based workflow.
> - Or maybe some of us could make that model and donate all or part
> of the profits to the Guix Foundation? (I think owning the
> hardware helps a lot)
>
> 3. Once we have money we can use, choose some people to maintain the
> infrastructure and pay them.
> - Can we really afford our machines? (are we paying for all of them?
> what are we going to do with the ones that are in a basement
> somewhere?)
> - Is Guix sustainable?
>
> 4. Maybe decide if we want to have paid
> maintainers/security-maintainers or committers (or teams!).
>
> 5. Relieve weight from people that have too much on their shoulders. I
> won't name names, but some of you are in the border to the burnout.
> - How could the rest of us mitigate that? Maybe it's time to speak
> and ask for help.
>
> 6. Propose more committers. Encourage committers to review patches,
> and also non-committers! (Steve, you are doing a valuable thing)
>
> 7. Add documentation about Guix's infrastructure to the Contributing
> section of the manual, so anyone can pay attention to that part of
> Guix too. I'll try to do that myself, if someone else is committed to
> commit it ;)
>
> Those points we could act on in the short/mid-term, or at least give
> us some direction.
>
> What do you think, am I missing something?
> Maybe some of the calls to action you don't like? Are they practical enough?
I have reservations regarding #3: we have enough money for machines but
not for people, and we’re not set up to pay people apart from
bounties/stipends maybe.
But really: all good directions to invest in and points to address,
I agree!
Ludo’.
next prev parent reply other threads:[~2024-10-29 23:05 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 22:08 Discussion on Guix funding // future Ekaitz Zarraga
2024-10-25 8:12 ` Steve George
2024-10-25 9:11 ` Ricardo Wurmus
2024-10-25 9:16 ` Ekaitz Zarraga
2024-10-25 9:37 ` Ricardo Wurmus
2024-10-25 11:05 ` indieterminacy
2024-10-25 11:22 ` Steve George
2024-10-25 11:51 ` indieterminacy
2024-10-25 12:05 ` Efraim Flashner
2024-10-26 17:16 ` Tomas Volf
2024-10-25 11:06 ` Steve George
2024-10-25 12:13 ` Ricardo Wurmus
2024-10-25 12:18 ` Efraim Flashner
2024-10-25 15:49 ` Steve George
2024-10-25 12:58 ` Thompson, David
2024-10-25 14:31 ` Christopher Howard
2024-10-26 6:57 ` Steve George
2024-10-28 16:47 ` Christopher Howard
2024-10-25 19:13 ` Ekaitz Zarraga
2024-10-25 23:25 ` Attila Lendvai
2024-10-26 12:49 ` Greg Hogan
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 [this message]
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
2024-10-28 9:21 ` Discussion on Guix funding // future Andreas Enge
2024-10-26 15:04 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
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
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
[not found] <mailman.1757.1729980481.21403.guix-devel@gnu.org>
2024-10-27 0:05 ` Andy Tai
2024-10-28 16:33 spacecadet
2024-10-30 23:43 ` Tomas Volf
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bjz2mrxx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=dthompson2@worcester.edu \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).