Request classic confinement for freelens-previous-name-was-revoked

[dex4er]

Really, I have now such name as previous name is blocked. Anyway:

---

• name: freelens-previous-name-was-revoked (seriously…)
• description: Free IDE for Kubernetes
• snapcraft: freelens-snap/snapcraft.yaml at main · freelensapp/freelens-snap · GitHub
• upstream: GitHub - freelensapp/freelens: Free IDE for Kubernetes
• upstream-relation: Snap published by the project
• supported-category: IDEs, kubernetes tools requiring arbitrary authentication agents
• reasoning: Kubernetes IDE shares the same context and tools as other CLI tools for Kubernetes. It would be unexpected if user couldn’t login to the cluster, ie. because of missing authentication helpers. Also IDE provides the terminal and it is expected to see the home directory with the access to the all dot directories and the commands from the host.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

Note that snappy-debug can be used to identify possible required interfaces. See https://snapcraft.io/docs/debug-snaps for more information.

[jslarraz]

Hey @dex4er

The request makes sense to me and I’ll be happy to grant it after publisher vetting.

However, it think it makes more sense to get the previous name (freelens) back before granting it. @store any chance you can take a look?

Thanks

[dex4er]

I think today is a full month of my waiting. During this time I published the initial version then upgraded new packages a few times: Homebrew, WinGet, Flathub, AUR. For all of them I’ve got nice, professional review and support from the owners of the publishing services.

I really don’t complain. I’m just curious, why I experience such things here. Has this store been abandoned by its owners?

Thanks.