Request for classic confinement for nbRsync

store-requests
1

Ok, let’s give it a shot! :slight_smile:

I’m the developer of nbRsync, a gui for rsync.

I would like to request classic confinement for it. The reason for this is to make it possible for the user to execute any programs as they see fit upon pre- and post operation, success or failure, and of course, be able to restore the data.

After reading Process for reviewing classic confinement snaps I realize that backup programs looks to be dangling between supported and unsupported categories, and thus should be handled by a senior reviewer and discussed with an architect.

I have uploaded a strict version of the snap but it’s private for now.

Source available here

and a release (with an AppImage)

I began some probing here to investigate the possibility to make it strict.

/Patrik

2

Given the snap is used for backing up/restoring, @pedronis could we get your opinion on whether this would be a suitable use case for classic?

3

Pinging @cav and @pedronis

4

Pinging @review-team @reviewers

5

Any thoughts on this request?

6

I have been advised by @pedronis that as snapd architect we can look to proceed with granting classic confinement in this case if we can successfully perform publisher vetting as per Process for performing Snap Publisher Vetting - does that sound reasonable @trixon ?

1 Like
7

Sounds good to me @alexmurray , send me a token and I will add it to GitHub - trixon/nbRsync: rsync GUI with an integrated scheduler, and a CLI