[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #10648] Submission of guile-cairo
From: |
Mario Castelán Castro |
Subject: |
[Savannah-register-public] [task #10648] Submission of guile-cairo |
Date: |
Mon, 04 Oct 2010 03:12:32 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; es-AR; rv:1.9.0.19) Gecko/2010072022 Iceweasel/3.0.6 (Debian-3.0.6-3) |
Follow-up Comment #3, task #10648 (project administration):
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
2010-10-03 in GNU Savannah task #10648: "Submission of guile-cairo".
Hi.
I noticed some problems with the tarball you submitted:
Files under "doc" lack Copyright & licensing information. Likewise
with "cairo/cairo-procedures.txt", "env.in", "HACKING",
"configure.ac", all instances of "Makefile.am". Please check your
files.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 copyrightable file, usually any file more
than 10 lines long.
In addition, if you haven't already, please include a copy of the
plain text version of the GNU LGPL, available from
http://www.gnu.org/licenses/lgpl.txt, into a file named "COPYING".
If some of your files cannot carry such notices (e.g. binary files),
then you can add a README file in the same directory containing the
copyright and license notices. An example of such README file can be
found at
http://git.savannah.gnu.org/cgit/emacs.git/tree/etc/images/README, but
you can use any layout as it's clear which files are under which
licenses, and their Copyright holder. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for
further information.
For more information, see
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html#SEC4.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please fix this issues and provide a updated tarball. You can ethier
attach it to the tracker or use an external hosting and provide a
*direct* download URL.
Regards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEAREIAAYFAkypRbgACgkQZ4DA0TLic4in1wCghQ/5QYVDqJkNJpQ2Iusjlf9p
/W0AoI47xYLpcczqiVozcnWcKmPpbwo1
=Nbkx
-----END PGP SIGNATURE-----
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?10648>
_______________________________________________
Mensaje enviado vía/por Savannah
http://savannah.gnu.org/