nothing ruins my motivation to send fixes to your open source project more than to ask me to sign a CLA for it.
sorry guys I'm just not that interested in reviewing a legal contract just to improve your software for free
nothing ruins my motivation to send fixes to your open source project more than to ask me to sign a CLA for it. sorry guys I'm just not that interested in reviewing a legal contract just to improve your software for free 18 comments
@erikarn @hailey @tursiae There's some nice examples and explanations here: https://softwareengineering.stackexchange.com/questions/168020/how-signing-out-a-cla-prevents-legal-issues-in-open-source-projects But as mentioned, it might be the difference between a full volunteer project and one with an organisational entity underlying it. @hailey @jacqueline Does a DCO have low enough friction to avoid the same reaction? Itβs still A Thing To Do, but at least it doesnβt feel like I ought to have a lawyer, I think, but Iβm curious if that tracks for you. @a @hailey @jacqueline Would you sign a CLA if the approval procedure is made as simple as DCO's? Is it a matter of principle, or is it a matter of convenience? @a @hailey @jacqueline don't they have two different goals? dco is for declaring you have the copyright of a patch (so you are allowed to say it's yours) and cla is for giving up your copyright to someone else? @jacqueline @hailey 6 << 6 (sorry it's a MISRA violation, but it's all I got in this economy) |
@hailey Iβve abandoned so many PRs and mailing list patches over this. π¬