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.
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…
I think it is important to differentiate between different kinds of projects that people might undertake, and 3 particular categories always come to my mind (you may have more):
* "plumbing" - all that infrastructure that isn't something you'd ever use directly, but the tools you do use wouldn't function without it. This work is generally intense during a "startup" phase, but then eases back to light-to-occasional as a stable phase is reached. It will likely happen whether there is funding or not, but may take longer and reach a different result without it.
* "well defined goal" - something that a person or a team can actually finish. It might or might not benefit from funding during its creation, but at some point, it is just done, and there's almost no reason to think about continuing work other than availability and minimal upgrades to follow other tools or platforms.
* "ever-evolving" - something that has no fixed end-goal, and will continue to evolve essentially forever. Depending on the scale of the task, this may or may not benefit from being funded so that there are people working on it full time, for a long time.
These descriptions originate in my work on software, but I think something similar can be said for lots of other human activities as well, without much modification.
There is effectively zero evidence suggesting a population on UBI will result in some sort of outpouring of creativity.
[1] https://en.wikipedia.org/wiki/Hikikomori and it's not a phenomenon limited to Japan.
Maybe there’s a feedback loop with societal expectations regarding the hikikomori / NEETs? The more they are demonized as unproductive, the less productive they become.
Also, there is at least one example of UBI contributing to an increase in activity:
"According to the research, 31% of BIA recipients reported an increased ability to sustain themselves through arts work alone, and the number of people who reported low pay as a career barrier went down from one third to 17%. These changes were identified after the first six months of the scheme and remained stable as the scheme continued." [1]
[1] https://musiciansunion.org.uk/news/ireland-s-basic-income-fo...
The fact that these groups are not producing mass amounts of creative works in no way implies that currently-productive people would not produce significantly more creative works if they had the time and resources to do so.
>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.
As it happens, the Japanese internet is absolutely rich with content created by individuals, most of it done for the sake of love for creative work rather than financial motivation. I spend much of my free time either consuming it or contributing to the pool of such work myself. The entire point of this discussion thread was about the potential for creativity if you were to unshackle it from the demands of financial self-sustenance.
As an aside, I believe this phenomenon manifested as strongly as it has in Japan because of the extremely low cost of living relative to the level of economic development; a studio apartment can be had for less than the equivalent of $200 USD per month, and many parents can afford to and are willing to pay this price to get the NEETs out of their house. In essence enabling them, not that they want to enable their adult children to depend on them but the burden is small enough that they can tolerate it.
This reinforces others talking about the flaws of hustle and grind culture. The status quo create the conditions for the negatives and then point to that and say “see”.
Jazz and other music genres in the US came without government welfare, they came from struggle and oppression. Motivated artists will still work part time to fund their dream, they don't necessarily wait for welfare to start making art.
IF you were to give a lot of people free money today, will you get more and higher quality art in return, or will most people just drink and smoke that money while playing videogames at home?
Society, people and the world today are vastly different than back in the 1960s, so we need new polices targeting the society of today, not 1960s policies.
It's not like becoming famous back then was easy either. Plenty of good bands never got anywhere. The Mona Lisa wasn't a famous painting until someone stole it in 1911, before that nobody gave damn and now it's the most famous of them all. Survivorship bias and randomness in art is real.
There will always be strivers who measure their self worth against superficial standards (Russ Hanneman “doors go up” hand gesture here), I just don’t see why everyone should be forced to play that game or starve I suppose. Giving everyone the option to settle for a life of basic dignity while caring for those around them, or going all in on some academic / creative pursuit seems equally valid investments for society.
UBI and safety net would just get eaten by economic rent. Basically your landlord would just raise the price of renting space leaving people right where they left off.
You need to impose a tax called the Land Value Tax to prevent landowners eating up the public money. Even then we got a long list of much needed public spending before we can even think about a Citizen's Dividend.
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].
There are a lot of dumb and even disagreeable open source projects. Why should someone be de facto forced to fund those projects?
It's like this ass-backwards way of selling something because you're allergic to markets or something. Honestly, it's quite rude to go on and on about free software and liberation and all these things and then turn sour grapes years later because everybody took you up on it. Nobody is forcing anyone to maintain any of these projects.
And maybe if you wrote some software that forms the basis of a trillion dollar + company and you're still sitting in the basement you're kind of dumb for giving it away and that's your fault.
> GitHub should charge every org $1 more per user per month
It's about org, not about every single person using Github.
The idea is basic and should have been written in the article. When a contributor release FOSS, it's fair to compensate if you business rely on it.
A contributor wouldn't like a free for personal use either. The ideal license is the Unreal one free for « Individuals and small businesses (with less than $1 million USD in annual gross revenue) »
> you're kind of dumb for giving it away and that's your fault.
It happens so many times and no just about software (but then it's not a million dollar company). It's not that you are dump, you done the right thing and some companies with money/power/opportunity to capitalize on it, did it and didn't compensate you fairly.
Nope.
Put it in the license, sell the software, or work for free, but stop complaining about it.
It's nice if businesses who benefit from specific software packages want to pay or show support, but it's not nice to release something "for free" but then jump on a moral grandstand and demand everyone pay so you can feel good about your ideology at the expense of everyone else.
> The ideal license is the Unreal one free for « Individuals and small businesses (with less than $1 million USD in annual gross revenue)
Then make that your license?
How to create more code I can enjoy using has been something that I've been thinking about for a long time. I've even advocated for a stance[0], similar to yours. While I don't agree it's correct to conflate the malign intent surrounding the xz takeover, with the banal ignorance as to why so many people don't want to support people creating cool things, (and here I don't just mean financial support.) I do acknowledge there are plenty of things about the current state we could fix with a bit more money.
But I don't want open source software to fall down the rabbit hole of expectations. Just as much as I agree with you, people opting-in to supporting the people they depend on is problematic. Equally I think the idea that OSS should move towards a transactional kind of relationship is just as bad. If too many people start expecting, I gave you money, now you do the thing. I worry that will toxify what is currently, (at least from my opinionated and stubborn POV), a healthier system, where expectations aren't mandatory.
The pocket base FAQ, and your hint towards burnout are two good examples, describing something feel is bad, and would like to avoid. But they are ones I feel are much easier to avoid with the framing of "this work was a gift". I have before, and will again walk away from a project because I was bored of it. I wouldn't be able to do so if I was accepting money for the same. And that's what leads to burn out.
I do want the world your describing (assuming you can account for the risks inherent into creating a system with a financial incentive to try to game/cheat), but I don't want that world to be the default expectation.
"Open Source" is hugely conflated in terms of the reasons people write open source software.
There are people who truly don't care to be compensated for their work. Some are even fine with corporations using it without receiving any benefit.
Some people prefer viral and infectious licenses the way that Stallman originally intended and that the FSF later lost sight of (the AGPL isn't strong enough, and the advocacy fell flat). They don't want to give corporations any wiggle room in using their craft and want anyone benefiting from it in any way to agree to the same terms for their own extensions.
Many corporations, some insidiously, use open source as a means of getting free labor. It's not just free code, but entire ecosystems of software and talent pools of engineers that appear, ready to take advantage of. These same companies often do not publish their code as open source. AWS and GCP are huge beneficiaries that come to mind, yet you don't have hyperscaler code to spin up. They get free karma for pushing the "ethos" of open source while not giving the important parts back. Linux having more users means more AWS and GCP customers, yet those customers will never get the AWS and GCP systems for themselves.
There are "impure" and "non-OSI" licenses such as Fair Source and Fair Code that enable companies to build in the open and give customers the keys to the kingdom. They just reserve the sole right to compete on offering the software. OSI purists attack this, yet these types of licenses enable consumers do to whatever they want with the code except for reselling it. If we care about sustainability, we wouldn't attack the gesture.
There are really multiple things going on in "open source" and we're calling it all by the same imprecise nomenclature.
The purists would argue not and that the OSI definition is all that matters. But look at how much of the conversation disappears when you adhere to that, and what behavior slips by.
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"
In general, people's time is not free if only because they have rent/mortgage, food, transportation, medical bills, education, etc.
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.
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?
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.
For the library to be secure, there needs to be funding, not by magic and expecting maintainers will do stuff on there free will.
And it leads to unmaintained libraries, since companies don't want to pay.
At some point, is open sourcing your work a liability?
I argue that open sourcing your work is no more liable than making a comment on social media. The biggest risk to an open source maintainer is publicly losing their patience and/or being heterodox in their beliefs. Code isn't a requirement for that to happen.
And then they can shrug and move on with their respective days. If I open source something it's a gift to the commons, not a promise to work on it for free in perpetuity. I don't really care if someone tries to shame me for that, as there's nothing to be ashamed of.
Maybe you're overloaded, maybe you just don't feel like it. It's totally normal, and different projects have different levels of resources, some with none anymore.
My main concern is supply chain compromise.
That said, everything in my previous post still applies: a nonzero buglist is totally normal and widely accepted.
What happens next is completely irrelevant. The maintainer can 100% decide to just ignore the issue or close it.
Opening issues doesn't create unmaintained software. In fact it helps.
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.
If they pay by popularity most of my $1 would go to javascript. I'd rather it went to libraries I actually use.
As suggested, I do think there should be room for grant funding, especially in the case of govts switching to open-source (LibreOffice, Linux, whatever) and open-source individuals and orgs can apply and granted each year dependent on actual use. Though, even then, govts should probably do more for funding, but I don't want a situation where the org just spends more money than they actually distribute for dev (looking at you Mozilla).
Personally I used to pay 7/month for personal use, then when MS bought it it went down to 4, and one day when my card expired I noticed I'm not using any of the paid features and private repos are now free... so now I'm paying 0.
1. https://www.forbes.com/sites/lesliekatz/2024/09/08/man-charg...
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.
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.
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.
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.
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.
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.
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.
imo corporations have more pull on governments than governments have on businesses at this point as far as long term culture goes.
But right now I see so many cracks in their game I am optimistic they wont control world and there will be new competition to challenge them.
Microsoft, a $3.4T company, should charge people for open source they didn't even write?
Hell no. Hell no.
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/
So this is a weird statement to me, like you always want more.
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.)
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.
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?
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.
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.
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.
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.
> 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.
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.
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.
Corporations should start paying their fair share, they've scammed society enough.
Maybe, but also maybe they just fork internally and fix the bug internally and don't publish the bugfix. And maybe it's never in their best interest to pay for it, maybe it's in their best interest to just freeload forever.
> 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 think it's good when we expect corporations to write checks to the people that write the open-source stuff they rely on. "A rising tide lifts all boats" is not automatically true in software, we have to choose to make it true. I think a world in which we make that choice is a better world. I'm not convinced we currently live in that world.
I don't, and I spend a lot of my time and efforts encouraging others not to, and doing the work to prove out alternative models :)
https://lgug2z.com/articles/normalize-identifying-corporate-...
https://lgug2z.com/articles/komorebi-financial-breakdown-for...
Then you jump on to a place like Reddit or HN and you have people mostly supporting the status quo. Of course people are going to do open source more than they should. And then if they complain later on, you will say they chose to make it open source. Reinforcing the status quo by blaming the individual.
Such a weird thing to reply to someone who very publicly disavows the use of open source licensing for individuals
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.
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.
OSS literally runs the modern infrastructure... https://www.fordfoundation.org/learning/library/research-rep...
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.
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.
GitHub charging its users, who themselves are mostly OSS developers (and not end users) doesn't seem like a sensible solution.
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.
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.
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.
Goodbye 90% of open source software I guess then
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 also kind of crazy to want Microsoft to manage FOSS taxation and funding.
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.)
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.
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.
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)
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.
But if they really wanted to do what the article says, create a project and people can donate what the want. For example, if M/S sends me $5 per month, I can redirect it to various open source projects instead.
When I was on GH, I did donate a little per month to 2 projects, it was a nice way to do that. But I moved off because I do not want to give M/S more personal information (like my Cell #), so I send a few $ to them using other means.
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.
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/
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?
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."
So yes, we can laugh at the proposed mechanism but I feel the world would be a better place if we could funnel more resources to OSS creators rather than just take because that's an easier path.