Unpopular opinion: this is absolute non-sense. If you want to create a commercial organization to maintain a project, by all means go ahead, but the idea that all open-source work should be paid for in equal terms is not healthy in the long term.
The community aspect used to be the most enjoyable part of open-source, and I gladly donated (a lot of) my own time. It’s about people coming together around a common need - if there’s enough demand more people will join in. I loathe the current state of marketing/funding/clout based OSS where projects become institutions of their own and break the natural attention balance.
I find that opinion, is not so much unpopular rather it might be that it arises from approaching the the question with a different set of parameters.
I am one of those people who write software for fun. I'm guessing I'm wired to get a dopamine rush from solving an interesting programming challenge the same way that someone doing the NY Times crossword puzzle is when they get all the words. Nobody claims that someone who spends hours doing crossword puzzles over the year is an underpaid crossword puzzle solver.
So when people have do things for themselves, perhaps their compensation is in the doing.
But when someone else decides to use some open source software, they are in a different place. They are using it as a tool that gives them value. Using our crossword solving problem; the person who gets a copy of the puzzle solver's answers and just fills in the squares is a user not a developer.
This is where the open source contract breaks down, because you can get user's who file issues to be fixed but supply no money or manpower to fix them. And the people who are writing the software because they enjoy writing software, may have no interest in your particular interest, it might bring them no joy at all to work on it, so they don't.
And in that gap, you get CVEs where an issue results in security problem for the tool user, but you don't have anyone able (or perhaps willing) to stop what ever they are doing and work on it. Could you imagine a person demanding someone figure out the word for 18 down "right now" because their other project needed that work to continue?
I would be interested in seeing an open source license that made the software free to use for anyone who contributed at least one fix or one feature to the code each year, but cost $10,000/year to license to use if you chose not to contribute any fixes or features. I don't think you need to restrict it to features or fixes that eventually get integrated just contributed and could be integrated (pass all CI/CD requirements). The reason there is the user would end up having to pay a software developer, perhaps part time, to come up with those features/fixes and presumably that would cost more than the $10,000/year.
My point is that without a way to tie the economic value of using the software back into its development cost (in order to pay people to do the grunge work that often nobody wants to do) you end up with imbalanced value equations like the ones we have today where you can't charge for the source code to people who just want to exploit it and add value in their own products that they keep.
> you can get user's who file issues to be fixed but supply no money or manpower to fix them
And then maintainer responds, "not on my roadmap, but patch would be welcome".
> And in that gap, you get CVEs where an issue results in security problem for the tool user, but you don't have anyone able (or perhaps willing) to stop what ever they are doing and work on it.
About time for idle users to step up and invest into their own security, right?
> free to use for anyone who contributed at least one fix or one feature
Sure, screw software freedoms, let's build unenforceable licenses with perverse incentives, driving NIH behaviour and contributions for sake of the fact of the contribution.
Free software is doing fine (and this gets better as mankind gets wealthier), thank you. Please don't contemplate force-feeding it.
> Free software is doing fine (and this gets better as mankind gets wealthier), thank you. Please don't contemplate force-feeding it.
Respectfully, if you read the linked article here, or the stories of people who maintain key infrastructure going broke[1], those pieces conclude exactly the opposite. They conclude that "free software" is not doing fine at all. Rather free software not benefiting at all from the wealth of the corporations exploiting it to their bottom line.
There are other people contributing lots to GnuPG and alternatives. GnuPG development receives thousands of euro in donations every month. Werner also seems to run a commercial company around GnuPG, hope it is doing well. Doesn't seem as tragic as "The World's Email Encryption Software Relies on One Guy, Who is Going Broke", did i miss something?
FOSS authors shouldn't tie their destiny to a project they like to work on. It quickly gets ugly, one example being Eric Raymond, who took the stance that he will work on whatever he feels like, "because it has to be me who is doing it", dismissing loads of people saying "get a job and stop punishing yourself and your family". But still his supporters back him to some extent via Patreon.
You can follow your passion, but who's to blame if you don't maintain the balance?
If you have a kid to raise, but you'd rather hack on free software all the time instead, are you eligible for free childminders and nursery just because?
Can you be doing whatever you feel like, have no obligations to anyone, and expect to have a decent living?
Ok, I can understand your argument, which if I restate it is this; "There are free software projects that are explicitly set up to support the developers, so the burden is on the developer to set up such a system, not on the users to find a way to support the developers." Would you agree with that restatement? Did I understand you correctly?
Where I am is in an interesting subsection of the entire solution space of "free software". Consider your statement:
> Can you be doing whatever you feel like, have no obligations to anyone, and expect to have a decent living?
On the surface, the answer to that question is no. Because of the expectations aspect. But phrase it a bit differently and we get to where I am;
"Can you be doing whatever you feel like, and one or more companies are making millions in revenue based on products made possible by what you are working on, and expect to have a decent living?"
I completely don't understand what you said about burden on developers to set up some system.
> "Can you be doing whatever you feel like, and one or more companies are making millions in revenue based on products made possible by what you are working on, and expect to have a decent living?"
Still no.
There are few good reasons to contribute to open source, and they are nothing about profits other users make, because the process and the product are rewarding to the contributor.
Now there are some bad reasons to contribute to open source, where the motivation is perverse, the situation looks distastrous, and only these cases would take advantage from any such policing, subsidizing, taxing, wealth redistribution.
Does that person do the work to use the product themselves? Then such external factors don't matter, the person extracts the value they intended to have.
Does that person do the work to meet interesting challenges, mess with smart people, and have fun? Obviously it's nothing about getting money from other users.
Does that person do the work to promote themselves in careers? Other users matter only as big or numerous names, not as revenue.
Does that person do the work with the only outcome being the profit for companies which the person expects to pay back, while putting on work under the license which does not require users to pay at all?
Or, in addition to that, they bring a FOSS product to the market, profit from providing value-add services to that, but get broke because someone else starts to provide similar value-add services with their product, all being legal?
Your thoughts are completely about these people, and these people have really perverse motives from the outset.
If I read you correctly, you feel strictly that when someone contributes to open source their reward is that the product/feature works for them. There is no other consideration expected or needed. Is that correct?
Where we might differ is that I have observed that people contributing to open source feel a sense of pride or "ownership" over the work they have contributed.
Further, when someone who has not been part of the community, or contributed to it in any meaningful way, uses that work to make themselves and perhaps people that work for them wealthy, I have observed that the people who feel ownership feel a certain level of "unfairness" if you will.
In a strict libertarian point of view there was never any sort of economic contract to share any wealth created by a thing with the people who created and maintained that thing. As such the people who created it are without recourse and should be happy with the satisfaction they got from creating and maintaining it in the first place. And that was "their choice" that they made.
If that is what you're saying, I don't find the feelings these people have to be "perverse" (which by definition would make them abnormal). I am not arguing that the people start out with a motivation to "make money on their work", I was discussing the situation that the original author notes which is that sometimes a little gizmo you make is useful to a lot of people, and so it gets very widely utilized. The number of users creates a tremendous maintenance burden which is unfunded. That maintenance is, in my opinion, a value-add service which isn't being compensated (or is being compensated at a below poverty level according to our author).
>you can get user's who file issues to be fixed but supply no money or manpower to fix them
A model I've seen that I'm optimistic of is assigning bounties to tickets. I've seen two flavors of this:
A. Users put money on tickets. Maybe three people put $25 dollars each on a ticket, so it's now worth $75 to resolve. Someone comes along and gets a pull request merged that solves the ticket. They get the money that's on the ticket.
B. Users contribute to an overall project budget (perhaps through something like Patreon) and a project lead assigns the money to the tickets that he wants to entice people to resolve.
>I would be interested in seeing an open source license that made the software free to use for anyone who contributed at least one fix or one feature to the code each year, but cost $10,000/year to license to use if you chose not to contribute any fixes or features. //
Any fix? I mean you can get a fix for something on Fiverr, I expect, but that might make more work for a project than it usefully resolves.
Personally I'm not a programmer, I've sent a couple of pull requests at most, but I do share stuff that I do - like I add places to OSM, upload "art" to OCAL [though it's down at the moment, worryingly], answer question on SE network sites and sometimes on Launchpad, report bugs and test other's bugs. Basically I do my best to be a contributing part of the FLOSS community.
I guess I see programmers create the many FLOSS apps I use as something like being a Scout leader (which is a volunteer position that costs you money), they do it to make a positive and lasting contribution for society with no expectation of financial gain. Though I realise, many do work on FLOSS for wages, just as many people work in outward bounds or as teachers, or what-have-you.
I see a lot of projects that I want to contribute to but I have absolutely no idea what needs to be contributed. Recently I created an issue for a tool that creates a template for a project. The tool allows you to enter an upper case folder name but if you start the project it will fail. So is the bug that you are allowed to enter upper case names or is the bug that the project fails to start? The fix probably wouldn't need to change more than a single line of code. I have no way to know that so instead of writing a misguided pull request I just created an issue instead.
Contributing to a project is incredibly difficult if you are an outsider.
Healthy for whom? Creator of Vue.js pulls in like 240k. Every open source contributor of any sort of popular project should be getting at least that much through various deals or pull the plug. Hold your software hostage, get freeloaders to pay a pittance for it. Ridiculous that so many billion dollar companies use these things and feel no obligation to sustain their development and have a mechanism set in place to do that automatically or as a part of due course of using that software.
Projects can do this already. It's the reason we have licenses. The problem are people want to license under MIT, but want more than just recognition.
If you want to get paid, use the GPL, and offer dual licensing. It's that easy.
Oh, it's not "that" easy? So you are really just using MIT as a marketing tool until you get large enough where you can pull the rug out from under everyone and start demanding things?
The problem isn't open source. The problem is the expectation that the MIT license means more than it does. You got what you asked for.
...should be getting at least that much through various deals or pull the plug. Hold your software hostage, get freeloaders to pay a pittance for it.
Funny, but this was almost exactly the unspoken (and actual) ethos of the Sales department dominated old school software company founded in the late 60's I used to work for.
I'm Chris from Airwindows. I'm patreon-backed and make upwards of fourteen HUNDRED dollars a month to serve a specialty market, audio plugins, that is heavily burdened by selfish devs and burdensome DRM strategies. Some of these companies are maybe million dollar companies but many are relatively small fry who still believe they 'should' get 240k (as if! This is still the music business! Or you could say that nothing in the music business is actually popular, therefore none of these can count as popular projects were they OSS)
I license by MIT license. My pitch regarding that is that I require credit, and nothing else. From my point of view, in my business (again, the music business) since long before I was born, the only people who get to be 'popular' are those who sign off on horribly exploitative contracts and get abused just like the OSS developers people are talking about. I assume it'll be the same with me so I allow 'exploitation' on the grounds that I generate enough goodwill to slap back at anyone who's found to be ripping my stuff without credit or shout-out. It's my problem to turn that into revenue.
I can easily believe the '1% to 10% of what you'd make commercially' line. I'm seeing more like 20-25% of what I would make commercially, but if you are an entrepreneur you must consider cashflow. The commercial thing is bursty: feast or famine, and it drives you in perverse directions, makes you play to your impression of what will be the most popular thing.
If you market yourself as an OSS dev free to do anything creative regardless of market pressures, that's its own demographic. It's working okay for me, because I do not have to pay Silicon Valley housing costs, or employees. Like Robert Fripp, I am a 'small, independent, mobile and intelligent unit'.
Why?
You said freeloaders. That angers me. I have a different name. I call them 'musicians'. Often they make the musics and genres I personally like. They also have to eat. I am able to provide them with tools that become their resources. I'd do more if I could: working on it.
If you aren't living on under $1500 a month you have no business calling a sum of money a 'pittance', and in no case do you get to tell me to hold my software hostage. (so I won't. No hard feelings)
You appear to be talking from a 'capital maximization' position, and from that angle all you say checks out. I am talking from a 'providing freedom' position, from which the actions of companies mean diddly-squat. I am there because should they license my stuff (some is trivially simple, some is quite significant) they will take my musicians and hold them hostage and demand a 'pittance', or better yet they'll demand 'a lot' simply because they can.
My musicians (or at least many of the worthy ones) are starving broke, because art does not make money. OSS is a way for me to make some money in a context people understand while giving these people not only tools, but the RIGHT to own, use, redesign these tools. What I give can't be taken away.
Won't trade that for money.
If that is hard to understand ask RMS. (ironically… since I'm using MIT and not GPL. But he would understand, plus people can take my stuff and extend and GPL it if they like. I could switch to GPL at ANY point, if I wanted)
Coming from ex-USSR country, I really don't get people who shake their fists saying that somebody is not fairly compensated, and deserves more, and somebody (rich businesses and enemies of nation obviously) should pay for it. Venezuela waits for you, evil capitalists are defeated here, and govt takes care of everyone.
> Every open source contributor of any sort of popular project should be getting at least that much through various deals
If they don't have such deals, who is to blame?
Users who are busy with their life, take a lot of things for granted and don't think much about thousands of FOSS libraries and apps they use every day?
Government which doesn't subsidize FOSS contributors?
Or maybe contributors themselves who are sloppy at selling themselves and getting deals?
> Ridiculous that so many billion dollar companies use these things and feel no obligation
Maybe exactly because FOSS is about terms which allow such use, and enable companies to build business models on that?
Maybe exactly because FOSS is about terms which allow such use, and enable companies to build business models on that?
Sure, but if such a business takes off and is awash in money then the owners should help to water the tree. Maybe that means writing a check once a year (boo hoo, goodbye money uwu) or contributing some business skill/innovation so that developers or artists can concentrate on their professional discipline rather than having to gain a load of business skills that they may not be temperamentally or intellectually suited for. Why isn't it as easy to monetize as to share a repo?
I suggested a simple solution for the problem. Ask users to meet a certain fund raising goal and if they don't come up with it, either stop working on the project, or pull it entirely and let them worry about it. This is a capitalist approach to the problem of capitalists exploiting communists. Better approach is probably not license your stuff under exploitative licenses and put clauses in there for bigger companies using your work.
The problem here is, nothing you can possibly do is worth more than money to a dedicated capitalist who already has tons of money.
You can do stuff they exploit, or not. Doesn't change the relative size of the pool of money from your true userbase (likely much smaller), and nothing you do can force the capitalist to buy into your code at a less-exploitative license.
They can and will just pass. And you can pressure your users in a wide number of ways: they are the same dark patterns used by proprietary, totally-closed software. You can become that to get paid… or, more accurately, you can become that, try to squeeze blood from a stone, and find out whether you can torture your users into providing you with the level of luxury you see fit.
This is not the motivation of Free Software, and is barely the motivation of Open Source. Might as well just be proprietary and be done with it. All this works on many levels and money/compensation is only one of the levels.
What is the problem you are talking about? Who exactly has that problem? What are "exploitative licenses"?
If money paid by licensees is the primary driving motivation for development, then FOSS is completely wrong type of licenses for this. This is called commercial development.
I expect creators of big libraries to make even more than $20K a month because of speaking gigs etc. But specifically why did you list $240K for Vue.js creator. Are they making money in some specific way?
The most interesting part (IMHO) of the post addressed Github, a multi-billion dollar acquisition on the backs of the open source contributors whose primary beneficiaries never seemed to give even a small portion of the profits back to the community.
If there are other people figuring out how to exploit the tendencies of open source developers, certainly it's fair to discuss how said developers can see a bit of those resources. Especially when the big winners aren't even considering giving back in a serious manner.
I find the Criticism of Github and Microsoft unwarranted; They contribute significantly to both the open source and startup business ecosystems;
Importantly; Free Public Github repositories; these aren't free to provide, they require storage and bandwidth. And not just for major projects, but any project. @ 28 million open source repositories, if you attribute that to the equivalent of $1/year; that is 10x what the author is calling for
Microsoft does a lot more too, whether it's "protecting" patents for Linux, or providing Visual Studio, Atom, sponsoring meetups and hackathons, and much more.
Disclaimer; Guest of Azure Incubation Week, had Microsoft sponsor BarCamps, and hackathons; And I host open source projects on github for free.
I completely agree with you. People should look at companies like Telmex (Mexican telecom company, owned by 3rd richest person in the world). They surely use a HUGE amount of Open Source and contribute zilch back.
In contrast, Github and Microsoft are huge contributors.
> "The most interesting part (IMHO) of the post addressed Github, a multi-billion dollar acquisition on the backs of the open source contributors whose primary beneficiaries never seemed to give even a small portion of the profits back to the community."
There I was, thinking that hosting (through high availability, and great tooling) the repositories for free was Github's way of "giving back to the community". But apparently that's somehow not enough?
That might have been a credible argument if the github platform were open source (as is the case with gitlab), but in absence of that it's fair to compare to similar free offerings like sourceforge and bitbucket.
Providing free hosting didn't win sourceforge or bitbucket or any of the other firms a multibillion dollar payout. What did was capturing the mindshare of open source developers and hosting high-profile projects. Ultimately, the value is derived from the fact that "everyone is using it" and the ecosystem built around it (because everyone is using it).
Honestly, AGPL license your projects: That will prevent obnoxious companies from taking your work without giving back.
If you deliberately pick a BSD-style license, then you don't get to complain about 'big winners' not cutting you a slice. They're doing exactly what you told them they could do.
People pick a BSD-style license because that's what they are told to do by VC-backed startups looking for a return. It's used as a marketing tool. The GPL and associated licenses are given a bad rap.
And now we have people complaining about big companies literally agreeing to the terms set out by little projects and someone they are being unfair?
The thing about AGPL is that you can still dual-license if you want. AGPL by default, and allow companies to purchase a non-AGPL version if you want.
The community aspect used to be the most enjoyable part of open-source, and I gladly donated (a lot of) my own time. It’s about people coming together around a common need - if there’s enough demand more people will join in. I loathe the current state of marketing/funding/clout based OSS where projects become institutions of their own and break the natural attention balance.