You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Now that I clarified that Redis core license is BSD and is not affected by the common clause switch, let's reason a bit about all the rest, and what I think about @RedisLabs modules being switched from AGPL to Apache + Common Clause.
Let's start with my role at the company. I work for Redis Labs and I believe Redis Labs to have the best Redis experience for customers of managed services, that really add value to Redis + things such as the CRDTs multi master feature and so forth. However I focus *just* on OSS.
So I'll stick with OSS licenses, while I believe Redis Labs as a company is right in stating that the current situation is broken. So on my side, I'll keep Redis core BSD because I believe at this point it is a collective effort, and Redis Labs is supporting me on that.
However users buying managed services are not "voting with their money" enough. Redis Labs is growing very fast, but yet not enough people IMHO understand that it's worth to buy the service from the folks that invest in the OSS side of such system.
So for the @RedisLabs modules it makes sense IMHO, given that they are almost solely developed inside the company, to say: "this is our added value, and we want to take the source `open`, and free as in beer if you install yourself. But we want more protection". I respect that.
However the Common Clause is not technically speaking open source, why it has certain degree of freedom, and this should be made clear indeed. For the same reason my Disque module will be released under the AGPL license.
I'd love to talk to the powers that be about how to structure the business to make money. As it is, this move will confuse the market and not accomplish what they want. It's an own goal and there are better ways to improve their situation.
Disclaimer: My company has a managed hosting department, PaaS offering and does operations for Industry companies, On all 3 we offer Redis. On none I know we use modules which went to common clause.
That being said, that switch is kind of wierd, because you basically bar any money making process around using addons. Including hosting fees. So someone who offers it is not allowed to charge you for the Hardware. Which is tbh pretty drastic. I have not used @RedisLabs
but in my experience it will have issues with most of our customers, as Cloud is a field day for Security and on-vpc has the issue that our customers usually forbid access from out-of-eu and safeguards that this cannot happen. It also has lacks an on-prem offering.
(With on-prem I not only mean industry customers, but also smaller provider which have like 10-20 services). In my opinion it feels like Redis wanted to hit the big providers, but have in the worst case hit a good bit of smaller offerings as roadkill.
Also, since it bans consulting, am I now barred from billing customers when I suggest Redis with one of the clause addons to them? So do I need to accidentially drop notes now? ;)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
