From owner-freebsd-hackers@freebsd.org Fri Jun 1 19:57:30 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 0330CF715B7 for ; Fri, 1 Jun 2018 19:57:30 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com [209.85.223.182]) (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 B7D4370061; Fri, 1 Jun 2018 19:57:29 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f182.google.com with SMTP id l19-v6so21257050ioj.5; Fri, 01 Jun 2018 12:57:29 -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=x3MkP0T5Oc/8t1nAqYxJdLDMTYn+kJ1NngA+hD70Vds=; b=VAnA38w0kidvxN1bIwDaBYSjnUSJ/xgMo647GYEVI9W4C22+HaPpczkQQSF/PRoeaW f4rV/ZSYkEqehk5Gg4G1672O6pH5UopUewx37dcKfE7yLIGcCNWsZIU3VroBq5tLXG2K uR4RuEQ2t7n7o7sxz3cl4nkd28ToDHXUAUqkblGJS5mdkHnEqFZ4gsd6iXL1ggjaj7YU 1po2UeFWWcMfuouQNVsRK8hAHakWu5bOZud3rpCqoeCrBvQNn2Qq9avfjb6RZlSlxw2T 7fQXNyOwkitfuiukFNCbxbRkac8FmunQDPZneVxBgUgaYqLUX4R8WphaZ76c9oSvD9eG 0hyA== X-Gm-Message-State: APt69E0Qvv/AonvJe3ZTXk/bz+GGzENSes7wyry0uyjFD0E90YWIkQD/ qTRLgczhF250Pdu3lkL5bJJfMuCO X-Google-Smtp-Source: ADUXVKI6a2OwfIBW3wpDzJjGdFo0NKZY0omlgTCJltVZQbvSBW1jX9ljUh1UsWzAx4Bf7D83ywvvzA== X-Received: by 2002:a6b:f817:: with SMTP id o23-v6mr12161487ioh.106.1527882651176; Fri, 01 Jun 2018 12:50:51 -0700 (PDT) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com. [209.85.223.182]) by smtp.gmail.com with ESMTPSA id e4-v6sm1528755iob.31.2018.06.01.12.50.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 12:50:50 -0700 (PDT) Received: by mail-io0-f182.google.com with SMTP id l19-v6so21237200ioj.5; Fri, 01 Jun 2018 12:50:50 -0700 (PDT) X-Received: by 2002:a6b:b513:: with SMTP id e19-v6mr12337482iof.267.1527882650577; Fri, 01 Jun 2018 12:50:50 -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 12:50:49 -0700 (PDT) In-Reply-To: <1527878412.32688.207.camel@freebsd.org> References: <20180531210212.GD24090@lonesome.com> <5f84bfc4-3e47-283f-184f-49df94e0d457@yandex.ru> <1527878412.32688.207.camel@freebsd.org> From: Conrad Meyer Date: Fri, 1 Jun 2018 12:50:49 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: PRs are being closed for bogus reasons :-( To: Ian Lepore 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 19:57:30 -0000 Hi Ian, On Fri, Jun 1, 2018 at 11:40 AM, Ian Lepore wrote: > On Fri, 2018-06-01 at 11:23 -0700, Conrad Meyer wrote: >> ... >> So my modified proposal is: >> >> 1. Create an announce-only bugs list that only receives new ports. Sorry, typo: that should be "new reports." >> ... > > Do you envision people being able to comment/reply/post to the list in > general? Nope. I think it should be Just New Bugs to keep noise down. The idea is to get the summary and description in front of eyeballs, and no follow-up notification unless you explicitly CC yourself. This is basically the model I use today, except I had to set up explicit email filters to get it from the existing list, and that's a totally unnecessary burden to put on everyone. As Ben Kaduk says, discussion can and should happen in Bugzilla. > What I'm curious about is the level of non-announce mail > that's going to be on the list. If it turns into general chit-chat > about the bugs that are announced, the noise level goes way way up. > Also, that would encourage discussion related to the bugs which should > probably happen in bugzilla comments rather than out-of-band mail. Totally agree. It's most useful announce-only. > Hmm, something that could reduce the traffic even more would be to send > out a once-daily mail summarizing the short description lines of all > bugs entered in the past 24 hours. Maybe that could be done and sent to > a few appropriate existing lists (one or more of stable@, current@, > ports@, etc, depending on the metadata in the PRs). I prefer the other model, but I believe mailman can accommodate this mode simultaneously with a single list =E2=80=94 I think users can configur= ed it to do this on a individual user basis. Conrad