<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.77 1.97 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<title>Why the FSF gets copyright assignments Gets Copyright Assignments from contributors Contributors
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/licenses/po/why-assign.translist" -->
<!--#include virtual="/server/banner.html" -->
<div class="article reduced-width">
<h2>Why the FSF gets copyright assignments Gets Copyright Assignments from contributors</h2>

<p>
by <strong>Professor Contributors</h2>

<address class="byline">by Professor Eben Moglen</strong>, Moglen, Columbia University
Law
School</p>

<blockquote><p>
[Explanatory School</address>

<div class="introduction"><p>
Explanatory note added in Jan 2013: this point applies to the
packages that are FSF-copyrighted.  When the developers of a program
make it a GNU package, they can decide either to give the copyright to
the FSF so it can enforce the GPL for the package, or else to keep the
copyright as well as the responsibility for enforcing the GPL.  If
they make it an FSF-copyrighted package, then the FSF asks for
copyright assignments for further contributions, and this page
explains why.]</p></blockquote> why.
<a
href="https://www.fsf.org/bulletin/2014/spring/copyright-assignment-at-the-fsf">
Additional pertinent explanation</a>.</p>
<hr class="no-display" />
</div>

<p>
Under US copyright law, which is the law under which most free
software programs have historically been first published, there
are very substantial procedural advantages to registration of
copyright.  And despite the broad right of distribution conveyed by
the GPL, enforcement of copyright is generally not possible for
distributors: only the copyright holder or someone having assignment
of the copyright can enforce the license.  If there are multiple
authors of a copyrighted work, successful enforcement depends on
having the cooperation of all authors.</p>

<p>
In order to make sure that all of our copyrights can meet the
recordkeeping and other requirements of registration, and in order
to be able to enforce the GPL most effectively, FSF requires that
each author of code incorporated in FSF projects provide a copyright
assignment, and, where appropriate, a disclaimer of any
work-for-hire ownership claims by the programmer's employer.  That
way we can be sure that all the code in FSF projects is free code,
whose freedom we can most effectively protect, and therefore on
which other developers can completely rely.</p>
</div>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer"> id="footer" role="contentinfo">
<div class="unprintable">

<p>Please send general FSF & GNU inquiries to <a
href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.  There are also <a
href="/contact/">other ways to contact</a> the FSF.  Broken links and other
corrections or suggestions can be sent to <a
href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">
        <web-translators@gnu.org></a>.</p>

        <p>For information on coordinating and submitting contributing translations of
        our web pages, see <a
        href="/server/standards/README.translations.html">Translations
        README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations README</a> for
information on coordinating and submitting contributing translations of this article.</p>
</div>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 4.0.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->

<p>Copyright © 2001, 2008, 2009, 2014 2013, 2014, 2017, 2022 Free Software Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivs 3.0 United States Attribution-NoDerivatives 4.0 International License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->

<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2022/07/04 18:04:55 $
<!-- timestamp end -->
</p>
</div>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>