TIL: FairCode is the software model Redis, ElasticSearch, etc. use
TIL: FairCode is the software model Redis, ElasticSearch, etc. use
Fair-code is not a software license. It describes a software model where software:
- is generally free to use and can be distributed by anybody
- has its source code openly available
- can be extended by anybody in public and private communities
- is commercially restricted by its authors
I love that website. Now I have an easy way to find all the licenses and projects and companies I need to stay away from.
Why though? Why do you think it's good that e.g. StealLabs can make use of OBS's actively and freely (as in, StealLabs does not pay a cent to OBS) maintained code, add their own stuff, no attributions, and give it away for a price? Not even for a price.. for a fucking monthly subscription!
In the above, StealLabs is the name of StreamLabs, but the former name is more descriptive.
It's GPL, they have to also provide the source. And you benefit from all the rights they do.
"Business" licenses try to prevent competition while still benefiting from free contributions, and pass it as "fairness". But how is it fair for anybody except that particular company? What about the contributors? If OBS used such a license and reaped all the benefits would you still contribute to them?
So a single entity is allowed to commercialize external contributions without any kind of reciprocity. Somehow it sounds worse to me than Shared Source.
If you are worried about leeches just use AGPL and call it a day.
Yeah, this model doesn't work as a long-term solution in my eyes, because as a potential open-source contributor, I do not see myself ever contributing to such a project.
I mean, I am avoiding anything which requires a CLA, in particular if I'd need to hand copyright over to a for-profit organization, but in those cases, because I don't yet know, if I'll get fucked over. With this "FairCode" thingamabob, I would feel fucked-over right away.
And that ultimately breaks with why open-source is popular. Because everyone can scratch their itch and improve it for everyone else. If it's just a for-profit organization dumping their source code, that's going to fall off in quality quickly.
So a single entity is allowed to commercialize external contributions without any kind of reciprocity
Where are you getting this from? This isn't my understanding of what's described on the webpage.
One way of making software more fair is by allowing developers to profit. Many companies today invest resources into taking an existing project and copying the ongoing work of the project creators; afterwards, creating and maintaining a hosted version using their code. In a fair circumstance, should they benefit from using the software, they could add certain features, fix bugs and support the community of users enjoying the product. In many cases they do, but fair-code ensures that this can happen by bringing businesses to the negotiation table when it comes to commercializing software.
This is bullshit when only a set of developers are allowed to profit. Every single project with a non-commercial license I know has an exception for the company that owns the repo. At that point external contributions are not open or fair anything, it's a company stealing labour.
Either licenses are symmetrical or they are inherently unfair, and calling it Fair is doublespeak.
If only there was an article that described the monetization of such a model… oh, wait…
We want people to make money off of their software, but we recognize that the community benefits from a project's economic success. Within fair-code, creators have the exclusive right of commercializing their work, ensuring long-term profitability. Companies that wish to commercialize the software can contact the author and form a business relationship that benefits both parties!
How much profit is Redis or Hashicorp kicking back to the people the contributed to it when it was FOSS? It's just "Fair code" now to allow its "creators" to profit, right?
Without every single contributor assigning copyright to a single entity for their code, the only way to commercialize a program distributed under such a license is to get every single contributor to agree to it separately (or not use their code).
If every single contributor assigns copyright to a single entity, the project is now controlled by it, and unless that entity was particularly nice with its contracts, those contributors are now powerless if (for example) this entity decides to change the license.
Damn this community is getting really toxic. Instead of addressing the huge elephant in the room (people getting jack shit for building great things and their labor being stolen by profit seeking entities), lets jump on the people who are trying to do something about it.
I think the idea of maintainers getting a kickback from downstream profits is a great thing and hugely better than normal foss.
P.S.: a system where you can just relicense the work of contributors with a CLA and profit off of them is not an inch better than this.
Damn this community is getting really toxic.
You're upset that a community called "open source" is pushing back against an attempt to co-opt the open source label? In my view this attempt is highly insidious and far worse than one corporate actor "stealing" (i.e. using) an open source project. These projects were all true free software before pulling the rug on the community and switching to a fauxpen source license, which makes it even worse - if these were proprietary from the beginning no one would have cared, but also fewer people would have contributed, because it doesn't feel as good doing volunteer work for a proprietary product.
I agree there needs to be a mechanism in place for free software developers to be financially compensated but if you're changing the license so that it's no longer free software then it's just proprietary software under some faux "open" label, at which point you might just drop the pretense of being "open" at all - just admit you're a proprietary software company that puts your financial interest ahead of the community's.
Long text for a really short topic: ideology
Software can be free and open while not allowing megacorps to profit without kicking back.
Being in this community regularly feels like coming to some backwater town where people gasp if you take the lords name in vain.
Wake up. There is no „we make free software and everyone loves each other“. People helping get shut down because they „arent submitting PRs“ but open issues because the maintainers barely have the time to look into issues. If you ask people in this community what they do to help, they respond with i cant code as if that was the only way to help.
The companies sucking in the profits made off of honest people‘s work is kneecapping open source development.
The absolute best joke in it all is that „free and open source software“ isnt at all free. I‘m not free to have individuals use it for free and companies pay because tHaTs nOt fReE. It is thinly veiled corporate exploitation and both corpos and the people with open eyes know it.
So far, I haven't seen a realistic proposition for OSI opensource projects to get fairly compensated or protected from leechers like mega-corps. If you're some widely used project without marketing like xz, then nobody cares about financing you until something big happens. I'll just make a post asking what people realistically expect should be done, because it does pique my interest now.
I know mate. You know I pretty much stand behind 99% of your posts and comments. I feel the same way about this. But I'm taking real issue with the treatment the members of this sub give to people who are asking uncomfortable questions.
P.S.: a system where you can just relicense the work of contributors with a CLA and profit off of them is not an inch better than this.
Unless you're a single developer, how are you supposed to profit off your own work without making contributors sign a CLA with these licenses? You only "own" the code you write personally, so AFAIU with these licenses making money off of your code becomes harder the more contributors you have (regardless of the amount they contributed).
I personally dont care if only the maintainers get money for maintaining the stuff while I contribute.
People really have to understand that 10 lines of code arent what makes a project cool. Its a person (or multiple) working on issues day in day out and those are the ones profiting.
Sometimes this issue feels like the low income folks voting pro billionaires because they could profit from that. Its like they have been lobotomized.
If you want to get paid, maintain, imo.
The faircode model assumes that contributions from random outside people are minor and that the bulk of the work is done by the founder(s). To the founders there is little actual benefit from being an open source project, anyway. I can understand the attraction of the model in that situation.
My ideal OSS project would be receiving a steady stream of contributions from a wide variety of people without an elite sub group that considers themselves to be "the authors", which would be obviously unsuited to the faircode model. Sadly few projects achieve that and are largely the work of one person.
IMO it depends on the situation/project.
Let's not forget... the reason this type of licensing exists is because large cloud providers were taking a large code base and selling them as services . Often, the main path for the creators to make any money from their code is to offer a paid, managed tier, along with professional services. They would end up competing, and losing, against those cloud providers.
Not saying this kind of license is good or bad, but the reason is often not to stop self-hosting or screw contributors, but to maintain couple of the only pathways FOSS can bring in revenue.
Create proprietary software project , sell the software and give all the profit to starving kids in africa beside taking in a modest salary (say the US median salary) and call fair code, it's more fair then hashicorp CEO getting something like 100K a month in salary and stocks.
Hashicorp is on this list
We already have a perfectly good term for this sort of licensing model: