> it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments.
I am. I enjoy making things, and it's even better when others enjoy them. Just because you have expectations that you should be compensated for everything line of code you write; doesn't make it ubiquitous, nor should your expectations be considered the default.
I'd argue If you're creating and releasing open source with the expectations of compensation, you're doing it wrong. Equally, if you expect someone creating open source owes you anything, you're also part of the problem, (and part of why people feel they deserve compensation for something that used to be considered a gift).
All that said, you should take care of your people, if you can help others; especially when you depend on them. I think you should try. Or rather, I hope you would.
I think this is the piece so many that are stuck in the hustle culture mindset miss, and why they are so quick to dismiss anything like UBI or a strong social safety net that might “reduce people’s motivation”. There are many many creative, caring people that are motivated to create things or care for each other for the sake of it, not for some financial reward. Imagine the incredible programs, websites, games, crafts, artworks, animations, performances, literature, journalism, hobby clubs, support groups, community organizations that would spring into existence if we all just had more bandwidth for them while having our baseline needs met.
Would it be chaotic? Sure, in the same way that open source or any other form of self-organization is. But boy it sounds a whole lot better than our current model of slavery-with-extra-steps…
My apologies - you’re correct. I didn’t mean that as “you should never expect anyone to have contributed code for free/the pleasure/for the puzzle solving aspect”. I do it all of the time.
I meant - it’s unfair to consider that because this labor “fell from the sky”, you should just accept it - and as others have said, in the case of projects that become popular, that the burden should just automatically fall on the shoulders of someone who happened to share code “for free”.
If/when someone ends up becoming responsible for work they hadn’t necessarily signed up for (who signs up for burnout?) - it’s ok/necessary/mandatory to see how everyone (and or Nvidia/Google/OpenAI etc) can, like, help.
My insistence is on the opt-out nature of this so that people who would be ok being compensated don't have to beg.
Consider how the xz malware situation happened [0]. Or the header & question 8 from the FAQ for PocketBase [1].
I agree with you, but I do think we have a bit of a problem in which an open source creator makes something and then suddenly finds themselves accidentally having created a load-bearing component that is not only used by a lot of people and companies, but where people are demanding that bugs be fixed, etc., and we lack great models for helping transition it from "I do this for fun, might fix the bug if I ever feel like it" to " I respect that this has become a critical dependency and we will find a way to make it someone's job to make it more like a product".
I gather that the open source maintainers who have found themselves in this situation sometimes get very unhappy about it, and I can see why -- it's not like they woke up one day and suddenly had a critical component on their hands, it kind of evolved over time and after a while they're like "uhoh, I don't think this is what I signed up for"
Yes and yes. I make open source software because I fundamentally enjoy the act of learning something new and then applying that knowledge by making something. I publish it for the ego boost only. I am equally likely to be irritated by contributions than to be excited by them. My day job contributions are up for scrutiny but the personal projects I publish on github are my island, my sovereign ground. As exciting as PR interest is, sometimes I don’t really want someone to paint over my painting. It’s mine after all. I obviously don’t speak for all open source contributors but I don’t want compensation. If someone wants to fork my work and turn it into a community then they are free to do so as a result of my licensing choice. If the first few contributions I receive are pleasant and someone takes over then that is great too. My point is that not all creators are aggregators. Leave us alone and stop complaining. We gave it away for free after all.
I was going to comment exactly the same thing, thanks for expressing it so well and here's my upvote. I think part of why I wanted to comment the same, is that for me this IS exactly the reason I make open source! It is my gift for everyone, please use it well.
I do think it would be nice to get paid anything at all, but that wouldn't change at all how I do things/release code. In fact, unless it'd be really no-strings-attached, I'd prefer to keep the current arrangement than being paid a pittance per month and then have extra obligations.
People really want to have a business with none of the work of running a business. They want to make something useful, then have people just pay them for it without any of the things that go into operating a business. In a perfect world value would directly correlate to income, but it isn't even close to being the case, there's a lot of coercion and control of supply that goes into owning a business.
> I'd argue If you're creating and releasing open source with the expectations of compensation, you're doing it wrong.
I think this is a little unfair, given that many (especially younger maintainers) get into it for portfolio reasons where they otherwise might struggle to get a job but stick around because of the enjoyment and interest. It still sucks that so many big orgs rely on these packages and we're potentially experiencing a future when models trained on this code are going to replace jobs in the future.
I think a lack of unionisation is what puts the industry in such a tough spot. We have no big power brokers to enforce the rights of open source developers, unlike the other creative industries that can organise with combined legal action.
thanks grayhatter. well said. been programming for 20+ years never earned a dime from it dont want it. its a silly assumption that everyone's motivation is money. this is very far from the truth.
>it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments
Yes it absolutely is. That is the exact social contract people 100% willingly enter by releasing something as Free and Open Source. They do give it as a gift, in exchange for maybe the tiny bit of niche recognition that comes with it, and often times out of simple generosity. Is that really so incredible?
Agreed. Supporting open source maintainers is a great idea in general, but shaming people for using something according to the exact license terms it was released with is getting old.
A natural solution for this kind of problem would be either a private or public grants program. Critical infrastructure built by random uncompensated people... ideally there would be some process for evaluating what is critical and compensating that person for continued maintenance.
Maybe it's just me, but I don't think the solution to the open source funding problem is to force people to pay for it. I think that goes against the spirit of open source. If there is forced payment, or even the expectation of payment, then we're not really doing the whole original open source thing, we're just doing bad source available commercial-ish software.
I think the solution is for people to understand that open source goes both ways. Unlike what this post says, users don't owe maintainers anything, but maintainers also don't owe the users anything. If I build something cool and share it freely, why should users expect anything from me? Why should you expect me to maintain it or add the features you want? I think we need a mentality change where less is expected from maintainers, unless funding is arranged.
After all, it's free and open source. No one is forcing you to use it. Don't like that I'm not actively developing it? Submit a PR or fork it. Isn't that what the original spirit of open source was? I think that open source has been so succesful and good that we've come to expect it to be almost like commercial software. That's not what it is.
> I think that goes against the spirit of open source
Strictly speaking open source originally was not to do with whether you paid for something or not, it was that if you did pay for it, you got the code and had the rights to make your own changes.
Think Free speech, not free beer, or the software equivalent of right to repair.
If this actually happens, get ready for an avalanche of AI-generated garbage code that exists for the sole purpose of boosting a scammer's metrics, so they can maximize their slice of the pie with the minimum amount of effort. Spotify is dealing with this same issue around AI-generated music [1].
Been living off grants and donations for a few years now. My 2c is you probably don't need to invent a new platform to fund open source development. There are tons of platforms and systems in place already. That's not's what's missing. You need to get open source developers that want to get paid for their work to spell that fact out to their users and supporters.
Yes this is uncomfortable, but the simple fact is that if you don't tell anyone you want to get paid, you probably won't be given any money. Standard seem to be maybe there's a donation link somewhere on the site, buried 4 clicks deep in the FAQ, more often than not something like a paypal.
The reality is that if you do ask for money, surprisingly often people will straight up just give you money if they like what you're doing. Like people get paid real money for screaming at video games on Twitch, meanwhile you're building something people find useful. Of course you can make money off it. But you gotta ask for it, the game screamers on twitch sure do. That's the secret. Sure there's a scale from asking for donations and doing a Jimmy Wales and putting a your face on a banner begging for donations; and while going full jimbo is arguably taking it too far, it's also probably closer to the optimum than you'd imagine.
If you have corporate users, word on the street is you can also just reach out to them and ask for sponsorship. They're not guaranteed to say yes, but they're extremely unlike to sponsor you spontaneously.
> Those funds would then be distributed by usage - every mention in a package.json or requirements.txt gets you a piece of the pie.
Usage is not a good proxy for value or ongoing effort. I have a npm package with tens of millions of weekly downloads. It's only a few lines long and it's basically done - no maintenance required.
I'm skeptical that there exists an algorithmic way to distribute funds that's both efficient and resistant to gaming.
The first order effect of this would be great, but the following onslaught of schlinkert spam would be devastating- its bad enough now with people making garbage dependencies and sneaking them in everywhere just for clout
Sadly I think this is true. There is already a problem with people making useless dependencies and pushing them into projects with PRs to increase their download numbers.
Showing high download numbers on your resume is more valuable than anything a fund like this could provide. There will always be a company who views high NPM download numbers as a signal of top 1% talent, even if it has become a game in itself.
Proposals like these seem to assume that FOSS is mostly produced by unpaid volunteers. But a lot of the open-source stuff that I personally use is produced by massively profitable companies.
For example, I am currently working with React, which was produced by Meta. I write the code using TypeScript, which was produced by Microsoft (and other corporate behemoths such as Google). I am writing this comment in Chrome (produced by Google). Etc.
Chrome is not FOSS btw. Google Chrome is proprietary software based on the open-source Chromium (also created by Google), which in turn is a fork of Webkit (by Apple, and with many corporate and non-corporate contributors), which itself is a fork of KHTML/KJS from the KDE project.
You are still right that corporations found and contribute to countless open source projects though.
If you willingly choose to make source code publicly available under an open source license you can’t then act all shocked that people don’t have to pay you for using that code. If you wanted to be guaranteed an income whenever your code gets used, you should have chosen a different license.
perfectly articulated. Moreover, the license is whatever the copyright holder wants to put into it. They can easily dual license , copy-left variants -- there are tons of licenses that provide compensation for commercial use.
And if you're ok with not getting paid but you are shocked that corporations take it and use it in a non-FOSS-compatible way (e.g. selling their version for money) you should have used GPL instead of MIT.
I paid 1 buck for WhatsApp back in the day. Better business model than what meta did with it. But we're moving closer and closer to 8 companies controlling the world. Both WhatsApp and github are owned by them.
> we're moving closer and closer to 8 companies controlling the world.
Which 8? In the control the world domain I see Meta, Google, Amazon, Apple, Microsoft. In terms of Market Cap you would add Tesla, Nvidia and TSMC, but these three aren't any where close to "controlling" the world category.
This would not fund the people you want it to fund.
Bad or borderline actors would be so much better at creating whatever metrics you're basing things off of that the actual value creators wouldn't stand a chance.
The transitive nature of dependencies makes fund allocation extremely wonky. Say you have Next.js as a dependency in your package.json file? How many dependencies does Next.js itself have? What portion of your funds go to Next.js versus all the transitive dependencies of Next.js?
$1 USD is ~90 Indian Rupees, 1450 Argentinian Peso or over 1 million Iranian Rial [1]. In some places, $1 USD could be a week's work. On the collection side, you could be seriously over-charging people. On the distribution side, you could be seriously overpaying people for their work - and encourage scams, etc.
> GitHub should charge every org $1 more per user per month and direct it into an Open Source fund, held in escrow.
Sure. It'll be some charity, then somebody gets paid $200k+ per year to distribute what remains after they've taken the majority, all whilst avoiding most taxes. To receive the money the person has to ID themselves, financial background checks need to be done, a minimum amount needs to be reached before a payment is made, and then after passing through multiple wanting hands, they end up with a fraction.
> Those funds would then be distributed by usage - every mention in a package.json or requirements.txt gets you a piece of the pie.
What even is "usage"? How many times it appears in a number of repos? How many users there are of the project? Is the usefulness and value of a project limited to the number of people that directly use it?
> Or don’t! Let’s not do anything! People’s code and efforts - fueling incredibly critical bits of infrastructure all around the world - should just be up for grabs. Haha! Suckers!
> Anyway, you all smarter than me people can figure it out. I just cannot accept that what we have is “GOOD”. xx
It's entirely possible you can make things worse by avoiding doing nothing. Sometimes in life you have to pick the lesser of evils.
Many open source projects are created by engineers being paid to solve a problem their employer has, and they just happen to release it freely.
I don't think Google needs a dollar every time I write a script in golang or run a container in kubernetes, and I would put a lot less trust in Envoy if I thought Lyft was building it profit and not because they needed to.
Instead of a dollar from github users, I think it should just be a hefty tax on big tech companies that have valuations of over a billion. The nature of software and tech means that there are massive monopolies where winner takes all. We should just accept that and leverage it.
No idea why this has got the traction it has. Absurd and poorly thought through. It sounds like you don’t like building open source software, so stop doing it. Don’t write a blog post whining about the cage you have shut yourself in. Absolute martyr complex.
Every day, millions go to work because they have to eat. Every day, thousands (?) go to their computers in their free time and make OSS software. Not because they have to eat but because [?]. Then they or others complain that people take their work that they do for free under no duress for free.
Maybe economists could do what is ostensibly their job and try to prevent the “tetris game of software depending on the OSS maintained by one guy in Nebraska...” situation. In the meanwhile people who do things under no duress for free could stop doing it.
(Not that OSS is all hobby activities. There are many who are paid to do it. But these appeals only talk about the former.)
One thing I thought that got me interested about Brave was this part of their business modell. It had the potential to support this type of economy almost without any attrition. It was not that different from flattr, with the difference that people would be able to contribute just by accepting the notification ads and passing along their earnings.
Unfortunately, the crypto angle made sure that mostly degens and speculators got into it. Perhaps if stabletokens were more established by the time they started, it would be easier to market it.
(I am not going to get into yet-another discussion about Brave as a company. I will flag any attempt at derailing the conversation.)
> Alright, I don’t know how you fund Linux (does Linux appear in a requirements file). Hmm.
By paying companies like Red Hat, Canonical, Google and Amazon, who in turn spend massive amounts of money employing software developers to work on Linux.
>It is crazy, absolutely crazy to depend on open source to be free (as beer).
Why? It's not crazy at all. It's the status quo with no sign of things changing. It is both possible right now and likely continue. Its not crazy.
If it's not worth maintaining people will stop. If people need it they will develop it. The current incentive structure has produced lots of open source code that is being maintained.
>It is not okay - it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments.
It is if there is no cost. You can always charge for it. But you can't make it free then pretend its not.
I think we sometimes treat "open" as automatically good without examining the tradeoffs.
You can easily sponsor Iran or Russia killing real people by doing such things.
Powerful tools, once released, can be used by anyone, including those with harmful intentions. And let's be honest: much of open source functions as a way for large companies to cut costs on essential but non-differentiating infrastructure. That's fine, but it complicates the idealistic narrative.
With generative AI, these questions matter more. Maybe it's time to revisit what open source should mean in this context.
This transformation of open-source into rent-seeking behaviour is quite distasteful to me. If you don't want to share your stuff without taxing everyone, then don't share it. Other licenses exist. You don't have to use MIT or the GPL.
Meta has even demonstrated an alternative with the Llama 4 License which has exclusion criteria:
> 2. Additional Commercial Terms. If, on the Llama 4 version release date, the monthly active users of the products or services made available by or for Licensee, or Licensee’s affiliates, is greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta, which Meta may grant to you in its sole discretion, and you are not authorized to exercise any of the rights under this Agreement unless or until Meta otherwise expressly grants you such rights.
Go put such terms in your licenses.
This is particularly rampant in the Rust community and if I'm being honest this forced tithing church nonsense from people who want to be priests makes participating in that community less desirable. I don't even want to donate to the RSF as a result.
All the other projects I've donated to in the past have been much more reasonable. This kind of pushy nonsense is unacceptable.
> If you don't want to share your stuff without taxing everyone, then don't share it. Other licenses exist. You don't have to use MIT or the GPL.
I agree. Yet some of my comments here have been met with downvoting and explanations that GPL licensing is a moral imperative, so there is certainly a contingent who would disagree.
> This is particularly rampant in the Rust community
This is interesting. Do you have examples? I am not cognizant enough of interactions there.
I've seen plenty of cases of making something a target where quality won't be measurable and immediately cut off the reward or apply penalties. I don't really want Microsoft to run a large fund that encourages people to try to take over roles and request cash, etc.
Literally anyone could create a support and maintenance organization that takes MIT license projects into an AWS like split and only get paid if the support they provide remains valuable to people who pay for the value of the support and maintenance.
I've spent a bit of time thinking about this[0] - as a maintainer (oapi-codegen, Renovate, previously Jenkins Job DSL Plugin and Wiremock), as someone who used to work on "how can we better fund our company's dependencies", and building projects and products to better understand dependency usage
As others have noted, there are a few areas to watch out for, and:
- some ecosystems have more dependencies over fewer, and so we need to consider how to apply a careful weighting in line with that
- how do we handle forks? Does a % of the money go to the original maintainers who did 80% of the work?
- how can companies be clever to not need to pay this?
- some maintainers don't want financial support, and that's OK
- some project creators / maintainers don't get into the work for the money (... because there is often very little)
- there's a risk of funding requirements leading to "I'm not merging your PR without you paying me" which is /not problematic/ but may not be how some people (in particular companies) would like to operate
I have a better idea-- why doesn't GitHub (that closed source platform) donate 20% of all revenue to opensource projects that enable the company to exist?
> every mention in a package.json or requirements.txt
OK, what about those of us who aren't writing libraries?
As a personal anecdote, the amount of opportunities that have been opened up to me as a result of my open source project are worth way more than any $1 per mention or user.
OSS works partially because a lot of stuff is free as in beer. I rely on probably many thousands of OSS projects directly or indirectly on a daily basis. So does everyone else.
The problem for some people is that they want to get paid for their work and just aren't; or not enough. I won't judge that. Writing software is hard work. Whether you donate your time and how much of your time is a personal choice to make. But of course a lot of OSS gets paid for indirectly via companies paying people to work on them (most long lived projects have paid contributors like that) or in a few cases because the companies behind these projects have some business model that actually works. Some people donate money to things they like. And some projects are parked under foundations that accept donations. That's all fine. But there are also an enormous amount of projects out there and most of them will never receive a dollar for any of it. OSS wouldn't work without this long tail of unpaid contributors.
I have a few OSS projects of my own. I don't accept donations for them. I don't get paid for them. I have my own reasons for creating these projects; but money isn't one of those. And people are welcome to use them. That's why these projects are open source.
MS and Github make loads of money. There's a reason they give the freemium version away for free: it funnels enough people into the non free version that it is worth it to them. Charging money to everyone might actually break that for them. I happily use their freemium stuff. I did pay for it a long time ago when private projects weren't part of the freemium layer. Anyway their reasons/motivations are theirs. I'm sure it all makes sense for them and their share holders.
If people feel guilty about not donating to each of the thousands of projects they rely on (or any, because why cherry pick?), you can pay back in a different way and try to contribute once in a while. Just pay it forward. Yes you somebody put a lot of work in the stuff that you use. And you put some work in stuff that others get to use. If enough people keep on doing that (and the success of OSS hints that they do), OSS will be here to stay.
$5 a month per dependency, OK let's go! Hold up I've just reorganized my packages into sqlalchemy-base, sqlalchemy-core-sql, sqlalchemy-orm, sqlalchemy-oh-you-want-deletes-also, sqlalchemy-fewer-bugs, and about eight more
People in tech thinks that micropayments work. Even if you leave out the drop off in entering card details, it just doesn't work, as if get some payment you are much more liable by law. e.g. Whatsapp is the closes example, which had cost of revenue of $52M for revenue of $10M[1] in the last filing.
No. I would get rid of "should" to "could" but it actually would warp the open source world once money is involved. People would start optimizing what they do to try and get a slice of the pie.
I think there could be a GH feature request that could do something like this in my opinion (opt-in though, not opt-out).
In my personal GH account there is a "sponsor" button that shows me what dependencies I have that I could sponsor. Unfortunately the list is empty.
My _organisations_ have hundreds of repo's, but there's no "sponsor" option at the org level in GH that says what dependencies the orgs use and then set up batch transactions at that level.
The dependency data already exists in dependabot for a lot of stuff, so it wouldn't be starting from scratch.
Corporations who use and benefit from software should be made to pay for their use of that software, but they don't want to, which is why they'll happily spend money promoting the use of corporate-friendly and maximally exploitable open source licensing among the passionate individuals who maintain the lions share of their dependency tree.
If you don't want to give your software away for free, don't give your software away for free. When they decide it is in their best interest to pay for it they will, i.e. support, bug fixes, changes. If you make open source software that just works they are unlikely to start writing checks nor should there be any expectation that they do that.
I wouldn't want some committee to decide who gets the money. It would make more sense to promote Github sponsorship. Suppose they occasionally gave all subscribers a $10 credit that they could use to sponsor whatever projects they want?
This is a terrible idea in my opinion and it's been tried/is being tried by services like thanks.dev. Yes, we need something here but this is not it. The reality is more complex.
It doesn't work well in practice. Because then people like https://github.com/sindresorhus?tab=repositories&type=source would get a shit ton of money because of the pure number of dependencies. And yes our stack also contains his code somewhere in a debug UI but our main product is entirely written in a different programming language with way fewer dependencies but if one of them goes away we'd be in trouble. In other words: Dependency count is not a good metric for this.
My "idea":
Lots of companies will have to create SBOMs anyway. Take all of those but also scan your machines and take all the open source software running on there (your package.lock does not contain VLC etc.) and throw it in a big company wide BOM, then somehow prioritise those using algorithms, data and just manual voting and then upload that to some distributor who then distributes this to all the relevant organisations and people and then (crucially) sends me (as a company) an invoice.
We've tried doing the right thing but sponsoring is hard - it works differently for every project/foundation and the administrative overhead is huge.
The reality is that "we" as an open-source community suck at taking money and I believe this is partially on us.
If you want to make a product and sell your software, make a product and sell it.
It is always people who make a thing for free then people find it useful and start using it then they start using that free and open source thing at work instead of writing a copy and that’s when the original person starts asking for donations and money.
The reason your project is popular is because it is free. If it wasn’t free we would have probably written our own or used something else.
Being on both sides of the open source value relationship, I feel somewhat skeptical of mechanisms that use dependency cardinality/"popularity" to allocate funding: at its best it's a proxy for core functionality (which is sometimes, but not always, the actually hard/maintenance-intensive stuff) and at its worst it incentivizes dependency proliferation (since two small core packages would be equally as popular as one medium-sized one).
I think that if GitHub had charged everyone from the beginning, it wouldn’t have become so popular and wouldn’t have attracted so many users. Maybe if they introduce charges now, it could work, but I’m still sure that a lot of users would drop off, and only those who are basically forced to use it would stay. And this would simply open the door for competitors to create similar products.
That's a mischaracterization of TFA's point. Your re-phrase makes it sound like the proposal is for filthy-rich Microsoft to pocket additional bucks from other people's open source work. Ostensibly, yes, Microsoft will be doing such action but the spirit of TFA is more like for Microsoft to act as a tax collector and, crucially, redistribute the collected tax back to the community---the money will not add to Microsoft's $3.4T-worth coffers!
Naturally this comment isn't a "fuck yes!" to the idea of Microsoft-as-tax-collector but if we're discussing TFA, let's not be needlessly cynical to the idea presented.
A problem is that some Python library with a sole developer who is on the verge of halting maintenance needs your $1 way more than the Linux Foundation.
It's as dumb as the german Pauschalabgabe, where everyone is forced to pay a specific amount of money for technical devices, because there is the possibility of private copies for licenced media.
> Those funds would then be distributed by usage - every mention in a package.json or requirements.txt gets you a piece of the pie.
Could have worked before LLMs.
Also, funding by popularity would mean alternatives would have a harder time to emerge and get the funding they need to compete against the established popular projects.
Being an Open Source project doesn't mean that it provides the best solution to the problem it's supposed to solve.
Diversity is important.
Or the copyright holders can start dual licensing their software for commercial use
license A is GPL or MIT for academic and free applications
License B is for commercial use, with a fee
The license is literally whatever you want to put into it.
IMO the issue is with the open source community gatekeeping these policies. Shaming developers for proposing commercial licensing, then shaming corporations for properly using the IP according to the free license (e.g. MIT)
I am working on open source projects. I believe we need a better licensing approach for open source. The current license system only works if users actually care about licenses, but most do not. They simply copy the code and do whatever they want. Finding a solution to this problem is more important than charging money.
I donate to specific projects through OpenCollective. I do not want Github to take extra money from me and then redistribute it to projects I don't care about according to some formula that will inevitably be exploited to get free $$$.
If you want to support a project, submit a PR or send them a check. Don't force me do it for you.
I do not agree. It should not be opt-out. If you want funding, make it opt-in. I do not want to be paid for it, and I also do not want to pay for it (and I also do not want to have too many dependencies, even if I do not have to pay for it).
Also, not all programs use package.json and requirements.txt, so that won't work anyways.
No, they shouldn't. Microsoft has so much money, they couldn't spend it in a thousand years. Much of that money earned, because they had not have to spend it on developers because they just use open source software. They should just invest more into open source, but out of their pocket.
GitHub already charges organisations to fund open source features. Otherwise it wouldn't lack so many enterprise level features, it wouldn't have half baked solution that do not take into consideration enterprise requirements. GH Actions for example is still not there yet after years
I do like this idea, as it seems easy to implement. Github can just increase its prices by $1/month/orguser and that fund could end up with like, i think, 6 million per month. Thats a sizeable amount of money and could help in making open source more sustainable & attractive.
No. Take some of that enterprise cash and lay it aside on a daily lottery which devs automatically enter based on usage metrics. And a bit more enterprise aside to give directly to the customers' deep dependency maintainers (which gh already knows).
Why not just offer dual license open source + commercial license.
If anyone is making money off the code they should pay annual fee which goes to contributors. Github can setup an escrow, manage licenses and distribute the money to contributors.
I'm not a fan of Github, I prefer to promote the competition, and I'm definitely not a fan of Microsoft, but Github is already sponsoring open source with unlimited repos.
So this is a weird statement to me, like you always want more.
Open source work is not a product, it is a gift to the community with no strings attached, and that goes both ways. You don't ask people who give you a gift to then unbox it, set it up, and maintain it for you.
It's a good idea! Extra bonus: the inevitable exodus of companies moving to a different platform might reduce github's scale to a point where they can handle their own traffic (zing!)
However it is opt-in aka "Launch a page in minutes and showcase Sponsors buttons on your GitHub profile and repositories". That's effort & friction and only simplifies the "begging" aspect that I am (strongly) reacting to.
>it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments
Or Microsoft could simply fund open source software since they provide a Linux subsystem to allow people to do proper work despite of them having to use windows
How about GitHub stops using GPL'd code to train models? The authors weren't asking for payment, they were just asking not to reuse their code without GPL.
While delegating fund collection and disbursement to one organization reduces overhead for each project, the centralized nature of the setup can be asking for trouble.
Instead, why not accept the reality that 1) projects may charge for their offerings and 2) users may have to pay for such offerings? As a user, if a project's offering is useful to me, then I should be willing to pay for it. As a creator, if I want to get paid for my offering, then I should be willing to ask for it. An upside of such a change could be that we start being more focused and prudent about what we use and create.
Without such delegation, projects will have to do the heavy lifting in terms of collection of funds; features such as sponsorship in GH or setting up e-payments via Stripe or Paypay may help reduce this brunt.
the payment isn't the problem so much as the payment processing. They wouldn't support crypto, even if they did, getting crypto without KYC hassle is a PITA, not worth it for paying one company $1. Not associating your real identity with a github repo is very important to most github users.
Payment could solve lots of problems, but there is no real and meaningful cash-equivalent payment system or method. This isn't a tech problem either, governments allow cash payments, but if it is digital, they won't allow any means that preserves privacy. Money laundering is their concern. You can't solve this without laws changing. Even if I don't mind buying crypto with a credit card, I still have to go through proving my identity with my id card, as if my credit-card company didn't do that already.
payment is a huge barrier to commerce these days, people think LLMs will change the world, but payment tech/laws will have a bigger effect in my opinion.
Let's say HN mods go a little crazy one day and want to let us tip each other for good posts and comments, imagine if all they had to do is add an html tag in the right place and that's it. All we had to do is click a button and it just works, and there is no exposure of private information by any involved party, and you could fund that payment by buying something (a card?) at a convenience store in person, just as easily as you could with a crypto payment, moneygram or wire transfer.
I __want__ to pay so many news sites, blogs,etc... I don't mind tipping a few bucks to some guy who wrote a good blog, or who put together a decent project on github that saved me lots of time and work.
It isn't merely the change in economics or people getting a buck here and there, but the explosion in economic activity you have to look at. The generation of wealth, not the mere zero-sum transferring of currency. This is the type of stuff that changes society drastically, like freeways being invented, women being able to ride bicycles, airplanes allowing fast transport, telegrams allowing instant messaging,etc..
Everyone being able to easily pay anyone at all, including funding private as well as commercial projects would be more disruptive than democracy itself, if I could dare make that claim. There is freedom of movement, there is freedom of communication and last there is freedom of trade. these are the ultimate barriers to human progress. Imagine if everyone from texas to beijing could fund research and projects, trade stocks in companies (all companies in the world). You won't need governments to fund climate change work, I think eventually taxation itself will have to suffer, because people would be able to direct exactly where their funds went. Not just what department in the government gets a budget, but exactly what projects they spend it on. being able to not just talk or meet each other instantly (and even those have a long way to go) but to also collectively or as individuals found each other, governments and companies, that'd be the biggest thing that could happen this century.
This could be done, but again, we don't need better tech as much as we need a change in attitude. For people to actually believe this would result in a better world for them.
> payment is a huge barrier to commerce these days, people think LLMs will change the world, but payment tech/laws will have a bigger effect in my opinion.
Having a native way to send micropayments on the web without having to pay a huge % of that transaction to Visa/Mastercard and Stripe and Co would be such massive game changer when it comes to this stuff.
As a silly example, every time I collect 1$ for my 1$/month club I actually get ~70c which is wild.
I agree with you, if there was a better way to directly send small amounts to people running interesting sites or projects the whole landscape could change.
And I also agree that a change in attitude is needed. I appreciated your comment.
should be the transitive dependencies, not just top-level (so the lock file or equiv) or you just reward the "barely wrap it and give it a new name" js crowd even more.
let everything be gratis and if you need something fixed, and engineer you hired to work for you in your org can fork or send in a patch. there, I solved it
Have Microsoft charge people $ for their repos, and then take their code to train their LLM for more $.
And they can use the surplus $ to fund open source projects to produce more code to train their LLM for even more $, and reduce their taxes thanks to the charitable donations.
Government grants can be used to cover infrastructural open source. Not every open source wants money, so this scheme has ro be opt-in. Further, entitled "paying" users[1] will make things much worse for small projects. "I paid for this package, so you need to fix this show-stopper bug before we ship on Friday"
Having a passion project is great, having it gain traction is even better, but that is not sufficient to make it a job / company. The utility of open source projects range from "I could implement the bits I use in under an hour" to "It would take 100-person team years".
> it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments.
Is that not what most of open source is? Things people make for themselves because they either found it fun or solved their own problem, then published it for others to use for free. Most projects are not worth the bureaucratic tax related headaches the income from them would bring (maybe that's just my EU showing).
What's not okay is demanding new features or to fix something urgently. That's paid territory.
Honestly this post is such a shit take it's borderline intentional ragebait.
People would milk the system as much as they could, only to become the most popular library, only to get most of the "pie".
I guess Python/JS devs would get the most of it. Because their ecosystem is most fragmented. C++ or assembly devs? Nothing.
I don't think this idea is thought out. Money corrupts things.
There already is a "market" for stars. But if stars would indicate how much someone earns, it would be morbid. Well, in some way, I guess they already do, but it's linked at least indirectly.
Sounds like force with a Hobson's choice. And who decides who gets how much?
This is a common anti-pattern of utopian, this will work this time(tm), improperly-educated dreamers who are much too comfortable with totalitarianism like taking money, property, and rights from others without asking for their consent.
Robbing peasants to build palaces and pet projects. Maybe start with "demanding" every big company fund them than taxing average people.
Deeply hate this. Just add a small fee. It's just a couple bucks. What are you, cheap?
Open Source Software underwrites everything. It makes the largest human endeavors work. It makes silly ephemeral games little notes apps and digital art run. Turning maintainers into a kind of digital landlord that charges a fee is both insultingly low bore and enough to squeeze the life out of computing as a hobby.
This line of thinking is utterly bizarre to me. People need to stop thinking of GitHub as anything other than a typical corporation. If they could charge an additional dollar they would keep it for themselves.
Oh, I know! Let’s redistribute royalty payments from AI subscriptions in Spotify-fashion from OpenAI and friends to developers, kind of like how Spotify pays artists for streams we get a cut of the token. Oh wait… no one’s profitable yet. Right.
I've been thinking about this very hard problem while walking the dog.
Individuals and companies love open source software, but the current donation models don’t really work.
I thought this problem was bad for programming libraries (e.g. the recent Tailwind stuff), but after using Linux desktop open source—which has much less incentive for companies to donate or sponsor—oh boy, it’s bad.
Open source evokes a lot of emotions, but at its core, to me, it’s two things:
A collection of “features” (depending on license / governance):
* You can use it for free, no matter what
* You can see how it works
* You can modify the software
etc.
These are genuinely valuable features, which is why open source has won.
But these features are unavoidably coupled to business models and incentive structures for the developers who create this value.
Right now, open source developers and companies can only extract a relatively small percentage of the (considerable) value they create. As a result, only very large or strategically important projects become financially sustainable.
I agree with the article that the solution likely involves a different business model or incentive alignment—but this is a very hard problem.
We’ve seen major business model shifts outside open source during my career:
- SaaS software (used to be one-time payments)
- Microtransactions in games (personally dislike them, but they radically changed incentives and revenue)
These shifts are often counterintuitive and closely tied to human behavior.
I don’t agree with the specific solution proposed in the article, but I don’t have a clean answer either.
My best (very rough) idea:
Create a non-profit that builds tooling and infrastructure to measure open source usage (tricky!).
Loosely, you run something like:
oss-usage
And it generates a report for a machine (or an entire company):
'tailwind': 5 # units TBD
'npm': 8
'haskell': 1
Then a centralized registry where individuals and companies can disclose usage and donations:
Donated funds are held centrally and can be claimed by project maintainers.
Companies can claim (or not) their usage. Developers can claim (or not) their projects and funds.
Donations are aggregated into one transaction per month, solving the microtransaction problem.
This creates a public, open record of who is funding open source. I think that could be a strong incentive for larger companies—engineers will notice when choosing where to work.
Bad actors who under-donate or refuse to disclose won’t be invisible; we’ll know where they stand.
Anyway - if you’ve read this far and are interested in working on or funding this idea, come find me:
https://richardgill.org
In principle it sounds like a grand idea, although there are a bunch of corner cases like how it works cross country borders, and de-anonymising maintainers.
If it was opt in for opensource projects, and there are strong guards against people forking/hard takover-ing then yes, it seems like a good idea in principle.
I will leave the AI enthusiasts to chime in about the future, and how we don't need OS anymore.
love this idea on so many levels. Of course, then the fight moves to how allocation happens, and how to avoid people further gaming things like repo stars, forks, PRs, voting, dependencies, etc.
in particular, there's repos with extremely high activity where funding doesn't help anyone and repos with low activity where funding ensures continuity for key components we all depend on but which are under-funded for various reasons.
The sense of entitlement is strong in these comments. If you haven’t built or maintained OSS I’m wondering why your opinion matters [edit: that's harshly worded I could have been more nuanced, hopefully the point is taken and it is a question]. There’s also the take that “this is fine” vs considering that the state of OSS things could be a LOT better with higher quality and more choices if we fed the beast properly.
I don't see any entitlement at all, in fact it's the opposite.
The article: "I expect open source maintainers to maintain their codebases and add new features. I have unilaterally decided that $1/package is a suitable amount, universally applicable to all packages and maintainers." <--- this is entitlement
The comments here: "Open source maintainers don't owe you shit."
Some comments were deferred for faster rendering.
grayhatter|1 month ago
I am. I enjoy making things, and it's even better when others enjoy them. Just because you have expectations that you should be compensated for everything line of code you write; doesn't make it ubiquitous, nor should your expectations be considered the default.
I'd argue If you're creating and releasing open source with the expectations of compensation, you're doing it wrong. Equally, if you expect someone creating open source owes you anything, you're also part of the problem, (and part of why people feel they deserve compensation for something that used to be considered a gift).
All that said, you should take care of your people, if you can help others; especially when you depend on them. I think you should try. Or rather, I hope you would.
pixelready|1 month ago
Would it be chaotic? Sure, in the same way that open source or any other form of self-organization is. But boy it sounds a whole lot better than our current model of slavery-with-extra-steps…
gregsadetsky|1 month ago
I meant - it’s unfair to consider that because this labor “fell from the sky”, you should just accept it - and as others have said, in the case of projects that become popular, that the burden should just automatically fall on the shoulders of someone who happened to share code “for free”.
If/when someone ends up becoming responsible for work they hadn’t necessarily signed up for (who signs up for burnout?) - it’s ok/necessary/mandatory to see how everyone (and or Nvidia/Google/OpenAI etc) can, like, help.
My insistence is on the opt-out nature of this so that people who would be ok being compensated don't have to beg.
Consider how the xz malware situation happened [0]. Or the header & question 8 from the FAQ for PocketBase [1].
[0] https://x.com/FFmpeg/status/1775178803129602500
[1] https://pocketbase.io/faq/
dgacmu|1 month ago
I gather that the open source maintainers who have found themselves in this situation sometimes get very unhappy about it, and I can see why -- it's not like they woke up one day and suddenly had a critical component on their hands, it kind of evolved over time and after a while they're like "uhoh, I don't think this is what I signed up for"
davidhyde|1 month ago
asah|1 month ago
In general, people's time is not free if only because they have rent/mortgage, food, transportation, medical bills, education, etc.
franciscop|1 month ago
I do think it would be nice to get paid anything at all, but that wouldn't change at all how I do things/release code. In fact, unless it'd be really no-strings-attached, I'd prefer to keep the current arrangement than being paid a pittance per month and then have extra obligations.
tracerbulletx|1 month ago
Quarrelsome|1 month ago
I think this is a little unfair, given that many (especially younger maintainers) get into it for portfolio reasons where they otherwise might struggle to get a job but stick around because of the enjoyment and interest. It still sucks that so many big orgs rely on these packages and we're potentially experiencing a future when models trained on this code are going to replace jobs in the future.
I think a lack of unionisation is what puts the industry in such a tough spot. We have no big power brokers to enforce the rights of open source developers, unlike the other creative industries that can organise with combined legal action.
Barbing|1 month ago
saidnooneever|1 month ago
chris_wot|1 month ago
Dilettante_|1 month ago
Yes it absolutely is. That is the exact social contract people 100% willingly enter by releasing something as Free and Open Source. They do give it as a gift, in exchange for maybe the tiny bit of niche recognition that comes with it, and often times out of simple generosity. Is that really so incredible?
securesaml|1 month ago
The expectation of FOSS is that the users and maintainer work together to resolve bug fixes/features/security issues.
However many companies will dump these issues to the maintainer and take it for granted when they are resolved.
It's not a sustainable model, and will lead to burnout/unmaintained libraries.
If the companies don't have the engineering resources/specialization to complete bug fixes/features, they should sponsor the maintainers.
Aurornis|1 month ago
nonethewiser|1 month ago
tehjoker|1 month ago
Unfunkyufo|1 month ago
I think the solution is for people to understand that open source goes both ways. Unlike what this post says, users don't owe maintainers anything, but maintainers also don't owe the users anything. If I build something cool and share it freely, why should users expect anything from me? Why should you expect me to maintain it or add the features you want? I think we need a mentality change where less is expected from maintainers, unless funding is arranged.
After all, it's free and open source. No one is forcing you to use it. Don't like that I'm not actively developing it? Submit a PR or fork it. Isn't that what the original spirit of open source was? I think that open source has been so succesful and good that we've come to expect it to be almost like commercial software. That's not what it is.
nottorp|1 month ago
If they pay by popularity most of my $1 would go to javascript. I'd rather it went to libraries I actually use.
DrScientist|1 month ago
Strictly speaking open source originally was not to do with whether you paid for something or not, it was that if you did pay for it, you got the code and had the rights to make your own changes.
Think Free speech, not free beer, or the software equivalent of right to repair.
primitivesuave|1 month ago
1. https://www.forbes.com/sites/lesliekatz/2024/09/08/man-charg...
captn3m0|1 month ago
stogot|1 month ago
marginalia_nu|1 month ago
Yes this is uncomfortable, but the simple fact is that if you don't tell anyone you want to get paid, you probably won't be given any money. Standard seem to be maybe there's a donation link somewhere on the site, buried 4 clicks deep in the FAQ, more often than not something like a paypal.
The reality is that if you do ask for money, surprisingly often people will straight up just give you money if they like what you're doing. Like people get paid real money for screaming at video games on Twitch, meanwhile you're building something people find useful. Of course you can make money off it. But you gotta ask for it, the game screamers on twitch sure do. That's the secret. Sure there's a scale from asking for donations and doing a Jimmy Wales and putting a your face on a banner begging for donations; and while going full jimbo is arguably taking it too far, it's also probably closer to the optimum than you'd imagine.
If you have corporate users, word on the street is you can also just reach out to them and ask for sponsorship. They're not guaranteed to say yes, but they're extremely unlike to sponsor you spontaneously.
aitchnyu|1 month ago
https://old.reddit.com/r/linux/comments/d2ic2e/krita_is_now_...
olalonde|1 month ago
Usage is not a good proxy for value or ongoing effort. I have a npm package with tens of millions of weekly downloads. It's only a few lines long and it's basically done - no maintenance required.
I'm skeptical that there exists an algorithmic way to distribute funds that's both efficient and resistant to gaming.
QuadmasterXLII|1 month ago
Aurornis|1 month ago
Showing high download numbers on your resume is more valuable than anything a fund like this could provide. There will always be a company who views high NPM download numbers as a signal of top 1% talent, even if it has become a game in itself.
abraham|1 month ago
kjgkjhfkjf|1 month ago
For example, I am currently working with React, which was produced by Meta. I write the code using TypeScript, which was produced by Microsoft (and other corporate behemoths such as Google). I am writing this comment in Chrome (produced by Google). Etc.
claudex|1 month ago
Which depends on a lot of code not produced by Google, like libxml2 which was on the news recently because the maintainer step down.
prussia|1 month ago
You are still right that corporations found and contribute to countless open source projects though.
ummonk|1 month ago
tonymet|1 month ago
immibis|1 month ago
porise|1 month ago
ksec|1 month ago
Which 8? In the control the world domain I see Meta, Google, Amazon, Apple, Microsoft. In terms of Market Cap you would add Tesla, Nvidia and TSMC, but these three aren't any where close to "controlling" the world category.
stravant|1 month ago
Bad or borderline actors would be so much better at creating whatever metrics you're basing things off of that the actual value creators wouldn't stand a chance.
ndr|1 month ago
It's easy to predict what sort of incentives this would produce, and how bad they would be. Fewer users and way more spammy projects to say the least.
GH could easily end up having to spend more than it collected in fighting abuse.
tracker1|1 month ago
s/thousands/millions/ the point stands that there are way more devs than commercial accounts, and even then, even if it's 1:1, you get $1?
GorbachevyChase|1 month ago
tshaddox|1 month ago
bArray|1 month ago
> GitHub should charge every org $1 more per user per month and direct it into an Open Source fund, held in escrow.
Sure. It'll be some charity, then somebody gets paid $200k+ per year to distribute what remains after they've taken the majority, all whilst avoiding most taxes. To receive the money the person has to ID themselves, financial background checks need to be done, a minimum amount needs to be reached before a payment is made, and then after passing through multiple wanting hands, they end up with a fraction.
> Those funds would then be distributed by usage - every mention in a package.json or requirements.txt gets you a piece of the pie.
What even is "usage"? How many times it appears in a number of repos? How many users there are of the project? Is the usefulness and value of a project limited to the number of people that directly use it?
> Or don’t! Let’s not do anything! People’s code and efforts - fueling incredibly critical bits of infrastructure all around the world - should just be up for grabs. Haha! Suckers!
> Anyway, you all smarter than me people can figure it out. I just cannot accept that what we have is “GOOD”. xx
It's entirely possible you can make things worse by avoiding doing nothing. Sometimes in life you have to pick the lesser of evils.
[1] https://www.x-rates.com/table/?from=USD&amount=1
hamdingers|1 month ago
I don't think Google needs a dollar every time I write a script in golang or run a container in kubernetes, and I would put a lot less trust in Envoy if I thought Lyft was building it profit and not because they needed to.
preommr|1 month ago
paul_h|1 month ago
yallpendantools|1 month ago
> Hence, a solution. Or an idea, really. Incredibly half-baked. Poke all the holes you want. It’s very unwrought and muy unripe.
UqWBcuFx6NV4r|1 month ago
keybored|1 month ago
Maybe economists could do what is ostensibly their job and try to prevent the “tetris game of software depending on the OSS maintained by one guy in Nebraska...” situation. In the meanwhile people who do things under no duress for free could stop doing it.
(Not that OSS is all hobby activities. There are many who are paid to do it. But these appeals only talk about the former.)
rglullis|1 month ago
Unfortunately, the crypto angle made sure that mostly degens and speculators got into it. Perhaps if stabletokens were more established by the time they started, it would be easier to market it.
(I am not going to get into yet-another discussion about Brave as a company. I will flag any attempt at derailing the conversation.)
bigfatkitten|1 month ago
By paying companies like Red Hat, Canonical, Google and Amazon, who in turn spend massive amounts of money employing software developers to work on Linux.
nonethewiser|1 month ago
Why? It's not crazy at all. It's the status quo with no sign of things changing. It is both possible right now and likely continue. Its not crazy.
If it's not worth maintaining people will stop. If people need it they will develop it. The current incentive structure has produced lots of open source code that is being maintained.
>It is not okay - it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments.
It is if there is no cost. You can always charge for it. But you can't make it free then pretend its not.
maxdo|1 month ago
You can easily sponsor Iran or Russia killing real people by doing such things.
Powerful tools, once released, can be used by anyone, including those with harmful intentions. And let's be honest: much of open source functions as a way for large companies to cut costs on essential but non-differentiating infrastructure. That's fine, but it complicates the idealistic narrative.
With generative AI, these questions matter more. Maybe it's time to revisit what open source should mean in this context.
arjie|1 month ago
Meta has even demonstrated an alternative with the Llama 4 License which has exclusion criteria:
> 2. Additional Commercial Terms. If, on the Llama 4 version release date, the monthly active users of the products or services made available by or for Licensee, or Licensee’s affiliates, is greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta, which Meta may grant to you in its sole discretion, and you are not authorized to exercise any of the rights under this Agreement unless or until Meta otherwise expressly grants you such rights.
Go put such terms in your licenses.
This is particularly rampant in the Rust community and if I'm being honest this forced tithing church nonsense from people who want to be priests makes participating in that community less desirable. I don't even want to donate to the RSF as a result.
All the other projects I've donated to in the past have been much more reasonable. This kind of pushy nonsense is unacceptable.
zephen|1 month ago
I agree. Yet some of my comments here have been met with downvoting and explanations that GPL licensing is a moral imperative, so there is certainly a contingent who would disagree.
> This is particularly rampant in the Rust community
This is interesting. Do you have examples? I am not cognizant enough of interactions there.
JacoboJacobi|1 month ago
Literally anyone could create a support and maintenance organization that takes MIT license projects into an AWS like split and only get paid if the support they provide remains valuable to people who pay for the value of the support and maintenance.
jamietanna|1 month ago
As others have noted, there are a few areas to watch out for, and:
- some ecosystems have more dependencies over fewer, and so we need to consider how to apply a careful weighting in line with that - how do we handle forks? Does a % of the money go to the original maintainers who did 80% of the work? - how can companies be clever to not need to pay this? - some maintainers don't want financial support, and that's OK - some project creators / maintainers don't get into the work for the money (... because there is often very little) - there's a risk of funding requirements leading to "I'm not merging your PR without you paying me" which is /not problematic/ but may not be how some people (in particular companies) would like to operate
[0]: https://www.jvt.me/posts/2025/02/20/funding-oss-product/
bitbasher|1 month ago
Lramseyer|1 month ago
OK, what about those of us who aren't writing libraries?
As a personal anecdote, the amount of opportunities that have been opened up to me as a result of my open source project are worth way more than any $1 per mention or user.
jillesvangurp|1 month ago
The problem for some people is that they want to get paid for their work and just aren't; or not enough. I won't judge that. Writing software is hard work. Whether you donate your time and how much of your time is a personal choice to make. But of course a lot of OSS gets paid for indirectly via companies paying people to work on them (most long lived projects have paid contributors like that) or in a few cases because the companies behind these projects have some business model that actually works. Some people donate money to things they like. And some projects are parked under foundations that accept donations. That's all fine. But there are also an enormous amount of projects out there and most of them will never receive a dollar for any of it. OSS wouldn't work without this long tail of unpaid contributors.
I have a few OSS projects of my own. I don't accept donations for them. I don't get paid for them. I have my own reasons for creating these projects; but money isn't one of those. And people are welcome to use them. That's why these projects are open source.
MS and Github make loads of money. There's a reason they give the freemium version away for free: it funnels enough people into the non free version that it is worth it to them. Charging money to everyone might actually break that for them. I happily use their freemium stuff. I did pay for it a long time ago when private projects weren't part of the freemium layer. Anyway their reasons/motivations are theirs. I'm sure it all makes sense for them and their share holders.
If people feel guilty about not donating to each of the thousands of projects they rely on (or any, because why cherry pick?), you can pay back in a different way and try to contribute once in a while. Just pay it forward. Yes you somebody put a lot of work in the stuff that you use. And you put some work in stuff that others get to use. If enough people keep on doing that (and the success of OSS hints that they do), OSS will be here to stay.
luqtas|1 month ago
OSS literally runs the modern infrastructure... https://www.fordfoundation.org/learning/library/research-rep...
zzzeek|1 month ago
init0|1 month ago
YetAnotherNick|1 month ago
[1]: https://www.sec.gov/Archives/edgar/data/1326801/000132680114...
keithnz|1 month ago
ianso|1 month ago
In my personal GH account there is a "sponsor" button that shows me what dependencies I have that I could sponsor. Unfortunately the list is empty.
My _organisations_ have hundreds of repo's, but there's no "sponsor" option at the org level in GH that says what dependencies the orgs use and then set up batch transactions at that level.
The dependency data already exists in dependabot for a lot of stuff, so it wouldn't be starting from scratch.
bsnnkv|1 month ago
Corporations who use and benefit from software should be made to pay for their use of that software, but they don't want to, which is why they'll happily spend money promoting the use of corporate-friendly and maximally exploitable open source licensing among the passionate individuals who maintain the lions share of their dependency tree.
https://lgug2z.com/articles/on-evils-in-software-licensing/
spullara|1 month ago
rmah|1 month ago
skybrian|1 month ago
https://docs.github.com/en/sponsors/sponsoring-open-source-c...
saxenaabhi|1 month ago
tobadzistsini|1 month ago
lars_francke|1 month ago
It doesn't work well in practice. Because then people like https://github.com/sindresorhus?tab=repositories&type=source would get a shit ton of money because of the pure number of dependencies. And yes our stack also contains his code somewhere in a debug UI but our main product is entirely written in a different programming language with way fewer dependencies but if one of them goes away we'd be in trouble. In other words: Dependency count is not a good metric for this.
GitHub actually offers something in that direction: https://github.com/sponsors/explore
My "idea": Lots of companies will have to create SBOMs anyway. Take all of those but also scan your machines and take all the open source software running on there (your package.lock does not contain VLC etc.) and throw it in a big company wide BOM, then somehow prioritise those using algorithms, data and just manual voting and then upload that to some distributor who then distributes this to all the relevant organisations and people and then (crucially) sends me (as a company) an invoice.
We've tried doing the right thing but sponsoring is hard - it works differently for every project/foundation and the administrative overhead is huge.
The reality is that "we" as an open-source community suck at taking money and I believe this is partially on us.
manuelmoreale|1 month ago
More broadly people suck at giving money for things they can get for free. That’s just the reality of how most people out there behave.
The only “solution” is to educate people but that is completely unfeasible.
nextlevelwizard|1 month ago
It is always people who make a thing for free then people find it useful and start using it then they start using that free and open source thing at work instead of writing a copy and that’s when the original person starts asking for donations and money.
The reason your project is popular is because it is free. If it wasn’t free we would have probably written our own or used something else.
woodruffw|1 month ago
maomaomiumiu|1 month ago
senko|1 month ago
Microsoft, a $3.4T company, should charge people for open source they didn't even write?
Hell no. Hell no.
yallpendantools|1 month ago
Naturally this comment isn't a "fuck yes!" to the idea of Microsoft-as-tax-collector but if we're discussing TFA, let's not be needlessly cynical to the idea presented.
vlad-roundabout|1 month ago
0x073|1 month ago
https://de.wikipedia.org/wiki/Pauschalabgabe
wiether|1 month ago
Could have worked before LLMs.
Also, funding by popularity would mean alternatives would have a harder time to emerge and get the funding they need to compete against the established popular projects.
Being an Open Source project doesn't mean that it provides the best solution to the problem it's supposed to solve. Diversity is important.
tonymet|1 month ago
license A is GPL or MIT for academic and free applications
License B is for commercial use, with a fee
The license is literally whatever you want to put into it.
IMO the issue is with the open source community gatekeeping these policies. Shaming developers for proposing commercial licensing, then shaming corporations for properly using the IP according to the free license (e.g. MIT)
einpoklum|1 month ago
It is also kind of crazy to want Microsoft to manage FOSS taxation and funding.
lasgawe|1 month ago
tjwebbnorfolk|1 month ago
If you want to support a project, submit a PR or send them a check. Don't force me do it for you.
prussia|1 month ago
zzo38computer|1 month ago
Also, not all programs use package.json and requirements.txt, so that won't work anyways.
7bit|1 month ago
alex_young|1 month ago
Halan|1 month ago
avaer|1 month ago
It'll never happen; open source doesn't have the legal team of Disney [1].
[1] https://openai.com/index/disney-sora-agreement/
wang_li|1 month ago
falloutx|1 month ago
SPICLK2|1 month ago
(this holds true for all of the other times this idea has been suggested, too).
And this does not take into account the various fees, taxes etc, that will be removed before any money gets into an OSS developer's bank account.
dj_gitmo|1 month ago
smashah|1 month ago
smcleod|1 month ago
perlgeek|1 month ago
GitHub charging its users, who themselves are mostly OSS developers (and not end users) doesn't seem like a sensible solution.
soorya3|1 month ago
If anyone is making money off the code they should pay annual fee which goes to contributors. Github can setup an escrow, manage licenses and distribute the money to contributors.
INTPenis|1 month ago
So this is a weird statement to me, like you always want more.
corvad|1 month ago
enricotr|1 month ago
ericyd|1 month ago
dbbk|1 month ago
gregsadetsky|1 month ago
However it is opt-in aka "Launch a page in minutes and showcase Sponsors buttons on your GitHub profile and repositories". That's effort & friction and only simplifies the "begging" aspect that I am (strongly) reacting to.
https://docs.npmjs.com/cli/v11/commands/npm-fund will also "list all dependencies that are looking for funding in a tree structure"
I want the step (or 5 steps) after that. Charge first, then distribute.
macinjosh|1 month ago
Not sure how open source got bamboozled into paying rent to Microsoft of all companies.
lm28469|1 month ago
Goodbye 90% of open source software I guess then
juancn|1 month ago
rglullis|1 month ago
falloutx|1 month ago
Aurornis|1 month ago
blubber|1 month ago
morshu9001|1 month ago
timcobb|1 month ago
kekqqq|1 month ago
PaulHoule|1 month ago
jstummbillig|1 month ago
blindstitch|1 month ago
worik|1 month ago
3oil3|1 month ago
kunley|1 month ago
no-name-here|1 month ago
What is "the biggest theft in tech history" that GitHub did?
rvprasad|1 month ago
Instead, why not accept the reality that 1) projects may charge for their offerings and 2) users may have to pay for such offerings? As a user, if a project's offering is useful to me, then I should be willing to pay for it. As a creator, if I want to get paid for my offering, then I should be willing to ask for it. An upside of such a change could be that we start being more focused and prudent about what we use and create.
Without such delegation, projects will have to do the heavy lifting in terms of collection of funds; features such as sponsorship in GH or setting up e-payments via Stripe or Paypay may help reduce this brunt.
anon5739483|1 month ago
dlahoda|1 month ago
greg just proposed sanctions, more sanction. without disriminating that for some kids 1 is too much or impossible.
greg why do you want more suffering to people?
verdverm|1 month ago
irjustin|1 month ago
The REAL problem becomes, who gets funding? ouch
notepad0x90|1 month ago
Payment could solve lots of problems, but there is no real and meaningful cash-equivalent payment system or method. This isn't a tech problem either, governments allow cash payments, but if it is digital, they won't allow any means that preserves privacy. Money laundering is their concern. You can't solve this without laws changing. Even if I don't mind buying crypto with a credit card, I still have to go through proving my identity with my id card, as if my credit-card company didn't do that already.
payment is a huge barrier to commerce these days, people think LLMs will change the world, but payment tech/laws will have a bigger effect in my opinion.
Let's say HN mods go a little crazy one day and want to let us tip each other for good posts and comments, imagine if all they had to do is add an html tag in the right place and that's it. All we had to do is click a button and it just works, and there is no exposure of private information by any involved party, and you could fund that payment by buying something (a card?) at a convenience store in person, just as easily as you could with a crypto payment, moneygram or wire transfer.
I __want__ to pay so many news sites, blogs,etc... I don't mind tipping a few bucks to some guy who wrote a good blog, or who put together a decent project on github that saved me lots of time and work.
It isn't merely the change in economics or people getting a buck here and there, but the explosion in economic activity you have to look at. The generation of wealth, not the mere zero-sum transferring of currency. This is the type of stuff that changes society drastically, like freeways being invented, women being able to ride bicycles, airplanes allowing fast transport, telegrams allowing instant messaging,etc..
Everyone being able to easily pay anyone at all, including funding private as well as commercial projects would be more disruptive than democracy itself, if I could dare make that claim. There is freedom of movement, there is freedom of communication and last there is freedom of trade. these are the ultimate barriers to human progress. Imagine if everyone from texas to beijing could fund research and projects, trade stocks in companies (all companies in the world). You won't need governments to fund climate change work, I think eventually taxation itself will have to suffer, because people would be able to direct exactly where their funds went. Not just what department in the government gets a budget, but exactly what projects they spend it on. being able to not just talk or meet each other instantly (and even those have a long way to go) but to also collectively or as individuals found each other, governments and companies, that'd be the biggest thing that could happen this century.
This could be done, but again, we don't need better tech as much as we need a change in attitude. For people to actually believe this would result in a better world for them.
manuelmoreale|1 month ago
Having a native way to send micropayments on the web without having to pay a huge % of that transaction to Visa/Mastercard and Stripe and Co would be such massive game changer when it comes to this stuff.
As a silly example, every time I collect 1$ for my 1$/month club I actually get ~70c which is wild.
I agree with you, if there was a better way to directly send small amounts to people running interesting sites or projects the whole landscape could change.
And I also agree that a change in attitude is needed. I appreciated your comment.
aaronblohowiak|1 month ago
ekjhgkejhgk|1 month ago
bpiroman|1 month ago
axel479343|1 month ago
mfru|1 month ago
conartist6|1 month ago
hartjer|1 month ago
MonkeyClub|1 month ago
Have Microsoft charge people $ for their repos, and then take their code to train their LLM for more $.
And they can use the surplus $ to fund open source projects to produce more code to train their LLM for even more $, and reduce their taxes thanks to the charitable donations.
Everyone wins, right?
Thankfully we still have Codeberg.
overfeed|1 month ago
Government grants can be used to cover infrastructural open source. Not every open source wants money, so this scheme has ro be opt-in. Further, entitled "paying" users[1] will make things much worse for small projects. "I paid for this package, so you need to fix this show-stopper bug before we ship on Friday"
Having a passion project is great, having it gain traction is even better, but that is not sufficient to make it a job / company. The utility of open source projects range from "I could implement the bits I use in under an hour" to "It would take 100-person team years".
moffkalast|1 month ago
Is that not what most of open source is? Things people make for themselves because they either found it fun or solved their own problem, then published it for others to use for free. Most projects are not worth the bureaucratic tax related headaches the income from them would bring (maybe that's just my EU showing).
What's not okay is demanding new features or to fix something urgently. That's paid territory.
Honestly this post is such a shit take it's borderline intentional ragebait.
drdrey|1 month ago
unknown|1 month ago
[deleted]
self_awareness|1 month ago
People would milk the system as much as they could, only to become the most popular library, only to get most of the "pie".
I guess Python/JS devs would get the most of it. Because their ecosystem is most fragmented. C++ or assembly devs? Nothing.
I don't think this idea is thought out. Money corrupts things.
There already is a "market" for stars. But if stars would indicate how much someone earns, it would be morbid. Well, in some way, I guess they already do, but it's linked at least indirectly.
jmclnx|1 month ago
csomar|1 month ago
seanclayton|1 month ago
burnt-resistor|1 month ago
This is a common anti-pattern of utopian, this will work this time(tm), improperly-educated dreamers who are much too comfortable with totalitarianism like taking money, property, and rights from others without asking for their consent.
Robbing peasants to build palaces and pet projects. Maybe start with "demanding" every big company fund them than taxing average people.
This is so dumb.
awkward|1 month ago
Open Source Software underwrites everything. It makes the largest human endeavors work. It makes silly ephemeral games little notes apps and digital art run. Turning maintainers into a kind of digital landlord that charges a fee is both insultingly low bore and enough to squeeze the life out of computing as a hobby.
heliumtera|1 month ago
philippz|1 month ago
thrawa8387336|1 month ago
anacrolix|1 month ago
gregors|1 month ago
unknown|1 month ago
[deleted]
hmokiguess|1 month ago
richardgill88|1 month ago
Individuals and companies love open source software, but the current donation models don’t really work.
I thought this problem was bad for programming libraries (e.g. the recent Tailwind stuff), but after using Linux desktop open source—which has much less incentive for companies to donate or sponsor—oh boy, it’s bad.
Open source evokes a lot of emotions, but at its core, to me, it’s two things:
A collection of “features” (depending on license / governance):
* You can use it for free, no matter what
* You can see how it works
* You can modify the software
etc.
These are genuinely valuable features, which is why open source has won.
But these features are unavoidably coupled to business models and incentive structures for the developers who create this value.
Right now, open source developers and companies can only extract a relatively small percentage of the (considerable) value they create. As a result, only very large or strategically important projects become financially sustainable.
I agree with the article that the solution likely involves a different business model or incentive alignment—but this is a very hard problem.
We’ve seen major business model shifts outside open source during my career:
- SaaS software (used to be one-time payments)
- Microtransactions in games (personally dislike them, but they radically changed incentives and revenue)
These shifts are often counterintuitive and closely tied to human behavior.
I don’t agree with the specific solution proposed in the article, but I don’t have a clean answer either.
My best (very rough) idea:
Create a non-profit that builds tooling and infrastructure to measure open source usage (tricky!).
Loosely, you run something like:
And it generates a report for a machine (or an entire company): Then a centralized registry where individuals and companies can disclose usage and donations: Donated funds are held centrally and can be claimed by project maintainers.Companies can claim (or not) their usage. Developers can claim (or not) their projects and funds.
Donations are aggregated into one transaction per month, solving the microtransaction problem.
This creates a public, open record of who is funding open source. I think that could be a strong incentive for larger companies—engineers will notice when choosing where to work.
Bad actors who under-donate or refuse to disclose won’t be invisible; we’ll know where they stand.
Anyway - if you’ve read this far and are interested in working on or funding this idea, come find me: https://richardgill.org
7ynk3r|1 month ago
cenobyte|1 month ago
KaiserPro|1 month ago
In principle it sounds like a grand idea, although there are a bunch of corner cases like how it works cross country borders, and de-anonymising maintainers.
If it was opt in for opensource projects, and there are strong guards against people forking/hard takover-ing then yes, it seems like a good idea in principle.
I will leave the AI enthusiasts to chime in about the future, and how we don't need OS anymore.
Davidbrcz|1 month ago
cush|1 month ago
trueismywork|1 month ago
asah|1 month ago
in particular, there's repos with extremely high activity where funding doesn't help anyone and repos with low activity where funding ensures continuity for key components we all depend on but which are under-funded for various reasons.
obligatory XKCD: https://xkcd.com/2347/
beeboop0|1 month ago
[deleted]
wetpaws|1 month ago
[deleted]
huflungdung|1 month ago
[deleted]
ProofHouse|1 month ago
[deleted]
amarant|1 month ago
Profit incentives like the one suggested is what brought us enshitification.
And the code is a free gift, unless the licence says otherwise. What's wrong with letting developers choose what to bill for?
axel479343|1 month ago
bahmboo|1 month ago
mjr00|1 month ago
The article: "I expect open source maintainers to maintain their codebases and add new features. I have unilaterally decided that $1/package is a suitable amount, universally applicable to all packages and maintainers." <--- this is entitlement
The comments here: "Open source maintainers don't owe you shit."