5 ms·
Honestly my colleagues did a poor job with such an announcement there, and I did not get a chance to read it (which is actually a good thing, it means that the
by antirez 8y ago
Honestly my colleagues did a poor job with such an announcement there, and I did not get a chance to read it (which is actually a good thing, it means that the OSS division, I'm part of, is independent and can work to the Github repositories without caring about what the commercial side does). But it was kinda of a manifest to announce that certain things made inside Redis Labs are now Common Clause licensed. In doubt, why not asking? Also people that follow me and Redis for years getting trapped into this idea is very strange, I would never do that and without explaining, prior notice, and so forth. So yep the Common Clause page at Redis Labs sucked but in doubt ask instead of creating news out of no actual information.
- l2dy 8y agoThe abbreviation "CC" will be confusing if Commons Clause got popular… We already have Creative Commons licenses.
- antirez 8y agoAgreed, fixed.
- millette 8y agoUtterly confused. Does this have anything to do with Creative Commons licences? That's what the articles calls it in its first and last sentences.
- jpobst 8y agoParticularly because the linked post calls it "Creative Common" twice and "Common Clause" elsewhere.
- tango24 8y agoWhen I see CC, I also tend to think it means Common Criteria : https://en.m.wikipedia.org/wiki/Common_Criteria https://en.m.wikipedia.org/wiki/Common_Criteria
- dilap 8y agoIt was clear to me from a careful reading that the page did not refer to Redis, but it also seemed deliberately designed to suggest that it did. It seemed pretty scummy. And the name itself of "Commons Clause" is practically a tiny version of fake news, since it tries to give an "open source" feeling to what is essentially a proprietary license. As a practical/PR matter, I think Redis Labs have likely shot themselves in the foot. I've been in a low-key debate advocating for Redis Labs over AWS elasticache on an upcoming project; my argument probably just got about 1000% harder, given the anti-RL sentiment I saw on our Slack last night. (Finally, if you'll forgive me a bit of personal advice, I think for better or worse Redis + your personal brand + RedisLabs are now all somewhat tied together -- I'm not sure how much sense it makes for you to just pay attention to the OSS side of the house...)
- sikhnerd 8y agoI'll pile on here as well, we were thinking about shifting from elasticache to RL, but this has made that decision super easy.
- fizzybeetle 8y agoElasticache is a totally closed source implementation that does not contribute back to the community. How did this situation change your decision?
- dilap 8y agowhat would they contribute back? elasticache is just vanilla redis. aws is selling you compute time and ram.
- scrollaway 8y ago> elasticache is just vanilla redis Only at the interface level. Elasticache is a heavily forked Redis. There's a reason it's several versions behind.
- hiccuphippo 8y agoIf the commercial side can change the license without your knowledge then it is not a good thing at all.
- deleted 8y ago[deleted]