[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #10401] Submission of Ultra Light Forum
From: |
Mario Castelán Castro |
Subject: |
[Savannah-register-public] [task #10401] Submission of Ultra Light Forum |
Date: |
Thu, 20 May 2010 15:20:25 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; es-AR; rv:1.9.0.19) Gecko/2010033022 Iceweasel/3.0.6 (Debian-3.0.6-3) |
Update of task #10401 (project administration):
Status: None => In Progress
Assigned to: None => marioxcc
_______________________________________________________
Follow-up Comment #1:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
May 20th 2010 in GNU Savannah task #10401: "Submission of Ultra Light
Forum".
Hi.
I'm evaluating the project you submitted for approval in GNU Savannah.
You can reach the rest Savannah hackers (Staff) in this list:
http://lists.gnu.org/mailman/listinfo/savannah-hackers-public.
I noticed some issues with the tarball you submited:
You added the license notices, but did not add appropriate copyright
notices.
In order to release your project properly and unambiguously under the
GNU GPL, 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, 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.
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. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for
further information.
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.
I'ts customary to put the all files inside a top directory named
acording to the project name & version before tar-ing'em. This is
*not* a hosting requirement at all but instead is sugested to avoid
the users the need to create a new directory before unpack the
tarball.
Regards.
Item status changes:
Assigned to -> marioxcc
Status -> In progress
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEAREIAAYFAkv1U4IACgkQZ4DA0TLic4hVCgCfaL/k/MxtgU9NnBOgjWVUGqHV
2EUAnjQD9gzk5TMIyh+tjbD1xjDWFB4D
=b4U3
-----END PGP SIGNATURE-----
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?10401>
_______________________________________________
Mensaje enviado vai/por Savannah
http://savannah.gnu.org/
- [Savannah-register-public] [task #10401] Submission of Ultra Light Forum,
Mario Castelán Castro <=