From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id cJYLDBPuG2ep9wAAqHPOHw:P1 (envelope-from ) for ; Fri, 25 Oct 2024 19:14:27 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id cJYLDBPuG2ep9wAAqHPOHw (envelope-from ) for ; Fri, 25 Oct 2024 21:14:27 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=elenq.tech header.s=soverin1 header.b=F8qC5Ury; dmarc=none; 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=1729883667; a=rsa-sha256; cv=none; b=WWwmnF8ocWjWATBTpB/tOqiEN6B29TaTfR/XwbN/Fe7unlpV3JiTdHJSQLxRs6qyVEjU2L 4Ef9YcUpgmzure4x4PKF3MPxWxxNj2bJ37Kbkr1OK85zxYF4dhYKIUM/kRvyrQyocFDUQP m+VIRKjdqTUjb5xLArotZCb2+yKba+jyjTlQnB+VuQrYJqcVW4pxn9QiokvKySrTdgFx25 eV6WK5KiDOxxqwYVUuLE3kPaaFC0qUpYFHUP3X+TwHCFQEuX+2kBfpoj202BVgN0/bsgLV 5ETbyQevGuv4XejnVBKuNnP2GQdMfLxvkH9CDI3yE46diwkOcuIxXxFXRTf5vg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=elenq.tech header.s=soverin1 header.b=F8qC5Ury; dmarc=none; 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=1729883667; 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:autocrypt:autocrypt; bh=mJrmd1ulgqocutt4Y0u1df7HhEbauU4gKfwqKlNw7yM=; b=KFwiOYPJXkE/2mavPy1nqaoKvcMcSqznjACkyNm0tNvA++M20zQ962tcjCYOac57SvENzx r+pqI5lUgLp2CTZGpX+vpSI8r8Sn1YBQzGuzAoVX6fL22XPr5oQRUUmvhDx2WMqJmEzTGE FBG3V5jf6k8L93tyGOa3E2ZxOS37/lTQqywuofp6W4dWfXtiCBnzCBSJ3CjhUvVAb31AAg 99BJhwusFoXr6sLCE1Prx5LqZIQnDll2ZyqsFiwUrhV4sOrjexknZWr/TA9OeXgL9swSbV OHwUJf5+OwLswWXz9czFrI7vOsSABkCoiuypYcDOhF6A4aoGV09UKm6GQ/EW6Q== 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 F0A07645EF for ; Fri, 25 Oct 2024 21:14:26 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t4Pku-0006fi-Qi; Fri, 25 Oct 2024 15:13:54 -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 1t4Pkr-0006fT-1L for guix-devel@gnu.org; Fri, 25 Oct 2024 15:13:49 -0400 Received: from dane.soverin.net ([2a10:de80:1:4091:b9e9:221e:0:1]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1t4Pkn-00034a-Nz for guix-devel@gnu.org; Fri, 25 Oct 2024 15:13:48 -0400 Received: from smtp.soverin.net (c04smtp-lb01.int.sover.in [10.10.4.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dane.soverin.net (Postfix) with ESMTPS id 4XZsrg2pwcz2xcp; Fri, 25 Oct 2024 19:13:39 +0000 (UTC) Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.100]) by soverin.net (Postfix) with ESMTPSA id 4XZsrf6ZFczK5; Fri, 25 Oct 2024 19:13:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elenq.tech; s=soverin1; t=1729883619; h=from:from: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:autocrypt:autocrypt; bh=mJrmd1ulgqocutt4Y0u1df7HhEbauU4gKfwqKlNw7yM=; b=F8qC5Urye9D+K954ynERsHOuwuEKHSQfoGyNCWqQvKkCb5yfcsf4tjbCQmUmTegxwM/3TP +8ZiDRpyNZX1SGDLmNlIuIc0allCjyBTb3R3wi4SSJywE2Sf0SZEXW0pJk1QxnV94qVhha BJqn94FovrtnldeQdnMXShgEYrXRTB8UzYfaKSYfvVtt1g/hQEorScz24d1PYckxN8kR4W u5zOVYTFij3g9XMJLfx77go06HLBZWVWO4Gj7QHRoqD3usWu3i7lOYShIne71GyWXI/JIv qvKpP6FJWSbBI+WouOw4tsizB0t6f5siHAm8GKJxc1L5h3Xbwi4LG4r5v0ws0g== Message-ID: <8c3b99d1-f348-439e-9379-73fbbd6a239d@elenq.tech> Date: Fri, 25 Oct 2024 21:13:37 +0200 MIME-Version: 1.0 Subject: Re: Discussion on Guix funding // future To: "Thompson, David" Cc: "guix-devel\\@gnu.org" References: <6daee7b4-a5d6-4f80-bbfa-995e65e17ae0@elenq.tech> Content-Language: en-US, es-ES, eu From: Ekaitz Zarraga Autocrypt: addr=ekaitz@elenq.tech; keydata= xsFNBGViSyIBEADY3g71uW/0CVaVm5/ObqTicQXXJRuh1uafIFiUUZoAp1V3V89b3LZ/m0cL 8YNHxTxsx8sKIMYTGlOvARAMiSpDvkmpf5pLn5T7+VvK90FOv/Pkp1tNNT+tvd0m/7C58+39 s7tN+XppbjVRtFuSXY0aFe8rpivZsKxv+tPUHUnQQszXvwgx0GQl8AX99IE+j75NJmBHFVg2 0geKa7QVymu669ix2+zU8vGoOKf5nIS0qG1m/vrtwR3ZuuyWX9/E/uP95ahX5ETWtjhTDbEm MEaRperwbczBewkdERJ34vRrverqKQA1xHXoPsx4NkLMocORFSSCJsveXcgWlU+pUIOYcKUA ARJjHhoWoUH4LZt5EOb7U17AaYMmATUXPCqq8G3jEXq6i0O1J1obCJGIRG02R9GiGp4zrVuv 2hmyoAmed4xYZAtf9WjcbwiunDkMGIxscdSlfEH/9dt7PGdEvkZ0dNSCTbp4ctMI4jAfobAL LReMSGx1CgPi01J61a/n/SgR66AiRJZCyC1u2V7AK1rBOAYzOU4UoePz+yF1I7crjZWAQVo6 DlmmXW+29l/lh2oK5jOuNEcvI6qi+tPCYxpDhUhZeYgqFU+/xgGlMj/XGvwuIFlpVg9ovFMg 6mxskOCVP9xNEp/qHiHqByYu5NRcITo/z/3BUimdXTT4KSq2cQARAQABzSJFa2FpdHogWmFy cmFnYSA8ZWthaXR6QGVsZW5xLnRlY2g+wsGOBBMBCAA4FiEEg/pnRVjAUpRlfkwZt5lM+Jly CyYFAmViSyICGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQt5lM+JlyCybjZxAAy+YW 3Q22xKoMWJYw03qGCy87WPK+xGWDpKD6TJ77+/IEbldObyQRrKYTTGjQSy6WgaJ0txJMIqeK JyuWuR3bq+Vkh86Byntl25jknOJ+jY1zwPs6HnWFr+hS48FcQh/0D26h57Cqc+6nbKhJcva8 JsInbHTbWPz7wye+xhqY1LfdgVTbCyADESXdmBY30/vP4LzqW81atwYF6X7dN7ko/JvyPPdv VlcspmbP6zNihoApBHdMfJwYscyAsu6tTyL4hMG3zpraeU+S857vZN39gFagRng+uyZG7rfB dHHAFzT1LKOZ4dahavOfA0gS1RZTgtAGsvhUEBn9vKxlB4efZuKhwMtgQEskRFD6JIF1DYCj pLgn5x/y3oI6rn35R46VDhLfohcUWpvzplu6LBft8ZNr+UgoVYc6qBezyDlxk0FmhGI7DEoh gfUxljTALXjSdUGEw2mvp/Mcrz+ffemWpG4+Zq0UXR8sZaHpv+PqmFLFFSQCOCRTYbMKzZBn y03wym3y0tGtunDGm5pR7NEPqUO9QbZdKyTy4ftRkSfTpiPCF8+KKYDT8HimSrusmtTfR4R1 nBJ4lNBYgTdOyJYFbHdF0Jxo9r0t+K2e+6hX6bK79o6aC+/LtzkoYgjCWvAEopO0ras/XQYM S7/bCzeDIhXX5RqmMIp5XN+oBP2roZDOwU0EZWJLIgEQAMIgPDpJY9aOhFiFICx58XMM28An yUPdN39t0A8VkUbsvKXH6eNqUZj/Q3yNcZrknAT1vinv9FN/4uCUnsaqEKp+mRAYgzmNfeJk SWuMzmA04fcISIBz3sJUR0w/59tWi8QxlNn7IR6McAA3lHDXC+KYh9ZfhaOARfan1M6Ppy6g YltUQGSSPXU807inmQZh8GFTi8iUza7vGuBEnaNRGhmhR+blMwHSqVWN4gD81e8dSAEi3zNR sLoBXneHUqTcJMHvsT5cOk7cGMoVAWIffA2EKWfrgda57Qw+w+0OPqWEfKoXwnyt35Tl+Lxl 7MAaAG9R5760yhgkf3LmnBNP3m6StZ8Fv09Gdn5cGSbVnoofHDkg4PQDTD6aGz9af3SnGVg9 nb1Zm1XbqtnYwG9JvQhcjgWAHwrPLkHAcvKtfYWNe4wiirMjXMXxADY08g33SEchPJR2r4pg wttJS4kHUJ2IQUmSH/43RO5PkftWsCucYGeaG1aPr+GAkeKIS1M3OZGuqhd800mltpiH73eL XrUPF8fgngC+SGMrHXLfzuhaRxPNYUbsdF+wRkvjRSO4tCmSVpgfPsHu5emoZgix1iiTO7GF do7L6n1Ay3oF4Witoxc0Gcbu7ltYlZHGmDnsVTVALartsJV2muSXpWcjQiXyC0gUkIkUD/3P jtgVxK8xABEBAAHCwXYEGAEIACAWIQSD+mdFWMBSlGV+TBm3mUz4mXILJgUCZWJLIgIbDAAK CRC3mUz4mXILJrIaD/9CXGckwRCojuRzP0r6+8/RvNDc03CSe2W17WrSaoYgiRb+h5asI/AL yqw+QRgwXZpt0i9hNiDCe/baD62mufIyjKFjHoAWSYJuZ5VK3vWnro6GaxWULYt1+c4c4Lz2 d1nSK6j8F3CxYo7BFk6afOusjYfh+0HywThcYY+x+K5Z+4SdJejDLiL5AzJn2W5Gt/ViK5nI wl7uRQpayMc9zmI8ytUT2NJxovq1/fT9nB8VPwlbJTE9zvIqfqHh9o9Apx5o8yTaSCyGUyu9 8h/klqxFy4HAPJJu/3JkiMaCI45ZdCqRR1LIwhtmW2lb73r0rP/0S1cKi+ehA4oQvwiUw7zh XXw7mqzSAJ0SWT92Vy2G8Z8qqgwxwfQcdFZAyJAL1rgEPQljNT91Vgbc6DCUka2XW5BqyhEB eS0n1gK0hYXbM9FKegRsZxlmRAXa4KGXCwr4BNK6k+zkKPitezjbtcLgcKSHa8/HyHNkW7xH R+MN16x2elQPmQ2d0Ien1HgsK98+3prlUGwZIVCqa1ddSoW0llU3JzGsKrMAiYbWg/rOXFil RJbuhjflaLBVmfI8VlRQRocP+WEH0lsUWrtjVaGcBj1/YnIoT+zT6fPSXwPsrBvAWEjfl8HH e1F4cYb+ugPDwUTd1s2Uj2tF0/fhCHPy9sXyx/EIL3gqyBw9M2Rz9A== In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spampanel-Class: ham Received-SPF: pass client-ip=2a10:de80:1:4091:b9e9:221e:0:1; envelope-from=ekaitz@elenq.tech; helo=dane.soverin.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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_LOW=-0.7, 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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -1.07 X-Spam-Score: -1.07 X-Migadu-Queue-Id: F0A07645EF X-Migadu-Scanner: mx12.migadu.com X-TUID: 22/cman5Gb3s Hi, We mostly agree with everything so let me focus on the points I were I'd like to add more. Thanks for adding your thoughts, they are really valuable. On 2024-10-25 14:58, Thompson, David wrote: > 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. I don't think this is the most important part of the problem, but it's really hard to measure. I think the level of technical proficiency a project like Guix demands is high enough to ensure that people who take part on it are able to use the email for their goals. It is weird for them, but I think that's something they can get over. (we could also discuss about English being a problem for most of the world, and here I am, talking in my third language) In most cases I saw, just some help via IRC or email makes people send their first patch and feel really accomplished. (This mentoring needs people and time to invest) The main problem I think comes later, when the contributor made all the effort to send the email and then no one answers back. If the first effort didn't kill the process, the lack of response murders any possible future contribution. I don't want to focus the conversation on this part, the forge vs email (maybe there's a way to support both). What we should discuss is the fact that is topic is really hard to discuss or make it to something we can apply. Things take too much time because, in practice, I don't think we have a governance model. > 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. A big part of this email is to try to be more clear about this. I think Guix Foundation is too separate from Guix, or the relation is not clear. How does the FSF take part in the funding? Is the Guix Foundation competing with it somehow or they collaborate or...? It should be easier to access and donate to from Guix's own website. Maybe also to accept large donations from the companies or organizations that need Guix to work well. I'm sure there has to be some. > 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. I think solving the governance issue would enable further action later. > 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. Exactly. It's a really tricky situation. I think we all look to Ludovic when something needs to happen. And I don't think he (hi!) needs to feel that kind of pressure. > Ludovic recently said > the next step is to get an RFC process in place. Sure... who makes the > call on that? I think Steve is working on it on top of what Simon did, and I'm happy to collaborate on that. > 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. :) I will, but I'll send it with guix-devel included, because I think that as connected as both are, we should blur the line totally and take more part on Guile. Your thoughts here David are a little bit biased to your position, where you have some of Andy's attention (you paid for it, this is also relevant to the topic of the email). Mine are biased to the other direction: in the last 3 years I had a little attention (or none) from Guile's side. I ported lightening (guile's JIT, a project that is managed by Andy, separately) to RISC-V but I have trouble fixing a segfault it has. I pass all the tests but in the last 3 years I had no help with that segfault, and I didn't see any effort to review my changes. I'm sure with a little bit of help I we could make it work, as all the boring part is done. But here we are, still, years later. I'm not blaming people, but this is very discouraging. I'll open the thread. Let's see if with help we can do guile thrive as it deserves. > Thanks for getting the conversation started! Thank you for your thoughts.