From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id +DWzD+6CAGRIlgAAbAwnHQ (envelope-from ) for ; Thu, 02 Mar 2023 12:05:18 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id uJHjDu6CAGQ3awAAG6o9tA (envelope-from ) for ; Thu, 02 Mar 2023 12:05:18 +0100 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 D367E24F10 for ; Thu, 2 Mar 2023 12:05:17 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pXgkD-0005h3-1U; Thu, 02 Mar 2023 06:05:05 -0500 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 1pXgkA-0005gi-ND for guix-patches@gnu.org; Thu, 02 Mar 2023 06:05:02 -0500 Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pXgkA-000809-EV for guix-patches@gnu.org; Thu, 02 Mar 2023 06:05:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pXgkA-0001mw-7F for guix-patches@gnu.org; Thu, 02 Mar 2023 06:05:02 -0500 X-Loop: help-debbugs@gnu.org Subject: [bug#61894] [PATCH RFC] Team approval for patches Resent-From: Andreas Enge Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Thu, 02 Mar 2023 11:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61894 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, Christopher Baines , 61894@debbugs.gnu.org, guix-maintainers@gnu.org Received: via spool by 61894-submit@debbugs.gnu.org id=B61894.16777550956859 (code B ref 61894); Thu, 02 Mar 2023 11:05:02 +0000 Received: (at 61894) by debbugs.gnu.org; 2 Mar 2023 11:04:55 +0000 Received: from localhost ([127.0.0.1]:55958 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXgk3-0001mZ-5g for submit@debbugs.gnu.org; Thu, 02 Mar 2023 06:04:55 -0500 Received: from hera.aquilenet.fr ([185.233.100.1]:52302) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pXgk1-0001mJ-7Y for 61894@debbugs.gnu.org; Thu, 02 Mar 2023 06:04:53 -0500 Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id F0BFD198F; Thu, 2 Mar 2023 12:04:46 +0100 (CET) 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 df4JXLlNLSAD; Thu, 2 Mar 2023 12:04:46 +0100 (CET) Received: from jurong (unknown [147.94.72.84]) by hera.aquilenet.fr (Postfix) with ESMTPSA id 53C65694; Thu, 2 Mar 2023 12:04:46 +0100 (CET) Date: Thu, 2 Mar 2023 12:04:44 +0100 From: Andreas Enge Message-ID: References: <878rgga1qv.fsf@inria.fr> <871qm8wf8e.fsf@cbaines.net> <87r0u86qgo.fsf_-_@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r0u86qgo.fsf_-_@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: guix-patches-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1677755118; a=rsa-sha256; cv=none; b=hThVXfYGFnv8Qm+PGYfLWEXk5pkdxIgEWD+qAoOvnDMvfQD3EmcBNdPmGaMAOPtlegx9W0 eaEXGoXuM+kx8BY1U2yZuIZeRkS+HFiLdExdIc9TkhFyC69QjXT8Egde68JrWRv0jevtDz LwhqYGK8uGOPT1HHyLiru8FAP9fymi61/V4VhzWIs+lOXxuNjjpfMf9xNff6YhAgAcqdy2 8CfV3nLaBeYzRikHr1Kx5HI9+u+zC30KYDfmSByGG4AjtufkB3u/TrvcK9qTRfg7DUfxtO wT3Bcz9laJ+Lg53Nq2MJtH7cQD1iGSlwrHNpMchGy4Ah2FZH56Cthy0spQcAuQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-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=1677755118; 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:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post; bh=H/YApqqCiCVXCor4bbwJMXzZh9Im5jk4K6xnX5riKxo=; b=QEifII4u8bP98gVKHtp26opW7wVW2SsMsloYuBdueVMVORGlLnhCCL0kfK0NG0yOzTEluo zliVd7pVBlZPnGQ6vn/xBQf5czmT15QcKL6TLVzFrj1FOTxYC0GFXjJbg1L3z/d4/8XDfe 2k8Mlw1RbnVftVRXJ7ym6XYBiXtthz6HjqfpCVTDdERdQJoMRGzLZpmtrwL/Aek9rL7Jxs UCvc3xIKisXn4O0Rs2/pqP9W1YE856mNryn7z8+zTLJFgVxyP0bDEc1uTNhmlUVsq5mSSy UEr27Sxx425a+Rc51OJ8frPwt9mQRMXci1euhGLG28GN+CsP2EgfugtJgg2LnQ== X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -2.69 X-Spam-Score: -2.69 X-Migadu-Queue-Id: D367E24F10 Authentication-Results: aspmx1.migadu.com; dkim=none; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=none X-TUID: s0+u97Bt8RIH Hello, in the current situation I think the suggestion is putting the horse before the cart. In a first step before adding policy, we should make the teams functional. While working on core-updates, I have been realising we are already spread too thin: Some important languages have teams with one or two members, who would effectively become bottlenecks. Other software has no team (Qt/KDE). All in all, I also think we have too few committers. Adding policy might completely stall the project... If for every trivial update of a Python package we need not only submit a patch to the bugtracker, wait for QA, get back to the patch, resign it, push it and close the bug, but additionally wait for one of the two Python team members to have a look at it (or let an additional week pass), incentives to participate will tend to zero. Your suggested policy can help against commits of too bad quality; but I do not think this is our problem, our problem is rather a lack of fast progress. So I think we need to add committers, add committers to teams, encourage teams to engage in work, and if everything works smoothly, maybe add policy. Andreas