All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: Dealing with bugzilla
Date: Thu, 19 Sep 2024 18:17:09 +0200	[thread overview]
Message-ID: <20240919161709.GA18875@breakpoint.cc> (raw)
In-Reply-To: <20240919091046.64cb49b6@hermes.local>

Stephen Hemminger <stephen@networkplumber.org> wrote:
> Up until now, I have been the volunteer screener of networking related bugzilla bugs.
> I would like to get out of doing that.

Understandable, thanks for doing all the prefiltering work all these
years!

> The alternatives are:
>    1. Change the bugzilla forwarding to netdev@vger.kernel.org (ie no screening)

"OH NEIN !!!11"

>    2. Get a new volunteer to screen

Even if someone would volunteer I don't think it would be good to have
this burden on one person alone.

>    3. Make a new mailing list target on vger (ie netdev-bugs@vger.kernel.org)

I'd go for 3) and see how that works out.

>    4. Find someone to make a bot to use get_maintainer somehow to forward

I'd say 3, then see if it can be refined somehow.
3) would also allow to get an impression on the volume, the signal/noise ratio etc.

>    5. Blackhole the bugzilla reports.
>    6. Bounce all the bugzilla reports somehow.

5 & 6 are worse than 7), which would be to close bugzilla
and keep it readonly archive.

  reply	other threads:[~2024-09-19 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 16:10 Dealing with bugzilla Stephen Hemminger
2024-09-19 16:17 ` Florian Westphal [this message]
2024-09-19 16:43   ` Stephen Hemminger
2024-09-19 23:06     ` Jacob Keller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240919161709.GA18875@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.