Hacker News new | past | comments | ask | show | jobs | submit login

But Redis was always BSD licensed. Every release of Redis was released with the full knowledge that anyone could do anything they wanted to with Redis, as long as they provided attribution and didn't claim a warranty.

Redis also continues to be BSD licensed.

For even more nuance, Redis Labs wasn't the author of Redis, they only sponsored the author. They weren't the first sponsors either, and nothing's stopping others from sponsoring Redis either, as long as it continues to be BSD licensed. That's the point of Open Source, that anyone can come with even just a brick to add to the cathedral, and everyone enjoys the benefits from the addition of that brick.

With closed source software, that freedom is gone.; all progress now has to go through (and be owned by) just one entity. I wouldn't want to contribute to a BSLed project because I'd be a second-class citizen in it. And even I did put out a BSLed patch to a BSLed project, the project owners can't use it for as long as I retain the copyrights on my patch.

Ok then, the extra modules that Redis Labs maintains, which used to be licensed under a modified Apache2 licence, and are now under a "source available" license because it causes less confusion about if it's actually OSI sanctioned or not.


Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact