| 81 |
the program. Therefore, accessibility of source code is a necessary |
the program. Therefore, accessibility of source code is a necessary |
| 82 |
condition for free software.</p> |
condition for free software.</p> |
| 83 |
<p> |
<p> |
| 84 |
|
One important way to modify a program is by merging in available free |
| 85 |
|
subroutines and modules. If the program's license says that you |
| 86 |
|
cannot merge in an existing module, such as if it requires you to be |
| 87 |
|
the copyright holder of any code you add, then the license is too |
| 88 |
|
restrictive to qualify as free.</p> |
| 89 |
|
<p> |
| 90 |
In order for these freedoms to be real, they must be irrevocable as |
In order for these freedoms to be real, they must be irrevocable as |
| 91 |
long as you do nothing wrong; if the developer of the software has the |
long as you do nothing wrong; if the developer of the software has the |
| 92 |
power to revoke the license, without your doing anything to give |
power to revoke the license, without your doing anything to give |
| 110 |
no longer unusual; such free commercial software is very important.</p> |
no longer unusual; such free commercial software is very important.</p> |
| 111 |
<p> |
<p> |
| 112 |
Rules about how to package a modified version are acceptable, if they |
Rules about how to package a modified version are acceptable, if they |
| 113 |
don't substantively block your freedom to release modified versions. |
don't substantively block your freedom to release modified versions, |
| 114 |
Rules that ``if you make the program available in this way, you must |
or your freedom to make and use modified versions privately. Rules |
| 115 |
make it available in that way also'' can be acceptable too, on the |
that ``if you make your version available in this way, you must make |
| 116 |
same condition. (Note that such a rule still leaves you the choice of |
it available in that way also'' can be acceptable too, on the same |
| 117 |
whether to publish the program or not.) It is also acceptable for the |
condition. (Note that such a rule still leaves you the choice of |
| 118 |
license to require that, if you have distributed a modified version |
whether to publish your version at all.) Rules that require release |
| 119 |
and a previous developer asks for a copy of it, you must send one, |
of source code to the users for versions that you put into public use |
| 120 |
or that you identify yourself on your modifications.</p> |
are also acceptable. It is also acceptable for the license to require |
| 121 |
|
that, if you have distributed a modified version and a previous |
| 122 |
|
developer asks for a copy of it, you must send one, or that you |
| 123 |
|
identify yourself on your modifications. |
| 124 |
|
</p> |
| 125 |
<p> |
<p> |
| 126 |
In the GNU project, we use <a href="/copyleft/copyleft.html">``copyleft''</a> |
In the GNU project, we use <a href="/copyleft/copyleft.html">``copyleft''</a> |
| 127 |
to protect these freedoms legally for everyone. But |
to protect these freedoms legally for everyone. But |
| 153 |
are many possible ways such a license could be unacceptably |
are many possible ways such a license could be unacceptably |
| 154 |
restrictive and non-free.</p> |
restrictive and non-free.</p> |
| 155 |
<p> |
<p> |
| 156 |
We can't possibly list all the possible contract restrictions that |
We can't possibly list all the ways that might happen. If a |
| 157 |
would be unacceptable. If a contract-based license restricts the user |
contract-based license restricts the user in an unusual way that |
| 158 |
in an unusual way that copyright-based licenses cannot, and which |
copyright-based licenses cannot, and which isn't mentioned here as |
| 159 |
isn't mentioned here as legitimate, we will have to think about it, |
legitimate, we will have to think about it, and we will probably |
| 160 |
and we will probably decide it is non-free.</p> |
conclude it is non-free.</p> |
| 161 |
<p> |
<p> |
| 162 |
When talking about free software, it is best to avoid using terms like |
When talking about free software, it is best to avoid using terms like |
| 163 |
``give away'' or ``for free'', because those terms imply that the |
``give away'' or ``for free'', because those terms imply that the |
| 269 |
| <a href="/philosophy/free-sw.ru.html">Русский</a> <!-- Russian --> |
| <a href="/philosophy/free-sw.ru.html">Русский</a> <!-- Russian --> |
| 270 |
| <a href="/philosophy/free-sw.sl.html">Slovinsko</a> <!--- Slovenian --> |
| <a href="/philosophy/free-sw.sl.html">Slovinsko</a> <!--- Slovenian --> |
| 271 |
| <a href="/philosophy/free-sw.sr.html">Српски</a> <!-- Serbian --> |
| <a href="/philosophy/free-sw.sr.html">Српски</a> <!-- Serbian --> |
| 272 |
|
| <a href="/philosophy/free-sw.tl.html">Tagalog</a> <!-- Tagalog --> |
| 273 |
| <a href="/philosophy/free-sw.tr.html">Türkçe</a> <!-- Turkish --> |
| <a href="/philosophy/free-sw.tr.html">Türkçe</a> <!-- Turkish --> |
| 274 |
] |
] |
| 275 |
</p> |
</p> |
| 299 |
|
|
| 300 |
<p> |
<p> |
| 301 |
Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free |
Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free |
| 302 |
Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA |
Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA |
| 303 |
02111, USA |
02110, USA |
| 304 |
<br /> |
<br /> |
| 305 |
Verbatim copying and distribution of this entire article is |
Verbatim copying and distribution of this entire article is |
| 306 |
permitted in any medium without royalty provided this notice is |
permitted in any medium without royalty provided this notice is |