3 ms·
Mostly true, but only up to an extent: without a CLA, they can't just update LICENSE.txt to replace the contents with the text of the new license and be on thei
by pwdisswordfish0 6y ago
Mostly true, but only up to an extent: without a CLA, they can't just update LICENSE.txt to replace the contents with the text of the new license and be on their merry way without any trace of the old one.
They can't hide the fact that it was once MIT/BSD/Apache licensed, and they still have to include copies of that original license (and any notices) even after the switch, as that is one of the conditions that contributors make their work available under, and failure to do so would mean the org is in violation if they haven't otherwise received approval.
- pritambarhate 6y agoEven if one has to include the original license and notices with the new version, the original license and notices apply to the portions which were present in the older versions. The new portions added to the software after the license change must be used only as per the new license. MIT, BSD and Apache licenses don't forbid you to use a new license to your own derivative work.
- pwdisswordfish0 6y agoEverything you just wrote is true, but it's not clear why you felt the need to spell it out, especially right here. (No one has said otherwise. No one has said anything that could be mistaken to mean otherwise.)