1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
|
<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.96 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<!--#set var="TAGS" value="essays licensing copyleft" -->
<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
<title>When a Company Asks For Your Copyright
- GNU Project - Free Software Foundation</title>
<link rel="canonical"
href="https://www.fsf.org/blogs/rms/assigning-copyright" />
<!--#include virtual="/philosophy/po/assigning-copyright.translist" -->
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
<!--#include virtual="/server/top-addendum.html" -->
<div class="article reduced-width">
<h2>When a Company Asks For Your Copyright</h2>
<div class="thin"></div>
<p>Companies that develop free software and release it under the GNU GPL
sometimes distribute some copies of the code in other ways. If they
distribute the exact same code under a different license to certain
users that pay for this, typically permitting including the code in
proprietary programs, we call it “selling exceptions.” If they
distribute some version of the code solely in a proprietary manner, we
call that releasing a purely proprietary version of the program.</p>
<p>“<a href="/philosophy/selling-exceptions.html">Selling exceptions
to the GNU GPL</a>” explains why
selling exceptions is acceptable, though only barely. By contrast,
releasing a purely proprietary version is outright wrong, like
any other proprietary software.</p>
<p>Companies normally do these things using code they
developed. Since they hold the copyright on that code, they can
legally distribute it in any manner, even in multiple manners in
parallel. But what happens when you publish a modified version of
that free program, and the company wants to include your changes in
its version?</p>
<p>Since you got the program under the GPL, when you distribute a
modified version you have to license it under the GPL. If the company
receives a copy, it will be able to use those changes under the GPL;
it won't be allowed to include your changes in that program and sell
exceptions for it. It also won't be able to release purely
proprietary versions containing your code. If this is the outcome you
want, you get it by default. However, if the company intends to sell
exceptions, it will probably decide not to use your changes.</p>
<p>Suppose, though, that you're not opposed to selling exceptions and
you're willing to let the company do so while including your changes
in the program. You can agree to this, but you need to be careful
about what you sign, or you may be surprised by the results.</p>
<p>The company will probably invite you to assign or license your
copyright to the company, by signing a copyright assignment contract
or a contributor license agreement. That in itself is not inherently bad; for
instance, many GNU software developers have assigned copyrights
to the FSF. However, the FSF never sells exceptions, and its
assignment contracts include a commitment to distribute the
contributor's code only with source and only permitting
redistribution.</p>
<p>The company's proposed contract may not include such a commitment. It
might instead let the company use your changes any way it likes. If
you sign that, the company could do various things with your code. It
could keep selling exceptions for a program including your code. It
could release purely proprietary modified or extended versions
including your code. It could even include your code <em>only</em> in
proprietary versions. Your contribution of code could turn out to be,
in effect, a donation to proprietary software.</p>
<p>It is up to you which of these activities to permit, but here are the
FSF's recommendations. If you plan to make major contributions to the
project, insist that the contribution agreement require that software
versions including your contributions be available to the public under
a free software license. This will allow the developer to sell
exceptions, but prevent it from using your contributions in software
that is only available under a proprietary license.</p>
<p>If your contributions are smaller, you could accept a weaker
condition, that the company make your contributions available in a
free software release as well as possibly in nonfree programs.
This would allow the company to use your contributions in
modified software that's only available under a proprietary license.
Releasing proprietary software is never a good thing, but if your
changes are smaller, it might be more important to improve the free
version than resist the nonfree versions.</p>
<p>You can control these outcomes by insisting on the proper conditions
in the contract. To allow selling exceptions for the program that
contains your code, but refuse to let the company release purely
proprietary versions containing your code, you can insist on a
condition more or less like this:</p>
<blockquote class="emph-box">
<p>Any program based on (as defined in GNU General Public License
version 3) Hacker's code that FOO distributes shall be made
available by FOO under <b>(a)</b> the “GNU General Public License (GPL),
version 2 or later,” or <b>(b)</b> the licensing in (a), above, but with “2”
replaced by any higher existing GPL version number. Provided FOO
makes the program available as source code gratis to the public in
this way, it may also distribute the identical program to some of
its users under terms permitting them to link the program's code
with nonfree code and release the combination in binary form under a
license of their own choosing.</p>
</blockquote>
<p>Or, if what you object to is that some variant <em>of your code</em>
might be released solely in a proprietary version, you can insist on a
condition more or less like this:</p>
<blockquote class="emph-box">
<p>Any program based on (as defined in GNU General Public License
version 3) Hacker's code that FOO distributes shall be made
available by FOO under <b>(a)</b> the “GNU General Public License (GPL),
version 2 or later,” or <b>(b)</b> the licensing in (a), above, but with “2”
replaced by any higher existing GPL version number. Provided FOO
makes the program available as source code gratis to the public in
this way, it may also distribute the same version of Hacker's code
in other programs released under other licenses of its own choosing.</p>
</blockquote>
<p>If the program is released under the GNU Affero GPL, then add “Affero”
before “General,” change “GPL” to “AGPL,” change “2 or” to “3 or,” and
it could make sense to replace “that FOO distributes” with “that FOO
distributes, or deploys on a server accessible to users other than
FOO.”</p>
<p>The FSF has had these texts reviewed by a lawyer, but you should get
your own legal advice before using them.</p>
<p>When a company says which of these conditions it will accept, that
will show you how far it plans to depart from the principles of free
software. Then you can respond to ensure your work will contribute to
the free software community and not be diverted into proprietary
software.</p>
</div>
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div 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 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 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 © 2010, 2014, 2021 Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
<!--#include virtual="/server/bottom-notes.html" -->
<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2021/10/01 17:02:54 $
<!-- timestamp end -->
</p>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>
|
