[Savannah-register-public] [task #10661] Submission of Gnome eXtended interface

[Mario Castelán Castro]

Update of task #10661 (project administration):

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

    _______________________________________________________

Follow-up Comment #4:

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

2010-10-23 in GNU Savannah task #10661: "Submission of Gnome eXtended
interface".

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
gxinterface-20101023.tar.bz2 (SHA256:
6dfd5f2072d284a723f6015570baade5747339acbf59498678ebb05ef5df5434).

Some non-code text files don't contain their licensing information
inside, but there is a README which covers them, however, the README
don't contains the "or any later version" clause.  Could you please
include it?

The reason for this is that when the Free Software Foundation publish
the next version of the GPL, it will be important for all GPL-covered
programs to advance to that new version.  If you don't put this in the
files now, the only way to port your program to the next version of
the GPL would be to ask each and every copyright holder, and that may
be very difficult.

We can explain the issue in more detail if you wish. If you have
concerns about "GNU GPL v3 or later", we'd be happy to address them
too.

Note: The README file is only _required_ for those files which can't
contain this information inside.  Usually text files contain their
Copyright & licensing information inside and every file which don't is
listed individually in the README.  For instance:
http://git.savannah.gnu.org/cgit/emacs.git/plain/etc/images/README.
However it's ok to list in README files which alredy contain their
licensing information inside, but that's optional.

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

Please fix the above issue 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 single top directory
named "TARNAME-VERSION" 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.

At your option we can continue the registration process in the (D)VCS
repository of your choise.  This means I would approve the project
just now provided you agree to fix any remaining or further issue (If
any) as soon as possible.

I will close this task when I can check all is ok but please bear in
mind you must follow the hosting requirements as long as you do use
GNU Savannah, independently of how the registration process is
finished.

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

Regards

Item status changes:

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

iEYEAREIAAYFAkzDZs4ACgkQZ4DA0TLic4g6HACfWZSOvlBGAVGvIpv2jJ7VakMO
TxMAmwbbg75MFN4GNrHGuN1LL0yUdJ0r
=1ofg
-----END PGP SIGNATURE-----


    _______________________________________________________

Reply to this item at:

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

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