This is to see how other distros are doing it:
https://protonvpn.com/support/linux-vpn-setup/

As always, B with the mic drop. 100% with the original @gozo suggestion of simple is best: ProtonVPN

I don't have a strong opinion, but I think protovpn or protonvpn-app would make the most sense. protonvpn-app would at least mirror linux-cli --> protonvpn-cli with linux-app --> protonvpn-app. But I also think more people will want to use the GUI instead of the CLI, so maybe protonvpn helps discoverability. I do know that not everyone understands what a GUI is, but the people who want a CLI know what that is.

Good pointS. Just thinking that the software center already listed ProtonVPN-cli and that having ProtonVPN might be confusing. But in general, simple is better…agreed.

Isn't less more?

Since there is already a -cli I would think -gui, no?

Should we call it protonvpn or protonvpn-gui?

package.yml refined

Build process complete. Now checking rundeps and submodules. Then fixing package.yml (sort order of deps and other stuff).

Only accepting this on the condition that it has/is given a sane configuration out of the box.

I'd like to see 2.9.1 released before we accept this.

Tentatively accepting, but this needs Clojure to build since...it's written in clojure.

Given it isn't being maintained, rejected for inclusion.

I would be interested in maintaining this, but it is no longer actively developed:

This project is not being actively maintained. I currently do not have the time nor energy to continue working on it

Banner on the homepage here: https://hg.sr.ht/~scoopta/wofi

While gamescope is under active development, I am rejecting it for inclusion. It uses a version of wlroots that does not exist (0.14.1 being latest and it wanting a non-existent 0.15.x+), uses a version of libliftoff that doesn't exist, and refuses to properly detect + use our stb.

I'm stepping up and will give it a try in the next days.

Note: Due to lack of response by maintainer, this package is being RFCed for a new maintainer. Lack of an update and new maintainer within next 30 days will result in deprecation from the repo.

I would propose to have a woeusb-shell or woeusb-cli package with the packaged bash script and leave woeusb package for GUI. woeusb then have to depend on the cli-package.

Thank you, @algent and @joebonrichie for all your help so far. :)

In T9402#187661, @JoshStrobl wrote:

Just a reminder that we are in need of a new maintainer for this package. If you use paperwork(-backend,gui) then I would encourage you to come forward, get engaged in our packaging process, and update paperwork to the latest release possible. Otherwise, this package is at risk at being deprecated from the repository.

All new dependencies are ready for review.

Enough work for today. I will come back in the next days and will update the arc diffs and include the missing packages. Give me some time to get it ready. I will post it here when I think I'm finished.

The paperwork-shell package has missing dependencies of fabulous and some getkey package. They are available with pip but not in solus repository.

As paperwork-gui is now paperwork-gtk. How should it be renamed?

I've looked at it and see that is consists now of five packages: