[commit-womb] gnumaint temail-2dub.txt

[Mike Gerwitz]

CVSROOT:        /sources/womb
Module name:    gnumaint
Changes by:     Mike Gerwitz <mikegerwitz>      19/01/14 22:03:19

Modified files:
        .              : temail-2dub.txt 

Log message:
        Summary: temail-2dub.txt: Update with changes from rms

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnumaint/temail-2dub.txt?cvsroot=womb&r1=1.5&r2=1.6

Patches:
Index: temail-2dub.txt
===================================================================
RCS file: /sources/womb/gnumaint/temail-2dub.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- temail-2dub.txt     13 Apr 2016 19:58:57 -0000      1.5
+++ temail-2dub.txt     15 Jan 2019 03:03:19 -0000      1.6
@@ -1,16 +1,22 @@
 From: address@hidden (Brandon Invergo)
 To: 
 Cc: address@hidden, address@hidden
-Subject: maintaining GNU 
+Subject: maintaining 
 
-I hereby appoint you as the new maintainer of GNU
+I hereby appoint you as the new maintainer of 
 Thanks for volunteering.
 
 Being a package maintainer is a relationship between you personally
-and the GNU Project.  The maintainer or maintainers are the ones
-who take the overall responsibility for the work done on the package.
+and the GNU Project.  The maintainer or maintainers are the ones who
+take the overall responsibility for the work done on the package, on
+behalf of the GNU Project.
+
 If you recruit others to contribute to the package (and some packages
-have hundreds of contributors), they work under your supervision.
+have hundreds of contributors), they work under your supervision.  You
+can delegate some of your authority to them, but you can also take it
+back.  Please make sure they don't come to think that you have ceded
+your authority to them and that they no longer have to follow your
+directions.
 
 The GNU Project will sometimes need to talk with you, sometimes
 privately, so please make sure we know a personal email address which
@@ -19,14 +25,29 @@
 in touch with you if email fails; we do not give them out.
 
 If you ever want to step down as maintainer, or would like someone
-else to replace you, please talk with address@hidden and
address@hidden about it.  When a package has no maintainer, we need to
-know about the problem so we can look for a new one.  Likewise, if you
-think someone else should join you as co-maintainer or take over from
-you as maintainer, please talk with us, since we will need to
-establish a relationship with that person.
+else to replace you, please talk with address@hidden about it.
+When a package has no maintainer, we need to know about the problem so
+we can look for a new one.  The program remains a GNU package
+unless/until the GNU project decides to drop ties with it.
+
+Likewise, if you think someone else should join you as co-maintainer
+or take over from you as maintainer, please suggest that to us, since
+we will need to establish a relationship with that person.  A person
+cannot become a GNU package maintainer except by being appointed by
+the GNU Project.
+
+Your appointment as maintainer is provisional at first.  We'll make
+your appointment full and permanent when we see that you're doing the
+job.  Usually that means we see that you've made a release properly,
+with the changes that the next release ought to have.  However, if
+making a proper release involves a lot of work, and will therefore
+take a long time, we could appoint you full maintainer when we see you
+have made a good start on the job.
+
+Please tell us the first time you're about to make a release, so we
+can guide you on doing it properly following our conventions.
 
-The GNU maintainer information in http://www.gnu.org/prep/maintain/
+The GNU maintainer information in https://www.gnu.org/prep/maintain/
 describes a lot of procedures for GNU maintainers.  It also
 describes who you can ask for various kinds of support or advice.  If
 you encounter a situation where it isn't clear what to do, you can
@@ -38,22 +59,19 @@
 gnu-prog-discuss list, which can be used for discussion among GNU
 maintainers, but whether to stay on the list is up to you.
 
-Please send a note to gnu-prog-discuss now with a brief description of
-your package, so that other GNU developers will learn about it.
-
 We strongly recommend using ftp.gnu.org to make distributions
 available.  Please see the GNU maintainers guide for the procedure,
-http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html.
+https://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html.
 When that is set up, you'll be able to do uploads yourself.  If you
 want to also distribute the package from a site of your own, that is
 fine.  To use some other site instead of ftp.gnu.org is acceptable,
 provided it allows connections from anyone anywhere.
 
 Please write or update the web pages about the program, to put in
-http://www.gnu.org/software/PROGNAME.  These pages should be the
+https://www.gnu.org/software/PROGNAME.  These pages should be the
 main web site for the program, and they should really have the
 information for users, not just a link to another site; please use
-http://www.gnu.org/software/PROGNAME whenever you give out the URL
+https://www.gnu.org/software/PROGNAME whenever you give out the URL
 for the home page of the program.  Please don't set up a "site for the
 program" anywhere else--if you want to do work on additional web pages
 about the program, please put them on www.gnu.org.
@@ -62,8 +80,8 @@
 site, and likewise for pages that access databases.)
 
 In writing the web pages, please follow the style guidelines in
-http://www.gnu.org/server/fsf-html-style-sheet.html.   See also
-http://www.gnu.org/prep/maintain/html_node/Web-Pages.html.
+https://www.gnu.org/server/fsf-html-style-sheet.html.  See also
+https://www.gnu.org/prep/maintain/html_node/Web-Pages.html.
 
 We ask that you register your package on Savannah, at least to maintain
 your package's web pages.  This is independent of where the actual
@@ -71,28 +89,21 @@
 for that too).  This makes it easy to update the web pages, since you
 will have access to a CVS repository for the web pages and can update it
 as you like.  Using Savannah will help the GNU Project in other ways,
-too.  To set this up, visit http://savannah.gnu.org/.
-
-If your package was already being developed on Savannah as nongnu, email
address@hidden and ask them to mark it there as a GNU
-package.  This should happen without your intervention, but feel free to
-ask them if a day or two has gone by without the change being made.
+too.  To set this up, visit https://savannah.gnu.org/.
 
 Please also write an entry or a change for the page
-http://www.gnu.org/people/people.html, and mail that to
+https://www.gnu.org/people/people.html, and mail that to
 address@hidden  Note that we don't want to talk about
 proprietary software, so if you have worked on any, please don't
 mention it here.  Your entry can include a link to your home page
 provided it fits our usual criteria for what we link to.
 
-Please make sure that the program has an up-to-date entry in our Free
-Software Directory (http://directory.fsf.org).  See
-http://www.gnu.org/help/directory.html#adding-entries for the details
-which are needed.
+Please update the program's entry in our Free Software Directory.  See
+https://www.gnu.org/help/directory.html#adding-entries for help.
 
 Mailing lists: Your package should already have a mailing list
 address@hidden for reporting bugs.  If not, please create it--see
-http://www.gnu.org/prep/maintain/html_node/Mail.html for the details of
+https://www.gnu.org/prep/maintain/html_node/Mail.html for the details of
 creating mailing lists.
 
 Some GNU programs with many users have another mailing list,
@@ -104,25 +115,25 @@
 Please post announcements of new releases of the program to
 address@hidden  Include a brief description of the program so people
 can tell whether they are interested in using it.  The announcement
-should mention the web pages on www.gnu.org, and say where to get the
-program by ftp.
+should mention the web pages on www.gnu.org, and say where to get
+releases, normally ftp.gnu.org.
 
 You can also send announcements to a special list address@hidden
 for your program if you think that is warranted.  (This list should be
 moderated.)
 
 Please also mention release announcements in the news feed of the
-savannah project site, <http://savannah.gnu.org/projects/PROGNAME>.
+savannah project site, <https://savannah.gnu.org/projects/PROGNAME>.
 The news feeds from the GNU project are aggregated at
-<http://planet.gnu.org/>.
+<https://planet.gnu.org/>.
 
 For more details about writing and publicizing announcements, please see
-http://www.gnu.org/prep/maintain/html_node/Announcements.html.
+https://www.gnu.org/prep/maintain/html_node/Announcements.html.
 
 For details on all policies and recommendations for GNU packages,
 please see the GNU maintainers information, at
-http://www.gnu.org/prep/maintain/, and GNU coding standards, at
-http://www.gnu.org/prep/standards/.
+https://www.gnu.org/prep/maintain/, and GNU coding standards, at
+https://www.gnu.org/prep/standards/.
 
 For the basic ideas of GNU and free software, please read these essays:
 http://www.gnu.org/gnu/the-gnu-project.html
@@ -134,8 +145,8 @@
 http://www.gnu.org/gnu/gnu-linux-faq.html
 http://www.gnu.org/philosophy/open-source-misses-the-point.html
 
-new-gnu people, could you please enter XYZ in gnuorg/maintainers and
-add him to the gnu-prog lists?
+new-gnu people, could you please enter XYZ in
+gnuorg/maintainers and add him to the gnu-prog lists?
 
 Savannah hackers, could you please ensure that XYZ is an administrator
 of the project on Savannah (if there is one)?