5 ms·
This is well expressed, and thought-provoking for those of us who work on open source geo. One (accidental) way to achieve “ethos licensing” as described in th
by Doctor_Fegg 6y ago
This is well expressed, and thought-provoking for those of us who work on open source geo.
One (accidental) way to achieve “ethos licensing” as described in the article, while remaining genuinely open source, is to license your code as WTFPL. I started doing that facetiously to express my disdain for licence holy wars, but it turns out that the bad guys are characterised by having large armies of lawyers, and large armies of lawyers really don’t like WTFPL. Google explicitly forbids it, and I’ve encountered other BigCos who won’t touch it. That’s a pretty decent side-effect for those of us who don’t want to support the ad-tracking industry.
(WTFPL does of course have the bug of not disclaiming warranty, but you can trivially fix that by inserting the sentence “There is no f——ing warranty.”)
- ATsch 6y agoAGPL does much of the same thing. Many bigcorps explicitly forbid it's use, while private individuals are totally fine with it.
- deleted 6y ago[deleted]