Earlier quoted context omitted.
Yep. Open Source developers who give away their work for $0 are undermining their own value and the value of other peoples skills. Open Source should always come with a commercial license for companies.
Hey @mbrodersen, this is really not appreciated here on HN. This pasting of what is essentially the same reply on every top-level comment is borderline spam.
Professional maintainers: a wake-up call
351–360 of 464 posts
Re: Professional maintainers: a wake-up call
#352Earlier quoted context omitted.
Why should the companies pay more than $0 for code with a price tag of $0? Do you normally pay more than the asking price for things you buy?
Why would anyone pay for business class airline tickets instead of (subsidized) coach? They both get to the destination at the same time!
Re: Professional maintainers: a wake-up call
#353Earlier quoted context omitted.
It is not a problem. It just is how humans function. So act accordingly. Trying to change how humans work is a waste of times. You are fighting millions of years of evolution. Good luck with that. Try not to be bitter when you fail.
That is one of those evo-psych just-so stories. American corporate culture in the late 20th/early 21st century is not representative of all humans at all times. I get that it's the dominant experience for you, but please don't confuse that with some sort of deep evolutionary imperative. One of the things that distinguishes humans as a species is how extremely social, how extremely cooperative we are. See, for example…
Re: Professional maintainers: a wake-up call
#354> Open Source maintainers graduating to sophisticated counterparties who send invoices for "support and sponsorship" on letterhead, and big companies developing procedures to assess, approve, and pay them as a matter of routine so that they can get what they need from the ecosystem. The first 1/2 already exists. It's the companies which need to change. I say this from experience. I'm self-employed, with my own compan…
If you offer your work with a price tag of $0 then people/companies will pay $0 for it. The nativity of open source developers thinking otherwise is jaw dropping. So yes I agree that commercial licensing is the way to go.
To my understanding, most people who want to get paid a reasonable amount to develop FOSS go one of two routes.
1) Service-oriented, à la the Cygnus Solutions (now Red Hat) approach. FOSS developers get paid to fix bugs, add features, answer questions, and provide training. This has been my approach.
2) Employer cost savings. Work as an employee for a company which saves money by developing software, but where the employer is not interested in bringing it to market.
See the section "Professionalizing the role of maintainer" of the linked-to essay for other examples of what a company might get through funding a FOSS project. ("security practices, like two-factor authentication and mandatory code review", etc.)
None of this is "work with a price tag of $0", and the very essay we're talking about gives counter-examples to your interpretation.
Furthermore, I tried selling FOSS software for a fee ($30K, not $0), and simple commercial licensing doesn't work either. Commercial proprietary licensing addressed certain economic problems that commercial FOSS licensing didn't resolve.
Re: Professional maintainers: a wake-up call
#355Earlier quoted context omitted.
If you offer your work with a price tag of $0 then people/companies will pay $0 for it. The nativity of open source developers thinking otherwise is jaw dropping. So yes I agree that commercial licensing is the way to go.
Your view of the "nativity of open source developers" is itself naïve. To my understanding, most people who want to get paid a reasonable amount to develop FOSS go one of two routes. 1) Service-oriented, à la the Cygnus Solutions (now Red Hat) approach. FOSS developers get paid to fix bugs, add features, answer questions, and provide training. This has been my approach. 2) Employer cost savings. Work as an employee f…
Re: Professional maintainers: a wake-up call
#356Earlier quoted context omitted.
You're largely correct, but I'm not speaking about peer pressure. 'Tis the season, so we've been listening to a lot of Christmas carols. One of my favorites is Good King Wenceslas, which concludes with the verse: "Therefore, Christian men, be sure, wealth or rank possessing, Ye who now will bless the poor, shall yourselves find blessing." Charity used to be a behavioral expectation in the West. Charity is not "giving…
Such a license doesn't seem likely to fit the Open Source Definition.
https://en.wikipedia.org/wiki/Multi-licensing#Business_model...
Re: Professional maintainers: a wake-up call
#357> Now is the perfect time for Open Source maintainers to become legible to the big companies that depend on them—and that want to get more out of them—and send them five-to-six figure invoices. Well, this is exactly what I've been doing around VideoLAN (VLC, x264) and FFmpeg for the last few years. In order to do that, I've created 2 official companies Videolabs and FFlabs (besides the non-profit orgs) and I've gone…
> So, large SV companies and startup should also start agreeing to pay for open source, when it's the core of the tech. Companies usually have a reason to keep their expenses low. Sometimes they are a public company with fiscal responsibilities. A startup will only have so much runway and is likely trying to reduce expenses. Given this situation, why will they pay for what they can get for free?
Sometimes they could keep hiring for cheap a provider for one of their core needs, but choose to pay much more to have an exclusive contract and guarantee the provider doesn’t get scooped or goes under.
There can be any rationale applied to paying more money than the minimum they could get away with.
Re: Professional maintainers: a wake-up call
#358I don't know... I just don't see how OSS will ever be a real, sustainable business. The moment it does, someone else will simply subvert the paid-for software with a look-alike that does 90% of what the original does, but for free. In my view, this is the birth story of OSS. And I don't see any real market there. Even if you manage to find a "niche", like some sustainable software-as-a-service with subscription, ther…
Re: Professional maintainers: a wake-up call
#359Earlier quoted context omitted.
Ultimately these tools have already been released for free so asking for a rent seeking style payment after the fact is a little bit like sour grapes. What stops me from just forking the project? Really nothing. If anything open source maintainers that want to get paid should look into a model that mirrors the bug bounty programs. Have bounties for features. Generally these projects only really need security updates.
What stops a company from forking and paying 200,000 a year for someone to maintain vs paying 20,000 back? Money.. cheaper to support than fork.
Re: Professional maintainers: a wake-up call
#360Earlier quoted context omitted.
I really don't understand this mentality. This is what we've all been fighting for since the 90s. A free (as in beer) and open stack of software that anyone can pull off the shelf and use. So many commercial platforms rely not just on ffmpeg and vlc but also on nginx, php, python, nodejs, linux, mariadb, and everything else you can imagine. We also pay for some very niche things that are simply not available from the…
So your argument is that people shouldn't be paid for their labor because the companies profiting from that labor might not be able to profit?