3 ms·

Care to say more about the Redis case? I haven't followed it carefully enough to make sense of their organizational trajectory.

Sir_Cmpwn 7y ago
RedisLabs switched a bunch of their software to nonfree licenses and antirez can't really do anything about it. No matter what he says, I don't think he's in a position (i.e. financially) to oppose that decision by RedisLabs, even though it's clearly against the interests of the open source project.
- antirez 7y ago
  Sorry but this is absolutely inaccurate. Redis Labs switched the license of a set of modules I never developed a single line of, so it was completely their work I never took part into. The Redis codebase that I and the community developed in the latest 10 years is, probably, one of the last few examples of popular codebases yet under a BSD license. It sounds quite natural that I don't have the right to say Redis Labs what to do with the code they created around Redis itself. I expected the power to say what to do with the codebase I was working on, the Redis core, and indeed it is yet BSD.
  - Sir_Cmpwn 7y ago
    Expected this comment. That's why I wrote: >No matter what [antirez] says, [...]
    - antirez 7y ago
      Yep but it is important to have arguments. I'll show mine, and then it's your turn to convince others. So this is the timeline: - I start the Redis project, BSD. - I get sponsors. - Finally the sponsor becomes Redis Labs. - I continue to develop Redis with my private roadmap, still BSD. - Redis Labs creates modules and other forks with enhanced capabilities, that were mostly out of the scope of the original project. - Redis Labs changes the license of such add-ons to a proprietary one. - The project on Github that everybody is participating to, and the only one I continue to develop, remains BSD. Given the above, it's up to you to tell exactly what went wrong with Redis. If you believe for the story to be right that I had to force Redis Labs to license their code in a specific way, I think your reasoning is odd.
      - Sir_Cmpwn 7y ago
        I'm not going to let this get derailed into a public fight with you about this. Take it to email if you want: sir@cmpwn.com.

Sir_Cmpwn 7y ago

RedisLabs switched a bunch of their software to nonfree licenses and antirez can't really do anything about it. No matter what he says, I don't think he's in a position (i.e. financially) to oppose that decision by RedisLabs, even though it's clearly against the interests of the open source project.

antirez 7y ago
Sorry but this is absolutely inaccurate. Redis Labs switched the license of a set of modules I never developed a single line of, so it was completely their work I never took part into. The Redis codebase that I and the community developed in the latest 10 years is, probably, one of the last few examples of popular codebases yet under a BSD license. It sounds quite natural that I don't have the right to say Redis Labs what to do with the code they created around Redis itself. I expected the power to say what to do with the codebase I was working on, the Redis core, and indeed it is yet BSD.
- Sir_Cmpwn 7y ago
  Expected this comment. That's why I wrote: >No matter what [antirez] says, [...]
  - antirez 7y ago
    Yep but it is important to have arguments. I'll show mine, and then it's your turn to convince others. So this is the timeline: - I start the Redis project, BSD. - I get sponsors. - Finally the sponsor becomes Redis Labs. - I continue to develop Redis with my private roadmap, still BSD. - Redis Labs creates modules and other forks with enhanced capabilities, that were mostly out of the scope of the original project. - Redis Labs changes the license of such add-ons to a proprietary one. - The project on Github that everybody is participating to, and the only one I continue to develop, remains BSD. Given the above, it's up to you to tell exactly what went wrong with Redis. If you believe for the story to be right that I had to force Redis Labs to license their code in a specific way, I think your reasoning is odd.
    - Sir_Cmpwn 7y ago
      I'm not going to let this get derailed into a public fight with you about this. Take it to email if you want: sir@cmpwn.com.