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

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

[Savannah-register-public] [task #10565] Submission of Insidious Big Bro


From: Mario Castelán Castro
Subject: [Savannah-register-public] [task #10565] Submission of Insidious Big Brother Database
Date: Sat, 21 Aug 2010 21:06:34 +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)

Update of task #10565 (project administration):

                  Status:                    None => In Progress            
             Assigned to:                    None => marioxcc               

    _______________________________________________________

Follow-up Comment #1:

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

August 21th 2010 in GNU Savannah task #10565: "Submission of Insidious
Big Brother Database".

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:

Some files (Makefile, ChangeLog) lack licensing information and a copy
of the GPL text is missing.

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.  The ChangeLog can contain that
information at the end if you wish.

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.  I'ts customary to put the all files inside a
top directory before tar-ing'em.  This is not a requirement at all but
is adviced 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)

iEYEAREIAAYFAkxwPzYACgkQZ4DA0TLic4ik7gCfWkd6H+bsawtGBcbfENDrwDc3
MqgAnAkKFXPdoOlcR912w6bBGMn5D9l5
=mUbc
-----END PGP SIGNATURE-----


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Mensaje enviado vía/por Savannah
  http://savannah.gnu.org/




reply via email to

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