[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #9491] Submission of cgit
From: |
Sylvain Beucler |
Subject: |
[Savannah-register-public] [task #9491] Submission of cgit |
Date: |
Mon, 22 Jun 2009 21:11:46 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009061220 IceCat/3.0.11-g1 |
Update of task #9491 (project administration):
Status: None => In Progress
Assigned to: None => Beuc
_______________________________________________________
Follow-up Comment #1:
Hi,
I'm evaluating the project you submitted for approval in Savannah.
Licensing under the "GNU GPL v2 only" is problematic. Would you agree to
license your project under the "GNU GPL v2 or later"?
The reason for this is that when we 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 vX or later", we'd be happy to address them too.
I notice you cannot use "GNU GPL v3 or later", as you link with Git which is
GPLv2 only, but you can release your code under "GNU GPLv2 or later".
Also, 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.
For more information, see
http://www.gnu.org/licenses/gpl.html#howto
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.
In addition, the address of the FSF has changed, and is now:
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Please update your COPYING file.
Updated versions of the GPL can also be found at:
http://www.gnu.org/licenses/gpl.txt
If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project. Upon review, we will
reconsider your project for inclusion in Savannah.
To help us better keep track of your registration, please use the tracker's
web interface by following the link below. Do not reply directly; the
registration process is not driven by e-mail, and we will not receive such
replies.
Regards.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?9491>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/