It was wise of @drewdevault to host redict (redis fork) on @Codeberg to maintain workflow parity with github and avoid any perceived conflicts of interest¹.
I wondered why LGPL and not of AGPL², which is also explained nicely: "but we want to make it as easy as possible for users to comply with the Redict license and we do not see any reason to discourage cloud providers from making use of Redict."
Hope other marquee projects follow suite.
¹https://fosstodon.org/@drewdevault/112167165399257154
² https://redict.io/posts/2024-03-22-redict-is-an-independent-fork/#why-lgpl
@immibis sorry, which part is FOSS class treason, I didn't follow.
@immibis ah okay, yeah I agree on principle for sure but not on existing projects that are already in use by the cloud providers. If redict was licensed as AGPL (which is what I would have thought) then none of the existing cloud companies would likely use redict. So none of the contributions they make would never make it out as FOSS.
1/2
@immibis But in this case, with LGPL they can/might switch to redict and could continue contributing. I'm using can/might/could to illustrate that it's a possiblity, not a guarantee, but AGPL would be a guaranteed no.
So in this specific case @drewdevault's choice gives a better shot for contributions from cloud providers to land on @Codeberg than AGPL hosted on sourcehut.
2/2
@immibis I think we misunderstood each other. I was using "work for free" the way you implied in your previous comment, creating value (code) without payment. Not making services from AWS free.
Also, we're on the same side of the argument here, corporations mooch off community effort without contributing value back. We're agreed on that.
@drewdevault @Codeberg
1/2
@immibis However, what this specific instance of license choice of LGPL does is to leave the door open for those corporations to continue contributing. The value has already been absorbed by them, there's no going back. Using a license that discourages corporate use at this stage is only going to hurt the FOSS community from getting value back in the form of corporate contributions.
2/2
@drewdevault @Codeberg