This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.
Hello, Is there any news?
Hello @AndreiDodu!
Sorry for the late response!
Given the snap’s functionality, the request makes sense to me, so +1 (#voteFor) from my side, for auto-connecting the removable-media interface to the noc-convert snap.
Hello,
This request is a +1 (#voteFor) from me for auto-connection of removable-media for the noc-convert snap. Thanks!
Voting period has ended. This request is approved with 2 votes for and 0 votes against.
thank you both @elisehdy and @yomonokio!
Hey folks, sorry for jumping in that late.
According to the Process for aliases, auto-connections and tracks, removable-media interface is considered sensitive as it may give access to sensitive documents, sensitive pictures/media, encryption keys, etc . According the docs it is reserved to major browsers and email clients and media editors/players/recorders.
In addition, snap/publisher is also required. In this regard, I don’t think “the application itself is a mature, well-known application” right now (#voteAgainst). Thus, I would ask other reviewers to reconsider their votes before granting the auto-connection.
At this point of the project, I think that manual connection makes more sense. The usual guidance in this case is to use snapctl is-connected to detect if the removable-media interface is already connected and ask the user to manually connect it when needed
Thank you @jslarraz for your opinion.