"Martin J. Bligh" <mbligh@xxxxxxxxxxx> wrote:
>
> 1. default owners -> lists:
>
> Setting default owners to existing lists is somewhat invasive, and
> might provoke riots ;-) Not only do you get the new bug notification,
> but also any updates, which may become irritating.
That's OK. It is a matter of people being aware that the updates will be
echoed to a mailing list and acting appropriately.
If some low-value stuff leaks through then ho-hum, at least it was
on-topic. It is not as if we are unused to low-value content...
It would be good if pure administrata such as changing the status were
filtered.
In fact, there is probably no point in sending anything bugzilla->list apart
from the initial report. If the bug is then pursued via bugzilla then OK.
If is is pursued via email then bugzilla just captures the discussion.
> There's probably
> some vaguely happy medium to be found between:
> a) sending newly logged bugs to existing lists,
> b) sending updates to some new list.
> Maybe if we just create a new list for each category, and let
> people subscribe at will to those ... and I keep sending newly logged
> bugs to linux-kernel? I can cc netdev / linux-scsi / whatever on those
> new ones if that helps?
I think sending the initial report to the relevant lists and then capturing
incoming email would suffice.
> 2. email back in.
>
> Email back in is harder, and needs more thought as to how to make it
> easy to use, whilst avoiding logging crap (eg. ensuing flamewars that
> derive from the bug reports, etc).
Well hopefully people will have the sense to cut the bugzilla address off
the Cc line if it drifts off-topic.
> My intuition is to log replies by
> default, and hack off certain threads by hand
Nah. Just log everything and hack off the crap by larting people.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|
