| 104 |
no longer unusual; such free commercial software is very important.</p> |
no longer unusual; such free commercial software is very important.</p> |
| 105 |
<p> |
<p> |
| 106 |
Rules about how to package a modified version are acceptable, if they |
Rules about how to package a modified version are acceptable, if they |
| 107 |
don't substantively block your freedom to release modified versions. |
don't substantively block your freedom to release modified versions, |
| 108 |
Rules that ``if you make the program available in this way, you must |
or your freedom to make and use modified versions privately. Rules |
| 109 |
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 |
| 110 |
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 |
| 111 |
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 |
| 112 |
license to require that, if you have distributed a modified version |
whether to publish your version at all.) Rules that require release |
| 113 |
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 |
| 114 |
or that you identify yourself on your modifications.</p> |
are also acceptable. It is also acceptable for the license to require |
| 115 |
|
that, if you have distributed a modified version and a previous |
| 116 |
|
developer asks for a copy of it, you must send one, or that you |
| 117 |
|
identify yourself on your modifications. |
| 118 |
|
</p> |
| 119 |
<p> |
<p> |
| 120 |
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> |
| 121 |
to protect these freedoms legally for everyone. But |
to protect these freedoms legally for everyone. But |