From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) by sourceware.org (Postfix) with ESMTPS id 04D2E385B532 for ; Mon, 6 May 2024 13:58:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 04D2E385B532 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=kitware.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kitware.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 04D2E385B532 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::830 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1715003927; cv=none; b=hkmWxZ+causIgT6VJHMCIA+ypHLWynKOcAHUyHrLeLnkxtRD/dUqMcj0F5XJ7kUQXOQsvPzUk7o+NyTt7RHIz8749jhSx+iwwz16mIULnl5DXHfU6GAdXxahuEuui6KvGDKNnPN08L9PMxcdEky72KhEPqNlU2vdoOJhXk45FOs= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1715003927; c=relaxed/simple; bh=w6yA+jGgVeOkmVWfYVbtBhL1xgYXZCuBXU0yfhA8cbE=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=kNEq58MPALKsxk21rsH8bx+MVwGuKplDPN3SOE8u3uT6YRPLZOqDtC4P42D43dORwS8g60eIKxHhrUBBU0LCJaKEFuliEEEieA91D1qoUxF4KrvgOsut9s58KvD2fmtA0TxHM7l/JSDG8vm+c7qNS8VH8Hu2WioUqf14tkXwnow= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-qt1-x830.google.com with SMTP id d75a77b69052e-43d3a33d41dso10003531cf.1 for ; Mon, 06 May 2024 06:58:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kitware.com; s=google; t=1715003924; x=1715608724; darn=gcc.gnu.org; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=+x7r4JdTZXYSug8ngAwP9SpEDq71GklkTtsYUTc5Vqc=; b=EGZoc4XiKS8ZeYvZ2qzK0iyaB5LjpEyRPWMQ71FwmdwsQE1wsy6ycJlC1WWY/gGrbO mE/Ce3CEL0mvfPP+Cic9XxjjLs1ymWMpGADLZn4IQTz724cbVpHCqI9QqjtCs0JYfbZZ /QEr1u9c5CmiOvDxcNjGuudrDbMo9oS+Cjmbs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715003924; x=1715608724; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+x7r4JdTZXYSug8ngAwP9SpEDq71GklkTtsYUTc5Vqc=; b=MlpJ34nnWuFy/95DsVw+4wy8A6yGst/Vz0XySYujvA3ZsLc6CevEQEOYutErS4V53l tZgkoKoEPqQGf33bMnTFT+ytYaP7uJGqiMUerqT9mvEutQe6X8kOoPtP3/GwoqkAUsqI uLAzyD8WHaKIYKYq+SFIsJzpRIJmGfIJNH4eQRF9iZqnK2x6zN00gXwiXdwDJtXphmqD biwSNbygWvTrFHRKL6pthJIOYFiI6/9w2qiYlAkSKWR7Ia1E5S90Z9RSZPalFApwEBhc mKtqzgGPf+r1xwmHUIHCu+dSpqbBElHOwu/2z5hVX4niFNeEQU1dxb05jXKepb7Xp1cU SZrw== X-Forwarded-Encrypted: i=1; AJvYcCUfPJxqdEmJBdG3GjPesYRV0agRtx8s5ADVmToIFQtYlY5mhPu8un6roMLTfnjkgI7ou/T0qoGg4k0hI1EBoyM= X-Gm-Message-State: AOJu0YxcaE5lkanee1a7Byexq/aZcJ0GuC+UXixHlDllfwB9mrjrRUto cR3LrIPhUFldp5paMrRRuhUPE732YyFBTH43+xOHzyponwmCJ96jnLhRYGvDMQ== X-Google-Smtp-Source: AGHT+IHDO+b9aSKeU/mgUcijCTEYCjsuUBcrrE+sWVssLd+f1xw7bI8g6V4FXxRvAcGe0ndx2sJp3w== X-Received: by 2002:ac8:5911:0:b0:43a:cbe9:2e32 with SMTP id 17-20020ac85911000000b0043acbe92e32mr12077344qty.55.1715003924097; Mon, 06 May 2024 06:58:44 -0700 (PDT) Received: from localhost (syn-142-105-146-128.res.spectrum.com. [142.105.146.128]) by smtp.gmail.com with ESMTPSA id bq24-20020a05622a1c1800b00437acb8a6basm5156857qtb.6.2024.05.06.06.58.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 May 2024 06:58:43 -0700 (PDT) Date: Mon, 6 May 2024 09:58:41 -0400 From: Ben Boeckel To: Benson Muite Cc: Overseers mailing list , Mark Wielaard , Jeff Law , Joseph Myers , libc-alpha@sourceware.org, Jason Merrill , gcc@gcc.gnu.org, gdb@sourceware.org, Sergio Durigan Junior , binutils@sourceware.org, Tom Tromey Subject: Re: Updated Sourceware infrastructure plans Message-ID: References: <20240418173726.GD9069@redhat.com> <87v849qudy.fsf@tromey.com> <87wmooep76.fsf@tromey.com> <0347e05a-94c6-4ecc-aa8f-cc90358a813d@gmail.com> <0d0af1d9-21f8-4c60-ad4c-cd82c0c0cabb@redhat.com> <20240501212618.GB6469@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Sun, May 05, 2024 at 08:22:12 +0300, Benson Muite wrote: > On 04/05/2024 22.56, Ben Boeckel via Overseers wrote: > > As a fellow FOSS maintainer I definitely appreciate the benefit of being > > email-based (`mutt` is far better at wrangling notifications from > > umpteen places than…well basically any website is at even their own), > > but as a *contributor* it is utterly opaque. It's not always clear if my > > patch has been seen, if it is waiting on maintainer time, or for me to > > do something. After one review, what is the courtesy time before pushing > > a new patchset to avoid a review "crossing in the night" as I push more > > patches? Did I get everyone that commented on the patch the first time > > in the Cc list properly? Is a discussion considered resolved (FWIW, > > Github is annoying with its conversation resolution behavior IMO; > > GitLab's explicit closing is much better). Has it been merged? To the > > right place? And that's for patches I author; figuring out the status of > > patches I'm interested in but not the author of is even harder. A forge > > surfaces a lot of this information pretty well and, to me, GitLab at > > least offers usable enough email messages (e.g., discussions on threads > > will thread in email too) that the public tracking of such things is far > > more useful on the whole. > > This is an area that also needs standardization of important > functionality. Some method of archiving the content is also helpful - > email does this well but typically does not offer dashboard. Sourcehut > makes reading threads using the web interface very easy. The other thing that email makes difficult to do: jump in on an existing discussion without having been subscribed previously. I mean, I know how to tell `mutt` to set an `In-Reply-To` header and munge a proper reply by hand once I find a `Message-Id` (though a fully proper `References` header is usually way too much work to be worth it), but this is not something I expect others to be able to easily perform. > Web interfaces are difficult to automate, but friendlier for occasional > use and encouraging new contributions. Tools separate from the version > control system such as Gerrit, Phabricator, Rhode Code and Review Board > also enable discussion management and overview. Note that forges tend to have very rich APIs. It's certainly not as easy as clicking around manually for one-off tasks or setting up a shell pipeline to process some emails, but building automation isn't impossible. --Ben