Request for manual-review for snap-kcm

store-requests
1

The snap kcm is a KCM Shell (Settings Module) for KDE. But, we can launch it independently, using the kcmshell6 binary. And that’s how I snapped it. I snapped the enitre kcmutils. It requires desktop-launch to launch the apps and snapd-control to change the permissions of snaps. This is using the snapd-glib api to communicate with snapd. I would like this to be in the stable KDE releases, before the 25.04 release, that’s why I am publishing this as a snap in the store. The snap manifest is here

And the whole project is here

https://invent.kde.org/soumyadghosh/snap-kcm

Currently, maintained by me.

Would request @policy-reviewers to look into this and give their suggestions and also, allow the plugs to be auto-connected.

2

Hey @soumyaDghosh

After discussion with @pedronis we will need to know a bit more about the maintainability store for this snap before we can grant an interface as privileged as snapd-control. Could you please give us more context in this regard and clarify if it will be only maintained by you or it is planned to be maintained by the KDE community?

Thanks

1 Like
3

Other than @scarlettmoore mam, I don’t know anyone in KDE Community has experience with snaps. So, it’ll be probably only me for some time. I’ll also get support from the KDE Community, specifically Discover team, with regard to tests and CIs. But the core part is only on me. If @kottens can join me, that would also be great. This snap will be mostly an interim release. My main target is to integrate this into the System Settings, so, a deb package. But, this might also be handy in the all snap KDE Core as this would be the only way to manage the permissions there.

4

@pedronis - Does it sound reasonable?

5

Hello,

Two things on my side:

  1. I don’t think you need to have a copy of kcmutils in this snap, it already depends on the kf6 runtime snap which brings kcmshell6
  2. I don’t think it brings much value as a snap, here is my reasoning: (a) you’re not on Ubuntu Core, you’ll get the KCM in the system settings on your host session, (b) you’re on Ubuntu Core, and the KCM will then be part of the session snap

In both (a) and (b) scenarios I think you’re better off making the KCM part of the Plasma release. To me this looks like a better move than providing a snap.

1 Like
6

Thanks I’ll look into it.

Yes, that’s what my motive is also too. But, because we can’t have it in any major releases soon, specifically Kubuntu 24.10, as there is already feature freeze. So, I am getting this snap to the store for testing and taking feedbacks, look for bugs etc. After everything is properly tested, we can easily have it in the 25.04 release. Also, in the meantime, someone might be able to help with a deb package also.

7

I see the motive. Why not a deb in a ppa for the time being? The thing is, with the snap you’d be testing something different than what you’d want in production in the end.

1 Like
8

I don’t know how to create deb packages, sadly.

9

I can create the deb and toss it in a ppa. As far as maintainership I would certainly hope it is to maintained by the kde community.

Scarlett

1 Like
10

Indeed, in parallel the effort should be made to bring it into the Plasma or Apps release, then it’ll get packaged with the rest as it should be.

1 Like
11

I would still like to pursue with the manual review, as a deb will be limited to a particular release of a particular distro. A snap is very easier to maintain and opens the gate for a big userbase.

As per my credibility and these plugs being super privileged, I am a member of Snapcrafters and Ubuntu, and also, I have a months-old request for Star Developer which has a +1 from @alexmurray.

So, I would request @jslarraz to continue with the request.