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: Sat, 26 Oct 2024 22:22:09 +0200 [thread overview]
Message-ID: <87ldyar4we.fsf@gnu.org> (raw)
In-Reply-To: <a5f0ae2d-68dc-4656-9c46-cc8dadaf482d@elenq.tech> (Ekaitz Zarraga's message of "Sat, 26 Oct 2024 16:49:13 +0200")
Hi!
Before I reply to Christine’s insightful message, here’s my
Chief Visionary *cough* view on the questions you ask:
Ekaitz Zarraga <ekaitz@elenq.tech> skribis:
> - Do we need independent funding so we can pay for our machines and
> maintenance?
We have enough money, about 50k€ currently at the FSF plus a couple
thousand € at Guix Foundation⁰.
⁰ There’s a ledger at
<https://framagit.org/guix-europe/guix-europe/-/blob/main/accounting/accounting.ledger>
but I don’t remember how to get the balance with the ‘ledger’ command.
:-)
> - Is the Guix Foundation the way to do it?
It is one way to do it, yes.
> - Does GNU, or the FSF, have some role on that?
GNU isn’t a legal structure, it “doesn’t exist” so to speak.
The FSF reimburses when we send them invoices; Guix Foundation can pay
services, hardware, etc. directly, which is more convenient.
My preference would be to have a single structure, to improve legibility
and simplify things, and that structure would not be the FSF.
> - Can we improve anything relieving weight from the shoulders of some
> people instead of putting even more on them?
Yes! Committers can review code; people interested in governance can
help with the next steps, in particular the RFC process at
<https://issues.guix.gnu.org/66844>; sysadmins/devops/hackers can help
with the infrastructure¹; and so on.
These are some of the thankless tasks that are key to a healthy project
and where we must ensure a fair distribution of work to avoid burnout.
¹ https://lists.gnu.org/archive/html/guix-devel/2024-05/msg00183.html
> - Would having more committers help relieve some of the weight?
Only if they participate in code review.
> - If so, should we propose commit access to people, instead of waiting
> them to propose themselves?
We should. I think maintainers started doing it?
> - Should we ease the process of becoming a committer?
Do you think the process is difficult? Or intimidating maybe?
Ludo’.
next prev parent reply other threads:[~2024-10-26 20:22 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldyar4we.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 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.