Is It Time For Open Source to Start Charging For Access? (theregister.com)
- Reference: 0181181228
- News link: https://developers.slashdot.org/story/26/03/29/2343236/is-it-time-for-open-source-to-start-charging-for-access
- Source link: https://www.theregister.com/2026/03/25/open_source_bill_opinion/
> Screw fair. Screw asking for dimes. You can't live off one-off charity donations... Depending on what people put in a tip jar is no way to fund anything of value... [A]ccording to a [2]2024 Tidelift maintainer report , 60 percent of open source maintainers are unpaid, and 60 percent have quit or considered quitting, largely due to burnout and lack of compensation. Oh, and of those getting paid, only 26 percent earn more than $1,000 a year for their work. They'd be better paid asking "Would you like fries with that?" at your local McDonald's...
>
> Some organizations do support maintainers, for example, there's [3]HeroDevs and its $20 million [4]Open Source Sustainability Fund . Its mission is to pay maintainers of critical, often end-of-life open source components so they can keep shipping patches without burning out. [5]Sentry's Open Source Pledge/Fund has given hundreds of thousands of dollars per year directly to maintainers of the packages Sentry depends on. Sentry is one of the few vendors that systematically maps its dependency tree and then actually cuts checks to the people maintaining that stack, as opposed to just talking about "giving back."
>
> Sentry is on to something. We have the Linux Foundation to manage commercial open source projects, the Apache Foundation to oversee its various open source programs, the Open Source Initiative (OSI) to coordinate open source licenses, and many more for various specific projects. It's time we had an organization with the mission of ensuring that the top programmers and maintainers of valuable open source projects get a cut of the tech billionaire pie.
>
> We must realign how businesses work with open source so that payment is no longer an optional charitable gift but a cost of doing business. To do that, we need an organization to create a viable, supportable path from big business to individual programmer. It's time for someone to step up and make this happen. Businesses, open source software, and maintainers will all be better off for it.
One possible future... Bruce Perens wrote the original Open Source definition in 1997, and now proposes a [6]not-for-profit corporation developing "the Post Open Collection" of software , distributing its licensing fees to developers while providing services like user support, documentation, hardware-based authentication for developers, and even help with government compliance and lobbying.
[1] https://www.theregister.com/2026/03/25/open_source_bill_opinion/
[2] https://www.sonarsource.com/the-2024-tidelift-maintainer-impact-report.pdf
[3] https://www.herodevs.com/
[4] https://www.herodevs.com/sustainability-fund
[5] https://opensourcepledge.com/
[6] https://news.slashdot.org/story/24/12/04/0426220/ask-bruce-perens-your-questions-about-how-he-hopes-to-get-open-source-developers-paid
I don't disagree. But... (Score:3)
For their money, large companies want the proverbial throat to choke - even when they've never successfully choked the throats they've paid for. The footprint of open source in these companies often grew through bottom up implementation. The moment that somebody has to pay an ongoing support contract, it will become a financial and strategic decision. That means vendor management, tech and vendor downselection, risk analysis... the best-effort maintainer isn't going to fly.
If I were a betting man, I think the result would be a decline in usage - and that might be fine. If the model isn't working, that definitely needs addressing. But the companies most able to afford licensing are probably the ones least likely to pay for it.
Non-commercial use only (Score:3)
Maybe the legal experts could sit down and work out how to modify licenses (including the GPL/LGPL) to be for non-commercial use only? As long as an entity wasn't making money using FOSS, it could use it just like now. Individuals and non-commercial projects wouldn't be affected. But if you're a business making money using FOSS? Not without paying for it you're not. Yes, this would go against the free-software principles. But principles don't pay the bills every month, and none of these changes would prevent anyone from staying with the existing licenses if they wanted to.
The first thing I think of as a problem would be a company setting up a separate entity that wouldn't make money, just make services available to the company using FOSS to get around the fees. The trick to preventing this would be to phrase the terms so that that entity truly had to pay it's own bills without having the company using it's services pay anything either directly or indirectly. Not even by doing things like providing hosting "free". I'd have to sit down with a bunch of rules lawyers and game out all the ways to funnel money into that entity and how to block them, but what's life without a little challenge?
Re: (Score:2)
Maybe not.
Re: (Score:3)
QT does a dual-licencing system, you have to pay if you don't want to share back via the GPL. And there is also the AGPL - which could work well in dual licencing for services?
Not quite the same, but there's some overlap in what it solves.
We're not getting paid for this (Score:3)
That was always one of the suspension of disbelief breaking aspects of Star Trek, too. As if anyone would deal with all the responsibilities and risks involved in being a starship crew member when you could just fake the entire experience in a holosuite instead.
Of course, open source developers working on their own time have the worst of both worlds - along with the rest of us, they're not living in a Star Trek post-scarcity society, and they're also not getting paid. I've always been kind of surprised that the movement didn't immediately fizzle out. If anyone asked me to do more of the same tasks I perform during my day job, but for gratis during my free time, I'd tell them in some not-so-kind language exactly where they can stick it.
Re: (Score:1)
> That was always one of the suspension of disbelief breaking aspects of Star Trek, too. As if anyone would deal with all the responsibilities and risks involved in being a starship crew member when you could just fake the entire experience in a holosuite instead.
Which is more believable? Simulating real life in a holodeck or the Goddess of Empathy?
Re: (Score:2)
> That was always one of the suspension of disbelief breaking aspects of Star Trek, too. As if anyone would deal with all the responsibilities and risks involved in being a starship crew member when you could just fake the entire experience in a holosuite instead.
Some people absolutely would want that responsibility and risk. But also, Starfleet is a military organization. They don't get a real choice in where they get assigned, outside of a few exceptions.
If payment's required to access open-source sw (Score:5, Insightful)
... then that project is really can't be described as open source anymore.
Huh (Score:2, Troll)
The same people who steal music, software, and videos now want others to pay for their work.
Time for a tax. (Score:3)
Vaughan-Nichols is right about the problem and wrong about the solution. Voluntary pledge funds and tip jars have existed for a decade and the 60% unpaid figure hasn't moved. Sentry is admirable precisely because it's an exception, the model doesn't scale because it depends on individual corporate virtue, which is in shorter supply than VC funding.
Perens' Post Open licensing approach is interesting but creates a two-tier ecosystem: "free for individuals, pay for commercial use" sounds clean until you realize it breaks the fundamental property that made open source eat the world. The moment a license is commercial-use-restricted, it's not open source, it's source-available, and enterprises will treat it accordingly (avoid it, fork it before the license change, or just use the last MIT-licensed version forever).
What's actually needed: mandatory contribution structured as a fee, not a license restriction. Here's one way to do it. Small flat fee on all US commercial revenue above $5M (the entire world runs on OSS, everyone pays to maintain it), larger marginal fee on companies whose products directly incorporate OSS. Fees flow into a scoring-based royalty pool: your project's share is proportional to how much commercial revenue depends on it, revenue-weighted so a hedge fund running its entire risk engine on a niche numerical library counts for more than fifty startups using the same package for weekend side projects. Maintainers register and claim their allocation like music royalties, no government agency decides who gets hired, just checks cut proportional to actual commercial stakes.
The core insight: you can't solve a collective action problem with voluntary action. You solve it by making the externality visible in the price.
Absolutely (Score:2)
Commercial access should definitely be charged, either in terms of money or developer contributions. If others want to profit off my work, they should have to share them with me, fairly
We must normalize paying for worth (Score:3)
Would an executive at any big tech company go to a nice restaurant and not tip the waiter? Of course not, because it is expected for them to pay for the worth.
This needs to be the case in open source. To not frame it as “donations,” but that worth should be paid for.
But how do we start this? I would love to find like-minded folks to help build a Pay It for Worth campaign. We get businesses to sign a pledge to pay for worth and give them advertising so that we get customers to see who isn't freeloading. And we get a grassroots way for small businesses to take paying for open source to be a legitimate business expense they can deduct on their taxes, unlike the current donation limit they currently have to deal with.
Re: (Score:2)
> But how do we start this? I would love to find like-minded folks to help build a Pay It for Worth campaign. We get businesses to sign a pledge to pay for worth and give them advertising so that we get customers to see who isn't freeloading. And we get a grassroots way for small businesses to take paying for open source to be a legitimate business expense they can deduct on their taxes, unlike the current donation limit they currently have to deal with.
Maybe start with a public leaderboard by projects simply naming annual and historical FUNDING.yaml the way AUTHORS, etc.are tracked. With a standard, machine-readable format totals could be added up across the ecosystem.
Naming the good actors provides a carrot and stick. Maybe if practice grows to the point people want to game it, this non-profit people dream of could step in and do the labor to vet, track, and vouch for contents of a formal funding registry.
stupid (Score:1)
so literally closing the source, or do you not know what the words mean
get it or don't (Score:1)
Honestly this is the stupidest article i've ever seen. The way to get open source maintainers paid is to make them the only source, ie to make open source software the only legal software. Which is a good idea anyway, because you are NOT a temporarily displaced millionaire, and the world would be better for it in ways you can't even imagine right now.
Torn on this (Score:2)
Concerned that the reason we keep doing open source is because we believe in access.
The false tradeoff there, is believing that access and exploitation are necessary corollaries. And I don't think they are.
It's a tough balance, and open source licenses have clearly failed us here.
But I'm not sure where to go with it. Shared source might be better, like the Mongo license, or something like it. The Kimi2 license had the right idea.
On the other hand, when you leave the open source path, you pay by losing acces
It would end F/OSS (Score:2)
Don't get me wrong. I am not complaining about the idea open source developers being paid.
But very few people use open source, in any serious way. If they had to pay for it, a lot less people would use it. Eventually, it would not be worth maintaining.
Good for basic income, no? (Score:2)
Unless this is really about fidelity to economics and not software, can you imagine the pure engineering productivity unleashed if engineers had a decent guaranteed inflation-proofed basic income and didn't have to listen to bosses telling them to artificially restrict access and features due to advertiser pressure?
Why now? (Score:4, Insightful)
This has literally been the case now for 40 years, and yet the open source movement is stronger than ever. So why now? Also charging for access? Stallman will rip your balls off.
How economic models work (Score:4, Interesting)
> This has literally been the case now for 40 years, and yet the open source movement is stronger than ever. So why now? Also charging for access? Stallman will rip your balls off.
Citation needed.
My current citation is Microsoft Secrets by Cusumano and Selby. Kind of old, so maybe someone can say how much things have changed over the years, but the point is that they are too optimized about getting more money. And they dominate the real world.
OSS is "stronger than ever"? In which dimension? I can't think of one. Even programmer satisfaction.
Me? I'm still hung up on the notion of a better structured charitable approach. Recovering costs, where the costs include appropriate payments for the programming work. The CSB (Charity Share Brokerage) will earn their way be providing project planning and management support. But I'm sure there will never be a CSB and it is too late to even try at this point. Very minor consolation that Microsoft also found project management difficult even back then...
Re: (Score:2)
I much prefer charging for access to having [1]corporate fifth column interlopers [itsfoss.com] steer linux away from all its core values, but it is very much the lesser of two evils.
[1] https://itsfoss.com/dylan-taylor-systemd-controversy/
Re: (Score:2)
> Stallman will rip your balls off.
Funding via pay per view? There's an Idiocracy joke in there somewhere...