Separate bugs mailing list?
Locked
 
|
Currently the vast majority of emails to this list are automatic
emails from bugs.kde.org, making it very hard to find the non-bug discussions and hard for non-developers who are trying to follow the digikam development process. To be specific, since the start of August there have been 333 non-spam emails to this list. Of those, 311 (over 93%) were automatic emails from bugs.kde.org, and another 9 were from git commits or reviewboard. Only 13 were announcements or discussions directly on the mailing list. Given the high volume of bug reports relative to other emails, I think it would be very helpful if bug reports were sent to a second, dedicated mailing list rather than the main list. This would make it easier to follow discussions and make it easier to filter and categorize emails in email programs. I suspect, but am not sure, that it would also encourage more discussion since emails to the list would not get lost so easily. -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
I agree.
There is a volumnter to ask a new email adress to kde team dedicated to trace bug report and configure it to bugzilla ? Gilles Caulier 2011/8/10 todd rme <[hidden email]>: > Currently the vast majority of emails to this list are automatic > emails from bugs.kde.org, making it very hard to find the non-bug > discussions and hard for non-developers who are trying to follow the > digikam development process. To be specific, since the start of > August there have been 333 non-spam emails to this list. Of those, > 311 (over 93%) were automatic emails from bugs.kde.org, and another 9 > were from git commits or reviewboard. Only 13 were announcements or > discussions directly on the mailing list. > > Given the high volume of bug reports relative to other emails, I think > it would be very helpful if bug reports were sent to a second, > dedicated mailing list rather than the main list. This would make it > easier to follow discussions and make it easier to filter and > categorize emails in email programs. I suspect, but am not sure, that > it would also encourage more discussion since emails to the list would > not get lost so easily. > > -Todd > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier
<[hidden email]> wrote: > 2011/8/10 todd rme <[hidden email]>: >> Currently the vast majority of emails to this list are automatic >> emails from bugs.kde.org, making it very hard to find the non-bug >> discussions and hard for non-developers who are trying to follow the >> digikam development process. To be specific, since the start of >> August there have been 333 non-spam emails to this list. Of those, >> 311 (over 93%) were automatic emails from bugs.kde.org, and another 9 >> were from git commits or reviewboard. Only 13 were announcements or >> discussions directly on the mailing list. >> >> Given the high volume of bug reports relative to other emails, I think >> it would be very helpful if bug reports were sent to a second, >> dedicated mailing list rather than the main list. This would make it >> easier to follow discussions and make it easier to filter and >> categorize emails in email programs. I suspect, but am not sure, that >> it would also encourage more discussion since emails to the list would >> not get lost so easily. >> >> -Todd > > I agree. > > There is a volumnter to ask a new email adress to kde team dedicated > to trace bug report and configure it to bugzilla ? > > Gilles Caulier CCed Tom Albers, who seems to be keeping track of the mailing lists at least to some extent. @ Tom: Do you have any suggestions on how to go about doing this? -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
----- Oorspronkelijk bericht ----- > On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier > <[hidden email]> wrote: > > 2011/8/10 todd rme <[hidden email]>: > >> Currently the vast majority of emails to this list are automatic > >> emails from bugs.kde.org, making it very hard to find the non-bug > >> discussions and hard for non-developers who are trying to follow > >> the > >> digikam development process. To be specific, since the start of > >> August there have been 333 non-spam emails to this list. Of > >> those, > >> 311 (over 93%) were automatic emails from bugs.kde.org, and > >> another 9 > >> were from git commits or reviewboard. Only 13 were announcements > >> or > >> discussions directly on the mailing list. > >> > >> Given the high volume of bug reports relative to other emails, I > >> think > >> it would be very helpful if bug reports were sent to a second, > >> dedicated mailing list rather than the main list. This would make > >> it > >> easier to follow discussions and make it easier to filter and > >> categorize emails in email programs. I suspect, but am not sure, > >> that > >> it would also encourage more discussion since emails to the list > >> would > >> not get lost so easily. > >> > >> -Todd > > > > I agree. > > > > There is a volumnter to ask a new email adress to kde team > > dedicated > > to trace bug report and configure it to bugzilla ? > > > > Gilles Caulier > > CCed Tom Albers, who seems to be keeping track of the mailing lists > at > least to some extent. > > @ Tom: Do you have any suggestions on how to go about doing this? > > -Todd Hi, Usually dedicated mailinglists for bugs don't work. It will only be interesting for 1 or 2 people. What I would like to suggest is this: We assign a special bugzilla user to all digikam bugs. That way the mails to the -devel mailinglist will stop. For people that want to get all the mails, they can go to bugzilla and 'follow' that special user. Then they get a mail for all changes as they have received up to now. Is that an idea? If so, please make a sysadmin bugreport (see footer bugs.kde.org) so we can set it up for you. Best, -- Tom Albers KDE Sysadmin _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers <[hidden email]> wrote:
> > > ----- Oorspronkelijk bericht ----- >> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier >> <[hidden email]> wrote: >> > 2011/8/10 todd rme <[hidden email]>: >> >> Currently the vast majority of emails to this list are automatic >> >> emails from bugs.kde.org, making it very hard to find the non-bug >> >> discussions and hard for non-developers who are trying to follow >> >> the >> >> digikam development process. To be specific, since the start of >> >> August there have been 333 non-spam emails to this list. Of >> >> those, >> >> 311 (over 93%) were automatic emails from bugs.kde.org, and >> >> another 9 >> >> were from git commits or reviewboard. Only 13 were announcements >> >> or >> >> discussions directly on the mailing list. >> >> >> >> Given the high volume of bug reports relative to other emails, I >> >> think >> >> it would be very helpful if bug reports were sent to a second, >> >> dedicated mailing list rather than the main list. This would make >> >> it >> >> easier to follow discussions and make it easier to filter and >> >> categorize emails in email programs. I suspect, but am not sure, >> >> that >> >> it would also encourage more discussion since emails to the list >> >> would >> >> not get lost so easily. >> >> >> >> -Todd >> > >> > I agree. >> > >> > There is a volumnter to ask a new email adress to kde team >> > dedicated >> > to trace bug report and configure it to bugzilla ? >> > >> > Gilles Caulier >> >> CCed Tom Albers, who seems to be keeping track of the mailing lists >> at >> least to some extent. >> >> @ Tom: Do you have any suggestions on how to go about doing this? >> >> -Todd > > Hi, > > Usually dedicated mailinglists for bugs don't work. It will only be interesting for 1 or 2 people. > > What I would like to suggest is this: > > We assign a special bugzilla user to all digikam bugs. That way the mails to the -devel mailinglist will stop. > > For people that want to get all the mails, they can go to bugzilla and 'follow' that special user. Then they get a mail for all changes as they have received up to now. > > Is that an idea? If so, please make a sysadmin bugreport (see footer bugs.kde.org) so we can set it up for you. That would be fine for me, but the digikam developers would need to make the final decision. -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
One user who receive all bugzilla mail ? It's weird...
typically, all developers are registered to a ML. Developers will be triggered to interesting reports (typically each developer maintain a part in digiKam). If only one guy receive bugzilla notification, this filtering will be broken. One people cannot dispatch/assign bug to right developers. Gilles Caulier 2011/8/10 todd rme <[hidden email]>: > On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers <[hidden email]> wrote: >> >> >> ----- Oorspronkelijk bericht ----- >>> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier >>> <[hidden email]> wrote: >>> > 2011/8/10 todd rme <[hidden email]>: >>> >> Currently the vast majority of emails to this list are automatic >>> >> emails from bugs.kde.org, making it very hard to find the non-bug >>> >> discussions and hard for non-developers who are trying to follow >>> >> the >>> >> digikam development process. To be specific, since the start of >>> >> August there have been 333 non-spam emails to this list. Of >>> >> those, >>> >> 311 (over 93%) were automatic emails from bugs.kde.org, and >>> >> another 9 >>> >> were from git commits or reviewboard. Only 13 were announcements >>> >> or >>> >> discussions directly on the mailing list. >>> >> >>> >> Given the high volume of bug reports relative to other emails, I >>> >> think >>> >> it would be very helpful if bug reports were sent to a second, >>> >> dedicated mailing list rather than the main list. This would make >>> >> it >>> >> easier to follow discussions and make it easier to filter and >>> >> categorize emails in email programs. I suspect, but am not sure, >>> >> that >>> >> it would also encourage more discussion since emails to the list >>> >> would >>> >> not get lost so easily. >>> >> >>> >> -Todd >>> > >>> > I agree. >>> > >>> > There is a volumnter to ask a new email adress to kde team >>> > dedicated >>> > to trace bug report and configure it to bugzilla ? >>> > >>> > Gilles Caulier >>> >>> CCed Tom Albers, who seems to be keeping track of the mailing lists >>> at >>> least to some extent. >>> >>> @ Tom: Do you have any suggestions on how to go about doing this? >>> >>> -Todd >> >> Hi, >> >> Usually dedicated mailinglists for bugs don't work. It will only be interesting for 1 or 2 people. >> >> What I would like to suggest is this: >> >> We assign a special bugzilla user to all digikam bugs. That way the mails to the -devel mailinglist will stop. >> >> For people that want to get all the mails, they can go to bugzilla and 'follow' that special user. Then they get a mail for all changes as they have received up to now. >> >> Is that an idea? If so, please make a sysadmin bugreport (see footer bugs.kde.org) so we can set it up for you. > > That would be fine for me, but the digikam developers would need to > make the final decision. > > -Todd > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
In reply to this post by todd rme
In the subscription options there is such a entry:
I think must be defined few topics like: general, Digikam-core-bug, kipi-plugin bugs. On Wed, Aug 10, 2011 at 11:09 AM, todd rme <[hidden email]> wrote:
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
In reply to this post by Gilles Caulier-4
On Wed, Aug 10, 2011 at 1:16 PM, Gilles Caulier
<[hidden email]> wrote: > 2011/8/10 todd rme <[hidden email]>: >> On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers <[hidden email]> wrote: >>> >>> >>> ----- Oorspronkelijk bericht ----- >>>> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier >>>> <[hidden email]> wrote: >>>> > 2011/8/10 todd rme <[hidden email]>: >>>> >> Currently the vast majority of emails to this list are automatic >>>> >> emails from bugs.kde.org, making it very hard to find the non-bug >>>> >> discussions and hard for non-developers who are trying to follow >>>> >> the >>>> >> digikam development process. To be specific, since the start of >>>> >> August there have been 333 non-spam emails to this list. Of >>>> >> those, >>>> >> 311 (over 93%) were automatic emails from bugs.kde.org, and >>>> >> another 9 >>>> >> were from git commits or reviewboard. Only 13 were announcements >>>> >> or >>>> >> discussions directly on the mailing list. >>>> >> >>>> >> Given the high volume of bug reports relative to other emails, I >>>> >> think >>>> >> it would be very helpful if bug reports were sent to a second, >>>> >> dedicated mailing list rather than the main list. This would make >>>> >> it >>>> >> easier to follow discussions and make it easier to filter and >>>> >> categorize emails in email programs. I suspect, but am not sure, >>>> >> that >>>> >> it would also encourage more discussion since emails to the list >>>> >> would >>>> >> not get lost so easily. >>>> >> >>>> >> -Todd >>>> > >>>> > I agree. >>>> > >>>> > There is a volumnter to ask a new email adress to kde team >>>> > dedicated >>>> > to trace bug report and configure it to bugzilla ? >>>> > >>>> > Gilles Caulier >>>> >>>> CCed Tom Albers, who seems to be keeping track of the mailing lists >>>> at >>>> least to some extent. >>>> >>>> @ Tom: Do you have any suggestions on how to go about doing this? >>>> >>>> -Todd >>> >>> Hi, >>> >>> Usually dedicated mailinglists for bugs don't work. It will only be interesting for 1 or 2 people. >>> >>> What I would like to suggest is this: >>> >>> We assign a special bugzilla user to all digikam bugs. That way the mails to the -devel mailinglist will stop. >>> >>> For people that want to get all the mails, they can go to bugzilla and 'follow' that special user. Then they get a mail for all changes as they have received up to now. >>> >>> Is that an idea? If so, please make a sysadmin bugreport (see footer bugs.kde.org) so we can set it up for you. >> >> That would be fine for me, but the digikam developers would need to >> make the final decision. >> >> -Todd > > One user who receive all bugzilla mail ? It's weird... > > typically, all developers are registered to a ML. Developers will be > triggered to interesting reports (typically each developer maintain a > part in digiKam). > > If only one guy receive bugzilla notification, this filtering will be > broken. One people cannot dispatch/assign bug to right developers. I think the idea is to have one "virtual" bugs.kde.org user, say "digikam-developers" or something like that. That user is automatically subscribed to all digikam bug reports. On bugs.kde.org, individual users can say that they want to "watch" particular users. Here is the description from bugs.kde.org, which explains it better than I can: "If you watch a user, it is as if you are standing in their shoes for the purposes of getting email. Email is sent or not according to your preferences for their relationship to the bug (e.g. Assignee)." So anyone who watches that virtual user will automatically get all the digikam bug reports emailed to them directly by bugs.kde.org without having to through a mailing list or individually subscribe to bugs. Anyone who wants to stop getting these emails can just remove the "virtual" user from their watch list. What is more, I think it could even be broken up more finely, with "virtual" users for any digikam component (although I am not sure about that). If you do it that way, users could pick which components they wish to follow by watching particular users. Did I explain that right, Tom? -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
----- Oorspronkelijk bericht -----
> On Wed, Aug 10, 2011 at 1:16 PM, Gilles Caulier > <[hidden email]> wrote: > > 2011/8/10 todd rme <[hidden email]>: > >> On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers <[hidden email]> wrote: > >>> > >>> > >>> ----- Oorspronkelijk bericht ----- > >>>> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier > >>>> <[hidden email]> wrote: > >>>> > 2011/8/10 todd rme <[hidden email]>: > >>>> >> Currently the vast majority of emails to this list are > >>>> >> automatic > >>>> >> emails from bugs.kde.org, making it very hard to find the > >>>> >> non-bug > >>>> >> discussions and hard for non-developers who are trying to > >>>> >> follow > >>>> >> the > >>>> >> digikam development process. To be specific, since the start > >>>> >> of > >>>> >> August there have been 333 non-spam emails to this list. Of > >>>> >> those, > >>>> >> 311 (over 93%) were automatic emails from bugs.kde.org, and > >>>> >> another 9 > >>>> >> were from git commits or reviewboard. Only 13 were > >>>> >> announcements > >>>> >> or > >>>> >> discussions directly on the mailing list. > >>>> >> > >>>> >> Given the high volume of bug reports relative to other > >>>> >> emails, I > >>>> >> think > >>>> >> it would be very helpful if bug reports were sent to a > >>>> >> second, > >>>> >> dedicated mailing list rather than the main list. This would > >>>> >> make > >>>> >> it > >>>> >> easier to follow discussions and make it easier to filter and > >>>> >> categorize emails in email programs. I suspect, but am not > >>>> >> sure, > >>>> >> that > >>>> >> it would also encourage more discussion since emails to the > >>>> >> list > >>>> >> would > >>>> >> not get lost so easily. > >>>> >> > >>>> >> -Todd > >>>> > > >>>> > I agree. > >>>> > > >>>> > There is a volumnter to ask a new email adress to kde team > >>>> > dedicated > >>>> > to trace bug report and configure it to bugzilla ? > >>>> > > >>>> > Gilles Caulier > >>>> > >>>> CCed Tom Albers, who seems to be keeping track of the mailing > >>>> lists > >>>> at > >>>> least to some extent. > >>>> > >>>> @ Tom: Do you have any suggestions on how to go about doing > >>>> this? > >>>> > >>>> -Todd > >>> > >>> Hi, > >>> > >>> Usually dedicated mailinglists for bugs don't work. It will only > >>> be interesting for 1 or 2 people. > >>> > >>> What I would like to suggest is this: > >>> > >>> We assign a special bugzilla user to all digikam bugs. That way > >>> the mails to the -devel mailinglist will stop. > >>> > >>> For people that want to get all the mails, they can go to > >>> bugzilla and 'follow' that special user. Then they get a mail > >>> for all changes as they have received up to now. > >>> > >>> Is that an idea? If so, please make a sysadmin bugreport (see > >>> footer bugs.kde.org) so we can set it up for you. > >> > >> That would be fine for me, but the digikam developers would need > >> to > >> make the final decision. > >> > >> -Todd > > > > One user who receive all bugzilla mail ? It's weird... > > > > typically, all developers are registered to a ML. Developers will > > be > > triggered to interesting reports (typically each developer maintain > > a > > part in digiKam). > > > > If only one guy receive bugzilla notification, this filtering will > > be > > broken. One people cannot dispatch/assign bug to right developers. > > I think the idea is to have one "virtual" bugs.kde.org user, say > "digikam-developers" or something like that. That user is > automatically subscribed to all digikam bug reports. > > On bugs.kde.org, individual users can say that they want to "watch" > particular users. Here is the description from bugs.kde.org, which > explains it better than I can: > > "If you watch a user, it is as if you are standing in their shoes for > the purposes of getting email. Email is sent or not according to your > preferences for their relationship to the bug (e.g. Assignee)." > > So anyone who watches that virtual user will automatically get all > the > digikam bug reports emailed to them directly by bugs.kde.org without > having to through a mailing list or individually subscribe to bugs. > Anyone who wants to stop getting these emails can just remove the > "virtual" user from their watch list. > > What is more, I think it could even be broken up more finely, with > "virtual" users for any digikam component (although I am not sure > about that). If you do it that way, users could pick which > components > they wish to follow by watching particular users. > > Did I explain that right, Tom? Perfectly! Come work for the sysadmin team :) One tiny correction: the mails from bugzilla contain the component in the headers if i recall correctly, so your breaking up idea is not needed, you can filter in your mail client. Best, -- Tom Albers KDE Sysadmin _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On Wed, Aug 10, 2011 at 1:36 PM, Tom Albers <[hidden email]> wrote:
> ----- Oorspronkelijk bericht ----- >> On Wed, Aug 10, 2011 at 1:16 PM, Gilles Caulier >> <[hidden email]> wrote: >> > 2011/8/10 todd rme <[hidden email]>: >> >> On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers <[hidden email]> wrote: >> >>> >> >>> >> >>> ----- Oorspronkelijk bericht ----- >> >>>> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier >> >>>> <[hidden email]> wrote: >> >>>> > 2011/8/10 todd rme <[hidden email]>: >> >>>> >> Currently the vast majority of emails to this list are >> >>>> >> automatic >> >>>> >> emails from bugs.kde.org, making it very hard to find the >> >>>> >> non-bug >> >>>> >> discussions and hard for non-developers who are trying to >> >>>> >> follow >> >>>> >> the >> >>>> >> digikam development process. To be specific, since the start >> >>>> >> of >> >>>> >> August there have been 333 non-spam emails to this list. Of >> >>>> >> those, >> >>>> >> 311 (over 93%) were automatic emails from bugs.kde.org, and >> >>>> >> another 9 >> >>>> >> were from git commits or reviewboard. Only 13 were >> >>>> >> announcements >> >>>> >> or >> >>>> >> discussions directly on the mailing list. >> >>>> >> >> >>>> >> Given the high volume of bug reports relative to other >> >>>> >> emails, I >> >>>> >> think >> >>>> >> it would be very helpful if bug reports were sent to a >> >>>> >> second, >> >>>> >> dedicated mailing list rather than the main list. This would >> >>>> >> make >> >>>> >> it >> >>>> >> easier to follow discussions and make it easier to filter and >> >>>> >> categorize emails in email programs. I suspect, but am not >> >>>> >> sure, >> >>>> >> that >> >>>> >> it would also encourage more discussion since emails to the >> >>>> >> list >> >>>> >> would >> >>>> >> not get lost so easily. >> >>>> >> >> >>>> >> -Todd >> >>>> > >> >>>> > I agree. >> >>>> > >> >>>> > There is a volumnter to ask a new email adress to kde team >> >>>> > dedicated >> >>>> > to trace bug report and configure it to bugzilla ? >> >>>> > >> >>>> > Gilles Caulier >> >>>> >> >>>> CCed Tom Albers, who seems to be keeping track of the mailing >> >>>> lists >> >>>> at >> >>>> least to some extent. >> >>>> >> >>>> @ Tom: Do you have any suggestions on how to go about doing >> >>>> this? >> >>>> >> >>>> -Todd >> >>> >> >>> Hi, >> >>> >> >>> Usually dedicated mailinglists for bugs don't work. It will only >> >>> be interesting for 1 or 2 people. >> >>> >> >>> What I would like to suggest is this: >> >>> >> >>> We assign a special bugzilla user to all digikam bugs. That way >> >>> the mails to the -devel mailinglist will stop. >> >>> >> >>> For people that want to get all the mails, they can go to >> >>> bugzilla and 'follow' that special user. Then they get a mail >> >>> for all changes as they have received up to now. >> >>> >> >>> Is that an idea? If so, please make a sysadmin bugreport (see >> >>> footer bugs.kde.org) so we can set it up for you. >> >> >> >> That would be fine for me, but the digikam developers would need >> >> to >> >> make the final decision. >> >> >> >> -Todd >> > >> > One user who receive all bugzilla mail ? It's weird... >> > >> > typically, all developers are registered to a ML. Developers will >> > be >> > triggered to interesting reports (typically each developer maintain >> > a >> > part in digiKam). >> > >> > If only one guy receive bugzilla notification, this filtering will >> > be >> > broken. One people cannot dispatch/assign bug to right developers. >> >> I think the idea is to have one "virtual" bugs.kde.org user, say >> "digikam-developers" or something like that. That user is >> automatically subscribed to all digikam bug reports. >> >> On bugs.kde.org, individual users can say that they want to "watch" >> particular users. Here is the description from bugs.kde.org, which >> explains it better than I can: >> >> "If you watch a user, it is as if you are standing in their shoes for >> the purposes of getting email. Email is sent or not according to your >> preferences for their relationship to the bug (e.g. Assignee)." >> >> So anyone who watches that virtual user will automatically get all >> the >> digikam bug reports emailed to them directly by bugs.kde.org without >> having to through a mailing list or individually subscribe to bugs. >> Anyone who wants to stop getting these emails can just remove the >> "virtual" user from their watch list. >> >> What is more, I think it could even be broken up more finely, with >> "virtual" users for any digikam component (although I am not sure >> about that). If you do it that way, users could pick which >> components >> they wish to follow by watching particular users. >> >> Did I explain that right, Tom? > > Perfectly! Come work for the sysadmin team :) > > One tiny correction: the mails from bugzilla contain the component in the headers if i recall correctly, so your breaking up idea is not needed, you can filter in your mail client. > > Best, So does this sound like a good plan to everyone? -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
On 08/23/11 10:36, todd rme wrote:
> On Wed, Aug 10, 2011 at 1:36 PM, Tom Albers<[hidden email]> wrote: >> ----- Oorspronkelijk bericht ----- >>> On Wed, Aug 10, 2011 at 1:16 PM, Gilles Caulier >>> <[hidden email]> wrote: >>>> 2011/8/10 todd rme<[hidden email]>: >>>>> On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers<[hidden email]> wrote: >>>>>> >>>>>> >>>>>> ----- Oorspronkelijk bericht ----- >>>>>>> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier >>>>>>> <[hidden email]> wrote: >>>>>>>> 2011/8/10 todd rme<[hidden email]>: >>>>>>>>> Currently the vast majority of emails to this list are >>>>>>>>> automatic >>>>>>>>> emails from bugs.kde.org, making it very hard to find the >>>>>>>>> non-bug >>>>>>>>> discussions and hard for non-developers who are trying to >>>>>>>>> follow >>>>>>>>> the >>>>>>>>> digikam development process. To be specific, since the start >>>>>>>>> of >>>>>>>>> August there have been 333 non-spam emails to this list. Of >>>>>>>>> those, >>>>>>>>> 311 (over 93%) were automatic emails from bugs.kde.org, and >>>>>>>>> another 9 >>>>>>>>> were from git commits or reviewboard. Only 13 were >>>>>>>>> announcements >>>>>>>>> or >>>>>>>>> discussions directly on the mailing list. >>>>>>>>> >>>>>>>>> Given the high volume of bug reports relative to other >>>>>>>>> emails, I >>>>>>>>> think >>>>>>>>> it would be very helpful if bug reports were sent to a >>>>>>>>> second, >>>>>>>>> dedicated mailing list rather than the main list. This would >>>>>>>>> make >>>>>>>>> it >>>>>>>>> easier to follow discussions and make it easier to filter and >>>>>>>>> categorize emails in email programs. I suspect, but am not >>>>>>>>> sure, >>>>>>>>> that >>>>>>>>> it would also encourage more discussion since emails to the >>>>>>>>> list >>>>>>>>> would >>>>>>>>> not get lost so easily. >>>>>>>>> >>>>>>>>> -Todd >>>>>>>> >>>>>>>> I agree. >>>>>>>> >>>>>>>> There is a volumnter to ask a new email adress to kde team >>>>>>>> dedicated >>>>>>>> to trace bug report and configure it to bugzilla ? >>>>>>>> >>>>>>>> Gilles Caulier >>>>>>> >>>>>>> CCed Tom Albers, who seems to be keeping track of the mailing >>>>>>> lists >>>>>>> at >>>>>>> least to some extent. >>>>>>> >>>>>>> @ Tom: Do you have any suggestions on how to go about doing >>>>>>> this? >>>>>>> >>>>>>> -Todd >>>>>> >>>>>> Hi, >>>>>> >>>>>> Usually dedicated mailinglists for bugs don't work. It will only >>>>>> be interesting for 1 or 2 people. >>>>>> >>>>>> What I would like to suggest is this: >>>>>> >>>>>> We assign a special bugzilla user to all digikam bugs. That way >>>>>> the mails to the -devel mailinglist will stop. >>>>>> >>>>>> For people that want to get all the mails, they can go to >>>>>> bugzilla and 'follow' that special user. Then they get a mail >>>>>> for all changes as they have received up to now. >>>>>> >>>>>> Is that an idea? If so, please make a sysadmin bugreport (see >>>>>> footer bugs.kde.org) so we can set it up for you. >>>>> >>>>> That would be fine for me, but the digikam developers would need >>>>> to >>>>> make the final decision. >>>>> >>>>> -Todd >>>> >>>> One user who receive all bugzilla mail ? It's weird... >>>> >>>> typically, all developers are registered to a ML. Developers will >>>> be >>>> triggered to interesting reports (typically each developer maintain >>>> a >>>> part in digiKam). >>>> >>>> If only one guy receive bugzilla notification, this filtering will >>>> be >>>> broken. One people cannot dispatch/assign bug to right developers. >>> >>> I think the idea is to have one "virtual" bugs.kde.org user, say >>> "digikam-developers" or something like that. That user is >>> automatically subscribed to all digikam bug reports. >>> >>> On bugs.kde.org, individual users can say that they want to "watch" >>> particular users. Here is the description from bugs.kde.org, which >>> explains it better than I can: >>> >>> "If you watch a user, it is as if you are standing in their shoes for >>> the purposes of getting email. Email is sent or not according to your >>> preferences for their relationship to the bug (e.g. Assignee)." >>> >>> So anyone who watches that virtual user will automatically get all >>> the >>> digikam bug reports emailed to them directly by bugs.kde.org without >>> having to through a mailing list or individually subscribe to bugs. >>> Anyone who wants to stop getting these emails can just remove the >>> "virtual" user from their watch list. >>> >>> What is more, I think it could even be broken up more finely, with >>> "virtual" users for any digikam component (although I am not sure >>> about that). If you do it that way, users could pick which >>> components >>> they wish to follow by watching particular users. >>> >>> Did I explain that right, Tom? >> >> Perfectly! Come work for the sysadmin team :) >> >> One tiny correction: the mails from bugzilla contain the component in the headers if i recall correctly, so your breaking up idea is not needed, you can filter in your mail client. >> >> Best, > > So does this sound like a good plan to everyone? > > -Todd I'm currently filtering dk messages with the following rules: name="dk-commit" action="Move to folder" actionValue="/INBOX/DigiKam/commits" condition="AND (\"x-commit-project\",begins with,digikam)" name="dk-bug-ml" action="Move to folder" actionValue="/INBOX/DigiKam/bugs-ml" condition="AND (\"x-bugzilla-url\",is,http://bugs.kde.org/) AND (\"list-id\",begins with,digiKam)" name="dk-ml" action="Move to folder" actionValue="/INBOX/DigiKam/devel" condition="AND (\"list-id\",begins with,digiKam)" name="dk-bugs" action="Move to folder" actionValue="/INBOX/DigiKam/bugs" condition="AND (\"list-post\",is,<mailto:[hidden email]>)" Something more simple and easyer for newcomers would be good. so +1 - Francesco _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
+1 for me too.
Marcel, Andi ? Gilles Caulier
2011/8/23 Francesco Riosa <[hidden email]>
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Separate bugs mailing list?
|
|
> +1 for me too. > > Marcel, Andi ? > > Gilles Caulier Ok for me, if I can still get mails from bugzilla and I can filter them with KMail to a folder _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On Tue, Aug 23, 2011 at 7:47 PM, Marcel Wiesweg <[hidden email]> wrote:
> >> +1 for me too. >> >> Marcel, Andi ? >> >> Gilles Caulier > > Ok for me, if I can still get mails from bugzilla and I can filter them with > KMail to a folder There doesn't seem to be any objections to this. Should we go ahead and make the switch? -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On Mon, Sep 26, 2011 at 10:45 AM, todd rme <[hidden email]> wrote:
> On Tue, Aug 23, 2011 at 7:47 PM, Marcel Wiesweg <[hidden email]> wrote: >> >>> +1 for me too. >>> >>> Marcel, Andi ? >>> >>> Gilles Caulier >> >> Ok for me, if I can still get mails from bugzilla and I can filter them with >> KMail to a folder > > There doesn't seem to be any objections to this. Should we go ahead > and make the switch? > > -Todd Any progress on this? I couldn't check my email for about 24 hours, and I now have 100 emails about bug updates from kde-imaging and digikam-devel. -Todd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |