jan-erik
Redis is not open source anymore.
That sucks.
I did a lot for Redis and in the community.
To this day I'm #23 on the contributor list of the main code base. I maintained the docs and several client libraries. I helped run the IRC channel back in the day.
I stopped most of my involvement some 6 years ago.
jan-erik
They also removed the "light governance model" they were running Redis under from 2020 onwards.
At least they are clear about it.
clacke
@shironeko No CLA necessary. Redis is simply exercising[0] their rights under the BSD license.
This is what happens when people use a permissive license and the project is run by one central entity, which then does a gradual bait-and-switch, what @webmink calls a "rights ratchet", see his posts for more on this.
[0] and overstepping, but they wouldn't have to, that's just clumsiness on their part
shironeko
jan-erik
@Exxo @clacke @shironeko @webmink there's a difference between the copyright and the license.
Them removing any notice of the former license and also copyright is questionable.
Them taking the code and releasing future versions under a new license is fine and allowed.
(and for my code contributions it probably doesn't matter, I'd be surprised if any of the actual code I ever wrote is still there)
Exxo
I disagree (at least following German law):
As long as no author has signed an CLA, they stay the owner of the intellectual property and their portion of code may only be used respecting the original (here BSD) license.
Every link in the post you mentioned also refers to contributor agreement as a component for the "rights ratchet".
But in practice I'm in doubt whether there is any chance in sueing Redis... so in consequence it makes no difference.
Simon Phipps
@Exxo
I focus on CLA because most projects use a license with at least a patent waiver and startups using rights-ratchet usually want to retain full patent leverage for their VCs so don't want to be subject to the license themselves. But in this case I don't think Redis started out as a rights-ratchet
clacke
@shironeko You are correct. They cannot relicense the contributions of others, for contributed code they need to adhere to BSD & ( RSAL | SSPL ).
Removing the BSD copyright notices is a license violation and shows a surprising level of incompetence. You'd think when making a controversial change they'd dot their Is and cross their Ts.
shironeko
shironeko
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.