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

[Sylvain Beucler]

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        04/10/08 21:51:40

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Adding section about new volunteers for project approvals

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

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.56 
administration/docs/hacking_savannah/hacking_savannah.texi:1.57
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.56     Thu Oct 
 7 20:08:58 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Fri Oct  8 
21:51:38 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.56 2004/10/07 20:08:58 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.57 2004/10/08 21:51:38 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -1874,6 +1874,7 @@
 * GNU projects::                
 * Rudy's Little HOWTO::         
 * Mathieu's Little HOWTO::      
+* New volunteers::              
 @end menu
 
 @node Prerequisites, Approving projects, Projects approval, Projects approval
@@ -2468,7 +2469,7 @@
 @end verbatim
 
 
address@hidden Mathieu's Little HOWTO,  , Rudy's Little HOWTO, Projects approval
address@hidden Mathieu's Little HOWTO, New volunteers, Rudy's Little HOWTO, 
Projects approval
 @section Mathieu's Little HOWTO
 
 This HOWTO is being merged within the chapter.
@@ -2547,6 +2548,49 @@
 @end verbatim
 
 
address@hidden New volunteers,  , Mathieu's Little HOWTO, Projects approval
address@hidden New volunteers
+
+When a volunteer is willing to help with project approvals, we usually
+ask him to read this chapter.
+
+Then, we give him access to the Savannah 'administration' group, so he
+has access to @file{administration/lists/} in the CVS repository. He
+also has access to the other modules, but there is no real danger:
+each commit is logged thanks to commit_prep&log_accum, and changes
+have to be manually updated at Savannah to be taken into account.
+
+Being able to edit @file{pending_projects_to_keep.txt}, the volunteer
+can pick up projects to review. Once a project is reviewed, instead of
+sending it directly, he first send it to a ``veteran'' Savannah
+hackers. This will make double-work for those veteran in a first step,
+but it is worth the effort. Projects also have to be activated by the
+admins (that's a requirement from Savane). Once everybody feels
+confident in the volunteers skills (including himself), so usually
+when there are no more error or omissions in the project reviews, we
+grant him administrator privilege on project @file{administration}, so
+he can approve the project himself. Then, we trust him to do his job
+right, and he's a full now a real Savannah hacker, working on project
+submissions.
+
+Note to new volunteers:
+
+Savannah is a website with users, and we need to be very reactive. So,
+if your timetable ever change, please notify
address@hidden If you suddently do not have time for
+Savannah, nobody will blame you; however, please don't be
+silent. Moreover, people often forget to add address@hidden
+in carbon copy of their reply, so we do not even know if people
+answered your reviews.
+
+Even a small among of work, like 30-60mn per day, does help. We just
+need a regular work, so that pending submitters are not waiting for
+more than a week before to get a reply.
+
+So, please keep us informed about your current timetable, and if you
+do not have time, also send us the status of your project approvals,
+so we can take care of them.
+
 
 
 @node Terminology, Thanks to..., Projects approval, Top