4 ms·
> The copyright owner can be either an individual, for example the person who wrote the code originally; or a company, for example a company that employed the p
by ChrisMarshallNY 5y ago
> The copyright owner can be either an individual, for example the person who wrote the code originally; or a company, for example a company that employed the person who wrote the code.
Here, there be dragonnes...
I can easily see an IC agreeing to a relicensing, thinking they had full rights, but their employer, at the time, had a "shower clause," and trying to (and maybe succeeding in) getting that section of license nullified. At least, costing the LLVM a bunch of money and time.
This was one reason that I made sure that my employer did not have a "shower clause," before starting to develop a lot of open-source software.
Knowing them, I'll bet that people hired after me had to sign that away, but I was never made to sign anything like that; even retroactively.
This is a mammoth effort, and I wish them well. I suspect they have already wargamed a lot of the possible issues.
- brnt 5y ago> The copyright owner can be either an individual, for example the person who wrote the code originally; or a company, for example a company that employed the person who wrote the code. Here be dragons indeed. This is flat out incorrect. In quite some jurisdictions, copyright is a nontransferable inalienable right any authors gains upon writing something, in perpetuity (can't even be transferred after death). Others, such as employers, may merely license is, sometimes exclusively.
- asdfasgasdgasdg 5y agoIs the distinction here really germane? If someone else holds an exclusive, transferrable, perpetual, sublicensable license to a work you produced, that's more or less the same as holding the copyright from LLVM's perspective. Of course all this only matters if they encounter a situation where it is difficult to determine the rightsholder, and they are not able to obtain agreement from all potential holders, and there ends up being a dispute.
- brnt 5y agoIn such jurisdiction, copyright attributions/assignments are simply not legally possible. We've had to scrap the one in place for on of our projects. The type of contract you should have contributors from such jurisdictions sign is a license to use. If you haven't, getting 'permission' is meaningless; the author possibly (in my experience: probably) doesn't know they're actually not legally able to agree to such a change.
- judge2020 5y agoBut if you grant a license that's sublicensable and exclusive (with all the extra legal rights granted), that's effectively transferring copyright since you can do everything you could as if you had transferred copyright.
- shakna 5y agoHowever, in most jurisdictions where copyright is non-transferable, the original holder also permanently retains a right to cancel any such licensing agreement, at any time without cause. They cannot grant a license in perpetuity, and any language in the license to that effect has no legal weight whatsoever.
- asdfasgasdgasdg 5y agoAs far as I can find online, this is an edge case that's unlikely to ever be relevant. Dutch law allows the voiding of licenses after "unreasonably long" terms. One suspects that it would be hard to show that a term is unreasonably long when you're talking about a contribution to open source software. In Poland, there's a limit of five years, on the author's wish, with one year's notice. Fair enough, a Polish contributor might possibly demand that their code be taken out of a projects with a year's notice. It seems unlikely that many Polish devs will exercise this right, since, if their contributions are significant, it would probably result in blacklisting, and if not significant, it would probably not be worth it. But I suppose it could happen. If it happened often, Polish devs would likely stop being welcome to contribute to open source projects. In Canada, there is automatic time-based reversion of rights 25 years after the author's death. So if you write code at 35, and die at 80, your estate could conceivably demand that your code could be removed from a project 70 years after you wrote it. Similarly, in the United States, you can revert your rights after going through some process and paying a fee after 35 years. The probability of any of these things happening seems sufficiently remote that it doesn't seem worth worrying about. Technically these CLAs might not actually grant perpetual licenses, but in practice they're likely close enough.
- valleyer 5y agoI'm sure you're right that that's how it works in some jurisdictions. But it's not how it works in the US, which is where the person responding to you lives. In the US, copyright is transferrable, and "works for hire" are initially owned by the employer. Either way, saying that the quoted bit is "flat out incorrect" seems like an overstep, in my opinion.
- brnt 5y agoLLVM has contributors from all over the world, hence it is relevant. It is certainly not an overstep. I work on a project with contributors from a few countries and this proved a major blocker for changing our license (not impossible, but much work!)
- bumblebritches5 5y ago> the LLVM NO. just like Batman, it's a proper name, "the" does not belong.