Raftt is a tool to easily manage development environments which we are about to release soon.
raftt doesn’t require root access to run.
We have two reasons to need classic confinement:
Allowing the user to configure arbitrary command for the tool to run - raftt allows users to configure commands to run on their local machine for gathering custom data to use in remote development environments.
Accessing files in any directory the user chooses to work on (which we obviously cannot know in advance). As far as we could find, the existing interfaces does not allow that (they only allow explicitly specified paths, home directory and removable media).
As per the Process for reviewing classic confinement snaps, raftt meets the requirements for classic confinement due to the need to execute arbitrary binaries and fits within the existing category for classic confinement of tools for local, non-root user driven configuration of/switching to development workspaces/environments. As such the requirements for classic confinement are understood.
@advocacy could you please perform publisher vetting?
Yes this is a “constant approval” - once this is granted any revision which declares confinement: classic should pass automated review (assuming any other issues are not detected).