From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.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 YAhgGbVx6GTDwAAASxT56A (envelope-from ) for ; Fri, 25 Aug 2023 11:17:41 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id eEdAGbVx6GT2igAAauVa8A (envelope-from ) for ; Fri, 25 Aug 2023 11:17:41 +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 2B8F757FF5 for ; Fri, 25 Aug 2023 11:17:41 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=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"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1692955061; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=u94IXmelSljKEZNshN9PiBTZZN3zQkpd6lWEj3iIXqs=; b=i+7rmNLGnXZz/qU6xxNilZCMG/T7JxhUxLs4z2pHvhZ261I7E8tadVLe8FD6sy7WS2XNiB nxrNY+GmuF+LIvCvMM2u6WJPGI1xl1hWtSm+BpuL5nf9Ph3QHqoK99xTQjZGFkPF3iS/oa CwTUq8/ezSJsNXxjVGt9IR1X7l01ntM8k4QW9PZXkTSQbLKLNecLQ99DwHjQ6DckF5dhPp uIYHlw6FwIMUNvyY0trzkl7L8esevppe51niIdhGsUq5QXteZ3iTZvezATWnUJROBvt9xQ /l0QLCGfcS9Nwmgs9WchKRj282weG0IYbI7oxOMFaq0Z52Y+E6Y4H3VFgaR6Kg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=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"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1692955061; a=rsa-sha256; cv=none; b=LBpdX/N8xQLFPWrg0E9fhDZ25zORzKnJ4D0HUDlVhMTP8GeyuCB+ukWMAfMLXoBOAnrA6D TG1MEiZDoNJGaZAQPsf+BunYDhbvXW3TO08hzUnv3tX2j1VCMuBdqf5/I1G95VdtmPd07C ydogzAUA8VZ+gkJ279tG9UmS2QuZhWKPhamDU2fTuhegVsmXv61Dp8DepGg4JxCjZI+B2k B5zz0pvV8drGryvFTFjPnH2GHqFJ7IXI+RdmnB+uGCxPHAftMjXZ666do7oijJrBkvAerx OYmPZky3A3eMqVjKiDDaT2JLDbCFkV3t0tH0kCE7vIoxJHwcevpV02XVxoD4Bg== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qZSwL-0000lh-3A; Fri, 25 Aug 2023 05:17:13 -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 1qZSwH-0000iF-Nb for guix-devel@gnu.org; Fri, 25 Aug 2023 05:17:09 -0400 Received: from hera.aquilenet.fr ([185.233.100.1]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qZSwC-0008W2-7g for guix-devel@gnu.org; Fri, 25 Aug 2023 05:17:06 -0400 Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id DF1D0BCD; Fri, 25 Aug 2023 11:16:59 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at hera.aquilenet.fr Received: from hera.aquilenet.fr ([127.0.0.1]) by localhost (hera.aquilenet.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qRWp2WoHlY0; Fri, 25 Aug 2023 11:16:59 +0200 (CEST) Received: from jurong (unknown [IPv6:2001:861:c4:f2f0::c64]) by hera.aquilenet.fr (Postfix) with ESMTPSA id 3609A298; Fri, 25 Aug 2023 11:16:59 +0200 (CEST) Date: Fri, 25 Aug 2023 11:16:57 +0200 From: Andreas Enge To: Attila Lendvai Cc: guix-devel@gnu.org, Katherine Cox-Buday Subject: Re: How can we decrease the cognitive overhead for contributors? Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=185.233.100.1; envelope-from=andreas@enge.fr; helo=hera.aquilenet.fr X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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: mx2.migadu.com X-Migadu-Spam-Score: -4.71 X-Spam-Score: -4.71 X-Migadu-Queue-Id: 2B8F757FF5 X-TUID: 00r7z6UzIq05 Hello, just a quick reply with what I do personally as one irrelevant data point :) Am Fri, Aug 25, 2023 at 08:07:53AM +0000 schrieb Attila Lendvai: > i couldn't even find out which tools are used by those who are comfortable with the email based workflow. i looked around once, even in the manual, but maybe i should look again. No tools at all, I would say, which indeed may be a bit inefficient... Or: terminal, mutt, vim, git A bit of web for browsing the manuals (of Guix and Guile) and issues.guix.gnu.org But then I type much faster than I click. > i'm pretty sure most maintainers have a setup where the emailed patches can be applied to a new branch with a single press of a button, otherwise it'd be hell of a time-waster. mutt save message to /tmp/x git am /tmp/x or something like this or: git clone https://git.guix-patches.cbaines.net/guix-patches/ git checkout issue-xxxxx git format-patch ... then in the development checkout of Guix: git am ...; make; ./pre-inst-env guix build > one fundamental issue with the email based workflow is that its underlying data model simply does not formally encode enough information to be able to implement a slick workflow and frontend. e.g. with a PR based model the obsolete versions of a PR is hidden until needed (rarely). the email based model is just a flat list of messages that includes all the past mistakes, and the by now irrelevant versions. For this, I either go to issues.guix.gnu.org to download the newest patches, in case the message is not in my inbox. Otherwise I do not get your point: I keep untreated messages with the latest patch version in my Guix inbox, and file away the others in a separate mbox. So things are not flat, but have two levels: "to be treated" or "done". Nothing to be documented, really, and I do not know whether these are just personal habits or whether others work similarly. These might be the ways of an aging non-emacs hacker... > https://sourcehut.org/ This comes up a lot in the discussion and looks like an interesting solution. It would be nice to be able to accomodate diverse styles of working on Guix beyond (but including) emacs and vim. Andreas