Mpc-qt automatic connection request to removable-media

store-requests privileged-interfaces
1
  • name: mpc-qt
  • description: Media Player Classic reimplemented with Qt and libmpv
  • snapcraft: Snap-MPC-QT/snapcraft.yaml at main · Kyuyrii/Snap-MPC-QT · GitHub
  • upstream: GitHub - mpc-qt/mpc-qt: Media Player Classic Qute Theater
  • upstream-relation: I only made the Snap version, but they are aware of the existence of the Snap version.
  • interfaces:
    • <interface-name>: removable-media
      • request-type: auto-connection
      • reasoning: This is necessary so that users can play videos that are on extra HDDs/SSDs. It is possible to use the XDG Desktop Portal to play the videos, but this forces the user to open MPC-QT and use the file selector to choose which files to open. This makes the experience inferior and confusing.
2

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

3

Hello @Kyuyrii !

Given that the mpc-qt snap falls under the media playerscategory, this is a +1 (#voteFor) from my side, for auto-connecting removable-media to the snap.

1 Like
4

Hello, This is a +1(#voteFor) from me as well for granting auto-connection for removable-media to the media player snap mpc-qt pending successful publisher vetting. Thanks!

1 Like
5

Voting period has ended. This request is approved with 2 votes for and 0 votes against.

6

Hey folks!

removable-media makes sense interface makes sense for media players. However, as defined in the Process for aliases, auto-connections and tracks

If the application falls into one of the above categories, then the following criteria will also be considered:

  • the application itself is a mature, well-known application

  • the snap’s (vetted) publisher is a mature, well-known entity

  • the snap’s (vetted) publisher is the upstream of the software

  • if the snap is published by someone other than upstream, the publisher must be vetted and either be an established committer to the upstream or the wider snap ecosystem (eg, an established well-known contributor to the software itself, a member of the snapcrafters group, etc)

    • if the publisher doesn’t meet these criteria, other options may or may not be considered such as the publisher joining snapcrafters, snapcrafters becoming a collaborator on the snap, auto-connection granted conditional on the snap packaging being accepted upstream, upstream stating they trust the publisher with the packaging, etc.

I don’t think you necessarily meet this criteria right now.

That said, I think you have been doing very valuable contributions over the past year to the snap ecosystem (and many others contributions have been blocked / required ugly workarounds because we couldn’t complete the publisher vetting successfully). At this point I think it would be beneficial for you as a publisher and for the snap community if you consider joining snapcrafters. To be honest, I’m not familiar with the concrete requirements, so possibly you don’t meet all of them yet, but if you are interested in joining this group it might be worth filling a [membership application](https://forum.snapcraft.io/c/snapcrafters/23) and see how it goes

1 Like