|
|
Log in / Subscribe / Register

"Critical" projects and volunteer maintainers

"Critical" projects and volunteer maintainers

Posted Jul 14, 2022 13:28 UTC (Thu) by martin.langhoff (subscriber, #61417)
Parent article: "Critical" projects and volunteer maintainers

We need to go back to larger libraries maintained collaboratively by a community of maintainers. All these solo maintainers with tiny-but-critical libraries are unsustainable.

It's a romantic ideal, it worked while OSS was on the margins, but it's impractical in real life in the mainstream.

As a developer using a library, you don't want a single "solo maintainer" dependency. In the best days, you are absorbing code changes without peer review. On a bad day, the maintainer can go rogue, have health issues, have credentials stolen...

Let's go back to larger "standard libraries" and frameworks, team maintained. Each part of them can be small, but the umbrella effort is larger, involves more people, can have 'peer review' rules and it's a more reasonable target for corp funding.


The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:

Note: you can avoid this step in the future by logging into your LWN account.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds