From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 5hjKEDDI+GSAdwAAauVa8A:P1 (envelope-from ) for ; Wed, 06 Sep 2023 20:42:56 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 5hjKEDDI+GSAdwAAauVa8A (envelope-from ) for ; Wed, 06 Sep 2023 20:42:56 +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 AB6E55640D for ; Wed, 6 Sep 2023 20:42:55 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=dkFDUd4G; 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=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1694025776; 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=7Ze0Wil6I4nQ37P4AbMqP5BoliSJI+d1mlEdrSL8kDw=; b=o775MWAtyL4uMh7yklcBitmMu8rQC/VI90M2iBuUt0ERhV+UwCSZuw/LIbV5iROOLPYma0 bgDuIi2C6lrbmdtC87K6Mp/OZmwESFXqOsMquUgfqNZvcXJ4HStpeKvQ/jgm2c7Irr6PzH PlBQnTtq0CClONOeHjqhGLzl7QXARyl83sovi0XCSYhrCmGvagEUl/sPf66JUS6r7HgBN/ SHXPQuEgOAg4S9ML37qvj36/+rlifea4Leb+GMaIqrK8at8g9QdQWAHLZT7ugO2Mwh96Gt irN6RLiHKA1kghbaFsRfl5Bi1fydfSUVX8X5VgSA6MT7Y7QTxSwAKw2Pb2BtbA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1694025776; a=rsa-sha256; cv=none; b=dcXbW4BMLOX6JVsrO/6CMRkjnOaj/VZXxR9zZDCfPBVmCAmv0IKTf+XbSOdGwWCoMvTWTH /tXLLDBAc/ymBER/PQaH+2ZV/wvAiIBute5OqoQjlFldOEDX6YpyHmtyY9qq+ItoV7CaLO KLgn6MihaaWOhpGBGA/EqtEtAqRafKlxNrl7Ujv00y8fLMAROX2BuKdbT+ONzu4iQ5C1sA RXEHQnVGsY2/xXfkRPxUdYzVhsAzLvQkUSNqdsM4cZQngAxpvEKKqres4CZDOvO8Oi37LP vDR1MVDh7Za8m05J8wSuqfUpmGwuRiAp/UzzesfNqWzw4lh+MaFxGk6LCmS06g== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=dkFDUd4G; 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=pass (policy=none) header.from=gmail.com Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qdxU9-00023j-PG; Wed, 06 Sep 2023 14:42:41 -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 1qdxU6-00023C-3R for guix-devel@gnu.org; Wed, 06 Sep 2023 14:42:38 -0400 Received: from mail-ed1-x543.google.com ([2a00:1450:4864:20::543]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qdxU1-0004ds-28 for guix-devel@gnu.org; Wed, 06 Sep 2023 14:42:37 -0400 Received: by mail-ed1-x543.google.com with SMTP id 4fb4d7f45d1cf-522bd411679so111709a12.0 for ; Wed, 06 Sep 2023 11:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694025750; x=1694630550; darn=gnu.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=7Ze0Wil6I4nQ37P4AbMqP5BoliSJI+d1mlEdrSL8kDw=; b=dkFDUd4G9jLBPov/lRly4lcHbR3QRb7JV8nV64o2yDcNMpOxnNogQneabRzCibJ1IY +An67wPTm2gdegCEeFmngLXOOgJJASK6CymhUvS6wsuUo/dUP53qXsEj8MR93E5npBVG 9uWXGHHGB/VLNGf44uAiu+HNBRf4KrYavvTDuM5Digodsj1jIvAw3WDWgMR4X/OF7ldN oqHH8No39nwPXJXzDq7LahKlN3/RCqCVoxHRAtG2VfAl9KjTMMbZ8ssjW9sVKXZDpidv 3Z0Gu/CZ1pKJBqVQTNplDco85Dc2FczDroODJdsm8cm11vE0xE0fVJC7/QqNcIGeA6ez F+Vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694025750; x=1694630550; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=7Ze0Wil6I4nQ37P4AbMqP5BoliSJI+d1mlEdrSL8kDw=; b=MawjgDNxFuXhawHbYjgB6SRpQnd7vmFJrJU6PbfH5TCGtDF3PWiXPGm4HQEwyxBAyM u5ImEeIkSdj3ndHEDcMHBqRCSBjwsf698w3TVKiqNtze0N5Bxs7MbjfWJfT8tWPgFzGe u2M6on9x1D25EFdr07Gwj9E3UljR9XkQI70z/BdlAZfNI+8CbX9vTuRyfGGvyJC0JNf0 h57AyNpo9P6FGjUWedz/DA/7+9XZZANV+d98JDAlR7sYI5uN3xExI8J/lF0Rr0okup34 mCRa21EkrQUeXMnnMPFFjGW51NhROUFc3qy392A2yw5RsURSjBHqMv9VJlO0wCiCxzBC AJ7g== X-Gm-Message-State: AOJu0YyAW2WDOH8cBZHDGFZKGSq6PvN85fjLe6NrTxA0o8FS+IkYJpMv Z1gvR546fM+D4m4xA5olQ7w= X-Google-Smtp-Source: AGHT+IFnPYeFLFifQOrAYMvh1aBmv+Wv5w3LRwwZgrHCUd0gHqLHdwsuj2D9uf2W/tysFTOXh+c3bg== X-Received: by 2002:a17:907:78cd:b0:9a2:b89:f82a with SMTP id kv13-20020a17090778cd00b009a20b89f82amr3034257ejc.49.1694025749980; Wed, 06 Sep 2023 11:42:29 -0700 (PDT) Received: from lumine.fritz.box (85-127-52-93.dsl.dynamic.surfer.at. [85.127.52.93]) by smtp.gmail.com with ESMTPSA id le18-20020a170906ae1200b0099bcbaa242asm9302177ejb.9.2023.09.06.11.42.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Sep 2023 11:42:28 -0700 (PDT) Message-ID: <53a36259a7870cb3e0daa49ae43a75d021e0a969.camel@gmail.com> Subject: Re: How can we decrease the cognitive overhead for contributors? From: Liliana Marie Prikler To: wolf Cc: "(" , Katherine Cox-Buday , Simon Tournier , Maxim Cournoyer , Saku Laesvuori , Attila Lendvai , Andreas Enge , guix-devel@gnu.org Date: Wed, 06 Sep 2023 20:42:26 +0200 In-Reply-To: References: <20230827135726.y33t55w4cvq6zsvb@X-kone> <874jkift8v.fsf@gmail.com> <867cp4sj7k.fsf@gmail.com> <38242808-2f06-4674-3842-aea1a5378d05@gmail.com> <87a5u0o3z2.fsf@disroot.org> <3b274703acaf446ec678e96c9d875c5d6b1a3e17.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 MIME-Version: 1.0 Received-SPF: pass client-ip=2a00:1450:4864:20::543; envelope-from=liliana.prikler@gmail.com; helo=mail-ed1-x543.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, FREEMAIL_FROM=0.001, 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-Scanner: mx0.migadu.com X-Migadu-Spam-Score: -7.09 X-Spam-Score: -7.09 X-Migadu-Queue-Id: AB6E55640D X-TUID: GT8uNMY18Q6t Am Mittwoch, dem 06.09.2023 um 00:04 +0200 schrieb wolf: > On 2023-09-05 22:43:04 +0200, Liliana Marie Prikler wrote: > > Am Dienstag, dem 05.09.2023 um 19:40 +0100 schrieb (: > > > Liliana Marie Prikler writes: > > > > Uhm, we have snippets? > > >=20 > > > Well, those are exclusive to Emacs :)=C2=A0 And without regard to > > > /that/ issue, I do think that there's a problem if the commit > > > format is so complex that it's not trivial for anyone new to the > > > project to write them out manually. > > By definition, no amount of typing is non-trivial, safe for the > > empty amount, which good luck trying to commit your changes by pure > > mouse movements, I guess? > >=20 > > Now, if you excuse my French, I think the problem isn't really as > > much that people struggle to type out the perfect ChangeLog on the > > first try, which also makes it odd to request a linter.=C2=A0 Bear in > > mind that committers will sign off anything that appears convincing > > enough, even if there are smaller mistakes in the message.=C2=A0 Trust > > me, I've been there and seen that; and also done it myself. > >=20 > > Instead, we have seen in this thread appeals to age, appeals to > > perceived lack of personal benefit, and now appeals to typing > > effort, none of which really make that great of an argument against > > the ChangeLog style, especially when they come in combination with > > a refusal to make use of already provided tools. >=20 > I went through the snippets, and through the GNU documentation[0] and > I am still not clear on how exactly should the commit message for a > change in .dir-locals.el look like.=C2=A0 Maybe I did miss some tools or > documentation? Our snippets cover the most common cases, and editing the .dir-locals happens quite rarely :) > The "you can check the commit history for example" advice from the > 22.6 page of documentations gives me 4 different styles in last 4 > commits.=C2=A0 Ok, just joking, 3 styles, the 4th is a typo (`* .dir- > localsl.el: Add ...'). Regarding only the ChangeLog, I see 1.5 styles =E2=80=93 that is "* .dir-locals.el:" and "* .dir-locals.el (some specifier):" Both are okay. Regarding the header, you are free in what to type, since it's at the top directory anyway. > 0: https://www.gnu.org/prep/standards/html_node/Change-Logs.html >=20 > > I think we're starting to see the moving of the goal post as the > > actual game here.=C2=A0 > >=20 > > Maybe it's time to take a step back and instead of asking =E2=80=9CHow = can > > we decrease the cognitive overhead for contributors?=E2=80=9D, we shoul= d > > perhaps ask =E2=80=9CFor which contributors do we want to/can we decrea= se > > the cognitive overhead?=E2=80=9D >=20 > While I do risk taking this slightly more off topic, I personally am > more interested in what can be done to help the committers, not > contributors.=C2=A0 My biggest grievance with trying to contribute is not > the process nor the tools, but the lack of reviews.=C2=A0 Having a patch > sitting there without any reaction nor feedback is frustrating.=C2=A0 Do > you see any process/tooling changes that could help on this front, > even if they would make life harder for the contributors? To be completely honest, mumi recalling everything at 0 precision is my biggest pet peeve at the moment, but I don't think it's solely responsible for the lack of reviews. Even back when it did produce reasonable results, patches were overlooked, which people often worked around by asking for attention e.g. on IRC. I don't think we should make things harder for contributors, but having an interface where e.g. patches that have been unnoticed for about a week or longer can easily be retrieved would definitely make things easier. Also, stuff like finding issues where CI lights green and (non-committer) reviewers have said LGTM would be a big help. I don't see how we could implement this without rolling out a big knowledge graph, though ;)