Hi,
on Bugzilla some of our frameworks have individual people as the default
assignee. This doesn't really match the reality of how KDE Frameworks
are developed since usually there's no single person responsible for a
given framework. It might give a false impression that this person is
going to take care of the bug. Furthermore, some of the assignees
haven't been active in KDE for as long as I remember.
A lot of Frameworks have "[email protected]" as default
assignee. I propose that we use that for the other frameworks as well
(unless there's a better alternative). We also might consider creating a
kde-frameworks-bugs-null or similar to avoid the historic connotation
with kdelibs.
In particular this would affect:
frameworks-activities-stats (which isn't technically a framework any
more): Ivan Čukić -> plasma-bugs-null
frameworks-attica: Frederik Gladhorn -> kdelibs-bugs-null
frameworks-baloo: baloo-bugs-null can stay
frameworks-karchive: kio-bugs-null -> kdelibs-bugs-null?
frameworks-kcalendarcore: pim-bugs-null -> kdelibs-bugs-null or keep?
frameworks-kcolorscheme: Nicolas Fella -> kdelibs-bugs-null
frameworks-kcompletion: David Gil -> kdelibs-bugs-null
frameworks-kconfig: Matthew Dawson -> kdelibs-bugs-null
frameworks-kcontacts: pim-bugs-null -> kdelibs-bugs-null or keep?
frameworks-kcoreaddons: Michael Pyne -> kdelibs-bugs-null
frameworks-kdeclarative: Marco Martin -> kdelibs-bugs-null
frameworks-kded: kio-bugs -> kdelibs-bugs-null
frameworks-kdesignerplugin: Alex Merry -> kdelibs-bugs-null
frameworks-kdnssd: Matthew Dawson -> kdelibs-bugs-null
frameworks-kdoctools: [email protected] can stay?
frameworks-kfilemetadata: Pinak Ahuja -> kdelibs-bugs-null
frameworks-kholidays: pim-bugs-null -> kdelibs-bugs-null or keep?
frameworks-khtml: Martin Sandsmark -> kdelibs-bugs-null
frameworks-ki18n: Chusslove Illich -> kdelibs-bugs-null
frameworks-kimageformats: Alex Merry -> kdelibs-bugs-null
frameworks-kio: kio-bugs-null -> kdelibs-bugs-null or keep?
frameworks-kitemviews: David Edmundson -> kdelibs-bugs-null
frameworks-kjs: Bernd Buschinski -> kdelibs-bugs-null
frameworks-kjsembed: Bernd Buschinski -> kdelibs-bugs-null
frameworks-kmediaplayer: Alex Merry -> kdelibs-bugs-null
frameworks-knewstuff: Dan Leinir Turthra Jensen -> kdelibs-bugs-null
frameworks-knotifyconfig: David Edmundson -> kdelibs-bugs-null
frameworks-kpackage: Marco Martin -> kdelibs-bugs-null
frameworks-kpeople: Aleix Pol -> kdelibs-bugs-null
frameworks-kquickcharts: Arjen Hiemstra -> kdelibs-bugs-null
frameworks-krunner: plasma-bugs-null keep?
frameworks-kservice: kio-bugs-null -> kdelibs-bugs-null
frameworks-kstatusnotifieritem: Alexander Lohnau -> kdelibs-bugs-null
frameworks-ksvg: plasma-bugs-null keep?
frameworks-ktexteditor: kwrite-bugs-null keep?
frameworks-ktextwidgets: Laurent Montel -> kdelibs-bugs-null
frameworks-kunitconversion: John Layt -> kdelibs-bugs-null
frameworks-kuserfeedback: Volker Krause -> kdelibs-bugs-null
frameworks-kwallet: Valentin Rusu -> kdelibs-bugs-null
frameworks-kwindowsystem: kwin-bugs-null -> kdelibs-bugs-null or keep?
frameworks-kxmlrpclient: Daniel Vrátil -> kdelibs-bugs-null
frameworks-modemmanager-qt: plasma-bugs-null -> kdelibs-bugs-null
frameworks-networkmanager-qt: plasma-bugs-null -> kdelibs-bugs-null
frameworks-prison: Sune Vuorela -> kdelibs-bugs-null
frameworks-purpose: Aleix Pol -> kdelibs-bugs-null
frameworks-solid: unassigned-bugs-null -> kdelibs-bugs-null
frameworks-sonnet: Martin Sandsmark -> kdelibs-bugs-null
frameworks-syndication: pim-bugs-null keep?
frameworks-syntax-highlighting: kwrite-bugs-null keep?
frameworks-threadweaver: Mirko Boehm -> kdelibs-bugs-null
Note that if somebody is really interested in receiving all bugreports
for a given component they can subscribe to it (don't ask me how though).
Any thoughts or concerns about this?
Cheers
Nico