From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id SJf4ImGWG2cJTwAAe85BDQ:P1 (envelope-from ) for ; Fri, 25 Oct 2024 13:00:17 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id SJf4ImGWG2cJTwAAe85BDQ (envelope-from ) for ; Fri, 25 Oct 2024 15:00:17 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=worcester.edu header.s=google header.b=J04Aac5C; dmarc=pass (policy=none) header.from=worcester.edu; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1729861217; a=rsa-sha256; cv=none; b=VfwPczGHwseQXjzf5wGwl64ZQYndcMCvntb7/RERAgKmk9/bIMM/ilQ+VrSGor++3F9mmH 2vDlhBkbq6LvPCYi+5BrwLAacQcT6Y0wUy1QXaTGFw2U8u65R57SA58UdS7NfowmJzXS2M jz7jQsqJ1Hl3dpccR4i0ir6b+JJzIcvbGl+XjD2qkaTNkLfz/U0NwhuZvd5T6ERhKBCyjR qafgkJVcL0iQXLYeWQiOVYiCMmmHSz6AVzEA/UVrKgcnKawxhhHr9vRe6L/41gHn2RkfP2 vneLyAwbTs5WQXsQ6huaKTPWm4OymvT8A8YRKej325s2Uo7R8e8LoBhWFNQ2lg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=worcester.edu header.s=google header.b=J04Aac5C; dmarc=pass (policy=none) header.from=worcester.edu; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1729861217; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=Kg2YJWNK+Wuh/kdmc6vVzDBNo3iW7O/WlCijV4xxOTk=; b=J1DSPymE4gZ0YN2PJYgrkHV4tY41H0gQTZig/gIxpPs+kVrD5nlX1Te4gOsIpnGvMNHYyP maEySFftiTKuDEIYn0TBS4JykEBxMP3v3045mFenAfXnMQj5ZPTI2e0NXlQ89+yMNJZ5iP 3cLy6O3SawCYqSEorXdkAhVgKJIhwgYFbaaHotApaTp3d8V/e/UXAuAOLX9H/BgzGlHBKg 2QapIBYLJsingV5fjJCEjZmzk4Dnn0Z/oX4/S+bWdcGd/LW8f2J7CBqyryNfpj6yXLXiD2 EupYV5EySvriVOm4F4W2noQCTaPkC0Z4otJk3LdNf7LAadXZNYql1tAz1nk8Cw== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id F18CA7586E for ; Fri, 25 Oct 2024 15:00:15 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t4JuQ-0008Rd-1G; Fri, 25 Oct 2024 08:59:18 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t4JuL-0008RD-U9 for guix-devel@gnu.org; Fri, 25 Oct 2024 08:59:13 -0400 Received: from mail-qt1-x829.google.com ([2607:f8b0:4864:20::829]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1t4JuJ-0005S0-6q for guix-devel@gnu.org; Fri, 25 Oct 2024 08:59:13 -0400 Received: by mail-qt1-x829.google.com with SMTP id d75a77b69052e-4608e389407so21733371cf.2 for ; Fri, 25 Oct 2024 05:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=worcester.edu; s=google; t=1729861150; x=1730465950; darn=gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Kg2YJWNK+Wuh/kdmc6vVzDBNo3iW7O/WlCijV4xxOTk=; b=J04Aac5Cdo3WnZwuV3BCKtB/Czh5oKDJUAkR9pg0ruIss3nMlTsYFgNAgUPL4PQFEz rkpQfTVr4ToBUSn8BE2me6D6x80VcKUeuaQtHpqld44rrqt1W2UfNh7OueiP5Bo5Elb2 wDWpy+MACsAslrYqn0R7lNNE4eLQFOS6nyvvA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729861150; x=1730465950; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Kg2YJWNK+Wuh/kdmc6vVzDBNo3iW7O/WlCijV4xxOTk=; b=Q8dWbc5KtgWYu/Pec0TtApsbEWiqJ0l7sRAPDK1dYSYEo0kUrBjqf++JaQyQlJXDAq 47efUwl4pEL8vkgB2lKNQFHKQpmU1ecbaGSXAsigjE5znW7V5d4prYUG0LIL0bj3FVW4 PAPY+sYf/JwFQA+m9NgwlIh8vFR1ch/CXecTYVLo2J/QAe2dewUmNH0DcCWO+9w+Riye /kC6vdg/NnNF6l8pLphMmXdl7mZgcQ/srT5/Sv/bl+qHB2o2PlG406qfEhDoiUctqtN2 edSReAn3wWd0NW093oGxrxyuZKcOtW07OJpzyktmWE3t5nRXdom2W5sMnABvYrnjjgd8 z0wA== X-Gm-Message-State: AOJu0Yx2rpzQuEdGtV2+peYKKcP9UU5xUVP+gJWjc7IGbMq6EijHcKY5 VTjEuhQNdHqlkGMWnWLqXTGBjMVY+UdS7XA9Gt3Cao+/7uz4IEluZ8jZyO5UnLZYLOjAaF0a8XX y1JRqP6TP+xaDRfnvleKZ3C8efo1ScG3B9q6sJe8hEBiC8q1wqcU= X-Google-Smtp-Source: AGHT+IGrYA2ZJZuX3dZzdyfZtzb/MkTBwMaevKizbRVHjburm8KVYyCdrqRVA6+bC3O8+H/oO7XngYKy/ZzAV8uJnJQ= X-Received: by 2002:a05:622a:cf:b0:461:2061:19a2 with SMTP id d75a77b69052e-461258d14demr54919201cf.29.1729861149552; Fri, 25 Oct 2024 05:59:09 -0700 (PDT) MIME-Version: 1.0 References: <6daee7b4-a5d6-4f80-bbfa-995e65e17ae0@elenq.tech> In-Reply-To: <6daee7b4-a5d6-4f80-bbfa-995e65e17ae0@elenq.tech> From: "Thompson, David" Date: Fri, 25 Oct 2024 08:58:58 -0400 Message-ID: Subject: Re: Discussion on Guix funding // future To: Ekaitz Zarraga Cc: "guix-devel\\@gnu.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::829; envelope-from=dthompson2@worcester.edu; helo=mail-qt1-x829.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.51 X-Spam-Score: -3.51 X-Migadu-Queue-Id: F18CA7586E X-Migadu-Scanner: mx10.migadu.com X-TUID: lZtGshrs5mfj Hey Ekaitz, I'm chiming in because I've been working on FOSS full-time for the past 2 years. Maybe it will be of some use. On Thu, Oct 24, 2024 at 6:08=E2=80=AFPM Ekaitz Zarraga = wrote: > > Hi, > > Recently I've been discussing with other members of the Guix community > about several things we consider we could be improved. > > The most important one in my opinion is the funding. I don't know (does > anybody know?) how Guix is funded, and it worries me. > > I've been funded to work on the bootstrapping part of Guix by NlNet > grants. I've been extremely lucky, and I'm very grateful for it. And I > tried to spread the money, paying people who deserved it. > > Grants are great for specific issues, but we are not going to make Guix > survive using only that kind of grants. I agree. NLnet is wonderful, but it should be considered a supplemental form of funding for very specific projects. Your bootstrapping work and Juli Sims' Goblins+Shepherd work are great examples. In the specific case of NLnet, its future is uncertain due to the EU potentially defunding it. A sustainable project *must* seek a diverse set of funding sources. > First of all, these grants don't pay much, and they are just for a year > or so. Many of us have the technical skills to get a job that pays way > more than a grant and is way more stable. This makes doing something > ethical and good become a punishment, and it's forcing many people to > choose. Most of the people don't have the privilege to choose. Very true. The amount that NLnet pays and the structure of those payments means it is not an option for me as I need stable full-time employment. > Second, grants work kind of well for specific tasks, but what happens > with the structural work? Is anybody actually getting paid for it? > > Finally, grants push individuals to try to do things, but don't > encourage collective action (also the amounts are not high enough for > collective action). That's not necessarily bad, but those individual > projects also drain energy from those who are structural to Guix. > Patches have to be reviewed, and commits need to be merged. We have not found these "side grants", if you will, draining at Spritely. Yes, there is review work, but it has been very manageable and it's a great way to make progress on specific objectives that the full-time staff cannot focus on themselves. We find interested partners and pitch all sorts of things to NLnet and see what sticks. > On a side note, I think we are missing reviewers, maintainers and > commiters, and I think that view is shared in the community. Let's use > my case as an example: I raised my hand to become a commiter, and I > don't know how that was lost in the mailboxes and nothing happened. At > this moment, I don't care anymore: when I need to make a commit, I know > there's people that trust me and I just ping them and they do it for me. > Should I bother people try to get commit access again? My life is very > comfortable as is... Some questions come again to my mind: Am I really > ready for the challenge? Am I going to be a good commiter? Is it fair to > continue like I am right now? I'd like to use this opportunity to say that the Guix project needs to stop relying upon email for *everything*. Whom amongst us doesn't have an overflowing inbox where they lose track of things? The email-based patch review workflow is particularly terrible. Newcomers by-and-large *do not* want to figure out how to send a patch over email and the review process is extremely clunky compared to literally any Git forge with a pull request feature. And I dare say it's inconvenient for experienced Guix contributors, too. It drives me bonkers. The mumi interface to debbugs makes things better, but Guix desperately needs to leave debbugs and Savannah behind for a forge from this millenium. > This issue and some others could be fixed with money. Simple, huh? Piece of cake! (Fundraising is a full-time job.) > I think we should try to invest more on the people, and that probably > means paying them for the work they do. At least to some, so they can > invest more time and care in others. > > This we can't do with grants with the NlNet flavor. We need other kind > of approach. > > Sovereign Tech Fund has a very interesting model for maintainers, but > still lacks the ability to invest on people freely. Is the Guix Foundation (https://foundation.guix.info/) the official non-profit for Guix? In addition to finding grants and large donors... is there an easy way for Guix to collect donations from individual supporters? The Guix Foundation website says they accept wire transfer and in-person donation at events. That's cool but there needs to be a donate button on the Guix website that makes it very easy to donate with a credit card. > Many people has been thanklessly working for this project, and some will > continue to anyway, but not having a proper funding model is probably > keeping us in an uncomfortable situation. The lack of people is pushing > away new people, and we are in a vicious circle where I think people > that are less stubborn than me just go spend time on other projects. I heard some speculation that the number of new contributors is on the decline? Is this true? I think this partly a funding/governance issue and partly a tools issue, as mentioned above. It is simply *too difficult* to submit a patch to Guix and it is *too annoying* to do code review through email. > We have had cases of people giving too much for the project for too > long. I don't think we acknowledge that enough, and probably we should. > We should take care of our people. > > > I think free software projects use to be precarious and we are too used > to that. However, I think we should try to break with that image, and > try to push for funding collectively, so we can cover structural costs: > people and machines. =F0=9F=92=AF > I think I'm just somehow sharing my will to help, and also trying to > encourage some conversation about the funding and how we could do > better. If anyone has ideas, please share. The biggest questions for me are: Who makes decisions right now? Who is handling money? What's the overlap? I know there's a desire for collective decision making, which is great, but *right now* I think a smaller group of core people (Ludovic + some others) needs to put a structure in place because it feels like nothing will happen otherwise. A little bit of benevolent dictatorish action could really get the ball rolling here. For example, I periodically express that Guix should break from the GNU FSDG and create its own guidelines. Each time I do, I'm informed that there's no structure in place to make such a decision so nothing changes. When the project started, Ludovic made a commitment to follow those guidelines in order to be approved as a free distro by GNU. Times have certainly changed, to say the least, but now that the project is bigger it can't adapt accordingly. Ludovic recently said the next step is to get an RFC process in place. Sure... who makes the call on that? > On a second (and last) side note, I also discussed with some members of > the community about the status of Guile. I may send separate email for > that, but it would be great if we could use some of the energy we have > to give Guile some love. We are too Guile-dependent to just let it rot. Definitely best for another thread, but I'll just say: I don't think Guile has been left to rot, but things have been moving too slowly and Andy/Ludovic are spread too thin. The Guile 3.0.10 release happened because Spritely paid for it in the form of Andy's contractor hours so he'd have the time to focus on it. I have told both Andy and Ludovic that I think Guile could use at least 1 additional maintainer that is focused on, ahem, "developer experience". Keeping up with the patch queue, improving documentation, ease of use, etc. I'll save further comments for a guile-devel thread, should you make one. :) Thanks for getting the conversation started! - Dave