savannah-register-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #10395] Submission of Ultra Light Blog


From: Mario Castelán Castro
Subject: [Savannah-register-public] [task #10395] Submission of Ultra Light Blog
Date: Tue, 18 May 2010 20:38:35 +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 #10395 (project administration):

             Assigned to:                    None => marioxcc               

    _______________________________________________________

Follow-up Comment #1:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

May 18th 2010 in GNU Savannah task #10395: "Submission of Ultra Light
Blog"

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.

Are you planning to move from SF to GNU Savannah?  If you do, this
link may be usefull to you:
http://savannah.gnu.org/maintenance/MigrationFromSourceForge.

Please note that GNU Savannah is a central place for development of
GNU and non-GNU free software, we don't want to be used just as a
mirror or backup if data and main development happens elsewhere.

I noticed some issues with the tarball you submited:

In order to release this (Or another) 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, 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.

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.

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

Item status changes:

Assigned to -> marioxcc
Status -> In progress
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkvy+wkACgkQZ4DA0TLic4gEBQCeLaQKwro8Jzim+SKiIjx0mq0A
B3oAnA1shQ/zNCQ/XmZNsTuINiAmXGwl
=YiB3
-----END PGP SIGNATURE-----


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?10395>

_______________________________________________
  Mensaje enviado vai/por Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]