Proposal to centralize KCM bugs inside the systemsettings product

[David Edmundson]

On Thu, 12 Mar 2020, 17:58 David Edmundson, <david at davidedmundson.co.uk>
wrote:

>
>
> On Wed, 11 Mar 2020, 16:55 Nate Graham, <nate at kde.org> wrote:
>
>> Forwarding to plasma-devel at David Edmundson's request because I
>> originally sent this to the wrong mailing lists. Will send future such
>> emails to plasma-devel, sorry about that.
>>
>> FWIW the proposed changes were already made, so this is mostly for
>> visibility and record-keeping at this point.
>>
>> Nate
>>
>>
>> -------- Forwarded Message --------
>> Subject: Proposal to centralize KCM bugs inside the systemsettings product
>> Date: Thu, 27 Feb 2020 07:42:23 -0700
>> From: Nate Graham <nate at kde.org>
>> Organization: kde.org
>> To: kscreen-bugs-null at kde.org, jgrulich at redhat.com, nowrep at gmail.com,
>> plasma-bugs at kde.org, albertvaka at gmail.com, nicolas.fella at gmx.de,
>> bhush94 at gmail.com, dantti12 at gmail.com
>>
>> Howdy folks!
>>
>> Right now most Bugzilla components for KCMs live inside the
>> systemsettings product, but there are a small number of exceptions:
>>
>> - bluedevil | kcm
>> - kdeconnect | kcm
>> - kscreen | kcm
>> - kscreenlocker | kcm
>> - plasma-pa | kcm
>> - plasma-nm | kcm
>> - print-manager | general
>>
>> I'd like to propose moving these into components of the systemsettings
>> product, which would make it easier for bug submitters to file bugs in
>> the right place, easier for bug triagers to keep track of System
>> Settings bugs, and easier for Plasma developers to notice significant
>> issues and regressions in KCMs, since we started a new policy of more
>> closely monitoring Plasma bugs, including those filed on the
>> systemsettings product.
>>
>
> It'll help filers and triagers, I'm worried about the impact for the
> maintainers that stick to their one specific domain, which is quite a few.
>
> On a more general comment I'd like us to be at a point where plasma is a
> very small very stable core with a rich ecosystem around it. That means
> approaching things without the monolithic mindset throughout.
>
> That said, what's done is done and we'll see what happens.
>
> With one exception: print manager.
>
> The version field will not match the product  version . This will be a
> problem.
>
> We also moved the applet bugs to plasmashell which is confusing since not
> even kdeplasma-addons are there.
>
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20200312/b921cadf/attachment.html>