Copyright assignment
May. 17th, 2011 01:14 pmThe fundamental problem with projects requiring copyright assignment is that there's an economic cost involved in me letting a competitor sell a closed version of my code without letting me sell a closed version of their code. If this cost is perceived as larger than the cost of maintaining my code outside the upstream tree, it's cheaper for me to fork than it is to sign over my rights. So if I have my own engineering resources, what rational benefit is there to me assigning my copyright?
Copyright Assignment in Germany?
Date: 2011-05-17 11:01 pm (UTC)So no matter what piece of paper he signs, legally nothing can take away the author's ownership of the IP, so while he can assign usage right to third parties, he will always retain his own rights to the things he wrote, including the right to relicense.
Or so is my understanding, at least.
Re: Copyright Assignment in Germany?
Date: 2011-05-17 11:42 pm (UTC)What you can't give up/sign over is the rights directly tied to authorship, such as the right to be named as the creator, or the right to not be named as the creator, and a few more. There are some more restrictions on authorship rights for software written as an employee as part of your job, IIRC.
Besides, Germany is not a rare case here. In Europe authors' rights would be basically everywhere but the UK, I think. Copyright is a system born from the UK legal philosophy and is thus found mostly in those countries whose legal tradition is influenced by it, such as the USA.