4 ms·
Yes I remember there was a similar scenario with Microsoft as well. > In other words, I'm not aware of a permissive license that's the same as BSD/Apache with
by ksec 6y ago
Yes I remember there was a similar scenario with Microsoft as well.
> In other words, I'm not aware of a permissive license that's the same as BSD/Apache with the only difference in that also says "use it as you wish but you must mention my name when you're a commercial enterprise making a splashy product announcement".
Yes. What we need is ABSD, AMIT or AAPL where the first A stands for appreciation / Attribution
- varispeed 6y agoOh the good old companies paying in exposure... If you make a profit from using someone else software you should pay them (plus appropriate tax) regardless of the software license.
- jaywalk 6y agoIf someone wants to get paid by people who profit off their software, they should license it in a way that requires that. Otherwise, tough luck.
- varispeed 6y agoThis is a loophole that allows big companies to avoid hiring engineers and paying right tax. Not sure why would you support this?
- tzs 6y agoIt's not a loophole. A loophole is when you have some case or situation not covered by the rules allowing someone to get away with something that the rules were not meant to allow. E.g., a company arranging for its shareholders to be able to report dividends as capital gains rather than ordinary income by doing a fractional stock split followed by a mandatory buyback instead of declaring a dividend, with the split/buyback designed so that each shareholder ends up with exactly the same percentage ownership they had before and with cash equal to the exact amount that would have been otherwise distributed as a dividend [1], that's a loophole. An author picking an open source license that specifically and intentionally allows anyone to use their software and make money from it without having to give the author anything is not a loophole. [1] Yes, this actually happened around 100 years ago. The rules on buybacks were changed to fix it. But them some legitimate cases of buybacks that should have been capital gains became ordinary income, so more fixes were needed. The result is that what once needed at most a line in the tax code, if it even needed mention at all, became several paragraphs. This is why we do not have a small, simple tax code--there is a massive incentive for people to find even the tiniest loophole and exploit it, and so you end up with multiple paragraphs for things you at first would think could be done in a sentence. (And don't say a flat tax would help...almost all of the complexity in the tax code is in determining what gets taxes, not how much the tax is once you have figured out the what).
- toast0 6y agoAll of my enduring open source contributions have been made while employed by a big(ish) company. I went through the effort to get them upstreamed so other people wouldn't have to make the same effort to debug and fix the same issues. Does that enable other companies to avoid hiring engineers to do the same work? Maybe, but it also enables everyone to benefit from things working just a bit better. I don't need a royalty from my fixes, I was compensated for my time. I don't even care about a credit, but I understand some do.
- karolist 6y agoAm I crazy for wanting a license that prohibits the free use of a project by mega-corps? "If you're a company valued > $XXX usage of this code is prohibited". I guess I can see OSS as a "free food" stall. Almost everyone can have a bite but I'm not fine with billionaires coming in to steal the recipes. They already have the means to increase their wealth efficiently, society would have much benefit if these mechanisms of wealth increase involved giving some of it back.
- Riverheart 6y agoIt's the same issue as taxes. They make buckets of money, use public infrastructure to do it, give pennies back. Apologists say why expect them to act different if the law let's them get away with it? How unreasonable of us. Unity's license is what we're aiming for yeah? Use it freely but at a certain dollar threshold, contribute back monetarily?
- segfaultbuserr 6y agoCongratulations, you've just reinvented the original BSD-4 license! It included what was called the "obnoxious advertising clause". > 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the <organization>. There's a good reason why we no longer use BSD-4 anymore. https://www.gnu.org/licenses/bsd.html https://www.gnu.org/licenses/bsd.html > The result is a plethora of licenses, requiring a plethora of different sentences. When people put many such programs together in an operating system, the result is a serious problem. Imagine if a software system required 75 different sentences, each one naming a different author or group of authors. To advertise that, you would need a full-page ad. This might seem like extrapolation ad absurdum, but it is actual fact. In a 1997 version of NetBSD, I counted 75 of these sentences. (Fortunately NetBSD has decided to stop adding them, and to remove those it could.)
- rbanffy 6y agoMaybe BSD4 is a good license in this case. I'd prefer AGPL, but then AWS would probably just avoid it.
- segfaultbuserr 6y agoThe advertising clause is inherently problematic to integrators, distributions, and packagers, which are an important part of the community. For a distribution, having to acknowledge 1,000+ authors in all promotional materials is unrealistic. Worse, it won't be a problem initially, but only after most people had noticed this trend: they would want their acknowledgements too, and everyone would start adding advertising clauses, in the end - everyone spams all posters with credit and nobody gains any notability, it's kind of a tragedy of the commons. The only way to stop this problem is explicitly discouraging everyone from using it. A idea is to reword and relax this license: Similar to LGPL, you can skip the acknowledgement if it's used in an unmodified form. But it doesn't really solve the problem - if the original project has been forked by the community, the exception becomes useless again. The next problem is that, it doesn't really cover all cases - in a previous incident involved Microsoft, Microsoft didn't even use a single line of the original code at all, it was just an inspiration from its framework, and the author was upset for not receiving any acknowledgement... Another idea is using AGPL's approach and targets cloud providers only, but still, it doesn't cover all the cases here. I'm not sure whether using copyright to require acknowledgement is a good idea after all. In the academia, copyright and credit/attribution are two entirely independent process. The credit is not a legal matter, but simply a form of code of conduct and informal politeness. Perhaps promoting a code of conduct for acknowledgement in the industry regarding the use of FOSS could work better.