Automatic connection request for gtk-theme-adw-gtk3

store-requests privileged-interfaces
1
  • name: gtk-theme-adw-gtk3
  • description: The theme from libadwaita ported to GTK-3
  • snapcraft: adw-gtk3/snap/snapcraft.yaml at main · lassekongo83/adw-gtk3 · GitHub
  • upstream: GitHub - lassekongo83/adw-gtk3: The theme from libadwaita ported to GTK-3
  • upstream-relation: I’m helping the theme editor release the Snap version and also get the auto-connect. Snap isn’t out yet. I just requested the name, but I’m ahead of schedule, as it may take a while to get the connection. And if needed, yes, I have access to the repository.
  • interfaces:
    • <interface-name>: gtk-3-themes
      • request-type: auto-connection
      • reasoning: It is a GTK theme, it is expected to be used automatically by apps, to generate a better user experience.
2

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

3

Pending vetting to ensure access to the upstream repo, +1 (#voteFor) granting global content auto-connect of gtk-3-themes

1 Like
4

I have already managed to launch Snap gtk-theme-adw-gtk3 on the stable channel.

5

+1 from me for (#voteFor) granting global auto-connection to the requested content interface. Note that publisher vetting is only needed if the snap exposes binaries or libraries (what requires an override). Otherwise, we can go ahead and grant it at the end of the voting period

6

I’m not sure if I understand correctly, does this mean that theme Snaps can receive automatic connection even without being published by the person who created the themes?

7

Hey @Desire_Kyuyrii

As it was discussed in one of your past topics, Auto connection request for flugir-budgie-theme Snap - #12 by jslarraz, the idea was to implement some checks in review-tools to remove the need for publisher vetting under certain situations.

Those checks are now in place and it is now possible for theme Snaps to receive automatic connection even without being published by the person who created the themes, assuming that binaries or libraries are exposed by the content interface.

It still depends on the reviewers criteria to decide whether the it makes sense or not for a concrete snap to receive the global auto-connection and if the snap publisher is likely to properly maintain the snap.

1 Like
8

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

9

Like jslarraz mentioned above, publisher vetting is not needed for this snap as there are no exposed binaries or libraries.

Request has been granted. This is now live.

1 Like