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

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

[Savannah-register-public] [task #10686] Submission of Opus Libre


From: Mario Castelán Castro
Subject: [Savannah-register-public] [task #10686] Submission of Opus Libre
Date: Tue, 12 Oct 2010 21:51:21 +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 #10686 (project administration):

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

2010-10-12 in GNU Savannah task #10686: "Submission of Opus Libre".

Hello.

You filled the Savannah hosting request, if you want to offer this
software to the GNU project read
http://www.gnu.org/help/evaluation.html.  Please note these are
separate issues each with its own processes.

If this project is accepted into the GNU project you may change its
type by asking us at the savannah-hackers-public mailing list or open
a support request in this project (Administration).  Until that
happens I will set this field to non-GNU.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The GPL header isn't that suggested by the GNU project.  Other files
lack Copyright & licensing information at all.

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, 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.
You can also find the adviced license notice there.

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 and thanks for your interest in free software.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAky01+oACgkQZ4DA0TLic4hrrACfXAgtJ3SofDBBh3SwX+1K5q54
N5wAn09/svyKDFSF5d2Fny6IkgzwCaWV
=Hwx+
-----END PGP SIGNATURE-----


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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