gnustandards ChangeLog maintain.texi

[Karl Berry]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       10/11/23 00:17:17

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        mention fsf, software maintenance fee possibilities

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.127&r2=1.128
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.194&r2=1.195

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -b -r1.127 -r1.128
--- ChangeLog   15 Nov 2010 22:36:31 -0000      1.127
+++ ChangeLog   23 Nov 2010 00:17:17 -0000      1.128
@@ -1,3 +1,8 @@
+2010-11-22  Karl Berry  <address@hidden>
+
+       * maintain.texi (Donations): mention FSF, software
+       maintenance fee possibilities.
+
 2010-11-15  Karl Berry  <address@hidden>
 
        * maintain.texi (Donations): do not explicitly mention paypal,

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.194
retrieving revision 1.195
diff -u -b -r1.194 -r1.195
--- maintain.texi       15 Nov 2010 22:36:31 -0000      1.194
+++ maintain.texi       23 Nov 2010 00:17:17 -0000      1.195
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate November 14, 2010
address@hidden lastupdate November 22, 2010
 @c %**end of header
 
 @dircategory GNU organization
@@ -1345,7 +1345,7 @@
 --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}.
@@ -2083,24 +2083,30 @@
 
 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
@@ -2109,6 +2115,10 @@
 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