Classic confinement request for waveterm

store-requests
1

Wave Terminal (waveterm) is a terminal emulator similar in functionality to zellij and tmux. It falls into the category “terminal emulators, multiplexers, and shells”. Wave Terminal consists of two components: an Electron frontend and a Go backend. These two components communicate primarily over WebSocket on localhost. We use an authentication key which is randomly generated on startup and passed to the backend when it is initialized, to authenticate between the frontend and the backend.

Our backend is what actually requires the classic confinement permissions, as it needs to be able to access any file on the filesystem to preview it in the frontend and it needs to be able to interact with the user’s shell environment to create PTY sessions and SSH to remote hosts.

Our repo is GitHub - wavetermdev/waveterm: An open-source, cross-platform terminal for seamless workflows and our website is https://www.waveterm.dev. We plan to support this Snap as an official package and as our primary target for Linux systems. We do offer native packages for Debian and Red Hat, but we do not plan to submit to their repositories. We also offer AppImage, but we are planning to deprecate it in favor of Snap.

This account is registered under our corporate email (builds@commandline.dev), which is the same one we use for our publisher account. I can provide our GPG key if necessary.

Please let me know if there’s any additional info you require to justify our classic confinement request.

Best regards, Evan Simkowitz (he/him)

2

Hey, thanks @commandlineinc for snapping this application. This snap clearly falls under terminal emulators, multiplexers and shells category and valid case for the classic confinement. Also as you mentioned, this is an official snap and I found PR also created on the repo. So this should be fine for me.

let me know @reviewers, if you have any concerns, I will start publisher vetting process soon

thanks

1 Like
3

Thanks @0xnishit for the quick response! Looking forward to the next steps.

4

Hey @0xnishit checking in, are we good to continue on to the verification stage?

5

Hey @commandlineinc I am starting vetting process as per Process for performing Snap Publisher Vetting

Please provide your github ID associated with this snap on the upstream project.

thanks

6

The upstream GitHub id is wavetermdev

7

thanks, I have DMed you about the next step for the vetting :slight_smile:

8

Publisher vetting has been completed successfully. Granting classic to this snap. this is now live

thanks

1 Like
9

Thank you @0xnishit, I see the first revision for arm64 is now approved, however the second revision with the amd64 package is showing as pending review. Do I need to submit additional information for both archs?

10

Hey @commandlineinc , it should be okay now. I have granted classic form our end and it should not block any future release

let me know if there is still an issue

1 Like