[Savannah-cvs] administration/docs/hacking_savannah AUTHORS ha...

[Sylvain Beucler]

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

Modified files:
        docs/hacking_savannah: AUTHORS hacking_savannah.texi 

Log message:
        Added description of the current projects approvals situation

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/AUTHORS.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.20&tr2=1.21&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/AUTHORS
diff -u administration/docs/hacking_savannah/AUTHORS:1.2 
administration/docs/hacking_savannah/AUTHORS:1.3
--- administration/docs/hacking_savannah/AUTHORS:1.2    Mon Aug  2 21:24:02 2004
+++ administration/docs/hacking_savannah/AUTHORS        Thu Aug 12 18:18:47 2004
@@ -7,4 +7,4 @@
 Michael J. Flickinger added section on web servers, updated project
 approval section, and added section on IRC.
 
-Elfyn McBratney currently fixed typos.
+Elfyn McBratney currently fixed typos and wrote the Mailman chapter.
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.20 
administration/docs/hacking_savannah/hacking_savannah.texi:1.21
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.20     Thu Aug 
12 11:43:44 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Thu Aug 12 
18:18:47 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.20 2004/08/12 11:43:44 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.21 2004/08/12 18:18:47 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -83,17 +83,21 @@
 
 @section Savannah.gnu.org
 
address@hidden
address@hidden,
address@hidden
address@hidden
address@hidden,
address@hidden 
address@hidden
address@hidden @columnfractions .33 .33 .33
address@hidden @uref{savannah.gnu.org}
address@hidden @uref{savannah.nongnu.org}
address@hidden @uref{sv.gnu.org}
address@hidden @uref{sv.nongnu.org}
address@hidden @uref{www.nongnu.org}
address@hidden @uref{freesoftware.fsf.org} 
address@hidden @tab @uref{www.freesoftware.fsf.org}
address@hidden multitable
 
 It is a SF.net-like development platform aimed at promoting free
 software and educating developers about freedom.
 
+[TODO: complete this section]
+
 @section This manual
 
 The present documentation aims at teaching new volunteers how to
@@ -103,8 +107,8 @@
 It covers:
 @itemize
 @item the inner workings of Savannah.gnu.org (including how to make a test 
installation)
address@hidden provide reference on how to maintain it efficiently.
address@hidden It also describes the various policies we follow.
address@hidden reference on how to maintain it efficiently.
address@hidden the various policies we follow.
 @item and it needs being cleaned up, indeed
 @end itemize
 
@@ -130,37 +134,46 @@
 Also read Savannah's FAQ.
 
 
address@hidden savannah-hackers
address@hidden savannah-hackers@@gnu.org
 
 Savannah hackers is a group of volunteers.
 
 Every Savannah hacker is subscribed to the savannah-hackers mailing
-list: @uref{http://mail.gnu.org/mailman/listinfo/savannah-hackers}
+list: @uref{http://lists.gnu.org/mailman/listinfo/savannah-hackers}
 
-This list is public, and subscription is moderated (though I don't
-really now why).
+This list is public.
 
-The @email{savannah-hackers@@gnu.org} address is placed at various places at
-Savannah and receives user requests, as well as notifications from
-group administration's trackers. You should Cc: all support requests
-you are dealing with to this list.
+The @email{savannah-hackers@@gnu.org} address is placed at various
+places at Savannah and receives user requests. It also receives
+notifications from group administration's trackers, project approvals,
+and various alerts, such as when a user tries to change his
+password. You should Cc: all support requests you are dealing with to
+this list, for archival purposes, and to inform the other hackers of
+your work.
 
 Discussions concerning Savannah also takes place here. If you need to
-talk about security-related stuff, it may be better to use the private
+talk about security-related stuff, it is be better to use the private
 list savannah-root first.
 
 Note that the FSF system administrators are not subscribed to this
 list, abeilt they sometimes read its contents.
 
-Try to reply to users as soon as possible. ;-)
+Try to reply to users as soon as possible. Usually, requests get a
+reply whthing 24 hours. Our responsiveness is part of what makes
+Savannah a good development platform.
+
 
address@hidden savannah-root@@gnu.org
 
address@hidden savannah-root
address@hidden://lists.gnu.org/mailman/listinfo/savannah-root}
 
-This mailing-list is private and allows to discuss non-public
-matters. Savannah hackers are also subscribed to this list. RMS talks
-to the Savannah hackers using it. The FSF system administrators
-receive mail sent to this list.
+This mailing-list is private.
+
+It allows to discuss non-public matters, such as security related
+issues, and management discussions where RMS takes part. Savannah
+hackers are also subscribed to this list. RMS most often talks to the
+Savannah hackers using it. The FSF system administrators receive mail
+sent to this list.
 
 Archives are managed using Mailman and are accessible to list members.
 
@@ -382,6 +395,8 @@
 #   mysql> grant select,update on foodb.* to address@hidden identified by 
'baz';
 @end verbatim
 
+
+
 @node Mailman Administration, Some Savannah tasks, MySQL, Top
 @chapter Mailman Administration
 
@@ -441,9 +456,11 @@
 list's `domains' subdirectory.
 
 
+
 @node Some Savannah tasks, Frequent support requests, Mailman Administration, 
Top
 @chapter Some Savannah tasks
 
+
 @section Adding a Frequently Asked Question
 
 First, all site-specific content in the savannah project under module
@@ -463,6 +480,7 @@
 even make you test your changes in your test installation before to
 commit :)
 
+
 @section Manually setting up commit e-mail notification
 
 The infra/ module of the 'savannah' project contains install-log-accum.
@@ -484,6 +502,7 @@
 Currently, the script does not support updating a configuration,
 you'll have to do that by hand.
 
+
 @section Updating the menu:
 
 Check /savannah/etc/gnu-content/menu.txt and
@@ -499,6 +518,7 @@
 provide a generic way to do so in Savane.
 
 
+
 @node Frequent support requests, Some quirks, Some Savannah tasks, Top
 @chapter Frequent support requests
 
@@ -624,7 +644,6 @@
 to forge a whole website and domain name to get this Savannah account.
 
 
-
 @section Unexpected Savannah password change notifications
 
 What should we do when the user reports a password change that was not
@@ -653,6 +672,7 @@
 Even without the discard modification possibility, it is important
 that the user check whether his account have been untouched.
 
+
 @section Moving from non-GNU to GNU
 
 @verbatim
@@ -680,6 +700,7 @@
 http://www.gnu.org/prep/maintain_21.html#SEC21)
 @end verbatim
 
+
 @section Removing a project group
 
 @subsection Policies
@@ -724,6 +745,7 @@
 @item as well as /savannah/cvs-backup/<group>-sources.tar.gz
 @end itemize
 
+
 @section Deleting a user account
 
 @enumerate
@@ -732,6 +754,7 @@
 @item @code{DELETE FROM user WHERE user_id=uid;}
 @end enumerate
 
+
 @section Renaming a project group
 
 @code{update groups set unix_group_name="<newname>" where
@@ -804,6 +827,7 @@
 You could also change the projects CVS files to change the user name
 associated with each change. Is there a cvs command to do that?
 
+
 @section Impersonating somebody
 
 Change the savannah password using MySQL.
@@ -881,16 +905,71 @@
 M php/include/sendmail.php // Modified to use SMTP by address@hidden
 @end verbatim
 
+Elfyn plans to make a temporary patchset and upgrade to Savane, Really Soon 
(tm).
+
+
 @node Projects approval, Terminology, Some quirks, Top
 @chapter Projects approval
 
address@hidden Project Approval
address@hidden The current situation
+
+Currently, project approvals are underway.
+
+For eight months, projects approvals was not possible for various reasons, 
including, in no particular order:
address@hidden @minus
address@hidden a complete staff change, replaced by people not knowing well of 
Savannah at first
address@hidden internal debates leading to repeated bloated discussions
address@hidden the need to still maintain Savannah and the about 2000 current 
projects
address@hidden the need to reply to user support requests, especially after all 
the post-crack changes
address@hidden the need to audit some parts of Savannah and have them work in 
the new secure infrastructure
address@hidden itemize
+
+Several of the issues were solved, allowing the Savannah Hackers to
+start reviewing projects again.
+
+However, there is now a backlog of more than 500 projects to review,
+which is a very long process. Usually one Savannah hacker writes an average of
+4 e-mails related to project approvals per day, and a project usually
+requires several mail exchanges to be completely processed. And of
+course, several new submissions are sent each day.
+
+Most of the old project registrations are irrelevant now. However,
+some people waited for all that time, or wish to move their project
+from another location back to Savannah.
+
+We first sent an announcement to all users who registered a project
+not yet reviewed, asking for people not interested anymore to warn
+us. We also planned to remove old unconfirmed project registrations
+after one month. This was a small mistake, because after one month, we
+would not be able to differentiate between a project still
+interested in being hosted, and an unconfirmed project probably hosted
+somewhere else or dead.
+
+We got confirmations to approve projects, though, so we could start
+working. We also started processing the recent requests, that need not
+confirmation.
+
+As soon as we finish processing this two categories of registrations,
+we plan to send another e-mail soon asking for everyone to confirm the
+status of their hosting request. The one-month limit also proved too
+optimistic, and will be delayed.
+
+
address@hidden Keeping each other in sync
+
+We are using the channel #savannah on @uref{irc.freenode.net} to
+coordinate this effort.
+
+Aside from IRC, we are also using a list to keep track of projects,
+that can be checked out using:
address@hidden -d:ext:@var{yourlogin}@@savannah.gnu.org:/cvsroot/administration 
co administration/lists/pending_projects_to_keep.txt}.
+
+You can also see it online at
address@hidden://savannah.gnu.org/@/cgi-bin/@/viewcvs/@/administration/@/administration/@/lists/@/pending_projects_to_keep.txt@/?rev=HEAD&content-type=text/vnd.viewcvs-markup}.
+
+The file is auto-documented. Submissions labelled ``Confirmed and
+Pending'' should be reviewed in priority.
 
-Currently, project approvals are underway.  We are using the channel
-#savannah on irc.freenode.net to coordinate this effort.  Aside from IRC, 
-we are also using a list to keep track of projects.  The list file, 
-''pending_projects_to_keep.txt'', may be found in the ''lists'' directory
- of the administration project's ''administration'' module.
 
 @section Rudy's Little Howto