[Savannah-cvs] administration/docs/hacking_savannah TODO

[Sylvain Beucler]

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

Modified files:
        docs/hacking_savannah: TODO 

Log message:
        *** empty log message ***

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

Patches:
Index: administration/docs/hacking_savannah/TODO
diff -u administration/docs/hacking_savannah/TODO:1.2 
administration/docs/hacking_savannah/TODO:1.3
--- administration/docs/hacking_savannah/TODO:1.2       Tue Nov 16 23:57:36 2004
+++ administration/docs/hacking_savannah/TODO   Wed Dec  8 23:36:26 2004
@@ -21,3 +21,44 @@
 [...]
 <asubedi> so the 'ping' is just a reminder to the submitter?
 <Beuc> yes, just in case he forgot, or in case we did'nt get a mail, before to 
definitely close the submission
+
+Approving projects:
+1) It is quite easy actually, you go to the pending page, you click on
+"Manage/Edit Project Registration", then you witch the status from
+"pending" to "active", clikc update, and then you click on the "Send
+New Project Instruction Email" link
+
+
+ When mjflick is coming over, I'll ask him about giving you a read-only access 
to Savannah.
+<Beuc> You will be able to study how Savannah works inside, and troubleshot 
some requests
+<zeus> ok
+
+<Beuc> What would be good is also giving you access to create mailing-lists.
+<zeus> Beuc: Where I can found the ruls to create a mailing-list ?
+<Beuc> the 'rules' are in the Savane code..
+<Beuc> nongnu-> address@hidden or address@hidden
+<zeus> Beuc: we just create the #nongnu.org mailing-list right ?
+<Beuc> gnu -> address@hidden or address@hidden or address@hidden or 
address@hidden or... let me check, there's one left
+<Beuc> oh yeah, address@hidden
+<Beuc> so, we also create @gnu.org
+
+
+
+
+    What is our (Savannah's) policy regarding the inclusion of trademark
+    logo images in the source code distribution of a project licensed
+    under GNU GPL? Specifically, I have a project at hand which allows the
+    distribution of trademark logos in the following terms:   
+
+It is no problem if the program contains trademarked images and names,
+provided the trademark usage and requirements don't make it difficult
+in practice to change the program and publish a modified
+version.  In other words, it has to be easy to find and remove the
+trademarks, if and when the trademark conditions require this.
+
+        Please note, all images showing "aroundme" or "barnraiser" logos are
+        a trademark  of Barnraiser. You can distribute them under the terms
+        of the copy license, however you are forbidden to alter them.
+
+This poses no problem at all, since they don't say you have to remove
+the trademarks under any condition.