From: Alejandro Colomar <alx-AT-kernel.org>
Hi all,
As you know, I’ve been maintaining the Linux man-pages project for the last 4 years as a voluntary. I’ve been doing it in my free time, and no company has sponsored that work at all. At the moment, I cannot sustain this work economically any more, and will temporarily and indefinitely stop working on this project. If any company has interests in the future of the project, I’d welcome an offer to sponsor my work here; if so, please let me know.
Have a lovely day! Alex
That’s why the current state of open source licenses doesn’t work. Commercial use should be forbidden for free users. You could dual license the work, with a single, main license applying to everyone, and a second addendum license that just contains the clause for that specific use, be it personal or corporate. Corporate use of any kind requires supporting the project financially.
I’m a single dude who sells custom electronics with open source software on them. I sell maybe two PCBs a month. It just about covers my hobby, I’m not even living off of it. I can’t afford commercial licenses. There has to be tiers.
In return, I’ve made every schematic, gerber file, and bill of material to my stuff freely available.
One way to allow for this would be a license that says if you sell them through an LLC or corporate entity of some kind, that should require financial support but if it’s you selling them in your own name or as a single owner business, with your reputation and liability on the line, then you should not be required to provide support. The other thought to include in a license is actual money earned from sales. Once a company earns, for example let’s say $1,000 or 1,000€ a month in profits, that’s when the financial support license kicks in and requires payments to the open source authors. Of course, that would require high earners to report their earnings accurately which is a different can of worms.
I would draw the line at shareholders.
You may use my software free of charge if you are a student, hobbyist, hobbyist with income, side hustler, sole proprietorship, LLC, S-Corp, non-profit, partnership, or other owner-operator type business.
Corporations with investors or shareholders will pay recurring licensing fees. Your shareholders may not profit from my work unless I profit from it more than they do. If you can afford a three inch thick mahogany conference table you can afford to pay for your software.
I hope we see an evolution of licensing. Giant companies shouldn’t get a free pass if they’re just going to treat the original devs like a commodity to be used up.
I agree, but this is mostly an issue with permissive licenses like MIT. GPL and its variants have enough teeth in them to deal with shit like this. I’m scared of the rising popularity of these permissive licenses. A lot of indie devs have somehow been convinced by corpos that they should avoid the GPL and go with MIT and alike
I might be misunderstanding the licenses so correct me if wrong.
Can companies use GPL code internally without release as long as the thing written with it doesn’t get directly released to the public?
… or does GPL pollute everything even if used internally for commercial purposes?
I think it kicks in when you distribute. For example, let’s say I have a fork of some GPL software and I’m maintaining it for myself. I don’t need to share the changes if I’m the only one using it.
The point is that people using a software should be able to read and modify (and share) the source when they want to.
IANAL and all that good stuff
If it’s only internal then technically the internal users should have access to the source code. Only the people who receive the software get the rights and freedoms of the GPL, no one else.
Oh I definitely agree with you there. I just think GPL is close but not close enough.
AGPL? Google has a ban on all AGPL software. Sounds like if you write AGPL software, corporations won’t steal it.
Any license that makes a corporation shit its pants like this is good enough to start from IMO.
https://opensource.google/documentation/reference/using/agpl-policy