[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #5917] Submission of ThemeX/Westgen Sit
[Savannah-register-public] [task #5917] Submission of ThemeX/Westgen Site-Wide Template Engine
Mon, 09 Oct 2006 15:15:29 +0000
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20060830 Firefox/220.127.116.11 (Debian-1.5.dfsg+18.104.22.168-1)
Update of task #5917 (project administration):
Status: In Progress => Wait reply
Follow-up Comment #6:
I have now evaluated the tarball you submitted and I noticed a few problems.
These problems are described below.
First of all, the license you've included in your tarball is outdated. The
address of the FSF has changed and you should fetch a fresh copy from
http://www.gnu.org/licenses/gpl.txt. This will also fix a problem with the
license file itself, as your version is missing the last section, 'How to
Apply These Terms to Your New Programs'. Please also note that whilst keeping
the license in a file named 'license.txt' is okay, it is recommended to name
that file 'COPYING'.
Secondly, your submission and your license headers in the tarball state that
you are licensing your project under the GPLv2 or later, is this still
correct? You mentioned that you wanted to use the GPLv2 only. In fact, we
would like you to use the GPLv2 or later. As I mentioned before, licensing
under the "GNU GPL v2 only" is problematic.
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.
Thirdly, there is a license missing for the binary files (ie. pictures, etc.)
in your tarball. Please add a README file in the same directory containing the
copyright and license notices. Check
http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices for further
The GPL FAQ explains why these procedures must be followed.
Another thing I've noticed is that the tiny_mce subdirectory is missing the
LGPL license text. Please include a verbatim copy of the LGPL in the tiny_mce
subdirectory. The easiest way to achieve that is to simply copy a 'clean'
version of the whole tiny_mce distribution into the subdirectory of your
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.
To help us better keep track of your registration, please use the tracker's
web interface following the link below. Do not reply directly, the
registration process is not driven by e-mail, and we will not receive such
Reply to this item at:
Message sent via/by Savannah