[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...
From: |
Sylvain Beucler |
Subject: |
[Savannah-cvs] administration/docs/hacking_savannah hacking_sa... |
Date: |
Wed, 20 Apr 2005 17:29:00 -0400 |
CVSROOT: /cvsroot/administration
Module name: administration
Branch:
Changes by: Sylvain Beucler <address@hidden> 05/04/20 21:29:00
Modified files:
docs/hacking_savannah: hacking_savannah.texi
Log message:
Project approved w/o source code need to get an official agreement from
the project submitter.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.105&tr2=1.106&r1=text&r2=text
Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.105
administration/docs/hacking_savannah/hacking_savannah.texi:1.106
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.105 Fri Apr
15 21:12:08 2005
+++ administration/docs/hacking_savannah/hacking_savannah.texi Wed Apr 20
21:29:00 2005
@@ -1,5 +1,5 @@
\input texinfo @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.105 2005/04/15 21:12:08 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.106 2005/04/20 21:29:00 Beuc Exp $
@comment %**start of header
@setfilename hacking_savannah.info
@include version.texi
@@ -14,7 +14,7 @@
@indent Copyright @copyright{} 2004 Michael address@hidden
@indent Copyright @copyright{} 2004 Rudy address@hidden
@indent Copyright @copyright{} 2004 Elfyn address@hidden
address@hidden Copyright @copyright{} 2004 Mathieu Roy
address@hidden Copyright @copyright{} 2004 Mathieu address@hidden
@indent Copyright @copyright{} 2005 Richard Stallman
@quotation
@@ -3292,9 +3292,14 @@
project with a description about planned platforms and programming
languages
-Once you feel the project can be approved, you do so the usual way,
-except that you place the tracker item in the ``Approved Projects to
-be Reviewed'' category, and let it open.
+Once you feel the project can be approved, you ask the user whether he
+agrees that we will review the project in the near future (like within
+one month), and may close it if it does not comply with our hosting
+policies.
+
+Once he agrees, you activate the project the usual way, except that
+you place the tracker item in the ``Approved Projects to be Reviewed''
+category, and let it open.
@node Approval Criteria, GNU projects, Approving projects, Projects approval