3 ms·
The real problem with the licenses is that they are not open source, but many users of them still seem to think they are doing open source. The funny thing is
by verdverm 7y ago
The real problem with the licenses is that they are not open source, but many users of them still seem to think they are doing open source.
The funny thing is that they are trying to protect themselves from Amazon and other competition before it usually exists, and that in reality, they are doing themselves more harm because the big co lawyers are starting to reject these unusual, project specific license. "If it takes more than a few minutes to understand, then I tell the devs No"
To all those would be users of the Faux Pas OSS licenses, why did you make it open source in the first place? If you want to protect your code, why no make it private? Why use one of these licenses?
- ghaff 7y agoI had a conversation with a company a few weeks ago about this. What they told me aligned with other things I've heard. Basically they're seeing customers giving preference to open source software and they believe (rightly or wrongly) that using one of these non-compete licenses will give them the marketing advantages of open source without the potential business model downsides. Of course, they also likely don't get the development model advantages of open source but anecdotally these companies don't much care about that. (And TBH a lot of single-company products/projects don't get a lot of outside contribution anyway.)
- verdverm 7y agoIt's like having your cake, and eating it too!
- Wowfunhappy 7y agoCould the company use something like AGPL in these instances? (The developing company ofc wouldn't follow the AGPL, but in this case the code is officially open source.)
- ghaff 7y agoIt's possible. Although a cloud provider could still potentially run a competing service so long as they made any modifications available to the public. (A cloud provider still might choose not to do so because of uncertainly about how the code interacts with other services in their infrastructure.) But, yes, "Why doesn't the AGPL solve your perceived problem?" is a reasonable question to ask in the context of these non-compete licenses.
- tripletao 7y agoAmazon can host your thing cheaper than you can, and it doesn't have to pay your developers. The AGPL means Amazon won't have better features, but they can still have better economics, better big-company reputation, better one stop shopping, etc.
- deleted 7y ago[deleted]
- kemitchell 7y agoThat doesn't track my experience advising on new licenses in the last few years. Most of the folks who ask me for or about them have been in open source for quite some time, have done their homework on licensing basics, and simply don't care whether anyone in particular tells them they're open source. Open source is at best a means to them, not an end, and not a perfectly effective one when it comes to advancing an activist cause, building a business, or advancing the technical state of the art.
- verdverm 7y agoWatch the video of FB head of legal talking at the FOSS conference about licenses. Success in advising these companies on crafting a license does not imply that the project or their choice to embrace this style of license will result in success. If they still call themselves open source, they are lying. The proper term is "source available."
- kemitchell 7y agoI've seen the talk. There are many talks. No license guarantees success in any dimension. Not MIT. Not BSD. Not Apache 2 or GPLv3 or WTFPL or any of the PolyForm terms. Most open source projects, as I suspect you define open source, fail. Very little uptake. Very little outside contribution. Net loss, financially speaking, for the developers. You're free to argue for or against whatever meaning of "open source" you like. But disagreeing with you, or refusing to accept the brand you'd force on them, does not make anyone a liar. I was quite doctrinaire about the issue myself, for many years. It wasn't until I got beyond reading what the OSI said about itself---parsing the OSD, reading its history, dealing with the mailing list process, seeing the shifts in FSF position, reading up on the "open" buzzwords wars before 1998---that I realized the "right answer" I was so proud of having wasn't so right and rigorous, after all. I regret how badly I treated others, for the sake of my own feeling of "correctness".
- verdverm 7y agoIf you think the PolyForm counts as open source, and you want to pervert the meaning of open source, go ahead. You can claim your own meaning for open source and licenses, but there is a governing body that we look to, to decide which licenses do qualify as open source. They have started denying this style license, and until they approve PolyForm as a qualifying license, you will be considered among the liars (people abusing ignorance and marketing for their own benefit) if you promote it as an open source license.
- tripletao 7y agoSo I build a thing, and I want to give it away to hobbyists and small, risk-tolerant non-competitors, as a public service and for marketing. I hope to make money later selling it (or selling consulting), probably mostly to big companies. How is any of what you write above a problem? If the big companies are willing to pay me, then I'll sign whatever commercial license they want--and if they're not, how does it benefit me for them to use it for free? Big tech companies have done an incredible job of harvesting the value of free software developers working for free. I don't see why a license that makes that harder for them is bad, except for the big tech companies. Perhaps defining "competitive" will be too mushy to make these licenses practical for anyone, but I appreciate the attempt.
- anonymfus 7y agoYou can just use one of the existing licenses that big corps don't like, for example AGPLv3+
- tripletao 7y agoAGPL means they can't compete on features, but they might have better hosting economics, better sales and marketing, etc. Or they can offer better features, but split those into a separate closed-source program that talks to yours. The latter is presumably why MongoDB switched away from the AGPL (which was controversial; but I'm always amazed at the entitlement shown by people receiving software for free).