[Digikam-devel] Separate bugs mailing list?

[todd rme]

On Wed, Aug 10, 2011 at 1:16 PM, Gilles Caulier
<caulier.gilles at gmail.com> wrote:
> 2011/8/10 todd rme <toddrme2178 at gmail.com>:
>> On Wed, Aug 10, 2011 at 1:05 PM, Tom Albers <toma at kde.org> wrote:
>>>
>>>
>>> ----- Oorspronkelijk bericht -----
>>>> On Wed, Aug 10, 2011 at 12:46 PM, Gilles Caulier
>>>> <caulier.gilles at gmail.com> wrote:
>>>> > 2011/8/10 todd rme <toddrme2178 at gmail.com>:
>>>> >> 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