PiVPN is no longer maintained. You can find more information here
I will maintain ownership of the repository, but I won’t pass it down to anyone else. First, because I feel it’s not up to me to decide who to pass the project down to, and second, because there is no one else to pass the project to.
“But I want and can maintain it, can I take it over?” Let me put it plain and simple: No! I don’t know you, I don’t trust you! Fork it and carry on!
Bravo
deleted by creator
Lesson learned from the whole XZ thing. Anything related to security does run the risk of nation state actors abusing trust. Makes it hard to do right
deleted by creator
Maybe he learned from what happened to uBO before the “Origin” label was needed.
I don’t see a problem in forking, except for issues regarding logistics
I vaguely remember some money calculating-related project guy who received a PR that heavily optimized and updated the project. Since he was very busy and no longer really wanted to maintain the project, rather than reviewing and merging the commit, he gave the contributor complete access to the repo for them to maintain the project at their own discretion. The project was unpopular back then—when he looked back a few years later, he was surprised to discover that the project had racked up several thousands of stars.
PiVPN is great and was one of the first services I experimented with on my old Pi 3.
Now with wireguard existing I didn’t feel the need for anything besides wg-quick or using wireguard directly. I didn’t even know PiVPN got support for wireguard, but it’s great that it got maintained for so many years.
