6 ms·
CLAs are very misunderstood in the software industry. Every open source project should make its contributors sign CLAs, and you should be wary of using one that
by paxys 3y ago
CLAs are very misunderstood in the software industry. Every open source project should make its contributors sign CLAs, and you should be wary of using one that doesn't. Why? Because any single contributor can claim at any point in the future that the project is using their code illegally, and that you/your company should pay them for using their proprietary IP for all of these years. Can you prove that you audited every single line in the project you used and were sure of its copyright status? A CLA ensures exactly that. There's a reason why Linux Foundation, Apache, CNCF, Mozilla, heck even FSF all have strict CLA requirements.
Relicensing is a completely separate conversation, and there are plenty of open source CLAs which don't have that provision.
- Pannoniae 3y agoThis kind of trolling can easily be prevented by saying "Sure, we will remove your contributions. Name the exact line numbers affected"
- jen20 3y agoThe burden of ensuring license compliance falls to the consumer, not the producer.
- unmole 3y ago> Because any single contributor can claim at any point in the future that the project is using their code illegally So, you've never heard of a Developer Certificate of Origin? If it's good enough for Linux, it's good enough for me.
- paxys 3y ago> The Developer Certificate of Origin (DCO) is a statement that a software developer agrees to, saying that the contributor is allowed to make the contribution and that the project has the right to distribute it under its license. So in other words, a CLA.
- unmole 3y ago> So in other words, a CLA. Sure, in the same way that a cantaloupe is a hand grenade.
- not2b 3y agoCLA's required by some projects effectively require the contributor to give away all rights to the receiving organization. There are other forms of CLA that do not transfer these rights, but are still agreements (which is what the A stands for) between the contributor and the receiving organization. These might allow the recipient to change the license, or they might not. The DCO is just a statement and does not permit the receiving organization to distribute under incompatible licensing terms.
- paxys 3y agoI'm sure some organization can write a "DCO" which says the exact same thing. Ultimately what matters isn't the title of the document but the content. There are plenty of CLAs that just ask for the bare minimum for the project to be able to function (see ones from any of the organizations I mentioned).
- not2b 3y agoUnfortunately, many CLAs give the company that controls the code the power to take the project proprietary (and they will call this the bare minimum of what they need). It's repeatedly happened, so contributors need to be careful with what they sign. Perhaps for a small bug fix they won't care, but for anything larger, beware.
- deleted 3y ago[deleted]
- xdennis 3y ago> Every open source project should make its contributors sign CLAs What's the point of open source if you have to reveal you real identity?
- xdennis 3y agoWow, is everybody here paid by Zuck to use their real names?