Snap name and classic confinement for Warp terminal

[emitorino]

Hey @david-warpdotdev ,

@david-warpdotdev

I tried registering the snap name warp, but got an error saying “The snap name “warp” is reserved.”. https://snapcraft.io/warp returns a 404, so it’s not clear whether the name is taken by a private snap or it’s something that could be granted upon request.

I believe the issue here is that the store prevents snaps to be registered with names consisting of 3 letter (only). But @verterok or @odysseus-k can provide further information.

@david-warpdotdev

we’ll want to use classic confinement for our Snap

Can you please describe the technical requirements behind this? Classic confinement is a last resource. It means the snaps runs basically unconfined and thus provides device ownership. We exercise due diligence in trying to understand application intent, user expectations, etc to make sure the application can run with the least privileges possible meanwhile enjoying the benefits of a stable runtime environment. Strictly confined snaps can usually achieve their functionality by plugging some of the supported interfaces. This guide should help with debugging the snap and try to detect missing interfaces.

If this still does not work for Warp Terminal, make sure you check the process-for-reviewing-classic-confinement-snaps.