[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: RFC: Per Component Bug Assignees
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2013-05-25 15:50:45
Message-ID: 1933014.aaCiPr9GDE () freedom
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Saturday, May 25, 2013 15:44:56 David Edmundson wrote:
> I propose the following:
> 
> Instead of using "plasma-bugs" to all new incoming bugs, we assign one
> new assignee per  per component
> i.e "plasma-bugs-component-widget-battery"

+1; what would be great is if we can arrange for an irc meeting that we can go 
over all the components in kde-workspace (not just plasma). we need to do this 
anyways for the eventual splitting of kde-workspace as part of the PW2 effort. 
with that list in hand, we can assign them into manageable groupings and see 
who (if anyone) is the maintianer(s). imho these two things (assigning modules 
and your proposed email arrangement) would be best done together.

(basically, i'm just suggesting to combine Martin's idea with yours :)

> We set up the original plasma-bugs user to do User Watching on all the
> newly created component assignees so that it remains exactly the same
> for people who don't like change.

with email filters, one can just filter on "plasma-bugs-"; no need for a 
separate user imho.

-- 
Aaron J. Seigo
["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]