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.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
