]> git.ipfire.org Git - thirdparty/gcc.git/blame - doc/funding.rst
sphinx: add missing trailing newline
[thirdparty/gcc.git] / doc / funding.rst
CommitLineData
c63539ff
ML
1..
2 Copyright 1988-2022 Free Software Foundation, Inc.
3 This is part of the GCC manual.
4 For copying conditions, see the copyright.rst file.
5
6Funding Free Software
7=====================
8
9If you want to have more free software a few years from now, it makes
10sense for you to help encourage people to contribute funds for its
11development. The most effective approach known is to encourage
12commercial redistributors to donate.
13
14Users of free software systems can boost the pace of development by
15encouraging for-a-fee distributors to donate part of their selling price
16to free software developers-the Free Software Foundation, and others.
17
18The way to convince distributors to do this is to demand it and expect
19it from them. So when you compare distributors, judge them partly by
20how much they give to free software development. Show distributors
21they must compete to be the one who gives the most.
22
23To make this approach work, you must insist on numbers that you can
24compare, such as, 'We will donate ten dollars to the Frobnitz project
25for each disk sold.' Don't be satisfied with a vague promise, such as
26'A portion of the profits are donated,' since it doesn't give a basis
27for comparison.
28
29Even a precise fraction 'of the profits from this disk' is not very
30meaningful, since creative accounting and unrelated business decisions
31can greatly alter what fraction of the sales price counts as profit.
32If the price you pay is $50, ten percent of the profit is probably
33less than a dollar; it might be a few cents, or nothing at all.
34
35Some redistributors do development work themselves. This is useful too;
36but to keep everyone honest, you need to inquire how much they do, and
37what kind. Some kinds of development make much more long-term
38difference than others. For example, maintaining a separate version of
39a program contributes very little; maintaining the standard version of a
40program for the whole community contributes much. Easy new ports
41contribute little, since someone else would surely do them; difficult
42ports such as adding a new CPU to the GNU Compiler Collection contribute more;
43major new features or packages contribute the most.
44
45By establishing the idea that supporting further development is 'the
46proper thing to do' when distributing free software for a fee, we can
3ed1b4ce 47assure a steady flow of resources into making more free software.