@c For double-sided printing, uncomment:
@c @setchapternewpage odd
@c This date is automagically updated when you save this file:
-@set lastupdate November 14, 2010
+@set lastupdate December 9, 2010
@c %**end of header
@dircategory GNU organization
@cindex version control
It is very important to keep backup files of all source files of GNU.
-You can do this using a source control system (such as RCS, CVS, Git,
-@dots{}) if you like. The easiest way to use RCS or CVS is via the
-Version Control library in Emacs (@pxref{VC Concepts,, Concepts of
-Version Control, emacs, The GNU Emacs Manual}).
+You can do this using a source control system (such as Bazaar, RCS,
+CVS, Git, Subversion, @dots{}) if you like. The easiest way to use
+RCS or CVS is via the Version Control library in Emacs (@pxref{VC
+Concepts,, Concepts of Version Control, emacs, The GNU Emacs Manual}).
The history of previous revisions and log entries is very important for
future maintainers of the package, so even if you do not make it
@cindex @code{savannah-hackers@@gnu.org}
The GNU Project provides a server that GNU software packages can use
for source control and other package needs: @code{savannah.gnu.org}.
-You don't have to use this repository, but if you plan to allow public
-read-only access to your development sources, it is convenient for
-people to be able to find various GNU packages in a central place.
-Savannah is managed by @email{savannah-hackers@@gnu.org}.
+Savannah is managed by @email{savannah-hackers@@gnu.org}. For more
+details on using and contributing to Savannah, see
+@url{http://savannah.gnu.org/maintenance}.
-All GNU maintainers are strongly encouraged to take advantage of
-Savannah, as sharing such a central point can serve to foster a sense
-of community among GNU developers and help in keeping up with project
-management.
+It's not a requirement, but all GNU maintainers are strongly
+encouraged to take advantage of Savannah, as sharing such a central
+point can serve to foster a sense of community among GNU developers
+and help in keeping up with project management.
@cindex @code{savannah-announce@@gnu.org} mailing list
If you do use Savannah, please subscribe to the
--keyserver keys.gnupg.net --send-keys @var{keyid}}, where @var{keyid}
is the eight hex digits reported by @code{gpg --list-public-keys} on
the @code{pub} line before the date. For full information about GPG,
-see @url{http://www.gnu.org/software/gpg})
+see @url{http://www.gnu.org/software/gpg}.
@item
Compose a message with the following items in some @var{msgfile}.
As a maintainer, you might want to accept donations for your work,
especially if you pay for any of your own hosting/development
-infrastructure. Following is some text you can adapt for your
-package's web site, @file{README}, or wherever you find it useful:
+infrastructure. Following is some text you can adapt to your own
+situation, and use on your package's web site, @file{README}, or
+in wherever way you find it useful:
@smallexample
We appreciate contributions of any size -- donations enable us to spend
more time working on the project, and help cover our infrastructure
expenses.
-If you'd like to make a small donation, please visit @var{url} and do
+If you'd like to make a small donation, please visit @var{url1} and do
it through @var{payment-service}. Since our project isn't a
tax-exempt organization, we can't offer you a tax deduction, but for
-all donations over @var{amount}, we'd be happy to recognize your
-contribution on @var{another-url}.
+all donations over @var{amount1}, we'd be happy to recognize your
+contribution on @var{url2}.
-If you can make a donation large enough to entirely fund a substantial
-change, such as $1000, then we could discuss with you what change we
-should do with your funds, and we could give you a certain amount of
-specific help in exchange. Write to us about this at @var{address}.
+We are also happy to consider making particular improvements or
+changes, or giving specific technical assistance, in return for a
+substantial donation over @var{amount2}. If you would like to discuss
+this possibility, write to us at @var{address}.
+
+Another possibility is to pay a software maintenance fee. Again,
+write to us about this at @var{address} to discuss how much you want
+to pay and how much maintenance we can offer in return. If you pay
+more than @var{amount1}, we can give you a document for your records.
Thanks for your support!
@end smallexample
developers should not use a service that requires them to sign a
proprietary software license, such as Google's payment service.
+Of course, it is also good to encourage people to join or contribute
+to the FSF (@url{http://www.fsf.org}), either instead of or as well as
+package-specific donations.
+
@node Free Software Directory
@chapter Free Software Directory
projects / gnulib.git / blobdiff