Re:Amazon: Not OK – Why we had to change Elastic licensing
by prepend on Tuesday January 19, 2021 @10:57AM
(#25834689)
That’s what I used to think, but now more companies use “open” with non-OSI licenses and they aren’t run out of town and told STFU.
Personally, any project using “open” in the name that’s not OSI, I pretty much ignore. But it seems to be growing (eg, “open core”, “openai”, stuff like this taking about open with non-open licenses).
It’s getting hard to filter out. One of the benefits I think to CCn is that it clearly lets users know what is and is not allowed. Having OSIn might help with people who don’t read licenses for fun.
Re:Amazon: Not OK – Why we had to change Elastic licensing
by MaxBarraclough on Tuesday January 19, 2021 @11:15AM
(#25834899)
OpenAI is a good example, see this comment from yesterday: https://news.ycombinator.com/item?id=25820080
I tend to capitalise the term, Open Source, to emphasise that I'm using it an a precise way. I do the same with Free Software. Not ironclad, but I figure it probably helps.
With all of that said, I don't think anyone should be permitted to deliberately mislead people when they're pushing a product. It's obviously right that false advertising is forbidden by law.