Removable media auto-connect request for celluloid-twin

Hello, I would like to know if the celluloid-twin Snap can receive automatic connection for the removable-media connection.

Celluloid-twin is basically an older version of Celluloid, which still used GTK3. I released it thinking about recovering design consistency, since the current Celluloid does not follow the user’s theme.

I would like it to access removable devices to improve the experience of those who want to use it.

The snapcraft.yaml for this Snap is in this link:

As discussed in the Autoconnect request for celluloid, removable-media requires of publisher vetting. Could you please clarify if you are a member of the upstream project?

Anyway, maybe using portals as proposed by @soumyaDghosh is a better approach.

Thanks

I’m not part of the project, celluloid-twin is an old version, which still uses GTK3 and is not libadwaita, precisely going against the current state of Celluloid.

I released it because I wanted to bring back design consistency across the system, as the current Celluloid doesn’t fit with the design of Budgie, Cinnamon, XFCE and Mate.

One question, in the other request I made, involving GTK themes, if the theme creator says I’m involved with the project, then Snap will be able to receive the automatic connection?

Or does the publisher specifically need to be the creator in order to receive the automatic connection?

In general, the snap publisher needs push access to the upstream repository to complete the publisher vetting, which is required as of now to receive the automatic connection.

One last question, in a theme Snap, does it need to be a separate Snap for the icons and another for the GTK themes? Or can they be all together?

And another question, can there be several different themes, or just variations of the same theme?

I ask this because it must be a lot of work to request automatic connection several times for each theme and each icon theme that the person has.

One last question, in a theme Snap, does it need to be a separate Snap for the icons and another for the GTK themes? Or can they be all together?

I think they can be all together.

And another question, can there be several different themes, or just variations of the same theme?

I would say just variations of the same theme, but maybe @alexmurray can correct me

I ask this because it must be a lot of work to request automatic connection several times for each theme and each icon theme that the person has.

For the time I’ve been doing reviews, I would say that auto-connection requests for themes are very rare. Also, content interface already auto-connect if snaps declaring the plug and the slot are published by the same person.

Finally, we also don’t want to grant global auto-connection without understanding the story behind the snap and the publisher, because any future change change in the theme snap may break all snaps using that theme.

Thanks

1 Like

There really are few themes in the Snap Store, and the lack of automatic connection takes away part or all of people’s desire to launch themes on Snapcraft.

For example, I saw that the lack of themes is a problem, I went looking to find out how to put a GTK theme in a Snap, and I discovered that it is extremely simple.

But it’s discouraging to see that whoever uses my Snap, a simple theme Snap, will need to use commands.

You can see the snapcraft.yaml of budgie-common-themes, there’s nothing special about it, it just copies the theme files into a Snap and allows them to be accessed.

It’s even simpler to understand than gtk-common-themes.

I understand that around here you need trust to be able to gain automatic connection to a Snap of themes, but if that is what is necessary, how do I gain your trust?

Via publisher vetting (as pointed out above) Process for performing Snap Publisher Vetting