Classic confinement for my-workshop

store-requests classic-confinement
1

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

  • name: my-workshop
  • description: Wrapper around the existing workshop snap to make it easier to use workshop for things that doesn’t make sense on a project level.
  • snapcraft: my-workshop/snap/snapcraft.yaml at main · bjornt/my-workshop · GitHub
  • upstream: GitHub - bjornt/my-workshop · GitHub
  • upstream-relation: I am the upstream
  • supported-category: tools for local, non-root user driven configuration of/switching to development workspaces/environments
  • reasoning: It needs to be able to drive workshop programatically. The only way of doing that is by executing the ‘workshop’ command.

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.

2

This request has been added to the queue for review by the @reviewers team.

3

Hi @bjornt,

Please note that classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that my-workshop should meet these criteria:

  • There should be a technical reason

  • It must be a mature, well-known application published by a mature, well-known entity.

  • It must fit in the supported categories

The reviewers’ team is still working on more concrete expectations. Considering the above factors, I think (b) does not clearly meet. Thus, I think this snap should not get classic confinement as of now.