[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...

[Sylvain Beucler]

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        04/08/24 12:43:34

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Updated list creation: Texinfo formatting, typo in config_list, and 
small draft paragraph

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.37&tr2=1.38&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.37 
administration/docs/hacking_savannah/hacking_savannah.texi:1.38
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.37     Sun Aug 
22 20:26:16 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Tue Aug 24 
12:43:34 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.37 2004/08/22 20:26:16 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.38 2004/08/24 12:43:34 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -669,36 +669,65 @@
 
 To actually create the list, run the following commands from the shell:
 
address@hidden/var/mailman/bin/newlist}
address@hidden
+$ /var/mailman/bin/newlist
address@hidden example
+
 When prompted enter the list name, the list owner email address and
 an initial pasword.  (Use common sense when choosing the password; 
 make sure it's >= 6 characters long and used at least letters and
 numbers.)
 
address@hidden /var/mailman/lists/<new-list-name>/domains}
+One fun way to 'generate' a password is to open GNU Emacs, them
+randomly type on the keyboard, and them arrange the resulting text to
+make it look like a Real Password. Moreover, you just saved the
+password and will be able to copy-paste it in the mail you'll send to
+the guy (unless Mailman does that when he notifies the list owner?
+Needs to be checked...)
+
address@hidden
+$ mkdir /var/mailman/lists/@var{new-list-name}/domains
address@hidden example
+
 Create the `domains' directory.
 
address@hidden /var/mailman/lists/<new-list-name>/domains/gnu.org}
-If the the list you are creating is for a GNU project, touch the
-file `gnu.org' in the list's `domains' subdirectory.
address@hidden
+$ touch /var/mailman/lists/@var{new-list-name}/domains/gnu.org
address@hidden example
+
+If the the list you are creating is for a GNU project, touch the file
address@hidden in the list's @file{domains} subdirectory.
+
address@hidden
+$ touch /var/mailman/lists/@var{new-list-name}/domains/nongnu.org
address@hidden example
 
address@hidden /var/mailman/lists/<new-list-name>/domains/nongnu.org}
 Otherwise, for non-GNU projects, touch the file `nongnu.org' in the
 list's `domains' subdirectory.
 
 Now it's time to configure the list:
 
address@hidden/var/mailman/bin/config_list -i ~/gnu-list-config}
address@hidden
+$ /var/mailman/bin/config_list -i ~/gnu-list-config @var{new-list-name}
address@hidden example
+
 If the list you have just created is for the GNU project.
 
address@hidden/var/mailman/bin/config_list -i ~/nongnu-list-config}
address@hidden
+$ /var/mailman/bin/config_list -i ~/nongnu-list-config @var{new-list-name}
address@hidden example
+
 If the list you have just created is for a non-GNU project.
 
 Finally, we export the new list to the mail exchangers:
 
address@hidden/mailman-export}
-This commands collects all Mailman managed list names (e.g., 
@email{savannah-hackers@@gnu.org})
-and builds a database on monty-python to be used by the mail exchangers.
address@hidden
+~/mailman-export
address@hidden example
+
+This commands collects all Mailman managed list names (e.g.,
address@hidden@@gnu.org}) and builds a database on
+monty-python to be used by the mail exchangers.
 
 And that's it.