[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] administration/content/gnu-content/faq Project_...

From: Sylvain Beucler
Subject: [Savannah-cvs] administration/content/gnu-content/faq Project_...
Date: Mon, 25 Apr 2005 17:05:26 -0400

CVSROOT:        /cvsroot/administration
Module name:    administration
Changes by:     Sylvain Beucler <address@hidden>        05/04/25 21:05:26

Modified files:

Log message:
        No duplication of information!


diff -u 
   Thu Apr 14 21:19:54 2005
       Mon Apr 25 21:05:26 2005
@@ -1,173 +1,5 @@
-<p><b>Registration prerequisite..</b>
+<p>Click on the "Register" link in the site menu, and follow the
+instructions. The first two screen are available to the non logged-in
+user and allow you to see our hosting policies.</p>
-<p>The steps described in this page are extracted from the project
-registration process so that you can have a quick look and figure out
-what it requires.  Since these are not the actual registration pages,
-they may be out of date (they are current at the date of March, 11
-2002). If you notice an inconsistency, please write to
- address@hidden
-<h2>***** Step 1: Services & Requirements</h2>
-<p><b>Use of Project Account</b>
-<p>The space given to you on this server is given for the expressed purpose of 
advancing Free Software (software development, documentation, organizing 
events, system administration of machines etc.). Using it to host or advertise 
non free software is considered harmful to Free Software. For more information, 
please read the Philosophy of the GNU Project.
-<p><b>No dependencies to non free software</b>
-<p>Your software may not depend on non free software. In order to be available 
to people who cannot use non free software, it has to be fully usable with the 
existing Free Software operating systems and programs.
-<p>You may not place any revenue-generating advertisements on a site hosted 
here. But you can point people to commercial support offerings for your Free 
Software project.
-<p><b>No GIF files</b>
-<p>You may not place any GIF files on a site hosted here. For more
-information please read Why there are no GIF files on GNU web pages: 
-<p><b>Free Software/Rights to Code</b>
-<p>You will be presented with a choice of Free Software licenses for your 
project. You will still be the owner of the content of your project. However, 
all these licenses give the freedom to anyone to use, copy, study from the 
source code and modify the software it contains.
-<p>If you wish to use another license that is not listed, let us know and we 
will review these requests on a case-by-case basis.
-<p>It is our intent to provide a permanent home for all versions of your 
project. We do reserve the right, however, to terminate your project if there 
is due cause.
-<h2>***** Step 2: Basic Information</h2>
-<p>We need a short description of your project. This description needs to 
contain the purpose of the project and a summarization of your goals.
-<p>If the GNU volunteers approve your project account, the account is to be 
used purely to meet the goals set forth in this statement. If you need to 
change this statement at any time, please inform the GNU volunteers and we will 
assist you in getting a new statement approved.
-<p>REQUIRED: Provide detailed, accurate description, with URLs
-<h2>***** Step 3: Project Name</h2>
-<P>We need some basic technical information for your project.
-There are two types of names that will be associated with this project.
-<P>The "Full Name" is descriptive, has no real name restrictions (except
-a 40 character limit), and
-can be changed. The "System Name" has several restrictions because it is
-used in so many places around the site. They are:
-<LI>Cannot match the system name of any other project
-<LI>Must be between 2 and 12 characters in length
-<LI>Can only contain characters, numbers, and dashes
-<LI>Must be a valid system username
-<LI>Cannot match one of our reserved domains
-<LI>System name will never change for this project
-<P>Your system name is important, however, because it will be used for
-many things, including:
-<LI>Directory names
-<LI>CVS repository name
-<LI>Group names
-<LI>Search engines throughout the site
-<h2>***** Step 4: License</h2>
-<P><B><I>If you are applying to become a webmaster of a part of the website, please
-select "website-only" from the choices below and proceed. Also check that
-the directory you intend to work on is not already ( ) associated with an 
existing Savannah project </I></B>
-<P>Choosing a license is a serious decision. Please take some time
-to read the text (and our explanations) of ( ) several licenses before
-making a choice about your project.
-<P>In order, to release your project, <B>you should write copyright notices 
and license notices at the beginning of every source code file</B>, and include 
a copy of the plain text version of the license. If your software is published 
under the GNU GPL license, you should read ( ) the section about applying license 
terms to your program.
-<P>For many legal reasons, 
-you may not change a project's license once it has been set. If you
-feel that you have a special case and legal capability to do this,
-we will work with you on a case-by-case basis.
-<P><B>Licenses compatible with the GNU GPL</B>
-<LI> GNU General Public License
-<LI> GNU Lesser General Public License
-<LI> GNU Free Documentation License
-<LI> X11 license
-<LI> Cryptix General License
-<LI> Modified BSD license
-<LI> The
-license of ZLib.
-<LI>The license of the iMatix Standard Function Library
-<LI> The
-W3C Software Notice and License
-<LI> The Berkeley Database
-          License (aka 
the Sleepycat Software Product License)
-<LI> The License of
-Python 1.6a2 and earlier versions
The Clarified Artistic License
-<LI> Expat license
-<h2>***** Step 5: Become a GNU package</h2>
-Calling a program GNU software means that its developers and the GNU
-project agree that "This program is part of the GNU project, released
-under the aegis of GNU"--and say so in the program.
-This means that we normally put the program on (although
-we could instead refer to the developer's choice of ftp site) and that
-we put the official pages describing the program on the GNU web
-server.  (It is ok to have more informal pages about secondary issues,
-such as discussion meant for people who want to help develop the
-package, on some other site.)
-It means that the developers agree to pay some attention to making the
-program work well with the rest of the GNU system--and conversely that
-the GNU project will encourage other GNU maintainers to pay some
-attention to making their programs fit in well with it.
-Just what it means to make programs work well together is mainly a
-practical matter that depends on what the program does.  But there are
-a few general principles.  Certain parts of the GNU coding standards
-directly affect the consistency of the whole system.  These include
-the standards for configuring and building a program, and the
-standards for command-line options.  It is important to make all GNU
-programs follow these standards, where they are applicable.
-Another important GNU standard is that GNU programs should come with
-documentation in Texinfo format.  That is the GNU standard
-documentation format, and it can be converted automatically into
-various other formats.
-If a GNU program wants to be extensible, it should use GUILE
-( ) as the programming
-language for extensibility--that is the GNU standard extensibility
-package.  If the program doesn't use GUILE today, at least there
-should be a firm plan to support it in the future.
-A GNU program should use the latest version of a license that the GNU
-Project recommends--not just any free software license.
-A GNU program should not recommend use of any non-free program, and it
-should not refer the user to any non-free documentation for free
-software.  The need for free documentation to go with free software is
-now a major focus of the GNU project; to show that we are serious
-about the need for free documentation, we must not contradict our
-position by recommending use of documentation that isn't free.
-Occasionally there are issues of terminology which are important for
-the success of the GNU project as a whole.  So we expect maintainers
-of GNU programs to follow them.  For example, the documentation files
-and comments in the program should speak of Linux-based GNU systems or
-GNU/Linux systems, rather than calling the whole system "Linux", and
-should use the term "free software" rather than "open source".
-Deciding that a program is GNU software does not necessarily require
-transferring copyright to the FSF; that is a separate question.  If
-you transfer the copyright to the FSF, the FSF will enforce the GPL
-for the program if someone violates it; if you keep the copyright,
-enforcement will be up to you.
-<P><font size="-1">Updated $Date: 2005/04/14 21:19:54 $</font>
+<p style="font-size: smaller">Updated $Date: 2005/04/25 21:05:26 $</p>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]