Ah yes, CLAs are not a real open source, which is why they're required by uhh FSF.
I mean I dislike CLAs personally, but I understand why they can be healthy for a project growth.
I mean I dislike CLAs personally, but I understand why they can be healthy for a project growth.
The last time I saw a FSF CLA, it was part of a larger agreement that also imposed obligations on the FSF.
In the long run, there may be risks to the FSF holding so many copyrights. But I don't think it clarifies matters to treat the FSF's CLAs the same as ones used by a "open core" VC funded startup.
Especially when the for-profit company openly announces this assignment of rights is for the purpose of selling code you wrote to others without giving back to the authors.
The FSF doesn't have a track record of asking for CLAs, and then selling your code to others under different licenses and pocketing the profits.
These two things are being conflated in this discussion. One thing is a CLA and copyright/license changes. The other is the license itself.