Dealing with bugzilla

Dealing with bugzilla

[Stephen Hemminger]

Up until now, I have been the volunteer screener of networking related bugzilla bugs.
I would like to get out of doing that.

The alternatives are:
   1. Change the bugzilla forwarding to netdev@vger.kernel.org (ie no screening)
   2. Get a new volunteer to screen
   3. Make a new mailing list target on vger (ie netdev-bugs@vger.kernel.org)
   4. Find someone to make a bot to use get_maintainer somehow to forward
   5. Blackhole the bugzilla reports.
   6. Bounce all the bugzilla reports somehow.

Any suggestions welcome.

Re: Dealing with bugzilla

[Florian Westphal]

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.

Re: Dealing with bugzilla

[Stephen Hemminger]

On Thu, 19 Sep 2024 18:17:09 +0200
Florian Westphal <fw@strlen.de> wrote:

> 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.

Volume is about 1 report every 2 weeks with about 10% dropped.
Most of the drops are because the report is for an vendor kernel which is tainted
or end of life.

Re: Dealing with bugzilla

[Jacob Keller]

On 9/19/2024 9:43 AM, Stephen Hemminger wrote:
> On Thu, 19 Sep 2024 18:17:09 +0200
> Florian Westphal <fw@strlen.de> wrote:
> 
>> 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.
> 
> Volume is about 1 report every 2 weeks with about 10% dropped.
> Most of the drops are because the report is for an vendor kernel which is tainted
> or end of life.
> 

That seems low enough volume that a few volunteers could handle it via
something like netdev-bugs.

What do you do with bugs once you screened them? Presumably try to
forward to relevant parties or the main netdev list?