From owner-freebsd-hackers@freebsd.org Fri Jun 1 18:23:56 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E7F8FDBEE9 for ; Fri, 1 Jun 2018 18:23:56 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f47.google.com (mail-it0-f47.google.com [209.85.214.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3442B6B12F for ; Fri, 1 Jun 2018 18:23:56 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f47.google.com with SMTP id l6-v6so2929970iti.2 for ; Fri, 01 Jun 2018 11:23:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=xuj51NVfEUWl60jSE+z7ywGvMWI8BaDiHWne77XeEV8=; b=qTez2fl/kwsRlCneF2tehIaGpBr8rX4WeeWt/6f7ZE2zdVNRRxqw26rnMjjKMJqg+m wJDYHlLriBRNPRTF9AUyH57SYtt7mS5jfaa9EEwr0P11fHNEtv/Kwfo9r+RPnts3Ysk1 cYLdeyFHS/pfnOkPat5X+Tzsb+gbDQB1Pj5A1ON2R5YTJ9l34bWoXgqz45BHUzHqdKYj wd+UY9eY4lfSmjSebwS0TAzqOgGZDPL30O6ABwqQ1x8Y4sb5W+YyXxgGdbb2k2NkOGKh /Q0lJGcQ+RofWj0XtVet7GawIHKtNfHOuHmF4vCQ7Rqud1/Mmd+DFixHhn2g+3ACHAz0 nwRw== X-Gm-Message-State: APt69E0cPBi5T/ETjjrtsREN0xvfH7FLGMROG3SJC72pdroK/nYe4bEO 5UPhv8nhj58QYC1jwF9O2MvL01wr X-Google-Smtp-Source: ADUXVKL7Pi9yc2Q0BbglZIBKU8sN4SnKsFvmP0PG5xHSVXMjjsMSVnV7DKNojsvmrlti530uLBGCCA== X-Received: by 2002:a24:2c03:: with SMTP id i3-v6mr5267577iti.90.1527877429293; Fri, 01 Jun 2018 11:23:49 -0700 (PDT) Received: from mail-it0-f54.google.com (mail-it0-f54.google.com. [209.85.214.54]) by smtp.gmail.com with ESMTPSA id e28-v6sm1395278itd.35.2018.06.01.11.23.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 11:23:49 -0700 (PDT) Received: by mail-it0-f54.google.com with SMTP id a3-v6so2937172itd.0 for ; Fri, 01 Jun 2018 11:23:49 -0700 (PDT) X-Received: by 2002:a24:100f:: with SMTP id 15-v6mr5517151ity.61.1527877429008; Fri, 01 Jun 2018 11:23:49 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:5995:0:0:0:0:0 with HTTP; Fri, 1 Jun 2018 11:23:48 -0700 (PDT) In-Reply-To: <5f84bfc4-3e47-283f-184f-49df94e0d457@yandex.ru> References: <20180531210212.GD24090@lonesome.com> <5f84bfc4-3e47-283f-184f-49df94e0d457@yandex.ru> From: Conrad Meyer Date: Fri, 1 Jun 2018 11:23:48 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: PRs are being closed for bogus reasons :-( To: "Andrey V. Elsukov" Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2018 18:23:56 -0000 On Fri, Jun 1, 2018 at 2:09 AM, Andrey V. Elsukov wrote= : > On 01.06.2018 00:02, Mark Linimon wrote: >> I'd like to see us do a lot better at dealing with "PRs with patches" -- >> even more so than "can't get FreeBSD to run" -- but without some kind >> of set of new volunteers willing to work on only such issues, it simply >> isn't going to happen. > > I suggest to forcibly subscribe any committers to the freebsd-bugs@ > mailing list in addition to *-committers@. :) Hi Andrey, Maybe this proposal was made in jest, but I actually like the idea. The dominant noise of freebsd-bugs@ comes from follow-up comments, bug status notifications (sometimes bulk changes made by e.g., Eitan), or direct email reply discussion (not really sure why bugs@ isn't just treated as announce-only). It's still sort of a firehose if you *just* receive new bug reports, but it's much more manageable and you can click through any that look interesting and mark the rest read with no risk of future notification. So my modified proposal is: 1. Create an announce-only bugs list that only receives new ports. Maybe it can have a name incorporating "triage." I don't care. 2. Subscribe committers to it by default. 3. Encourage people to stay subscribed and help them set up inbox filters to separate it from higher priority email, so it's less of a nuisance. 4. Finally, allow opting out. Bug triage isn't for everyone. But it is definitely an area where "many hands make light work," and we don't have a lot of hands doing it right now. Special thanks to Mark, who spends an amazing amount of time helping to triage the incoming bug firehose, annotate bugs with patches, and get bugs in front of relevant eyeballs. Best, Conrad What Is Core Doing About It?=E2=84=A2