[commit-womb] gnumaint Makefile howto-decommission.txt temail...

[karl]

CVSROOT:        /sources/womb
Module name:    gnumaint
Changes by:     karl <karl>     15/03/19 23:51:46

Modified files:
        .              : Makefile howto-decommission.txt 
                         temail-4post.txt 
Added files:
        .              : howto-commission.txt 

Log message:
        howto for new package

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnumaint/Makefile?cvsroot=womb&r1=1.60&r2=1.61
http://cvs.savannah.gnu.org/viewcvs/gnumaint/howto-decommission.txt?cvsroot=womb&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnumaint/temail-4post.txt?cvsroot=womb&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnumaint/howto-commission.txt?cvsroot=womb&rev=1.1

Patches:
Index: Makefile
===================================================================
RCS file: /sources/womb/gnumaint/Makefile,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -b -r1.60 -r1.61
--- Makefile    6 Feb 2015 23:11:31 -0000       1.60
+++ Makefile    19 Mar 2015 23:51:45 -0000      1.61
@@ -1,5 +1,5 @@
-# $Id: Makefile,v 1.60 2015/02/06 23:11:31 karl Exp $
-# Copyright 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014
+# $Id: Makefile,v 1.61 2015/03/19 23:51:45 karl Exp $
+# Copyright 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
 # Free Software Foundation, Inc.
 #
 # Copying and distribution of this file, with or without modification,

Index: howto-decommission.txt
===================================================================
RCS file: /sources/womb/gnumaint/howto-decommission.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- howto-decommission.txt      17 Mar 2015 17:04:58 -0000      1.1
+++ howto-decommission.txt      19 Mar 2015 23:51:46 -0000      1.2
@@ -1,4 +1,4 @@
-$Id: howto-decommission.txt,v 1.1 2015/03/17 17:04:58 karl Exp $
+$Id: howto-decommission.txt,v 1.2 2015/03/19 23:51:46 karl Exp $
     Copyright 2013, 2014, 2015 Free Software Foundation, Inc.
 
     Copying and distribution of this file, with or without modification,
@@ -14,15 +14,16 @@
   try writing mlist if there is one.
   update: package web page - takeaction.html - www.gnu.org home page
   on savannah: status=orphaned; note in summary; post job.
+  (in more detail, see fp:/gd/gnuorg/README)
 
 decommissioned:
   maintainers - activity-report.txt
-  - gnupackages.txt,pkgblurbs.txt -> oldpackages.txt
-  - directory
-  - address@hidden
+  - gnupackages.txt,pkgblurbs.txt -> oldpackages.txt;
+    then regenerate autopackage lists (see Makefile and howto-commission.txt)
+  - address@hidden ftp.gnu.org dir to old-gnu
   - lists: advertised=no, mv domains/gnu.org ...
   - project home page
-  - move to end list on software.html - webpages
+  - add to list of old packages on software.html - webpages
   - savannah: status=orphaned; note in summary.
 
 When a maintainer resigns, implicitly or explicitly, the story is

Index: temail-4post.txt
===================================================================
RCS file: /sources/womb/gnumaint/temail-4post.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- temail-4post.txt    3 Jun 2013 00:30:18 -0000       1.2
+++ temail-4post.txt    19 Mar 2015 23:51:46 -0000      1.3
@@ -1,20 +1,26 @@
-[stuff to talk to new maintainers about, right after they are appointed.]
+Sample blurbs for sending to new maintainers, to be edited as appropriate.
 
 ------------------------------------------------------------------
-[a first msg.]
-
 [check savannah; if they aren't there, get them to create an account.]
+[a first msg, right after they are appointed]
 
 I added you to the gnu-prog lists.  You should have received the welcome
 msgs just before this.
 
-Meanwhile, can you please send us a phone number / mailing address /
+Also, can you please send us a phone number / mailing address /
 alternative email, just to have as backup?  We try to collect these for
 all GNU maintainers.  Of course we won't publicize the information
 anywhere on the web.
+
+[for new packages only]
+Also, can you please write a couple of sentences describing your
+package, for use on http://www.gnu.org/manual/blurbs.html?
+
 -------------------------------------------------------------------
+[a second msg, after they reply]
 Thanks for the contact info.
 
+[for replacement maintainers only]
 Please go ahead and update any of the information at the savannah
 project and on the web pages (e.g., remove the looking-for-a-maintainer
 notice :) as needed.

Index: howto-commission.txt
===================================================================
RCS file: howto-commission.txt
diff -N howto-commission.txt
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ howto-commission.txt        19 Mar 2015 23:51:45 -0000      1.1
@@ -0,0 +1,72 @@
+$Id: howto-commission.txt,v 1.1 2015/03/19 23:51:45 karl Exp $
+    Copyright 2015 Free Software Foundation, Inc.
+
+    Copying and distribution of this file, with or without modification,
+    are permitted in any medium without royalty provided the copyright
+    notice and this notice are preserved.
+
+Notes on what an "assistant GNUisance" needs to do when a new package is
+officially dubbed.  Only rms can dub a new package; he sends mail to
address@hidden (which all and only such assistants should be on), and
+other recipients.
+
+When a replacement or co-maintainer for an existing package is dubbed,
+most of the below is unnecessary: just add the person to
+gnu-prog[-discuss] (item 1), and to the maintainers file (item 4), and
+send them the post-dubbing message (item 10).
+
+1. Add the new maintainer to gnu-prog and gnu-prog-discuss right away,
+as stated at the end of the dubbing message.
+https://lists.gnu.org/mailman/admin/gnu-prog/members/add
+https://lists.gnu.org/mailman/admin/gnu-prog-discuss/members/add
+
+2. Sometimes the package identifier is not completely clear from rms's
+message, especially if it has not gone through the normal evaluation
+process.  The identifier should be all lowercase (no exceptions!), no
+spaces, not start with "gnu" unless there is good reason for it, and be
+reasonably descriptive and unique in the universe of free software (at
+least).  The identifier is the common key linking the package in many
+disparate places, so it is worth a little time and discussion with the
+new maintainer if need be to make it good.  rms does not generally need
+to be involved in that detail.
+
+3. A package can have a "mundane name" that includes spaces, capitals,
+etc.  Sometimes that dispels fears the new maintainer might have.
+
+4. Once the package identifier is settled, things can proceed.  Add the
+new maintainer to /gd/gnuorg/maintainers, with the new package name.
+See /gd/gnuorg/README for editing specifics.  Update activity-report.txt
+at the same time, as described in that README.
+
+5. In womb/gnumaint, add the entry to gnupackages.txt.  The only entries
+likely to require some thought are the doc-category and doc-summary.
+It can always be fixed later, but usually isn't, so it's worth thinking
+about.  Whatever else, do not commit a placeholder or other fake
+entries, since it will get propagated to www.gnu.org below.  The doc-url
+will typically be "none" for a new package.
+
+6. Also in womb/gnumaint, add an entry to pkgblurbs.txt.  Here it can be
+a two-line placeholder:
+ package: newpkgid
+ blurb: null (newpkg/YYYYMMDD)
+We'll ask the new maintainer for a blurb in the post email, below.
+
+7. Items 5 and 6 should be done right away, as otherwise consistency
+checks will start to fail (as soon as /gd/gnuorg/maintainers is
+updated).  Commit these changes.
+
+8. Regenerate the allgnupkgs.html et al. web page includes here:
+  make html-update # writes into www checkout at ${gw}
+  make html-diff   # cvs diff of the generated files
+  cd $gw && cvs commit ...
+It's important to do the diff and actually look at the output, to ensure
+both that the files have not been hand-edited on the www side, and that
+the generation actually did what is expected.
+
+9. The savannah people should ensure that the new package is marked gnu,
+if it already exists on savannah, or accept it.  And for
+replacement/co-maintainers, they should ensure that the new person is
+made an admin of the package, if it exists.
+
+10. Send the post-appointment email from the template temail-4post.txt,
+suitably edited.