From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.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 eKeuBFwV02YXzgAA62LTzQ:P1 (envelope-from ) for ; Sat, 31 Aug 2024 13:06:36 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id eKeuBFwV02YXzgAA62LTzQ (envelope-from ) for ; Sat, 31 Aug 2024 15:06:36 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=elenq.tech header.s=soverin1 header.b=kRW9teDm; 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=1725109596; 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=PpMtDRZxmpB7FsJqxtOBA4nkgKGxn0fPuMMCvZkEV70=; b=oRxqsX5mdJmy272saOZIsPaCT3D5oIFOT5+WDPpFXtBUAGhi4qmcVeiRWjT/K4xxvpUnqd w39Ph+9fKKDTSd3isBgguJ6JXID8L0QeuA2obxH+AuN4sH6PNLstO/+iyli9IkBLBgcjxF XDfI2d90ky7RzTsP1NPz64i336Wgigio/AlhemZloKdvGREyNYC1hOIzzeD0p9Z0IaafO1 y9/vOoYVGghYYLzgJxfKesZOjAJzseIXSwWC3KJ4JzKbip86RbUyOI49mJ7opWEoTeZaw4 bYJ388fRwOX81DZr4JhlxB76LYsaPdeKI/vLREy2CVNajreKFV6hzCafykIJPQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1725109596; a=rsa-sha256; cv=none; b=BiA6NGUHw49Y5+bYpF8EOm0bTqZokUqVFtlx8ztD3ICVALpHKb2qlZGReQG5GVUVwdXTi3 AeHqvS7Go6DRugRxMB/zikjUPCQff5iDGl0azAkjc0Gaqa8ydFqc66mB3roAU7Gcg7t9tQ ne6yUS7v724B/FjtGmlE/0L5gu7GNjpOlc932MoNrFMTESHTCvong4emCBN6dGaaWWuRmo Hlxq8Ffi9qKYyDk9Llpo8v0XJE0k624P9wyONIY51XrAzAi2p89X3hs3Gqc74y4WC+ok8+ vujaMFa5xiq4p/+NII5zeN2+NI2WchVdgKhjNv9cv8Gh4H4tG+iu6NdtlVdR/g== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=elenq.tech header.s=soverin1 header.b=kRW9teDm; 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" 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 DFA5873185 for ; Sat, 31 Aug 2024 15:06:35 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1skNnw-0005OG-9k; Sat, 31 Aug 2024 09:06:12 -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 1skNns-0005Nj-Mc for guix-devel@gnu.org; Sat, 31 Aug 2024 09:06:08 -0400 Received: from dane.soverin.net ([185.233.34.31]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1skNnn-0002Ah-AG for guix-devel@gnu.org; Sat, 31 Aug 2024 09:06:07 -0400 Received: from smtp.soverin.net (unknown [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 4WwwHq4bVzz2xLr; Sat, 31 Aug 2024 13:05:59 +0000 (UTC) Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.100]) by soverin.net (Postfix) with ESMTPSA id 4WwwHq0MqxzHy; Sat, 31 Aug 2024 13:05:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elenq.tech; s=soverin1; t=1725109559; 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=PpMtDRZxmpB7FsJqxtOBA4nkgKGxn0fPuMMCvZkEV70=; b=kRW9teDm2xBnh+uAZTMl4a4TDQibpYvFh7p5yN8GLgwrDJsXha2spNGwkS1TUaEofZNlqX l0iTO3xgL1X2y17D1459SsM9SqzaHxEukOyqtlDJZ3fqvj1bgb1n3StoM0LNvdutqtcgZE OKUGMHN9jLNjKifvAYommFtnZcQ8S5l0L83q/FBEtYBg7X+h7EVHyLsgVNs+piLu9FVw4b qMiqfiDzS7DNE32q5ZPaorFy/5AHRlGgnOWRm1V0yAzwuML8K79h95r8gb/6OPIuMXHRKB R3ORNNNAjO7GINbcgEs1VLN0xTy71btS69w143oKsjPt1IouTVgApvfPo74mYQ== Message-ID: <58fde3c5-7d74-ee21-0ec8-a1802dcec171@elenq.tech> Date: Sat, 31 Aug 2024 15:05:58 +0200 MIME-Version: 1.0 Subject: Re: Simplify contribution by using user-friendly bug tracker and git interface To: Jan Wielkiewicz Cc: guix-devel@gnu.org References: <20240831003521.5c956363@interia.pl> <57b92ff9-6c6f-2c1b-6c3b-4c3d9daecce2@elenq.tech> <20240831140556.3e47df9f@interia.pl> 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: <20240831140556.3e47df9f@interia.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spampanel-Class: ham Received-SPF: pass client-ip=185.233.34.31; 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, T_SCC_BODY_TEXT_LINE=-0.01 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-Queue-Id: DFA5873185 X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -9.60 X-Spam-Score: -9.60 X-TUID: A6gzFRDKXiua Hi, On 2024-08-31 14:05, Jan Wielkiewicz wrote: > Hello again, > > On Sat, 31 Aug 2024 01:45:04 +0200 > Ekaitz Zarraga wrote: > >> Hi Jan, >> >> >> First, there are tags in the issue system: >> >> https://issues.guix.gnu.org/search?query=tag%3Aeasy >> > > Missed this completely. Where is this documented? In the bottom of the search box, you can show hints and then it suggests to use them. >> >> The issue of friendliness has been brought up in the past, I suggest >> you to search in the mailing list for previous interactions in the >> topic. >> >> In fact, I took part on a discussion about more general topics and I >> mentioned we should be more empathetic with other people's needs: >> https://lists.gnu.org/archive/html/guix-devel/2023-09/msg00488.html >> > > Okay, will read this later. > >> >> Tedious and counterintuitive are very loaded words, and not very >> objective either. The intuitiveness of things is based on the >> previous context people has. This is a GNU project, and the context >> for many GNU developers is autotools, mail based workflow and so on: >> maybe for GNU developers that's the most intuitive thing. Who should >> we please? >> > > I used these words because they convey my feelings related to the > current process. The discoverability of the system is low - every time > I send patches I need to reread documentation to then finding out my > email provider does not cooperate (failing SMTP, having to re-enable > email client support to proceed). So I probably need to change my email > provider in order to contribute to Guix smoothly. This was literally my situation not that long ago. I'll explain more below. > I'm aware this is a GNU project, I'm a free software enthusiast and > GNU/Linux user myself, but I'm not an epic GNU hacker and you can't > expect all contributors (who simply want to update a package they use) > to be epic GNU hackers. I agree with this. We are not expecting that either. That's why I was trying to push for a better documentation. I read your original message as coming from frustration and I don't think you were very empathetic when you wrote it. >> In my case, I find the Github-like PR based approach quite >> counterintuitive, but I got used to it before collaborating in Guix >> and now I don't dislike it. Starting using PRs for everything made me >> a little bit reluctant to try the email based approach. Surprisingly, >> it happens to be way easier than it looks, and it's actually quite >> cool. >> > > Wasn't easy to learn it at first, but running "git push origin" to > update a remote branch linked to a PR is pretty straight-forward. As simple as `git send-email HEAD~`. Our way is not more complex, it's just different. >> You should give it a go: https://git-send-email.io/ >> (If you don't like or you can't use that, you can paste the patches >> in an email, or send them as attachments, which is as difficult as >> taking part in this mailing list.) > > I have this installed and use it, can't send patches to Guix > otherwise... The link is a very good tutorial on how to use git-send-email. I like to share it because it made a huge difference to me. It's just a very short tutorial that explains very well the workflow in a practical way. >> Once you use it for as long as you used other options, I'd love to >> have this conversation with you again (I'm not saying you'd change >> your mind, but the conversation would be fairer). >> >> I will share some thought here that I know many people in the >> community doesn't agree with (and I'm kind of a 50-50 on it) but I >> think it's worth sharing: >> >> >> So, it is true that making the access to things harder than the >> possible minimum is simply stupid. There's no discussion there. >> That being said, it would be very sad if a seasoned software >> developer, who proved to be able to write code for a complex project >> like Guix, is not able, is discouraged to, or is afraid of sending >> the patches via email (but is ok opening an account, making a fork, >> making a pr and so on). > > I'm apparently smart enough to install Guix as my daily driver distro, > learn Emacs with Paredit and hack together packages, and then an > email-based system filters me out... This is a very interesting point and I encourage you to dive deeper on it. In my case I had pushed for a less emacs-centric approach in the docs, and I wrote some parts of the documentation for people that used other editors. I'm not smart enough to use emacs, and I gave up on it, but with the tutorial above I overcame my fears with the email based approach. >> Putting it in a different way: not every contribution is worth >> attention. If people who want to contribute are not able to send an >> email, I don't think their potential contributions would be that >> interesting or worthy. The skills needed to be able to participate in >> Guix are quite advanced, I don't think the email is a burden for >> people that have them. >> So let's say, yes: we do migrate to codeberg.org. And now what? Do >> you think the amount of contributions will skyrocket? Do you think >> the amount of meaningful contributions will be higher? > > Guix is not one thing - updating packages is not the same kind of task > as for example hacking on low-level system or package manager > functionality. I believe simplifying or making contributions more > similar to what other projects have would indeed help. One example > would be a free software game project I take part in. The original > founder of the game did not know git and maintained the game using > GitHub's online editor. Then when he stepped down, we moved the project > to Codeberg. In the very same project we also taught a literal Windows > user how to use git and command line which then enabled him to make > cool and meaningful contributions. And then I myself did several > contributions to Guix while barely knowing what I'm doing. So I'd be > careful with underestimating the power of inexperienced users. Yeah, I can agree with you, but we should as a whole make a cost-benefit analysis of this. Maybe making our current audience uncomfortable just for potential contributions that we don't know how many they can be is not a good idea. We should think about this deeply, and I opposed your email just because it was too categorical and I wanted to share the other side of the coin with you. >> I know what I say here might smell like some intellectual classism or >> something, but if we slow down a little bit: implying that there's a >> lot of people wanting to contribute to Guix and they cannot overcome >> the burden of the tooling we use is a little bit condescending to >> them. > > I'm doing my best to overcome the burden of tooling, but in the very > same time I could just make my own channel with software I want updated > on Codeberg, instead of contributing them to upstream Guix. > This is fine, Guix's nature does not only allow this but also encourage it. In the moment you want to upstream your changes, you'll have my help in the IRC or in the Mailing List to guide you over the process. >> >> *People are smart*. They'll figure out. Our process could be better, >> specially the documentation for newcomers (which btw improved a lot >> recently, and mumi is great), for sure, but, in summary: > > Yeah, the current format of the document makes it easy to overlook > important things, for example there's no header called "Canceling Your > Issue", "Updating Your Patch Series", etc. Codeberg's user interface > makes these things discoverable under nice green/red buttons. > This is way more constructive than your previous email and is very interesting. Suggestions like this help a lot to make a better documentation and become more welcoming and are not radical changes that require a huge agreement in the community. This we can do, right now. About those specific issues, debbugs allows to close the issues by email. Guix documentation shows how to do it with mumi: mumi compose --close But I agree we could do better, and I suggest you to point out all the things you'd like to have and I commit myself to updating the documentation with them. >> >> - I don't dislike the PR style >> - I doubt if using a PR based approach would result in more and >> better contributions >> - Just because something is more popular that the other thing it >> doesn't mean the latter is less intuitive >> - Our process is not more complex, but it might be *new* for people >> - If we provide GOOD documentation, people will understand it >> - We have communication channels (that work) for the cases when >> people gets stuck >> >> >> Those are my thoughts. > > In the end you could argue that it's my own fault for using a > broken/incompetent email provider, but then it's the contribution > system of Guix that exposed this issue as opposed to alternative > systems like web GUIs that usually just work. Perhaps adding "your > email provider may be broken, try using a different one" and "make sure > to enable support for a standalone email clients in your email > settings" to the documentation would help? I spent more time than > needed in my life looking for solutions to fix email sending. > I have had SMTP problems with my previous email provider (protonmail) and I had to paste the patches in the body of the emails, or add them as attachments. It worked, but this was one of the main things that prevented me from trying git-send-email. I am familiar with your issue, and it's really disappointing. I finally changed my provider and my quality of life was improved dramatically. If you don't want to change your provider, which is perfectly ok, you are probably going to find some things a little bit more uncomfortable, but it's still possible. When I had issues with all this, people in the Guix community helped me with the setup, corrected my patches, and encouraged me to be do it better next time. I wasn't scared off by people: nobody here wants that. What I got were some mentors that encouraged me to give the best of myself, not only in this project but also in others. Please correct me if I'm wrong but from your previous message I read you were frustrated and maybe angry about it. From this message I read what you need is just some support. I think I can help. If you want, we can guide you to be more comfortable with the platform and document everything that made your life easier in order to make next person's approach to Guix smoother. > So yeah, that's pretty much it What do you think? Should we start?