From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id wPvwIDbD7WRl6AAA9RJhRA:P1 (envelope-from ) for ; Tue, 29 Aug 2023 12:06:46 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id wPvwIDbD7WRl6AAA9RJhRA (envelope-from ) for ; Tue, 29 Aug 2023 12:06:46 +0200 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 678C536EB7 for ; Tue, 29 Aug 2023 12:06:46 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=msavoritias.me header.s=20210930 header.b=iZr3KNDu; 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"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=msavoritias.me (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1693303606; 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=urCDWGLKvofj7/NxrMzNHjHOBZ+SedHhVcWbdJs90eQ=; b=lwNpg5oir9eDQ1DsB7gbECEBw2Ocs/X4941olCqstCZ+s82tv84VzNeHKpzflkwYOYXsRr cqgwtv+b8PBZc5UQvIWGRcJ/sRhC2ZhV29iMzndKneG6aA+8h0KvPDVDZh8QDkzQ5DKgLT 3TjnXlAkhQS4iYGhcWkdILZ3Fc4jaVFo2hCAyXYxl8eCSY/aUjkdFYzA6r4eMNzPixDOgD 0Aju4Zh4TCT43VcTwrCt129CvzCLAwTwL8Cb0HrTW1raiPq35vP0GIHQJ1wE/c+8MhUuC4 1PcUkZhsZI9EEXV/Dw6jSheT+t7NBHjLYw6VzczzRXrI+kPQOv37Dg4MFiO5Fw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=msavoritias.me header.s=20210930 header.b=iZr3KNDu; 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"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=msavoritias.me (policy=none) ARC-Seal: i=1; s=key1; d=yhetil.org; t=1693303606; a=rsa-sha256; cv=none; b=dE/bdaUTOCwJSw22oXRoPH/sga06OacxJfmgCHc6McW6dxZeulzECy0+SAI9BJzpHP8z17 tv+gaNtjDKx3BcQi/DOCw9b05dzJ9hAdxZASafPw0nMxer7ckQXPwfnlP+ROlwNWaahwu6 OMvpKmMZV0h8pFdOo0fTjMmdGaCPf2Qi/SKyFvVJhgC85AmNRst58UOlDb5XzmdW5bhuyw R9hp+kZ2ME1wY7sKwQ3lSbfHwKmtYmzthIjTIGYjkyyhPXIHwlW5kP5Iscm8i8r1uWxeHf QftN46yrLz8LKblT0m3e9lJja52/NV/Ha1WAFDld1KyuIwgR6NZJvh7US0GbpA== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qavc4-0006pU-Vp; Tue, 29 Aug 2023 06:06:21 -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 1qavc3-0006ne-ES for guix-devel@gnu.org; Tue, 29 Aug 2023 06:06:19 -0400 Received: from mail.webarch.email ([81.95.52.48]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qavbz-000526-4Z for guix-devel@gnu.org; Tue, 29 Aug 2023 06:06:19 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 3F5D61A8CFCF; Tue, 29 Aug 2023 11:06:02 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msavoritias.me; s=20210930; t=1693303572; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=urCDWGLKvofj7/NxrMzNHjHOBZ+SedHhVcWbdJs90eQ=; b=iZr3KNDux5Aj9L3ylCsnlAtvuCtvCYLvoAkyR84GqeqmnDNJJDDfWRKrUq81HXs//yMWNw syspF38EFE6/r31tKnzplLFaBovQmlqkQ6AFX2fLRjC+7sTdlXTYU/7+eVCkoqqFidXljV a3oV1YCYeYO3wPBDtdNZTY3HPRSLW/BadgCtP55CIBhIHs6wlCjhYMVuS9bXa2k+DdlQYA PjUJPRAfa2miEd6pVNWFB60eFErSBqvscnwOqjqcbDRuEHdxOkdUE8xwlK0swTkaKn0pQY 5DNqz/GsLIYTl41QP8LA4a48q3sMVs7Jj88xSL1phIx/CclEJ77WJec0L9M0yw== References: <20230827135726.y33t55w4cvq6zsvb@X-kone> User-agent: mu4e 1.10.5; emacs 28.2 From: MSavoritias To: Liliana Marie Prikler Cc: Saku Laesvuori , Attila Lendvai , Andreas Enge , Katherine Cox-Buday , guix-devel@gnu.org Subject: Re: How can we decrease the cognitive overhead for contributors? Date: Tue, 29 Aug 2023 13:04:31 +0300 In-reply-to: Message-ID: <873502qi2e.fsf@fannys.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Last-TLS-Session-Version: TLSv1.3 Received-SPF: pass client-ip=81.95.52.48; envelope-from=email@msavoritias.me; helo=mail.webarch.email X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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-Scanner: mx2.migadu.com X-Migadu-Spam-Score: 1.28 X-Spam-Score: 1.28 X-Migadu-Queue-Id: 678C536EB7 X-TUID: SIPdXE9+Z84V Liliana Marie Prikler writes: > Hi, > > Am Sonntag, dem 27.08.2023 um 16:57 +0300 schrieb Saku Laesvuori: >> > >=20 >> > not sure how most people consume their emails nowadays, but for me >> > it's one flat list per thread, in a browser (i.e. it's not a tree). >>=20 >> The point is that the emails contain the information on how to >> construct a tree out of them. It's just that most web clients (which >> most people are unfortunately using nowadays) are so bad that they >> render the tree as a flat list. > Not sure about "most", but Guix folk are definitely biased towards > dedicated mail clients (terminal, graphical, Emacs=E2=80=A6), so perhaps = my own > perception was a little off in that people will always benefit from > having the tree. Then again, you can share your email between multiple > clients, which isn't that easy to do with code repositories sadly. =C2=A0 > > Of course, you can mirror the repo, but your bug trackers aren't that > easily mirrored. > >>=20 >> > and all i'm trying to achieve here is to move the discussion away >> > from email-is-superior-period, to look at what requiremenets we >> > have and what tools satisfy them, if any. >>=20 >> I think that is a good discussion to have, but I think it would be >> better to describe some of the requirements you think we should >> consider instead of just saying email isn't superior. It might not >> be, but it might also be. We should consider what we need and >> evaluate the available tools based on that, and if the result is that >> email is the best then it is. > Not needing to register yet another account for one-off contributions > is an argument that kills all the forges, sadly :) > With Sourcehut you can contribute without an account. There is also https://forgefed.org/ which is for federated forges using activitypub. So you can have one account for all forges that federate. :D MSavoritias >> > > at the ChatGPT-related stuff that has been submitted). There >> > > sadly is no pleasing everyone here and unless these tools are >> > > incredibly simple to maintain, the utilitarian approach of least >> > > misery leads you to plain email. >> >=20 >> > but is a least-misery model appropriate here? how do you even >> > account for the contributions that could have happened in a >> > different environment, but did not happen? >> >=20 >> > similarly, e.g. demanding a dated ChangeLog format for commit >> > messages has a filtering effect on who will contribute, and then >> > who will stick around. most engineers have a hard time jumping >> > through hoops that they find pointless (git automatically encodes >> > that information), and i'd suggest considering what the effect are >> > of such rules on Guix asan emergent order. >>=20 >> I agree on the ChangeLogs being a weird thing to require in commit >> messages. I think of commit messages as the place where you record >> the reasons behind the change in the commit. The ChangeLog seems to >> just record the changes which the diff of the commit already >> automatically records more accurately. > First things first, I disagree with the framing here. Engineers do > pointless things all the time and both code style and commit message > style have near endless potential for bikeshedding (which we are > currently engaged in btw). There are like thirteen competing standards > on how to format C code and similar debates in other languages. In > fact, I'd go so far as to argue that a language ecosystem that has no > such debate is potentially lacking in diversity. > > A proper ChangeLog doesn't simply "record the changes the diff already > records more accurately". It adds semantics. For instance, when > bumping a package, we write the same line twice; once for the header, > once for the ChangeLog. What we don't write is that we also adjusted > the hash along with the version. Doing so would give us no new > information, but the diff includes it anyway, because diffs are stupid. > Humans writing (and reading) ChangeLogs aren't stupid and can rely on > contextual meta-information =E2=80=93 however, the ChangeLog should still= be > self-contained in the sense that it doesn't rely on other parts of the > message to infer the actual changes made. > >> If someone has use cases for the ChangeLog commits, I'd like to hear >> them. Maybe there is something that can't be achieved with git >> history without ChangeLogs, but I can't think of anything. Someone >> mentioned grepping the git log with them, but I think the same thing >> can be done with git log and git blame regardless of the commit >> message format. > In my humble opinion, you underestimate the benefits of not having to > invoke another command on a commit. For a great number of changes, the > ChangeLog style allows me to imagine the code that was written without > having to see it in a way that a simple diffstat just can't. Of > course, whether you use ChangeLog style commit messages, Emoji commits > or any other formatting guide is a political question between everyone > involved in a project, but there are benefits to having guidelines and > following them. =C2=A0 > > It's similar to following generally accepted etiquette in any circle.=20 > People will generally be happy as long as you follow them and can often > tolerate small deviations, but at a certain point it just becomes > uncomfortable, so we kindly ask you to follow the established > practices. > > Cheers