> Even if through some process the license changes in the future, your contributions were still to an open source license and that version of the code will remain open forever.
Well, that's a good take. You're right of course: the exact version of the codebase you contributed to, was licensed as OSS and it will always stay like that.
So yes, copyleft is more about providing guarantees about the future, while non-copyleft can only provide guarantees about the present.
I think this way of putting it is clearer than my previous way of saying it. Thanks for bringing up this point of view.
> This is the reason why projects like MAME have contributor agreements now.
Hence articles such as [1] and [2], which have been posted in HN before, albeit with pretty much zero conversation.
Still, just like I'm interested in the topic of OSS licenses and the thought process of people who choose them for their projects, I find also interesting the matter about CLAs and whether to go on with one or instead opting to use a DCO [3], which some well known OSS projects have preferred in the past: [4], [5].
[1]: Why CLAs aren't good for open source -- https://opensource.com/article/19/2/cla-problems
[2]: Why you probably shouldn’t add a CLA to your open source project -- https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-...
[3]: CLA vs. DCO: What's the difference? -- https://opensource.com/article/18/3/cla-vs-dco-whats-differe...
[4]: (GitLab) We're switching to a DCO for source code contributions -- https://about.gitlab.com/blog/2017/11/01/gitlab-switches-to-...
[5]: Helm Moves To DCO -- https://helm.sh/blog/helm-dco/