I've created a #fedora-kernel channel on freenode in response to the large number of /msg's I continue to get which really should be going to a wider audience.
I expect it to be low-traffic, but it may be a worthwhile experiment to see if it helps any for triage, coordination etc.
Dave
On 21/09/2007, Dave Jones davej@redhat.com wrote:
I've created a #fedora-kernel channel on freenode in response to the large number of /msg's I continue to get which really should be going to a wider audience.
I expect it to be low-traffic, but it may be a worthwhile experiment to see if it helps any for triage, coordination etc.
Is there any value is punting out a message to fedora-test to get more people on the case with triaging? I'm getting to the point now where bugs aren't so old any more therefore people remember why they filed, can still replicate the bug so the process rate is slowing somewhat. When you say /msg do you mean people in IRC or bugzilla emails about bug status changes. Is it worth setting up a bugzilla monitor to show status changes to kernel bugs?
Also, is it worth setting mailman to change the reply-to address so it goes to the list rather than the poster a-la -devel and -test?
Cheers Chris
On Fri, Sep 21, 2007 at 04:23:57PM +0100, Christopher Brown wrote:
On 21/09/2007, Dave Jones davej@redhat.com wrote:
I've created a #fedora-kernel channel on freenode in response to the large number of /msg's I continue to get which really should be going to a wider audience.
I expect it to be low-traffic, but it may be a worthwhile experiment to see if it helps any for triage, coordination etc.
Is there any value is punting out a message to fedora-test to get more people on the case with triaging?
Yeah, can't hurt.
I'm getting to the point now where bugs aren't so old any more therefore people remember why they filed, can still replicate the bug so the process rate is slowing somewhat. When you say /msg do you mean people in IRC or bugzilla emails about bug status changes.
People.
Is it worth setting up a bugzilla monitor to show status changes to kernel bugs?
There's always #fedorabot (though that shows bug changes to all packages). Perhaps we could get whoever controls it to join #fedora-kernel too if it can be trained to only talk about kernel bugs, though I'm not sure if it'll be annoying or not. Opinions?
Also, is it worth setting mailman to change the reply-to address so it goes to the list rather than the poster a-la -devel and -test?
I try to stay out of that argument as much as possible, as it seems have vocal proponents/opponents on both sides, and tbh, I don't think there's a way that'll please everyone.
Dave
On Fri, 2007-09-21 at 11:35 -0400, Dave Jones wrote:
On Fri, Sep 21, 2007 at 04:23:57PM +0100, Christopher Brown wrote:
On 21/09/2007, Dave Jones davej@redhat.com wrote:
I've created a #fedora-kernel channel on freenode in response to the large number of /msg's I continue to get which really should be going to a wider audience.
Yay, more channels on $%@&! Freenode. Which one shall I quit in order to join the new one, I wonder... :)
Also, is it worth setting mailman to change the reply-to address so it goes to the list rather than the poster a-la -devel and -test?
http://www.unicom.com/pw/reply-to-harmful.html
I try to stay out of that argument as much as possible, as it seems have vocal proponents/opponents on both sides, and tbh, I don't think there's a way that'll please everyone.
Indeed. And the failure more one way round is much worse than the failure mode the other way round.
Maybe we should start shipping a decent mail client with a proper 'reply to all' button? :)
Dnia 2007-09-26, o godz. 15:54:44 Christian Iseli Christian.Iseli@licr.org napisał(a):
Maybe we should start shipping a decent mail client with a proper 'reply to all' button? :)
yum install claws-mail ?
Which is a great MUA, but by default it "replies to list" and doesn't have a shortcut for "reply to sender" at all (but it can be done using the menu, I admit). It also doesn't seem to have any "reply" button honoring "reply-to" header on the lists. That's far from usual :)
Lam
kernel@lists.fedoraproject.org