I would like to request classic confinement for ghostty, which is a terminal emulator. I’ve done the packaging and upstream is willing to take it over once we have things all sorted out in the store.
Once we get the snap released in the store and automated builds in place, I will transfer ownership to the upstream project and continue to assist in maintaining the packaging.
The snapcraft.yaml is upstream, @kenvandine is doing the publishing on their behalf and he himself is a star developer, so +1 on this.
This is a terminal emulator, like alacritty, so requires by its nature to be classic.
I believe @zyga worked on a snap for zig, which might clean up the snapcraft.yaml a bit, but it does look like it is following some best practices. The current pull of zig could be done with advanced grammar and organize to keep it a bit more declarative, but that is icing on the snapcraft.yaml looks.
+1 from me.
As for Zig, sadly I don’t have enough deep insight into the ecosystem to offer a comprehensive review.
I just want to note I’m the project creator and maintainer and @kenvandine has my blessing for this.
As a terminal emulator ghostty meets the requirements for classic confinement and fits in a supported category. Whilst @kenvandine is Starred Developer and hence vetted publisher, if it gets transferred we would need to vet the new publisher first.
Classic confinement override granted for ghostty but @kenvandine please let us know before you initiate the transfer so we can verify the new publisher as the official upstream.
