GNU nano is especially useful in editing files in the system directories in the classic system.
As a result, although this application is definitely possible to be snapped under strict confinement, it can be more useful if we also provide a version that is in classic confinement. I am willing to make compromises in order to make it past the vetting process(like transferring the snap to any trustworthy entity to reduce the risk to the users).
Personally, I think the path least likely to cause confusion among users would be to make the existing nano snap classic, matching other editors. Note that because classic is less secure than strict, systems will not automatically upgrade to it. They’ll be on the old version until manually upgraded with --classic.
@jdstrand I can confirm that @Lin-Buo-Ren is a prolific Snapcraft contributor, well known to us and would certainly be a great candidate to maintain the nano snap. That said, as far as I know, @Lin-Buo-Ren is not an upstream nano contributors/maintainer.