X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fmaintain.texi;h=7d4f5829cff48d47ae2e8b178418c2232af45acb;hb=88418d5fd24c99aac393d3e2f564f6939e4e2fe3;hp=c6eb0904367e542bee747dbaebb8d28dcbcadbff;hpb=e9e556f53c74014cb122e8c7fd0405f40f7c9acb;p=gnulib.git diff --git a/doc/maintain.texi b/doc/maintain.texi index c6eb09043..7d4f5829c 100644 --- a/doc/maintain.texi +++ b/doc/maintain.texi @@ -5,7 +5,7 @@ @c For double-sided printing, uncomment: @c @setchapternewpage odd @c This date is automagically updated when you save this file: -@set lastupdate October 8, 2010 +@set lastupdate December 9, 2010 @c %**end of header @dircategory GNU organization @@ -70,6 +70,7 @@ Texts. A copy of the license is included in the section entitled * Ethical and Philosophical Consideration:: * Terminology:: * Hosting:: +* Donations:: * Free Software Directory:: * Using the Proofreaders List:: * GNU Free Documentation License:: @@ -624,8 +625,11 @@ domain, if the movie companies don't continue buying laws to further extend copyright. If you copy a file into the package from some other program, keep the copyright years that come with the file. -Do not abbreviate the year list using a range; for instance, do not -write @samp{1996--1998}; instead, write @samp{1996, 1997, 1998}. +You can use a range (@samp{2008-2010}) instead of listing individual +years (@samp{2008, 2009, 2010}) if and only if: 1)@tie{}every year in +the range, inclusive, really is a ``copyrightable'' year that would be +listed individually; @emph{and} 2)@tie{}you make an explicit statement +in a @file{README} file about this usage. For files which are regularly copied from another project (such as @samp{gnulib}), leave the copyright notice as it is in the original. @@ -1095,10 +1099,10 @@ useful for your package. @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 @@ -1109,15 +1113,14 @@ some day. @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 @@ -1341,7 +1344,7 @@ good to also send your key to the GPG public key server: @code{gpg --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}. @@ -2063,7 +2066,7 @@ following the rules stated in the license of each package. For more information, see http://www.gnu.org/philosophy/free-sw.html. If you are looking for service or support for GNU software, see -http://www.gnu.org/help/gethelp.html for suggestions of where to ask. +http://www.gnu.org/gethelp/ for suggestions of where to ask. If you would like to contribute to the development of one of these packages, contact the package maintainer or the bug-reporting address @@ -2072,6 +2075,50 @@ on www.gnu.org for more information on how to contribute. @end smallexample +@node Donations +@chapter Donations +@cindex Donations, for packages +@cindex Money, donated to packages + +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 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{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{amount1}, we'd be happy to recognize your +contribution on @var{url2}. + +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 + +We don't recommend any specific payment service. However, GNU +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 @cindex Free Software Directory