Proposal to centralize KCM bugs inside the systemsettings product

David Edmundson david at davidedmundson.co.uk
Mon Mar 16 14:03:35 GMT 2020


On Mon, Mar 16, 2020 at 1:42 PM Nate Graham <nate at kde.org> wrote:
>
> On 3/12/20 10:58 AM, David Edmundson wrote:
> > With one exception: print manager.
> >
> > The version field will not match the product  version . This will be a
> > problem.
>
> Hmm, you're right. I suppose the applet bugs should be moved back into
> print-manager then. Would you like me to do that? There are only four
> bugs in there so it should not generate a flood or emails.

ok.

> > 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.
>
> > We also moved the applet bugs to plasmashell which is confusing since
> > not even kdeplasma-addons are there.
>
> Right now the split between the applets in plasmashell vs
> kdeplasma-addons is a reflection of the implementation detail of which
> repo each applet lives in.
>
Not entirely.

At a repo level we have a deliberate split between core stuff and
non-essential stuff.
The bugzilla grouping is a reflection of that intentional split.

Though that original code split isn't as clear cut as it could be.

> Right now we are not consistent about this: some Bugzilla products are a
> 1:1 mapping of where-relevant-code-lives-to-Bugzilla-product, while
> others are more meta-aggregators of logically connected components (e.g.
> System Settings).
>
Fully ack.

> I prefer the logical grouping approach vs the "perfectly mirror the code
> repos" approach but IMO what's really needed is to be consistent.


More information about the Plasma-devel mailing list