selling.html (10832B)
1 <!--#include virtual="/server/header.html" --> 2 <!-- Parent-Version: 1.96 --> 3 <!-- This page is derived from /server/standards/boilerplate.html --> 4 <!--#set var="TAGS" value="essays aboutfs principles" --> 5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> 6 <title>Selling Free Software 7 - GNU Project - Free Software Foundation</title> 8 <!--#include virtual="/philosophy/po/selling.translist" --> 9 <!--#include virtual="/server/banner.html" --> 10 <!--#include virtual="/philosophy/ph-breadcrumb.html" --> 11 <!--GNUN: OUT-OF-DATE NOTICE--> 12 <!--#include virtual="/server/top-addendum.html" --> 13 <div class="article reduced-width"> 14 <h2>Selling Free Software</h2> 15 16 <p><em><a href="/philosophy/selling-exceptions.html">Some views on the 17 ideas of selling exceptions to free software licenses, such as the GNU 18 GPL</a> are also available.</em></p> 19 <hr class="thin" /> 20 21 <p> 22 Many people believe that the spirit of the GNU Project is that you 23 should not charge money for distributing copies of software, or that 24 you should charge as little as possible—just enough to cover 25 the cost. This is a misunderstanding.</p> 26 27 <p> 28 Actually, we encourage people who redistribute 29 <a href="/philosophy/free-sw.html">free software</a> to charge as much 30 as they wish or can. If a license does not permit users to make 31 copies and sell them, it is a nonfree license. If this seems 32 surprising to you, please read on.</p> 33 34 <p> 35 The word “free” has two legitimate general meanings; it can refer 36 either to freedom or to price. When we speak of “free software,” 37 we're talking about freedom, not price. (Think of “free speech,” 38 not “free beer.”) Specifically, it means that a user is free to run 39 the program, study and change the program, and redistribute the program with or 40 without changes.</p> 41 42 <p> 43 Free programs are sometimes distributed gratis, and sometimes for a 44 substantial price. Often the same program is available in both ways 45 from different places. The program is free regardless of the price, 46 because users have freedom in using it.</p> 47 48 <p> 49 <a href="/philosophy/categories.html#ProprietarySoftware">Nonfree programs</a> 50 are usually sold for a high price, but sometimes a store will give you 51 a copy at no charge. That doesn't make it free software, though. 52 Price or no price, the program is nonfree because its users are denied 53 freedom.</p> 54 55 <p> 56 Since free software is not a matter of price, a low price doesn't make 57 the software 58 free, or even closer to free. So if you are redistributing copies of free 59 software, you might as well charge a substantial fee and <em>make 60 some money</em>. Redistributing free software is a good and 61 legitimate activity; if you do it, you might as well make a profit 62 from it.</p> 63 64 <p> 65 Free software is a community project, and everyone who depends on it 66 ought to look for ways to contribute to building the community. For a 67 distributor, the way to do this is to give a part of the profit to free software development projects or to the 68 <a href="https://www.fsf.org/">Free Software Foundation</a>. This way you can 69 advance the world of free software.</p> 70 71 <p> 72 <strong>Distributing free software is an opportunity to raise 73 funds for development. Don't waste it!</strong></p> 74 75 <p> 76 In order to contribute funds, you need to have some extra. If you 77 charge too low a fee, you won't have anything to spare to support 78 development.</p> 79 80 81 <h3>Will a higher distribution price hurt some users?</h3> 82 83 <p> 84 People sometimes worry that a high distribution fee will put free 85 software out of range for users who don't have a lot of money. With 86 <a href="/philosophy/categories.html#ProprietarySoftware">proprietary 87 software</a>, a high price does exactly that—but free software 88 is different.</p> 89 90 <p> 91 The difference is that free software naturally tends to spread around, 92 and there are many ways to get it.</p> 93 94 <p> 95 Software hoarders try their damnedest to stop you from running a 96 proprietary program without paying the standard price. If this price 97 is high, that does make it hard for some users to use the program.</p> 98 99 <p> 100 With free software, users don't <em>have</em> to pay the 101 distribution fee in order to use the software. They can copy the 102 program from a friend who has a copy, or with the help of a friend who 103 has network access. Or several users can join together, split the 104 price of one CD-ROM, then each in turn can install the software. A high 105 CD-ROM price is not a major obstacle when the software is free.</p> 106 107 108 <h3>Will a higher distribution price discourage use of free software?</h3> 109 110 <p> 111 Another common concern is for the popularity of free software. People 112 think that a high price for distribution would reduce the number of 113 users, or that a low price is likely to encourage users.</p> 114 115 <p> 116 This is true for proprietary software—but free software is 117 different. With so many ways to get copies, the price of distribution 118 service has less effect on popularity.</p> 119 120 <p> 121 In the long run, how many people use free software is determined 122 mainly by <em>how much free software can do</em>, and how easy it 123 is to use. Many users do not make freedom their priority; they 124 may continue to use proprietary software if 125 free software can't do all the jobs they want done. Thus, if we want 126 to increase the number of users in the long run, we should above all 127 <em>develop more free software</em>.</p> 128 129 <p> 130 The most direct way to do this is by writing needed 131 <a href="https://savannah.gnu.org/projects/tasklist">free software</a> 132 or 133 <a href="/doc/doc.html">manuals</a> yourself. But if you do 134 distribution rather than writing, the best way you can help is by 135 raising funds for others to write them.</p> 136 137 138 <h3>The term “selling software” can be confusing too</h3> 139 140 <p> 141 Strictly speaking, “selling” means trading goods for 142 money. Selling a copy of a free program is legitimate, and we 143 encourage it.</p> 144 145 <p> 146 However, when people think of “<a 147 href="/philosophy/words-to-avoid.html#SellSoftware">selling software</a>,” 148 they usually imagine doing it the way most companies do it: making the 149 software proprietary rather than free.</p> 150 151 <p> 152 So unless you're going to draw distinctions carefully, the way this 153 article does, we suggest it is better to avoid using the term 154 “selling software” and choose some other wording instead. 155 For example, you could say “distributing free software for a 156 fee”—that is unambiguous.</p> 157 158 159 <h3>High or low fees, and the GNU GPL</h3> 160 161 <p> 162 Except for one special situation, the 163 <a href="/licenses/gpl.html">GNU General Public License</a> (GNU GPL) 164 has no requirements about how much you can charge for distributing a 165 copy of free software. You can charge nothing, a penny, a dollar, or 166 a billion dollars. It's up to you, and the marketplace, so don't 167 complain to us if nobody wants to pay a billion dollars for a 168 copy.</p> 169 170 <p> 171 The one exception is in the case where binaries are distributed 172 without the corresponding complete source code. Those who do this are 173 required by the GNU GPL to provide source code on subsequent request. 174 Without a limit on the fee for the source code, they would be able set 175 a fee too large for anyone to pay—such as a billion 176 dollars—and thus pretend to release source code while in truth 177 concealing it. So <a href="/licenses/gpl.html#section6">in this case we 178 have to limit the fee</a> for source in order 179 to ensure the user's freedom. In ordinary situations, however, there 180 is no such justification for limiting distribution fees, so we do not 181 limit them.</p> 182 183 <p> 184 Sometimes companies whose activities cross the line stated in the GNU 185 GPL plead for permission, saying that they “won't charge 186 money for the GNU software” or such like. That won't get them anywhere 187 with us. Free software is about freedom, and enforcing the GPL is 188 defending freedom. When we defend users' freedom, we are not 189 distracted by side issues such as how much of a distribution fee is 190 charged. Freedom is the issue, the whole issue, and the only issue.</p> 191 </div> 192 193 </div><!-- for id="content", starts in the include above --> 194 <!--#include virtual="/server/footer.html" --> 195 <div id="footer" role="contentinfo"> 196 <div class="unprintable"> 197 198 <p>Please send general FSF & GNU inquiries to 199 <a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>. 200 There are also <a href="/contact/">other ways to contact</a> 201 the FSF. Broken links and other corrections or suggestions can be sent 202 to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p> 203 204 <p><!-- TRANSLATORS: Ignore the original text in this paragraph, 205 replace it with the translation of these two: 206 207 We work hard and do our best to provide accurate, good quality 208 translations. However, we are not exempt from imperfection. 209 Please send your comments and general suggestions in this regard 210 to <a href="mailto:web-translators@gnu.org"> 211 <web-translators@gnu.org></a>.</p> 212 213 <p>For information on coordinating and contributing translations of 214 our web pages, see <a 215 href="/server/standards/README.translations.html">Translations 216 README</a>. --> 217 Please see the <a 218 href="/server/standards/README.translations.html">Translations 219 README</a> for information on coordinating and contributing translations 220 of this article.</p> 221 </div> 222 223 <!-- Regarding copyright, in general, standalone pages (as opposed to 224 files generated as part of manuals) on the GNU web server should 225 be under CC BY-ND 4.0. Please do NOT change or remove this 226 without talking with the webmasters or licensing team first. 227 Please make sure the copyright date is consistent with the 228 document. For web pages, it is ok to list just the latest year the 229 document was modified, or published. 230 231 If you wish to list earlier years, that is ok too. 232 Either "2001, 2002, 2003" or "2001-2003" are ok for specifying 233 years, as long as each year in the range is in fact a copyrightable 234 year, i.e., a year in which the document was published (including 235 being publicly visible on the web or in a revision control system). 236 237 There is more detail about copyright years in the GNU Maintainers 238 Information document, www.gnu.org/prep/maintain. --> 239 240 <p>Copyright © 1996-1998, 2001, 2007, 2015, 2021 241 Free Software Foundation, Inc.</p> 242 243 <p>This page is licensed under a <a rel="license" 244 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative 245 Commons Attribution-NoDerivatives 4.0 International License</a>.</p> 246 247 <!--#include virtual="/server/bottom-notes.html" --> 248 249 <p class="unprintable">Updated: 250 <!-- timestamp start --> 251 $Date: 2021/09/10 10:58:36 $ 252 <!-- timestamp end --> 253 </p> 254 </div> 255 </div><!-- for class="inner", starts in the banner include --> 256 </body> 257 </html>