[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 20:05:59

Modified files:
        docs/hacking_savannah: AUTHORS hacking_savannah.texi 

Log message:
        Added new material on the approval process

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

Patches:
Index: administration/docs/hacking_savannah/AUTHORS
diff -u administration/docs/hacking_savannah/AUTHORS:1.3 
administration/docs/hacking_savannah/AUTHORS:1.4
--- administration/docs/hacking_savannah/AUTHORS:1.3    Thu Aug 12 18:18:47 2004
+++ administration/docs/hacking_savannah/AUTHORS        Thu Aug 12 20:05:58 2004
@@ -1,10 +1,10 @@
 Records of which significant portions were written by whom:
 
-Sylvain Beucler <address@hidden> packed up most of the documentation
-from various private or public emails (posters mentioned in the , and from his 
experience in
-hacking Savannah.
+Sylvain Beucler <address@hidden> wrote and packed up most of the
+documentation from various private or public emails (posters mentioned
+in the documentation), and from his experience in hacking Savannah.
 
-Michael J. Flickinger added section on web servers, updated project
-approval section, and added section on IRC.
+Michael J. Flickinger wrote the web servers section, contributed to
+the project approval section, and added the IRC section.
 
 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.22 
administration/docs/hacking_savannah/hacking_savannah.texi:1.23
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.22     Thu Aug 
12 18:59:46 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Thu Aug 12 
20:05:58 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.22 2004/08/12 18:59:46 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.23 2004/08/12 20:05:58 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -908,6 +908,37 @@
 Elfyn plans to make a temporary patchset and upgrade to Savane, Really Soon 
(tm).
 
 
address@hidden Web Server Syndication
+
+Content for pages on www.gnu.org and www.nongnu.org is controlled by
+Savannah's respective project webcvs repositories.  Both www.gnu.org 
+and www.nongnu.org are syndicated to reflect the changes to Savannah's 
+webcvs repositories.
+
+Upon project approval, syndication does not begin automatically.
+Since the FSF will not allow Savannah hackers shell access to GNU's 
+main webserver, for understandable security concerns, there is a URL 
+we must use to enable project web syndication, for both GNU and non-GNU 
+projects.
+
+The URL is: @uref{http://www.gnu.org/new-savannah-project/new.py}
+
+It takes two arguments, ''type'' and ''project''.
+
+For ''type'', you choose whether the project is ''gnu'' or ''non-gnu''.
+
+For ''project'', you enter the name of the respective project.
+
address@hidden
+
+Example usage, with curl:
+
+curl http://www.gnu.org/new-savannah-project/new.py -F type=non-gnu -F 
project=fkt
address@hidden verbatim
+
+(mjflick)
+
+
 @node Projects approval, Terminology, Some quirks, Top
 @chapter Projects approval
 
@@ -971,6 +1002,141 @@
 Pending'' should be reviewed in priority.
 
 
address@hidden Approval Policies
+
+Savannah does not host any software, and not even any free software.
+
+When we point you to an URL, this means you do have to read it in
+order to be able to review a pending project at Savannah.
+
+
address@hidden Licenses
+
+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.
+
+As a special exception, it also accepts projects licensed under the
+Affero General Public License, since it is designed to be compatible
+with the GNU GPL version 3.
+
+See @uref{http://www.gnu.org/licenses/license-list.html} for a list of
+licenses, telling whether they are compatible with the GNU GPL, and
+whether they are Free Software licenses.
+
+Dependencies are pieces of software used or required by the project,
+and not hosted at Savannah. We require that this dependencies be Free
+Software, ie compatible with the Free Software Definition. They can be
+incompatible with the GNU GPL. For example, requiring modifications to
+be released as patches is considered compliant with the FSD, but is
+incompatible with the GNU GPL.
+
+See the Free Software Definition at
address@hidden://www.gnu.org/philosophy/free-sw.html}.
+
+Those URLs are required readings for any serious Savannah Hacker. Some
+of us even think they should be taught in Computer Science lessons :)
+
+Keep in mind that a project released under the GNU GPL, be it hosted
+at Savannah or not, cannot be legally linked to software released
+under a GPL-incompatible license, unless both the project and the
+dependency make special exceptions to their licenses. We feel it is a
+delicate point and urge you to contact the GPL Compliance Lab in such
+case. Just remember that dependencies of a program released under the
+GNU GPL has to be compatible with this license.
+
+The GNU Lesser General Public License (LGPL) is basically compatible
+with any dependencies linked dynamicaly (to keep it short). In fact,
+there are complex restrictions on how programs are linked with
+LGPL-covered code, so it is recommanded to read this license at least
+once (as well as some other common licenses such as the GPL,
+MIT/mBSD/X11, Affero, ZLib and Perl's).
+
+Speaking of Perl, it is dual-licensed, under both the GNU GPL and the
+Artistic v1 license (Perl 6 is planned to be released under the
+Artistic License 2.0, which is GPL-compatible). The latter is
+considered too vague to be a Free Software license, which means it is
+not only incompatible with the GPL, but cannot be accepted as a
+dependency's license.
+
+This can be problematic when a project depends on a Perl module which
+is not dual licensed, but only released under the Artistic v1. In such
+case, we try to contact the module authors and talk them into using
+the same license as Perl for consistency, making it a possible Savannah
+project dependency.
+
+If you are unsure of the compatibility of a license, please ask the
+GPL Compliance Lab at @email{licensing@@gnu.org}.
+
+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'' [TODO, make an
+appropriate xref call]; see
address@hidden://www.gnu.org/prep/maintain_8.html} and
address@hidden://www.gnu.org/prep/maintain_9.html}.
+
+
address@hidden Kind of software
+
+We accept any kind of software except in a few cases.
+
+If the project is big, and since we do not have unlimited hard-disk
+space and bandwidth, we do not accept it. For example, we do not host
+operating system distributions. If possible, we suggest the author to
+split his project into several smaller project, and submit each of
+these separately.
+
+If the software is primarily aimed at cracking purposes, we also
+reject it. However, if the software @emph{can} be used at cracking
+purposes, but it primarily aimed at better goals (such as network
+analysis tools), we can accept it.
+
+Approving GNU User Groups (GUG) or GNU/Linux User Groups (GLUG - which
+can inappropriately be called Linux User Groups or LUG) is not made by
+the Savannah hackers, but by people maintaining the GUG page at
address@hidden://www.gnu.org/gnu/gnu-user-groups.html}. They can be
+reached at @email{user-groups@@gnu.org}. Once the GUG is listed on that
+page, the project can be accepted.
+
address@hidden Words to avoid
+
+The approval process is adequate to teach our users about our
+philosophy and make sure they understand it. Among others, we want to
+be sure that users use an appropriate vocabulary when talking about
+free software. Check
address@hidden://www.gnu.org/philosophy/words-to-avoid.html}.
+
+Mainly, we should teach people to use 'free software' and not 'Open
+Source' if they mention the latter in their project description.
+
+Ditto for Linux and GNU/Linux.
+
address@hidden GIFs
+
+GIF is a symbol in the fight against software patents. For that reason, and 
because it is illegal to use this format without patent license, we require 
that users convert their materials in the GIF format to other ones, such as PNG 
or JPEG.
+Check @uref{http://www.gnu.org/philosophy/gif.html}.
+
address@hidden://www.gnu.org/philosophy/} and Richard Stallman's book
+(@uref{http://www.gnupress.org/book13.html}) also present interesting
+materials about software patents and the damages they cause.
+
+
address@hidden GNU projects
+
+We do not accept GNU projects directly. If a project mention the 'GNU'
+type, they is first created as non-GNU (if approved, of course), then
+we tell the GNU evaluation team about it by using the link in Group
+Management Savannah webpage. We will change the project type if the
+GNU evaluation team accepts the project as part of the GNU project.
+
+Also, we have this FAQ entry about the meaning of being a GNU package:
address@hidden://savannah.gnu.org/@/faq/@/?question=What_does_it_mean_to_become_a_GNU_package.txt}
+
+Canonical URL to refer to this information is:
address@hidden://www.gnu.org/evaluation/evaluation.html}
+(I'll make the FAQ a rediction soon)
+
+
 @section Rudy's Little HOWTO
 
 @verbatim
@@ -1252,106 +1418,6 @@
 
 
 
address@hidden GNU projects
-
-Note that we do not accept GNU projects directly. First, they are
-accepted as non-GNU (if they comply with Savannah's policies), then we
-tell the GNU evaluation team about it by using the link in group
-management, and we will change the project type once the GNU
-evaluation team accepts the project as GNU.
-
-Also, we have this FAQ entry:
address@hidden://savannah.gnu.org/@/faq/@/?question=What_does_it_mean_to_become_a_GNU_package.txt}
-Canonical URL to refer to this information is:
address@hidden://www.gnu.org/evaluation/evaluation.html}
-(I'll make the FAQ a rediction soon)
-
-(sylvain)
-
-
address@hidden Web Server Syndication
-
-Content for pages on www.gnu.org and www.nongnu.org is controlled by
-Savannah's respective project webcvs repositories.  Both www.gnu.org 
-and www.nongnu.org are syndicated to reflect the changes to Savannah's 
-webcvs repositories.
-
-Upon project approval, syndication does not begin automatically.
-Since the FSF will not allow Savannah hackers shell access to GNU's 
-main webserver, for understandable security concerns, there is a URL 
-we must use to enable project web syndication, for both GNU and non-GNU 
-projects.
-
-The URL is: @uref{http://www.gnu.org/new-savannah-project/new.py}
-
-It takes two arguments, ''type'' and ''project''.
-
-For ''type'', you choose whether the project is ''gnu'' or ''non-gnu''.
-
-For ''project'', you enter the name of the respective project.
-
address@hidden
-
-Example usage, with curl:
-
-curl http://www.gnu.org/new-savannah-project/new.py -F type=non-gnu -F 
project=fkt
address@hidden verbatim
-
-(mjflick)
-
address@hidden GUG
-
address@hidden
-> Hi!
-> 
-> I would like to register a project for our LUG (actually I call it a
-> GNU/UNIX/Linux User Group (with a strong focus on free software)) to
-
-Thank you for focussing on Free Software in your usergroup.  However,
-if you publically keep calling it a "LUG", people will see it as a
-"Linux User Group".
-
-> use the savannah services for web hosting and mailing list. I host
-> these things myself right now on my home server. However sometime in
-> the future I may not anymore be able to host the "LUG" pages + mailing
-> list, so I'm looking for an alternative. 
-
-Please see http://www.gnu.org/gnu/gnu-user-groups.html, if you get
-listed on that page we will surely help you.
-
-Thank you for your time,
--- 
-Rudy Gevaert                address@hidden
address@hidden verbatim
-
-
address@hidden Words to avoid
-
-Check synonymous page at www.gnu.org.
-
-Mainly, I think we also should teach people to use 'free software' and
-not 'Open Source' if they ever mention the latter in their project
-description.
-
-Ditto for Linux and GNU/Linux.
-
-
address@hidden License
-
-We don't want to host software released under a license incompatible
-with the GNU GPL.
-
-The idea is that users can be sure that they can use and mix any
-packages found in Savannah.
-(hugo)
-
-Also we don't want to host software that uses nonfree software
-(rudy)
-
-Last, I guess we can invite everybody to bookmark 
-http://www.gnu.org/licenses/license-list.html
-(sylvain)
-
 
 @node Terminology, Copying This Manual, Projects approval, Top
 @appendix Terminology