Great! FreeBSD needs help with WiFi!
this post was submitted on 18 Feb 2025
685 points (99.3% liked)
Technology
65819 readers
5249 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
And this is how I see Linux quickly unravelling and planned insecurities creeping in over the next decade or so.
how so?
load more comments
(4 replies)
The future of Foss is in corporate time donations for projects that are useful for them. Open software collaboration is one hell of an efficiency gain. Whenever me or my colleagues have dead time I ask them to work on improving open source projects. It's just a few days every few months but it adds up. Also we like to fix bugs in Foss software that affects our customers as we usually fix and upstream them and can bill that to the customer. So the company gets played, the worker gets payed and open source gets funding. No more sole maintainers for life that don't have money to heat their homes because nobody donates. :)
I would've figured there were multiple standards and such requiring multiple drivers and maintainers, nonetheless manufacturers doing it themselves.
One maintainer, multiple supported devices
You're right that there are many drivers and people from manufacturers responsible for hardware families, but there still needs to be a maintainer for the subsystem as a whole.
That person reviews what the manufacturers and other contributors send in, to validate that things are still compatible where they touch in the kernel, and that the code is good enough. They then prep the commits of the subsystem for inclusion into the next kernel version and pass that to Linus, is my understanding.