3 ms·
Historically the FSF required copyright assignment for FSF works. This was to avoid having any potential problems where a contributor thought they were OK to co
by icebraining 11y ago
Historically the FSF required copyright assignment for FSF works. This was to avoid having any potential problems where a contributor thought they were OK to contribute, but the employer potentially had a "work for hire" claim.
How would that work? If you don't have the legal standing to contribute to the project, you certainly can't reassign the copyright to another party.
The copyright assignment is so that the FSF can sue if someone break the project's license. They also require a disclaimer that the work isn't for-hire, but that's a different issue.
http://www.gnu.org/licenses/why-assign.en.html http://www.gnu.org/licenses/why-assign.en.html
- btilly 11y agoThe process of getting the employer disclaimer mentioned in your link exists exactly to catch cases where the contributor was mistaken about their ability to legally contribute.
- icebraining 11y agoYes, but the disclaimer is not the copyright assignment, they're different legal acts.
- btilly 11y agoTrue, they are different forms. However they are both part of the process of making sure that the FSF actually owns that copyright.