Live data from Hacker News

Missing open-source contributor presents a dilemma when accepting their PR

bettersoftware.uk

21–30 of 73 posts

Re: Missing open-source contributor presents a dilemma when accepting their PR

#21

I don't like them and won't contribute to projects with them but isn't this the exact point of a CLA[1]? A textfile in the repo seems a lot easier to track and audit than PR comments and a bot to chase people. 1. https://en.m.wikipedia.org/wiki/Contributor_License_Agreemen...

No. The purpose of a CLA is so that the owner of the project can use the code in a commercial product that might not comply with the OSS license (particularly if that license is a copyleft licence such as GPL, AGPL, or MPL) and/or they can change the license more easily.

Re: Missing open-source contributor presents a dilemma when accepting their PR

#24
post #23

> ... asks for confirmation the code change is copyright-free Don't you mean patent-free? Or maybe you are asking for copyright assignment? Not sure what "copyright-free" means... Like do you only accept public domain code?

Yeah. In most countries copyright is automatic as soon as you create the work. Surely they mean they want confirmation they have a licence to use the copyrighted work?

Re: Missing open-source contributor presents a dilemma when accepting their PR

#25
post #17

"Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede." https://docs.github.com/en/site-policy/github-terms/github-t...

Really good to see Github being pro-active to the benefit of the open source community.

Re: Missing open-source contributor presents a dilemma when accepting their PR

#26
" and I find it hard to see how damages could be levied in this situation."

Unfortunately, this would be intentional copyright infringement (assuming the code is copyrightable, blah blah blah), since you are doing it on purpose with knowledge that it is copyrighted.

In a number of countries, copyright infringement is also strict liability - it doesn't matter if you had any intent to commit it, but if you did, the damages often start much much higher. So the former case you'd probably have some nominal statutory damages, assuming you can't prove any actual loss. But in the later case, those damages get quite high.

In the US, for example, statutory damages for intentional copyright infringement (IE you don't have to prove any actual damage) are 150k per infringement.

I make no claims any of this makes sense, or someone will actually sue you, or that you should do anything different than "nothing".

My only claim is that "and I find it hard to see how damages could be levied in this situation." is totally the wrong view in a lot of countries - you should expect, if it did get to that point, you would have plenty of damages levied against you.

The author appears to be in the UK, where statutory damages for infringement were historically not available. but post-brexit, they were actually doing consultation/blah blah blah on making them available. I have no idea what happened.

But even if they have no statutory damages, it won't prevent you from being sued wherever the contributor is, and having that law apply rather than your home law :)

It just makes it harder to collect.

Re: Missing open-source contributor presents a dilemma when accepting their PR

#28
post #21

I don't like them and won't contribute to projects with them but isn't this the exact point of a CLA[1]? A textfile in the repo seems a lot easier to track and audit than PR comments and a bot to chase people. 1. https://en.m.wikipedia.org/wiki/Contributor_License_Agreemen...

No. The purpose of a CLA is so that the owner of the project can use the code in a commercial product that might not comply with the OSS license (particularly if that license is a copyleft licence such as GPL, AGPL, or MPL) and/or they can change the license more easily.

Python has a CLA that allows the PSF board to relicense the code to "any other open source license approved by unanimous vote".

Re: Missing open-source contributor presents a dilemma when accepting their PR

#30
> The contribution bot asks for confirmation the code change is copyright-free

A confirmation is simply unnecessary. Can't it work like, writing this somewhere that says, by creating a pull request, you agree all your code and the discussions around the pull request is now copyright free? Saves everybody time and avoid hassles like this.

The other side of this is I get very annoyed by CLAs -- there have been a number of times I want to contribute to Google and Microsoft's open source projects, but they all require CLAs which require me to get explicit permissions from my employer to contribute to those projects. It is possible, but is a slow and complicated process that nobody wants to go through at my company. So instead of creating a pull request to address the problem, I open an issue and mention how it can be addressed. Which may or may not be picked up by someone else who wants to work on this. This is just frustrating.

Post reply on HN