[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/14 17:01:44

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Various fixes

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

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.27 
administration/docs/hacking_savannah/hacking_savannah.texi:1.28
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.27     Sat Aug 
14 14:21:22 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Sat Aug 14 
17:01:44 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.27 2004/08/14 14:21:22 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.28 2004/08/14 17:01:44 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -63,18 +63,18 @@
 @end ifnottex
 
 @menu
-* Introduction::                About this manual
-* Communication::               Getting in sync with the Savannah Team
-* Savannah configuration::      Savannah configuration in-depth description
-* MySQL::                       Basic tips on using MySQL
-* Mailman Administration::      Mailman command line tips
-* Some Savannah tasks::         Frequent administration tasks
-* Frequent support requests::   How to answer common support requests
-* Some quirks::                 To clear up sooner or later
-* Projects approval::           Savannah policies and HOWTO
-* Terminology::                 Precise wording
-* Copying This Manual::         How to make copies of this manual
-* Indices::                     Concept index
+* Introduction::                About this manual.
+* Communication::               Getting in sync with the Savannah Team.
+* Savannah configuration::      Savannah configuration in-depth description.
+* MySQL::                       Basic tips on using MySQL.
+* Mailman Administration::      Mailman command line tips.
+* Some Savannah tasks::         Frequent administration tasks.
+* Frequent support requests::   How to answer common support requests.
+* Some quirks::                 To clear up sooner or later.
+* Projects approval::           Savannah policies and HOWTO.
+* Terminology::                 Precise wording.
+* Copying This Manual::         The GNU Free Documentation License.
+* Indices::                     A menu covering many topics.
 @end menu
 
 
@@ -159,7 +159,7 @@
 @end menu
 
 @node savannah-hackers, savannah-root, Mailing lists, Mailing lists
address@hidden @email{savannah-hackers@@gnu.org}
address@hidden savannah-hackers@@gnu.org
 
 Savannah hackers is a group of volunteers.
 
@@ -189,7 +189,7 @@
 
 
 @node savannah-root, sysadmin, savannah-hackers, Mailing lists
address@hidden @email{savannah-root@@gnu.org}
address@hidden savannah-root@@gnu.org
 
 @uref{http://lists.gnu.org/mailman/listinfo/savannah-root}
 
@@ -205,11 +205,11 @@
 
 
 @node sysadmin,  , savannah-root, Mailing lists
address@hidden @email{sysadmin@@gnu.org}
address@hidden sysadmin@@gnu.org
 
-This sends a message to Paul Fisher (rao) and James E. Blair (corvus),
-who are employees of the FSF working as Sysadmins. It is managed via
-RT (Request Tracker).
+This sends a message to Paul Fisher (@email{rao@@gnu.org}) and James
+E. Blair (@email{corvus@@gnu.org}), who are employees of the FSF
+working as Sysadmins. It is managed via RT (Request Tracker).
 
 Sysadmins are well known for not being consistent in e-mail exchanges,
 hence the following policy:
@@ -223,21 +223,26 @@
 @end quotation
 says Rudy.
 
+Also, they often reply directly to you, ignoring any people in Cc:. If
+it is the case, do not forget to forward their reply to
address@hidden@@gnu.org}, and to tell them not to forget
+again to do so.
+
 
 @node IRC,  , Mailing lists, Communication
 @section IRC
 
-Currently, we have a channel, #savannah, on irc.freenode.net for discussion 
-on Savannah.  The channel is used for slight discussion and it also allows for
-easier administration of Savannah.  The channel allows us to not tread on
-anyone elses toes, by providing us with real-time communication.  This makes
-handling project approvals and support requests easier.
-
-IRC is not, by any means, a substitute for the mailing list.  While slight
-decisions may be agreed upon in IRC, the mailing list is where all important,
-policy-related and administrative decisions are made.
+Currently, we have a channel, #savannah, on @uref{irc.freenode.net}
+for discussion on Savannah.  The channel is used for slight discussion
+and it also allows for easier administration of Savannah.  The channel
+allows us to not tread on anyone elses toes, by providing us with
+real-time communication. This makes handling project approvals and
+support requests easier.
+
+IRC is not, by any means, a substitute for the mailing list. While
+slight decisions may be agreed upon in IRC, the mailing list is where
+all important, policy-related and administrative decisions are made.
 
-(mjflick)
 
 @node Savannah configuration, MySQL, Communication, Top
 @chapter Savannah configuration
@@ -247,7 +252,6 @@
 
 It is still incomplete.
 
-
 @menu
 * Some technical information::  
 * Here is how I made [am making] a Savannah test install on my faithful 
PI-133::  
@@ -542,12 +546,13 @@
 @node Manually setting up commit e-mail notification, Updating the menu, 
Adding a Frequently Asked Question, Some Savannah tasks
 @section Manually setting up commit e-mail notification
 
-The infra/ module of the 'savannah' project contains install-log-accum.
+The infra/ module of the @file{administration} project contains
address@hidden
 
 Here is a simple launch, so you see what is done:
 
address@hidden
-# ./install-log-accum.pl -v testytest address@hidden
address@hidden
+# ./install-log-accum.pl -v testytest beuc@@beuc.net
 Installing program `cat' in `/savannah/cvsroot/testytest/bin'
 Installing program `commit_prep' in `/savannah/cvsroot/testytest/bin'
 Installing program `log_accum' in `/savannah/cvsroot/testytest/bin'
@@ -556,7 +561,7 @@
 Creating directory `/savannah/cvsroot/testytest/var/run/log_accum'
 Writing commitinfo file 
`/savannah/cvsroot/testytest/cvsroot/testytest/CVSROOT/commitinfo'
 Writing loginfo file 
`/savannah/cvsroot/testytest/cvsroot/testytest/CVSROOT/loginfo'
address@hidden verbatim
address@hidden example
 
 Currently, the script does not support updating a configuration,
 you'll have to do that by hand.
@@ -565,17 +570,17 @@
 @node Updating the menu,  , Manually setting up commit e-mail notification, 
Some Savannah tasks
 @section Updating the menu
 
-Check /savannah/etc/gnu-content/menu.txt and
-/savannah/etc/nongnu-content/menu.txt. There are also other menu*.txt
-for localization.
+Check @file{/savannah/etc/gnu-content/menu.txt} and
address@hidden/savannah/etc/nongnu-content/menu.txt}. There are also other
address@hidden for localization.
 
 The ``Cryptographic software legal notice'' link is required in the USA.
 Check 
@uref{http://lists.gnu.org/archive/html/savannah-hackers/2004-06/msg00086.html}
 
 Some parts of the menu are hardcoded in
-/frontend/php/include/menu.php. If you need to modify those, try to
-find a way to do so that will not break future Savane update, ie
-provide a generic way to do so in Savane.
address@hidden/frontend/php/include/menu.php}. If you need to modify those,
+try to find a way to do so that will not break future Savane update,
+ie provide a generic way to do so in Savane.
 
 
 
@@ -588,6 +593,7 @@
 
 @menu
 * Manually change an e-mail ::  
+* Actually doing it::           
 * Unexpected Savannah password change notifications::  
 * Moving from non-GNU to GNU::  
 * Removing a project group::    
@@ -597,53 +603,67 @@
 * Impersonating somebody::      
 @end menu
 
address@hidden Manually change an e-mail , Unexpected Savannah password change 
notifications, Frequent support requests, Frequent support requests
address@hidden Manually change an e-mail , Actually doing it, Frequent support 
requests, Frequent support requests
 @section Manually change an e-mail 
 
address@hidden
+* Policy::                      
address@hidden menu
+
address@hidden Policy,  , Manually change an e-mail , Manually change an e-mail
address@hidden Policy
+
 Bradley Kuhn says:
 @quotation
 I suggest that we follow this procedure:
 
-   * Send a message to the address on file, and see if it bounces.  If it
-     doesn't bounce, then we must ask the original user why, and decide
-     what to do on a case by case basis.  We should be EXTREMELY reluctant
-     -- if not outright REFUSE -- to change an email address if the one on
-     file does not bounce.
-
-   * If the mail does bounce, we should ask the user if they can produce
-     any evidence that they once had that email address.  The best
-     evidence would be a GPG-signed message that is signed with a key that
-     has both their old and new email address on it, and that the GPG key
-     be available from a well-known public keyserver.  While this could be
-     forged, it would be substantial work to do so and could easily get
-     discovered.
-
-     (Note, this is why I say the key much be on a public keyserver.  Even
-      if they forge the key to refer to email addresses they don't control
-      (i.e., generate a key that includes bogus info), putting on a public
-      key server could likely flag the real owner of the email address.)
-
-
-   * If they cannot use the GPG solution, I suppose we should accept any
-     plausible explanation for why their old email address is bouncing
-     (e.g., changed ISP).  If someone truly wants to social engineer their
-     way into commit access on a project, they can likely do it.  We
-     can't beat it; we can just make it some effort to succeed in such
-     social engineering.
-
address@hidden
address@hidden
+Send a message to the address on file, and see if it bounces.  If it
+doesn't bounce, then we must ask the original user why, and decide
+what to do on a case by case basis.  We should be EXTREMELY reluctant
+-- if not outright REFUSE -- to change an email address if the one on
+file does not bounce.
+
address@hidden
+If the mail does bounce, we should ask the user if they can produce
+any evidence that they once had that email address.  The best evidence
+would be a GPG-signed message that is signed with a key that has both
+their old and new email address on it, and that the GPG key be
+available from a well-known public keyserver.  While this could be
+forged, it would be substantial work to do so and could easily get
+discovered.
+
+(Note, this is why I say the key much be on a public keyserver.  Even
+if they forge the key to refer to email addresses they don't control
+(i.e., generate a key that includes bogus info), putting on a public
+key server could likely flag the real owner of the email address.)
+
address@hidden
+If they cannot use the GPG solution, I suppose we should accept any
+plausible explanation for why their old email address is bouncing
+(e.g., changed ISP).  If someone truly wants to social engineer their
+way into commit access on a project, they can likely do it.  We can't
+beat it; we can just make it some effort to succeed in such social
+engineering.
address@hidden itemize
 
-Do any savannah-hackers object to this procedure?  If not, then please go
-ahead with it.
+Do any savannah-hackers object to this procedure?  If not, then please
+go ahead with it.
 @end quotation
 
-rudy+sylvain:
address@hidden
-mysql -u root -p savannah
+
address@hidden Actually doing it, Unexpected Savannah password change 
notifications, Manually change an e-mail , Frequent support requests
address@hidden Actually doing it
+
+
address@hidden -u root -p savannah}
+
 [mysql.txt contains the password]
-update user set email="new e-mail" where user_name = "username" and 
user_id=uid;
-Double checking the user_name and user_id is good for security :)
address@hidden verbatim
 
address@hidden user set email="new e-mail" where user_name = "username" and 
user_id=uid;}
+
+Double checking the user_name and user_id is good for security :)
 
 
 sylvain:
@@ -692,7 +712,7 @@
 * Examples::                    
 @end menu
 
address@hidden Examples,  , Manually change an e-mail , Manually change an 
e-mail
address@hidden Examples,  , Actually doing it, Actually doing it
 @subsection Examples
 
 For the record, he is an appraisal of X's reply:
@@ -721,7 +741,7 @@
 to forge a whole website and domain name to get this Savannah account.
 
 
address@hidden Unexpected Savannah password change notifications, Moving from 
non-GNU to GNU, Manually change an e-mail , Frequent support requests
address@hidden Unexpected Savannah password change notifications, Moving from 
non-GNU to GNU, Actually doing it, Frequent support requests
 @section Unexpected Savannah password change notifications
 
 What should we do when the user reports a password change that was not
@@ -785,10 +805,10 @@
 
 @menu
 * Policies::                    
-* Actually doing it::           
+* Doing it::                    
 @end menu
 
address@hidden Policies, Actually doing it, Removing a project group, Removing 
a project group
address@hidden Policies, Doing it, Removing a project group, Removing a project 
group
 @subsection Policies
 
 If the request is because the project is hosted elsewhere, keeping it
@@ -809,8 +829,8 @@
 -- 
 Mathieu Roy
 
address@hidden Actually doing it,  , Policies, Removing a project group
address@hidden Actually doing it
address@hidden Doing it,  , Policies, Removing a project group
address@hidden Doing it
 
 Steps to remove a project:
 @itemize @bullet
@@ -1214,7 +1234,7 @@
 
 
 @node Approval Policies, GNU projects, Overview of the approval process, 
Projects approval
address@hidden Approval Policies
address@hidden Approval Requirements
 
 Savannah does not host all kinds of software, and not even all kinds
 of free software.
@@ -1236,6 +1256,9 @@
 @node Program License, Dependencies, Approval Policies, Approval Policies
 @subsection Program License
 
+[savannah.el: sv-problem-license-gplincompatible,
+sv-problem-license-mpl-alike, sv-problem-gpl-two-only]
+
 Savannah only hosts code that is compatible with the GNU General
 Public License (GPL). The idea is that users can be sure that they can
 use and mix any packages found in Savannah.
@@ -1312,16 +1335,17 @@
 @node Java, .Net, Perl and the Dual GPL&Artistic License, Dependencies
 @subsubsection Java
 
-[savannah.el: sv-problem-java]
+[savannah.el: sv-problem-java, sv-reject-java-nonfree]
 
 Java is a non-free dependency that a lot of people use, even when
-writing free software. It is very similar to using Qt, when Qt was
-non-free (it is released under the GPL now).
+writing free software. It is an important issue, very similar to using
+Qt, when Qt was non-free (it is released under the GPL now).
 
-Unlike TrollTech, Sun is not willing to release Java under a free
-license for now. However, there is now a Java compiler in GCC, GCJ
-(GNU Compiler for Java), as well as a Java bycode interpreter, GIJ
-(GNU Interpreter for Java). The Kaffe JVM (Java Virtual Machine) is
+Unlike TrollTech (Qt's copyright holder), Sun is not willing to
+release Java under a free license for now. However, there is now a
+free Java compiler in GCC, @acronym{GCJ} (@dfn{GNU Compiler for
+Java}), as well as a Java bycode interpreter, @acronym{GIJ} (@dfn{GNU
+Interpreter for Java}). The Kaffe JVM (Java Virtual Machine) is
 another free JVM. The GNU Classpath project aims at writing a free
 replacement for the Java API, and GNU Classpathx is doing the same for
 commonly used libraries. These projects are not complete - mainly,
@@ -1333,26 +1357,47 @@
 environment. People at GNU Classpath may want to help project
 submitters to make their project work that way [NEEDS CONFIRMATION].
 
+You need to make the user aware of that issue. Usually, you will have
+to ask him whether his project can be run using a free Java
+environment, and if needed, point him to the GNU Java software page.
+
+Sometimes, the user will argue that he's using the Java API and free
+software Java libraries only, avoiding sun.* internal classes and
+non-free libraries. This is not enough, since there is not a free
+implementation of the whole Java API. The user user do have to test
+his application using a free Java platform, and make it run under
+it. If the user is not willing to accept this constraint, then we
+cannot approve his project.
+
+
 @node .Net,  , Java, Dependencies
 @subsubsection .Net
 
-.Net as a dependency has similar issues to Java. You have to make sure
-the program can be run under a free implementation of .Net, such as
-DotGNU or Mono.
+.Net as a dependency is a similar issue to Java (@pxref{Java}). You
+have to make sure the program can be run under a free implementation
+of .Net, such as DotGNU or Mono.
 
 [TODO: add links]
 
 @node Legal Notices, Kind of software, Dependencies, Approval Policies
 @subsection Legal Notices
 
+[savannah.el: sv-problem-gpl-info, sv-problem-lgpl-info,
+sv-problem-fsf-address, sv-problem-license-truncated]
+
 We require that all non-trivial files in a project contain a copyright
-notice and a license notice. This process is described is
-``Information For Maintainers of GNU Software'' @pxref{Top,,,standards}; see
+notice and a license notice (@pxref{Top,,,maintain, Information For
+Maintainers of GNU Software}).
+
+Especially,
 @uref{http://www.gnu.org/@/prep/@/maintain_8.html} and
 @uref{http://www.gnu.org/@/prep/@/maintain_9.html}.
 
 [TODO: make appropriate xref call, with links to Info sections]
 
+The main reason is that we want to avoid legal issues, and take
+Copyright (and Copyleft) seriously.
+
 Here are some steps to perform when checking the notices:
 @itemize
 @item Check the presence of the copyright notice in the top of the file
@@ -1363,6 +1408,8 @@
 @item If is is the GPL, be sure that it mentions 'version 2 or later'. We do 
not accept version 2 only.
 @end itemize
 
+In addition, a full copy of the license should be added to the
+package, preferably in a file named @file{COPYING}.
 
 @node Kind of software, Words to avoid, Legal Notices, Approval Policies
 @subsection Kind of software
@@ -1471,10 +1518,6 @@
 @section Rudy's Little HOWTO
 
 @verbatim
-
-To delete a project type the following as root on savannah:
-
-
 We have an emacs .el file for this, when using m-x sv_register_discad
 it asks for projectname and reason and pasts the command above in the
 buffer.  I start emacs locally, execute m-x eshell, and then ssh to