[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] administration/infra/elisp savannah.el
|
From: |
Sylvain Beucler |
|
Subject: |
[Savannah-cvs] administration/infra/elisp savannah.el |
|
Date: |
Sun, 13 Feb 2005 06:01:33 -0500 |
CVSROOT: /cvsroot/administration
Module name: administration
Branch:
Changes by: Sylvain Beucler <address@hidden> 05/02/13 11:01:33
Modified files:
infra/elisp : savannah.el
Log message:
Removed newlines that were meant to make the text respect the
80-chars-width limit. Since we are using the tracker interface, it is
better to let the PHP wrapping function do the job.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/infra/elisp/savannah.el.diff?tr1=1.7&tr2=1.8&r1=text&r2=text
Patches:
Index: administration/infra/elisp/savannah.el
diff -u administration/infra/elisp/savannah.el:1.7
administration/infra/elisp/savannah.el:1.8
--- administration/infra/elisp/savannah.el:1.7 Thu Feb 3 20:25:19 2005
+++ administration/infra/elisp/savannah.el Sun Feb 13 11:01:33 2005
@@ -65,7 +65,7 @@
;; sv-closing-resubmit, and added sv-deleted-pending and
;; sv-problem-fdl-info.
;;
-;; $Id: savannah.el,v 1.7 2005/02/03 20:25:19 Beuc Exp $
+;; $Id: savannah.el,v 1.8 2005/02/13 11:01:33 Beuc Exp $
;;
;; General
@@ -89,14 +89,9 @@
""
(insert "Please register your project once more with the changes mentioned
above.
-We cannot track projects that have been answered but not approved, so we
-must ask you to re-register the project again whenever you change the
-registration. Make sure to apply all changes requested, so you will
-only need to re-register once.
-
-The re-registration URL found in our acknowledgment of your earlier
-registration will direct you to the proper location where you can
-re-register your project.
+We cannot track projects that have been answered but not approved, so we must
ask you to re-register the project again whenever you change the registration.
Make sure to apply all changes requested, so you will only need to re-register
once.
+
+The re-registration URL found in our acknowledgment of your earlier
registration will direct you to the proper location where you can re-register
your project.
Regards,\n\n")
(message "Inserted sv-closing-resubmit text.")
@@ -107,9 +102,7 @@
(defun sv-closing-english-resubmit ()
(interactive)
""
- (insert "Please resubmit your project in English. English is the
-only language that the whole Savannah team understand and needed for
-transparency and archival.
+ (insert "Please resubmit your project in English. English is the only
language that the whole Savannah team understand and needed for transparency
and archival.
Regards,\n")
(message "Inserted sv-closing-english-resubmit text.")
@@ -120,9 +113,7 @@
(defun sv-closing-reply ()
(interactive)
""
- (insert "If you are willing to make the changes mentioned above, please
provide
-us with an URL to an updated tarball of your project. Upon review, we
-will reconsider your project for inclusion in Savannah.
+ (insert "If you are willing to make the changes mentioned above, please
provide us with an URL to an updated tarball of your project. Upon review, we
will reconsider your project for inclusion in Savannah.
Regards,\n\n")
(message "Inserted sv-closing-reply text.")
@@ -138,9 +129,7 @@
I am waiting for an answer from you.
-If within one week I still do not get a reply, I will remove your
-project. You will still be able to register it again once you have the
-time to deal with the registration issues.
+If within one week I still do not get a reply, I will remove your project. You
will still be able to register it again once you have the time to deal with the
registration issues.
Regards,\n\n")
(message "Inserted sv-ping text.")
@@ -152,15 +141,11 @@
""
(insert "Hi,
-We did not get a response from you, so we deleted your project from
-the pending queue.
+We did not get a response from you, so we deleted your project from the
pending queue.
-If you would still like to have your project hosted at Savannah,
-please register it again.
+If you would still like to have your project hosted at Savannah, please
register it again.
-The re-registration URL found in our acknowledgment of your earlier
-registration will direct you to the proper location where you can
-re-register your project.
+The re-registration URL found in our acknowledgment of your earlier
registration will direct you to the proper location where you can re-register
your project.
Regards,\n\n")
(message "Inserted sv-timeout text.")
@@ -175,9 +160,7 @@
(defun sv-problem-details ()
(interactive)
""
- (insert "We need a detailed technical description that specifies such
-requirements as programming languages and external libraries. It should
-be at least one-half a page.\n\n")
+ (insert "We need a detailed technical description that specifies such
requirements as programming languages and external libraries. It should be at
least one-half a page.\n\n")
(message "Inserted sv-problem-details text.")
)
@@ -186,20 +169,11 @@
(defun sv-problem-tarball ()
(interactive)
""
- (insert "Please register your project again and include an \(perhaps
temporary\)
-URL pointing to the source code. The description you gave when
-registering will not be read by the general public. If you are still
-concerned with privacy, however, you can forward the code to me by email
-\(<address to send to>\).
-
-We wish to review your source code, even if it is not functional, to
-catch potential legal issues early.
-
-For example, to release your program properly under the GPL you must
-include a copyright notice and permission-to-copy statements at
-the beginning of every file of source code. This is explained in
-http://www.gnu.org/licenses/gpl-howto.html. Our review would help catch
-potential omissions such as these.\n\n")
+ (insert "Please include a \(perhaps temporary\) URL pointing to the source
code. The description you gave when registering will not be read by the
general public. If you are still concerned with privacy, however, you can
forward the code to me by email.
+
+We wish to review your source code, even if it is not functional, to catch
potential legal issues early.
+
+For example, to release your program properly under the GPL you must include a
copyright notice and permission-to-copy statements at the beginning of every
file of source code. This is explained in
http://www.gnu.org/licenses/gpl-howto.html. Our review would help catch
potential omissions such as these.\n\n")
(message "Inserted sv-problem-tarball text.")
)
@@ -211,18 +185,13 @@
(interactive)
""
(insert "In order to release your project properly and unambiguously under
the
-GPL, please place copyright notices and permission-to-copy statements at
-the beginning of every file of source code.
+GPL, please place copyright notices and permission-to-copy statements at the
beginning of every file of source code.
-In addition, if you haven't already, please include a
-copy of the plain text version of the GPL, available from
-http://www.gnu.org/licenses/gpl.txt, into a file named \"COPYING\".
+In addition, if you haven't already, please include a copy of the plain text
version of the GPL, available from http://www.gnu.org/licenses/gpl.txt, into a
file named \"COPYING\".
For more information, see http://www.gnu.org/licenses/gpl-howto.html.
-The GPL FAQ explains why these procedures must be followed. To learn
-why a copy of the GPL must be included with every copy of the code, for
-example, see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.\n\n";)
+The GPL FAQ explains why these procedures must be followed. To learn why a
copy of the GPL must be included with every copy of the code, for example, see
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.\n\n";)
(message "Inserted sv-problem-gpl-info text.")
)
@@ -233,13 +202,9 @@
(defun sv-problem-lgpl-info ()
(interactive)
""
- (insert "In order to release your project properly and unambiguously under
the
-LGPL, please place copyright notices and permission-to-copy statements
-at the beginning of every file of source code.
+ (insert "In order to release your project properly and unambiguously under
the LGPL, please place copyright notices and permission-to-copy statements at
the beginning of every file of source code.
-In addition, if you haven't already, please include a copy
-of the plain text version of the LGPL, available from
-http://www.gnu.org/licenses/lgpl.txt, into a file named \"COPYING\".
+In addition, if you haven't already, please include a copy of the plain text
version of the LGPL, available from http://www.gnu.org/licenses/lgpl.txt, into
a file named \"COPYING\".
For more information, see http://www.gnu.org/licenses/lgpl.html#SEC4.\n\n";)
(message "Inserted sv-problem-lgpl-info text.")
@@ -253,12 +218,9 @@
(interactive)
""
(insert "In order to release your project properly and unambiguously under
the
-FDL, please place copyright notices and permission-to-copy statements
-after the title page of each work.
+FDL, please place copyright notices and permission-to-copy statements after
the title page of each work.
-In addition, if you haven't already, please copy a copy
-of the plain text version of the FDL, available from
-http://www.gnu.org/licenses/fdl.txt, into a file named \"COPYING\".
+In addition, if you haven't already, please copy a copy of the plain text
version of the FDL, available from http://www.gnu.org/licenses/fdl.txt, into a
file named \"COPYING\".
For more information, see http://www.gnu.org/licenses/fdl.html.\n\n";)
(message "Inserted sv-problem-fdl-info text.")
@@ -285,10 +247,7 @@
(insert "The license does not contain the last section, titled \"How to Apply
These Terms to Your New Programs\".
-Please use a complete verbatim copy of the license, which
-may be found at http://www.gnu.org/licenses/gpl.txt,
-http://www.gnu.org/licenses/lgpl.txt or
-http://www.gnu.org/licenses/fdl.txt.
+Please use a complete verbatim copy of the license, which may be found at
http://www.gnu.org/licenses/gpl.txt, http://www.gnu.org/licenses/lgpl.txt or
http://www.gnu.org/licenses/fdl.txt.
The license must be copied verbatim and in its entirety.\n\n")
(message "Inserted sv-problem-license-truncated text.")
@@ -299,18 +258,13 @@
(defun sv-problem-java ()
(interactive)
""
- (insert "You must determine whether your project can run on a Free Software
Java
-suite \(see http://www.gnu.org/software/java/ for more information\).
+ (insert "You must determine whether your project can run on a Free Software
Java suite \(see http://www.gnu.org/software/java/ for more information\).
-We recommend you to test your project using GCJ and GNU Classpath, and
-ensure that your Java code runs on this Free Software Java suite.
+We recommend you to test your project using GCJ and GNU Classpath, and ensure
that your Java code runs on this Free Software Java suite.
-GCJ is the GNU Compiler for Java, part of the GCC (GNU Compiler
-Collection). The Classpath project aims to develop a free and portable
-implementation of the Java API \(the classes in the 'java' package\).
+GCJ is the GNU Compiler for Java, part of the GCC (GNU Compiler Collection).
The Classpath project aims to develop a free and portable implementation of the
Java API \(the classes in the 'java' package\).
-More information is available at http://gcc.gnu.org/ and
-http://www.gnu.org/software/classpath/,
+More information is available at http://gcc.gnu.org/ and
http://www.gnu.org/software/classpath/ .
Please provide us with more information about this point.\n\n")
(message "Inserted sv-problem-java text.")
@@ -335,15 +289,11 @@
(defun sv-problem-uses-gnu-name ()
(interactive)
""
- (insert "Your project is not yet part of the GNU project, so we cannot
accept its
-current name.
+ (insert "Your project is not yet part of the GNU project, so we cannot
accept its current name.
-While there are non-GNU programs with names that include 'gnu', such
-as gnuplot and gnuboy, they are not hosted on Savannah.\n We want to
-maintain the distinction between GNU and non-GNU projects.
+While there are non-GNU programs with names that include 'gnu', such as
gnuplot and gnuboy, they are not hosted on Savannah.\n We want to maintain the
distinction between GNU and non-GNU projects.
-When your project is accepted into the GNU project you may change its
-name. You can do this by asking us.\n\n")
+When your project is accepted into the GNU project you may change its name.
You can do this by asking us.\n\n")
(message "Inserted sv-problem-uses-gnu-name text.")
)
@@ -353,12 +303,9 @@
(interactive)
""
(insert "Your project is not part of the GNU project, so we cannot accept its
-current type. We want to maintain the distinction between 'GNU' and
-'non-GNU' projects. If your project is approved for inclusion into
-Savannah, we will set it's type to 'non-GNU'.
+current type. We want to maintain the distinction between 'GNU' and'non-GNU'
projects. If your project is approved for inclusion into Savannah, we will set
it's type to 'non-GNU'.
-If your project is accepted into the GNU project you may change its
-type. You can do this by asking us.\n\n")
+If your project is accepted into the GNU project you may change its type. You
can do this by asking us.\n\n")
(message "Inserted sv-problem-uses-gnu-type text.")
)
@@ -367,21 +314,15 @@
(defun sv-problem-license-gplincompatible ()
(interactive)
""
- (insert "The license you chose qualifies your software as free software but
it is
-incompatible with the GNU GPL.
+ (insert "The license you chose qualifies your software as free software but
it is incompatible with the GNU GPL.
-We only host software published under licenses compatible with the GPL,
-which allows developers to combine files from any project without fear
-of a licensing problem.
+We only host software published under licenses compatible with the GPL, which
allows developers to combine files from any project without fear of a licensing
problem.
-If you are willing to switch to a GPL-compatible license, please
-resubmit the project.
+If you are willing to switch to a GPL-compatible license, please resubmit the
project.
-You can get a list of various licenses and comments about them at
-http://www.gnu.org/philosophy/license-list.html.
+You can get a list of various licenses and comments about them at
http://www.gnu.org/philosophy/license-list.html.
-If you still wish to use your current license, we will be happy to
-discuss it with you.\n\n")
+If you still wish to use your current license, we will be happy to discuss it
with you.\n\n")
(message "Inserted sv-problem-license-gplincompatible text.")
)
@@ -390,25 +331,15 @@
(defun sv-problem-license-mpl-alike ()
(interactive)
""
- (insert "The license you chose qualifies your project as free software but
it is
-incompatible with the GNU GPL because it is similar to the MPL.
+ (insert "The license you chose qualifies your project as free software but
it is incompatible with the GNU GPL because it is similar to the MPL.
+
+MPL 1.0 is incompatible with the GNU GPL. That is, combining a module covered
by the GPL with a module covered by the MPL is not legal. MPL 1.1, however,
allows \(section 13\) a program \(or parts of it\) to offer a choice of another
license as well. Any part of a program that allows the GNU GPL, or many of its
variants, as an alternate choice, is considered to have a GPL-compatible
license.
-MPL 1.0 is incompatible with the GNU GPL. That is, combining a module
-covered by the GPL with a module covered by the MPL is not legal.
-MPL 1.1, however, allows \(section 13\) a program \(or parts of it\) to
-offer a choice of another license as well. Any part of a program that
-allows the GNU GPL, or many of its variants, as an alternate choice, is
-considered to have a GPL-compatible license.
-
-We only host software published under licenses compatible with the GPL,
-which allows developers to combine files from any project without fear
-of a licensing problem.
+We only host software published under licenses compatible with the GPL, which
allows developers to combine files from any project without fear of a licensing
problem.
-If you're willing to switch to a GPL-compatible license, or dual license
-with a GPL-compatible license and a MPL 1.1 license, please resubmit.
+If you're willing to switch to a GPL-compatible license, or dual license with
a GPL-compatible license and a MPL 1.1 license, please resubmit.
-You can read a discussion of various licenses at
-http://www.gnu.org/philosophy/license-list.html for more information.\n\n")
+You can read a discussion of various licenses at
http://www.gnu.org/philosophy/license-list.html for more information.\n\n")
(message "Inserted sv-problem-license-mpl-alike text.")
)
@@ -417,13 +348,9 @@
(defun sv-problem-open-in-name ()
(interactive)
""
- (insert "Savannah's mission is to host free software projects, and we want
the
-public to think of them as free software projects. A project name that
-says \"open\" will tend to lead people to think of the project as \"open
-source\" instead of \"free software\".
+ (insert "Savannah's mission is to host free software projects, and we want
the public to think of them as free software projects. A project name that
says \"open\" will tend to lead people to think of the project as \"open
source\" instead of \"free software\".
-We would be glad if you accept to use \"free\" instead of \"open\" in your
-project name.\n\n")
+We would be glad if you accept to use \"free\" instead of \"open\" in your
project name.\n\n")
(message "Inserted sv-problem-open-in-name text.")
)
@@ -432,17 +359,11 @@
(defun sv-problem-gpl-two-only ()
(interactive)
""
- (insert "Licensing under the \"GNU GPL v2 only\" is problematic. Would you
agree
-to license your project under the \"GNU GPL v2 or later\"?
+ (insert "Licensing under the \"GNU GPL v2 only\" is problematic. Would you
agree to license your project under the \"GNU GPL v2 or later\"?
-The reason for this is that when we publish GPL v3, it will be important
-for all GPL-covered programs to advance to GPL v3. If you don't put
-this in the files now, the only way to port your program to GPL v3
-would be to ask each and every copyright holder, and that may be very
-difficult.
+The reason for this is that when we publish GPL v3, it will be important for
all GPL-covered programs to advance to GPL v3. If you don't put this in the
files now, the only way to port your program to GPL v3 would be to ask each and
every copyright holder, and that may be very difficult.
-We can explain the issue in more detail if you wish. If you have
-concerns about \"GNU GPL v2 or later\", we'd be happy to address them too.
+We can explain the issue in more detail if you wish. If you have concerns
about \"GNU GPL v2 or later\", we'd be happy to address them too.
")
(message "Inserted sv-problem-gpl-two-only text.")
)
@@ -452,8 +373,7 @@
(defun sv-problem-linux-vs-gnu ()
(interactive)
""
- (insert "\"Linux\" is just a kernel of a more complex system that we like to
refer
-to as GNU/Linux, to emphasize the ideals of the Free Software movement.
+ (insert "\"Linux\" is just a kernel of a more complex system that we like to
refer to as GNU/Linux, to emphasize the ideals of the Free Software movement.
Would you mind changing references to Linux as an OS to GNU/Linux?
@@ -466,13 +386,9 @@
(defun sv-problem-gif ()
(interactive)
""
- (insert "Please remove GIF image files from your project and replace them
with an
-other format \(such as PNG or JPEG\).
+ (insert "Please remove GIF image files from your project and replace them
with an other format \(such as PNG or JPEG\).
-Because of the patents \(Unisys and IBM\) covering the LZW compression
-algorithm which are used when making GIF files, it's impossible to have
-free software to generate proper GIFs. These patents also apply to the
-compress program.
+Because of the patents \(Unisys and IBM\) covering the LZW compression
algorithm which are used when making GIF files, it's impossible to have free
software to generate proper GIFs. These patents also apply to the compress
program.
For more information, see http://www.gnu.org/philosophy/gif.html.\n\n";)
(message "Inserted sv-problem-gif text.")
@@ -491,24 +407,13 @@
We only host projects that can run on a free operating system \(such as
Debian GNU/Linux\).
-We have adopted this policy because now that completely free operating
-systems exist, we do not want to encourage users of those systems to
-start using proprietary operating systems so that they can use your
-program.
-
-If you are willing to maintain a version for free operating systems,
-which work as well as or better than other ports, you can then provide
-versions for non-free systems as well. The idea is that at no point
-should only-free users be at a disadvantage compared to users of
-proprietary software.
-
-Your project should always work equally well in free systems as in
-any other version you provide; if you have some modules for non-free
-systems, you can delay their release until you have released the free
-operating system version.
+We have adopted this policy because now that completely free operating systems
exist, we do not want to encourage users of those systems to start using
proprietary operating systems so that they can use your program.
+
+If you are willing to maintain a version for free operating systems, which
work as well as or better than other ports, you can then provide versions for
non-free systems as well. The idea is that at no point eshould only-free users
be at a disadvantage compared to users of proprietary software.
-If you accept this commitment then please register your project again
-and it should be approved in Savannah.
+Your project should always work equally well in free systems as in any other
version you provide; if you have some modules for non-free systems, you can
delay their release until you have released the free operating system version.
+
+If you accept this commitment then please register your project again and it
should be approved in Savannah.
Thank you for your understanding.
@@ -521,16 +426,11 @@
(defun sv-reject-proprietary ()
(interactive)
""
- (insert "Your project requires proprietary software and cannot be hosted on
-Savannah for this reason.
+ (insert "Your project requires proprietary software and cannot be hosted on
Savannah for this reason.
-Savannah is willing to provide resources and time to developers writing
-Free Software that can be used without the need to ask permission from
-proprietary software vendor.
-
-If, someday, you get free of those dependencies (see
-http://www.gnu.org/software/java for more information), do not hesitate
-to resubmit your project.
+Savannah is willing to provide resources and time to developers writing Free
Software that can be used without the need to ask permission from proprietary
software vendor.
+
+If, someday, you get free of those dependencies (see
http://www.gnu.org/software/java for more information), do not hesitate to
resubmit your project.
Thank you for your understanding.
@@ -546,13 +446,9 @@
(insert "Your project requires proprietary software and cannot be hosted on
Savannah for this reason.
-Savannah is willing to provide resources and time to developers writing
-Free Software that can be used without the need to ask permission from a
-proprietary software vendor.
-
-If, someday, you get free of those dependencies (see
-http://www.gnu.org/software/java for more information), do not hesitate
-to resubmit your project.
+Savannah is willing to provide resources and time to developers writing Free
Software that can be used without the need to ask permission from a proprietary
software vendor.
+
+If, someday, you get free of those dependencies (see
http://www.gnu.org/software/java for more information), do not hesitate to
resubmit your project.
Thank you for your understanding.
@@ -565,15 +461,9 @@
(defun sv-reject-cracking ()
(interactive)
""
- (insert "You described your project as a piece of software primarily aimed at
-cracking purposes. We do not want to encourage such practice, and hence
-cannot approve your project.
-
-However, if you think this project can be modified to primarily serve
-system administrators aims instead of the crackers', and if you want
-to keep the development in that direction, we may reconsider your
-project. Please then resubmit your project with a description fitting
-this goal.
+ (insert "You described your project as a piece of software primarily aimed
at cracking purposes. We do not want to encourage such practice, and hence
cannot approve your project.
+
+However, if you think this project can be modified to primarily serve system
administrators aims instead of the crackers', and if you want to keep the
development in that direction, we may reconsider your project. Please then
resubmit your project with a description fitting this goal.
Regards,\n\n")
(message "Inserted sv-reject-cracking text.")
@@ -590,8 +480,7 @@
""
(insert "Hi,
-I have approved your project. You will receive an automated e-mail
-containing detailed information about the approval.
+I have approved your project. You will receive an automated e-mail containing
detailed information about the approval.
Regards,\n\n")
(message "Inserted sv-approve text.")
@@ -602,13 +491,9 @@
(defun sv-approve-as-nongnu ()
(interactive)
""
- (insert "We have approved your project as a non-GNU project. In order to
-evaluate it as a GNU package, we need more information - a clear
-description of the design and plans for the whole package, and
-preferably part of the code.
+ (insert "We have approved your project as a non-GNU project. In order to
evaluate it as a GNU package, we need more information - a clear description of
the design and plans for the whole package, and preferably part of the code.
-When those things are ready, write to address@hidden to ask for an
-evaluation of your project for inclusion in GNU.
+When those things are ready, write to address@hidden to ask for an evaluation
of your project for inclusion in GNU.
Regards,\n\n")
(message "Inserted sv-approve-as-nongnu text.")
@@ -642,11 +527,7 @@
""
(insert "Note that commercial does not mean proprietary.
-Free Software means that users have certain freedoms; it does not mean
-zero price. \"Commercial\" means \"associated with business\"; a commercial
-program may be free or non-free, depending on its license. So it is a
-mistake to treat \"free\" and \"commercial\" as contraries. When a business
-develops free software, that is free commercial software.\n\n")
+Free Software means that users have certain freedoms; it does not mean zero
price. \"Commercial\" means \"associated with business\"; a commercial program
may be free or non-free, depending on its license. So it is a mistake to treat
\"free\" and \"commercial\" as contraries. When a business develops free
software, that is free commercial software.\n\n")
(message "Inserted sv-confusion-commercial-and-proprietary text.")
)
@@ -655,16 +536,11 @@
(defun sv-confusion-open-and-free ()
(interactive)
""
- (insert "Note that Savannah supports projects of the Free Software movement,
not
-projects of the Open Source movement.
+ (insert "Note that Savannah supports projects of the Free Software movement,
not projects of the Open Source movement.
-We are careful about ethical issues and insist on producing software
-that is not dependent on proprietary software.
+We are careful about ethical issues and insist on producing software that is
not dependent on proprietary software.
-While Open Source as defined by its founders means
-something pretty close to Free Software, it's frequently
-misunderstood. For more information, please see
-http://www.gnu.org/philosophy/free-software-for-freedom.html.\n\n";)
+While Open Source as defined by its founders means something pretty close to
Free Software, it's frequently misunderstood. For more information, please see
http://www.gnu.org/philosophy/free-software-for-freedom.html.\n\n";)
(message "Inserted sv-confusion-open-and-free text.")
)