[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] administration/content/gnu-content/faq Project_...
|
From: |
Michael Clarke |
|
Subject: |
[Savannah-cvs] administration/content/gnu-content/faq Project_... |
|
Date: |
Mon, 19 Mar 2007 21:21:41 +0000 |
CVSROOT: /web/administration
Module name: administration
Changes by: Michael Clarke <clarkema> 07/03/19 21:21:41
Modified files:
content/gnu-content/faq: Project_-_How_do_I_add_searchterms.txt
Project_-_How_do_I_set_up_a_FAQ.txt
Project_-_How_to_get_it_approved_quickly.txt
Project_-_Is_there_a_way_to_clean_it_all.txt
Project_-_What_does_it_mean_to_become_a_GNU_package.txt
Project_-_What_is_the_registration_process.txt
Project_-_What_is_the_status_of_my_project_registration.txt
Log message:
Migrated the Project* FAQs to the Wiki
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_How_do_I_add_searchterms.txt?cvsroot=administration&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_How_do_I_set_up_a_FAQ.txt?cvsroot=administration&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_How_to_get_it_approved_quickly.txt?cvsroot=administration&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_Is_there_a_way_to_clean_it_all.txt?cvsroot=administration&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_What_does_it_mean_to_become_a_GNU_package.txt?cvsroot=administration&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_What_is_the_registration_process.txt?cvsroot=administration&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/Project_-_What_is_the_status_of_my_project_registration.txt?cvsroot=administration&r1=1.1&r2=1.2
Patches:
Index: Project_-_How_do_I_add_searchterms.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_How_do_I_add_searchterms.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Project_-_How_do_I_add_searchterms.txt 14 Apr 2005 21:19:54 -0000
1.1
+++ Project_-_How_do_I_add_searchterms.txt 19 Mar 2007 21:21:40 -0000
1.2
@@ -1,3 +1 @@
-<P>Add <meta keywords="keyword1 keyword2 keywordn"> to your project
description.
-
-<P><font size="-1">Updated $Date: 2005/04/14 21:19:54 $</font>
\ No newline at end of file
+FAQ moved here: http://savannah.gnu.org/maintenance/HowDoIAddSearchTerms
Index: Project_-_How_do_I_set_up_a_FAQ.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_How_do_I_set_up_a_FAQ.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Project_-_How_do_I_set_up_a_FAQ.txt 14 Apr 2005 21:19:54 -0000 1.1
+++ Project_-_How_do_I_set_up_a_FAQ.txt 19 Mar 2007 21:21:40 -0000 1.2
@@ -1,4 +1 @@
-For the moment, it's impossible. We are working on it.
-
-
-<P><font size="-1">Update $Date: 2005/04/14 21:19:54 $</font>
\ No newline at end of file
+FAQ moved here: http://savannah.gnu.org/maintenance/HowDoISetUpAProjectFAQ
Index: Project_-_How_to_get_it_approved_quickly.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_How_to_get_it_approved_quickly.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- Project_-_How_to_get_it_approved_quickly.txt 10 Feb 2006 03:33:46
-0000 1.4
+++ Project_-_How_to_get_it_approved_quickly.txt 19 Mar 2007 21:21:40
-0000 1.5
@@ -1,142 +1 @@
-<p><em>It seems always better to precise that: this is not the
-official hosting policy, just an help.</em></p>
-
-<p>When you submit a project, it is reviewed by the Savannah hackers,
-to check for compliance with the Savannah hosting policies.</p>
-
-<p>Here is a compliance <strong>check-list</strong>, then further
-explanations.</p>
-
-<ul>
-
-<li>Make sure your project runs primarily on a completely <strong>free
-OS</strong>;</li>
-
-<li>Use a license compatible with the GNU GPL;</li>
-
-<li>Write a half-page technical description of your project: its goal,
-its programming language and its depencies (with URLs);</li>
-
-<li>Don't forget to give a pointer to the <strong>source
-code</strong>;</li>
-
-<li>Apply valid <strong>copyright</strong> and
-<strong>license</strong> notices using our templates; include a copy
-of the license you chose</li>
-
-<li>Convert your <strong>GIFs</strong> to PNGs or JPEGs;</li>
-
-<li>Refer to the <strong>GNU/Linux</strong> operating system instead
-of the Linux, which is the kernel. Advertise the <strong>free
-software</strong> movements, which we support, and not the open source
-one, which we don't. Do not use "Open" in your project
-name.</li>
-
-</ul>
-
-<p> </p>
-
-<p>The review we do can be long and tedious for both the submitter and
-the reviewer. Be sure to follow these steps; if your project doesn't
-comply with our requirements, we will ask you to make changes to your
-project or register again. This ensure a level of quality for projects
-hosted at Savannah.</p>
-
-<P>Here are further details:</p>
-
-<ul>
-
-<li>Project dependencies: to make the approval process quicker, give
-us <strong>URLs</strong> to your depencies, and if possible direct
-links to their licenses</li>
-
-<li><strong>GNU GPL-compatible</strong> license: your license should
-be listed as compatible at
-http://www.gnu.org/licenses/license-list.html. You can also use the
-Affero GPL (since it is very likely to compatible with GPLv3). For
-documentation, we are currently clarifying exactly what licenses we
-accept. Of course, we accept our GNU Free Documentation License (and
-compatibles), even if it is not compatible with the GNU GPL.<br />
-
-<li>Consistent licensing:
-
- <ul>
-
- <li>Write appropriate <strong>copyright</strong> and
- <strong>license</strong> notices, at the beginning of <em>all</em>
- of your files. http://www.gnu.org/licenses/gpl-howto.html and
- http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
- are good starting points to understand these issues and provide
- standard templates, that you should use to speed up the
- approval. More answers at
- http://www.gnu.org/licenses/gpl-faq.html. For the GFDL, check
- http://www.gnu.org/licenses/fdl-howto.html</li>
-
- <li>Include a <strong>verbatim copy</strong> of the license as plain
- text, do not point users to an external source to get the
- license;</li>
-
- <li>Moreover, do not combine code with <strong>incompatible
- licenses</strong> (e.g. GNU GPL'd code with CPL'd code). The GPL
- Compliance Lab, address@hidden, may provide advice for complex
- cases. For Perl code, avoid the modules released under the Artistic
- license only; for PHP, avoid modules released under the PHP
- license. Or talk their authors into releasing them under licenses
- compatible with the GNU GPL :)</li>
-
- </ul>
-</li>
-
-<li>No proprietary dependencies: your project
-
- <ul>
-
- <li>must work on a <strong>completely free operating
- system</strong>. Find free replacements for your non-free
- dependencies. Develop and test your Java applications with GNU
- GCJ and Classpath, and your .Net ones with DotGNU (or other
- free
- alternatives). http://www.gnu.org/philosophy/java-trap.html
- explains why.</li>
-
- <li>Runs <strong>primarily</strong> on a free operating
- system. Proprietary platforms such as Microsoft Windows should
- be considered as secondary targets, and cannot provide
- additional features over the ports to free OSes. </li>
-
- </ul>
-
-</li>
-
-<li>No storage or back-up-only project: we exist to help people
-develop software and technical documentation. Other hosting services
-offer storage space. We expect to be used primarily and not as a
-back-up, although we do not require all parts of the project to be
-hosted at Savannah.</li>
-
-<li>No <strong>GIFs</strong>: just convert them to PNGs or JPEGs,
-because the GIF format is encumbered by patents
-(http://www.gnu.org/philosophy/gif.html)</li>
-
-<li>Tell people that there are using the <strong>GNU/Linux</strong>
-variant of the GNU operating system, and that Linux is its kernel, not
-the whole OS. Check http://www.gnu.org/gnu/linux-and-gnu.html and
-http://www.gnu.org/gnu/gnu-linux-faq.html</li>
-
-<li>We support the <strong>free software</strong> movement, and not
-the open source one, because we are careful about ethics, that is, our
-primary focus is the freedom offered to users of free
-software. Further information at
-http://www.gnu.org/philosophy/free-software-for-freedom.html . As a
-consequence, we do not accept project with the work <em>open</em> in
-their name; we suggest you replace it with <em>free</em> instead, or
-use another project name of your choice.</li>
-
-</ul>
-
-
-<p>If you followed these advices and prepared your project
-accordingly, you're likely to gain time during your project
-registration, and are likely to get approved after the first
-review.</p>
-
+FAQ moved here:
http://savannah.gnu.org/maintenance/HowToGetYourProjectApprovedQuickly
Index: Project_-_Is_there_a_way_to_clean_it_all.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_Is_there_a_way_to_clean_it_all.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Project_-_Is_there_a_way_to_clean_it_all.txt 15 Apr 2005 18:20:12
-0000 1.2
+++ Project_-_Is_there_a_way_to_clean_it_all.txt 19 Mar 2007 21:21:40
-0000 1.3
@@ -1,11 +1 @@
-<p>No, the system is not meant to erase traces - it is rather designed
-to keep them.</p>
-
-<p>It is not possible to have a perfectly "clean" project, just like
-it is not possible to get a perfectly "clean" CVS repository in the
-long run :)</p>
-
-<p>We recommand instead to use new CVS modules, and close/categorize
-noisy trackers items.</p>
-
-<p style="font-size: smaller">Updated $Date: 2005/04/15 18:20:12 $</p>
+FAQ moved here: http://savannah.gnu.org/maintenance/HowDoIResetMyProject
Index: Project_-_What_does_it_mean_to_become_a_GNU_package.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_What_does_it_mean_to_become_a_GNU_package.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Project_-_What_does_it_mean_to_become_a_GNU_package.txt 14 Apr 2005
21:19:54 -0000 1.1
+++ Project_-_What_does_it_mean_to_become_a_GNU_package.txt 19 Mar 2007
21:21:40 -0000 1.2
@@ -1,60 +1 @@
-<P>
-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.
-<P>
-This means that we normally put the program on ftp.gnu.org (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.)
-<P>
-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.
-<P>
-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.
-<P>
-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.
-<P>
-If a GNU program wants to be extensible, it should use GUILE
-(http://www.gnu.org/software/guile/guile.html) 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.
-<P>
-A GNU program should use the latest version of a license that the GNU
-Project recommends--not just any free software license.
-<P>
-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.
-<P>
-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".
-<P>
-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>
-<i>Richard M. Stallman</i>
\ No newline at end of file
+FAQ moved here:
http://savannah.gnu.org/maintenance/WhatDoesItMeanToBecomeAGNUPackage
Index: Project_-_What_is_the_registration_process.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_What_is_the_registration_process.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Project_-_What_is_the_registration_process.txt 25 Apr 2005 21:05:26
-0000 1.2
+++ Project_-_What_is_the_registration_process.txt 19 Mar 2007 21:21:40
-0000 1.3
@@ -1,5 +1 @@
-<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 style="font-size: smaller">Updated $Date: 2005/04/25 21:05:26 $</p>
+FAQ moved here:
http://savannah.gnu.org/maintenance/WhatIsTheRegistrationProcess
Index: Project_-_What_is_the_status_of_my_project_registration.txt
===================================================================
RCS file:
/web/administration/administration/content/gnu-content/faq/Project_-_What_is_the_status_of_my_project_registration.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Project_-_What_is_the_status_of_my_project_registration.txt 14 Apr 2005
21:19:54 -0000 1.1
+++ Project_-_What_is_the_status_of_my_project_registration.txt 19 Mar 2007
21:21:40 -0000 1.2
@@ -1,13 +1 @@
-<p>Please have a look at:
-https://savannah.gnu.org/task/?group=administration&category_id=1&status_id=1&set=custom
-</p>
-
-<p>That page lists the projects currently under review.</p>
-
-<p>Note that you will always be notified by mail on the result of our
-review. We do not silently reject submissions.</p>
-
-<p>If your project is present in the list, and if you are waiting for
-a reply from us, then it is likely we have some backlog and need some
-delay. In that case, please wait, or else notify us that you will try
-another solution.</p>
+FAQ moved here:
http://savannah.gnu.org/maintenance/WhatIsTheStatusOfMyProjectRegistration
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] administration/content/gnu-content/faq Project_...,
Michael Clarke <=