126
PiVPN Releases Final Version and Announces Project Shutdown (linuxiac.com)
submitted 2 years ago by to c/linux@lemmy.ml
13 comments fedilink hide all child comments
 

PiVPN is no longer maintained. You can find more information here

https://github.com/pivpn/pivpn/releases/tag/v4.6.0

you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 2 years ago* (last edited 2 years ago) (1 child)

But why take a chance?

This could be a simple answer as : I don't wanna cause inconveniences to my users to a more complexe one such as.... umm, ideological reasons... I don't want to see a project I started get archived or taken down..

Let them prove themselves.

It's a requirement..

to me finding mainteners is part of what makes a FOSS project successful

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago

    As I see it, there are 3 options.

    Allow forks and let community sort itself.

    Pass on to someone trusted, that ideally has been part of the project for a long time, or even the start.

    Have a fork that is officially endorsed.

    Depending on the software, different approaches may be appropriate. For something like this with VPN, I would want the fork to be vetted by the community before trusting it. If the original owner endorsed one, id probably update to it quickly but keep an eye on the community.

    If it was something with less security risk, id probably move quicker if features were added I like. With something like this, with higher risk, id be assessing forks and alternatives equally.

  • permalink
  • fedilink
  • source
  • parent