125
PiVPN Releases Final Version and Announces Project Shutdown
(linuxiac.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Apr 2024
125 points (99.2% liked)
Linux
45578 readers
764 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Bravo
If I ever maintain a FOSS Project this one will be one of the things I need to figure out along the way, surely there's someone trustworthy out there, surely
But why take a chance? It's easy for anybody who's truly interested to fork it, and if you're calling it a day it's all the same to you.
The problem with endorsing someone else is that they inherit all the clout without having put their time in. Let them prove themselves.
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..
It's a requirement..
to me finding mainteners is part of what makes a FOSS project successful
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.
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
Indeed, or buying-off other maintainers and making them turn against you đź‘€, it's crazy world we live in and everything goes
I don't see a problem in forking, except for issues regarding logistics
Maybe he learned from what happened to uBO before the "Origin" label was needed.
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.