employer/employee copyright
employer/employee copyright
Posted Aug 28, 2016 2:42 UTC (Sun) by giraffedata (guest, #1954)In reply to: 25 Years of Linux — so far by pabs
Parent article: 25 Years of Linux — so far
... reasons that Linux developers should demand to keep their copyrights in Linux instead of giving them to their employers.
Maybe you're trying to make a political point with this wording, but it's misleading. In the US, when someone pays someone else to write code, the copyright naturally belongs to the employer and the employer would have to give it to the developer for the developer to have it. Copyrights are man-made rights and the people who created them defined who's rights they would be.
Posted Aug 29, 2016 10:08 UTC (Mon)
by pabs (subscriber, #43278)
[Link] (1 responses)
http://www.copyright.gov/title17/92chap2.html#201
Posted Aug 30, 2016 2:27 UTC (Tue)
by giraffedata (guest, #1954)
[Link]
That's the opposite of the impression a reader would get from the phrasing, "employees should demand to keep their copyrights in Linux." The word "keep" implies that the copyright starts off belonging to the employee and the employee should insist on keeping it that way. If we want to give the correct impression (unless, again, we're trying to make a political point about truly natural rights being different from the ones created by law), a better wording would be, "employees should demand to own the copyright in their work on Linux."
employer/employee copyright
https://www.gov.uk/guidance/ownership-of-copyright-works#...
I believe those are exactly the points I made. We made up copyright law and arbitrarily decided that by default it belongs to the employer (I see "naturally" could be taken another way; I just meant that with the law in place and no further action, the employer has the copyright), so for the employee to have it, the employer has to do something to give it up.
employer/employee copyright