3 ms·

Seems like a good case study in poor communication then. It doesn't excuse people spreading misinformation without a decent attempt to ascertain the facts, but

Seems like a good case study in poor communication then. It doesn't excuse people spreading misinformation without a decent attempt to ascertain the facts, but it seems Redis Labs mainly have themselves to blame. Their page [0] starts out: "Initiated by a coalition of top infrastructure software companies to protect their rights...". So they're trying to make it sound like a Big Deal, and beyond just for Redis. Then later we hear 'oh it's just relicensing a couple of non-core modules, what are you all carrying on about?' Even now it's not clear to me (not being particularly familiar with Redis) what direction things are changing in. shakes head Edit: Oh, and the confusing name. Why is it called "Commons Clause"? [0] https://redislabs.com/community/commons-clause/ https://redislabs.com/community/commons-clause/

sqrt17 8y ago
> Oh, and the confusing name. Why is it called "Commons Clause"? Exactly. What is in effect crossing the boundary between open source and shared source (as Microsoft called the first source release of the .Netruntime) is made to sound like an afterthought. So, instead of AGPL (widely recognized as off-limits for corporate users), you could claim it's "Apache plus Commons Clause" which sounds nice as long as you squint really hard. It's ok to put software under a BSD-inspired or Apache-inspired noncommercial-only license - in fact plenty of people are doing this already - but it's disingenuous to use the name of the open source license you took inspiration from in the hope to profit from the open source halo for non-open-source software.