X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;ds=inline;f=doc%2Fmaintain.texi;h=241663e3dd9384069797a1bb4c80d04662fd84b5;hb=b34698eb8843377024315f407ec63ba67c82b686;hp=126b19cff9b2853f33121bad1f26e7edd0ef6ebc;hpb=b6772983c800c6faee7fc793b83975afb6d58bcc;p=gnulib.git diff --git a/doc/maintain.texi b/doc/maintain.texi index 126b19cff..241663e3d 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 May 9, 2011 +@set lastupdate August 14, 2011 @c %**end of header @dircategory GNU organization @@ -93,8 +93,8 @@ In addition to this document, please read and follow the GNU Coding Standards (@pxref{Top, , Contents, standards, GNU Coding Standards}). @cindex @code{bug-standards@@gnu.org} email address -@cindex Savannah repository for gnustandards -@cindex gnustandards project repository +@cindex Savannah repository for @code{gnustandards} +@cindex @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 @@ If you have an idea for who should take over, please tell 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 @@ useful for your package. 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 @@ change log that you would not want to hand over to another maintainer 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 @@ -1426,8 +1427,8 @@ finally email the resulting @file{@var{msgfile}.asc}), to @enumerate @item -Name of package(s) that you are the maintainer for, and your -preferred email address. +Name of package(s) that you are the maintainer for, your +preferred email address, and your Savannah username. @item An ASCII armored copy of your GPG key, as an attachment. (@samp{gpg @@ -2041,32 +2042,36 @@ about GNU. @node Free Software and Open Source @section Free Software and Open Source -@cindex free software +@cindex free software movement @cindex open source -@cindex movements, Free Software and Open Source - -The terms ``free software'' and ``open source'' are the slogans of two -different movements which differ in their basic philosophy. The Free -Software Movement is idealistic, and raises issues of freedom, ethics, -principle and what makes for a good society. The Open Source Movement, -founded in 1998, studiously avoids such questions. For more explanation, -see @url{http://www.gnu.org/philosophy/open-source-misses-the-point.html}. - -The GNU Project is aligned with the Free Software Movement. This +@cindex movement, free software +@cindex development method, open source + +The terms ``free software'' and ``open source'', while describing +almost the same category of software, stand for views based on +fundamentally different values. The free software movement is +idealistic, and raises issues of freedom, ethics, principle and what +makes for a good society. The term open source, initiated in 1998, is +associated with a philosophy which studiously avoids such questions. +For a detailed explanation, see +@url{http://www.gnu.org/philosophy/open-source-misses-the-point.html}. + +The GNU Project is aligned with the free software movement. This doesn't mean that all GNU contributors and maintainers have to agree; your views on these issues are up to you, and you're entitled to express them when speaking for yourself. -However, due to the much greater publicity that the Open Source -Movement receives, the GNU Project needs to overcome a widespread -mistaken impression that GNU is @emph{and always was} an activity of -the Open Source Movement. For this reason, please use the term ``free +However, due to the much greater publicity that the term ``open source'' +receives, the GNU Project needs to overcome a widespread +mistaken impression that GNU is @emph{and always was} an ``open +source'' activity. For this reason, please use the term ``free software'', not ``open source'', in GNU software releases, GNU documentation, and announcements and articles that you publish in your role as the maintainer of a GNU package. A reference to the URL given above, to explain the difference, is a useful thing to include as well. + @node GNU and Linux @section GNU and Linux @cindex Linux