gnustandards-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog maintain.texi


From: Karl Berry
Subject: gnustandards ChangeLog maintain.texi
Date: Sun, 14 Aug 2011 17:00:25 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       11/08/14 17:00:25

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        discourage private GNU packages on Savannah

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.139&r2=1.140
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.201&r2=1.202

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.139
retrieving revision 1.140
diff -u -b -r1.139 -r1.140
--- ChangeLog   30 Jun 2011 17:24:19 -0000      1.139
+++ ChangeLog   14 Aug 2011 17:00:22 -0000      1.140
@@ -1,3 +1,8 @@
+2011-08-14  Karl Berry  <address@hidden>
+
+       * maintain.texi (Old Versions): Discourage private GNU packages on
+       Savannah.  Other small wording changes.
+
 2011-06-30  Karl Berry  <address@hidden>
 
        * maintain.texi (Free Software and Open Source): Open Source

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.201
retrieving revision 1.202
diff -u -b -r1.201 -r1.202
--- maintain.texi       30 Jun 2011 17:24:19 -0000      1.201
+++ maintain.texi       14 Aug 2011 17:00:23 -0000      1.202
@@ -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 June 30, 2011
address@hidden lastupdate August 14, 2011
 @c %**end of header
 
 @dircategory GNU organization
@@ -93,8 +93,8 @@
 Standards (@pxref{Top, , Contents, standards, GNU Coding Standards}).
 
 @cindex @code{bug-standards@@gnu.org} email address
address@hidden Savannah repository for gnustandards
address@hidden gnustandards project repository
address@hidden Savannah repository for @code{gnustandards}
address@hidden @code{gnustandards} project repository
 Please send corrections or suggestions for this document to
 @email{bug-standards@@gnu.org}.  If you make a suggestion, please
 include suggested new wording if you can.  We prefer a context diff to
@@ -200,12 +200,11 @@
 maintainer needs the GNU Project's confirmation, but your judgment that
 a person is capable of doing the job will carry a lot of weight.
 
-As your final act as maintainer, it would be helpful to set up the
-package under @code{savannah.gnu.org} if it is not there already
-(@pxref{Old Versions}).  This will make it much easier for the new
-maintainer to pick up where you left off and will ensure that the
-source tree is not misplaced if it takes us a while to find a new
-maintainer.
+As your final act as maintainer, it would be helpful to set up or
+update the package under @code{savannah.gnu.org} (@pxref{Old
+Versions}).  This will make it much easier for the new maintainer to
+pick up where you left off and will ensure that the source tree is not
+misplaced if it takes us a while to find a new maintainer.
 
 
 @node Recruiting Developers
@@ -1170,8 +1169,8 @@
 
 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 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
+CVS, Git, Subversion, @dots{}) if you like.  An easy way to use
+many such systems is via the Version Control library in Emacs
 (@pxref{Introduction to VC,, Introduction to Version Control, emacs,
 The GNU Emacs Manual}).
 
@@ -1182,16 +1181,18 @@
 some day.
 
 @cindex @code{savannah-hackers@@gnu.org}
-The GNU Project provides a server that GNU software packages can use
+The GNU Project provides a server that GNU packages can use
 for source control and other package needs: @code{savannah.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}.
 
-It's not a requirement, but all GNU maintainers are strongly
+It's not an absolute 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.
+point can serve to foster a sense of community among GNU developers as
+well as help in keeping up with project management.  Please don't mark
+Savannah projects for GNU packages as private; that defeats a large
+part of the purpose of using Savannah in the first place.
 
 @cindex @code{savannah-announce@@gnu.org} mailing list
 If you do use Savannah, please subscribe to the



reply via email to

[Prev in Thread] Current Thread [Next in Thread]