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

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

[Savannah-register-public] [task #5250] Submission of phoenix


From: Sebastian Wieseler
Subject: [Savannah-register-public] [task #5250] Submission of phoenix
Date: Mon, 13 Feb 2006 13:13:31 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Update of task #5250 (project administration):

                  Status:                    None => Need Info              
             Assigned to:                    None => kickino                

    _______________________________________________________

Follow-up Comment #1:

Hi,
I'm evaluating the project you submitted for approval in Savannah.


At first, "phoenix" is an invalid name, that's why the nowadays "firefox" is
know as "firefox" and not as "phoenix", because "phoenix" is used in
proprietary software I think. CMIIW.

So please change the project name.



At second, 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 GPL v3,
it will be important for all GPL-covered programs to advance to GPL v3.
If you don't put this in the files now, the only way to port your program to
GPL v3 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 v2 or later", we'd be happy to address
them too.



If you would like to inform yourself about GPLv3 have a look at
http://gplv3.fsf.org/ there you find all information about the new version of
the GPL.



Furthermore please include a (perhaps temporary) URL pointing to the source
code.
The description you gave when registering will not be read by the general
public.
If you are still concerned with privacy, however, you can forward the code to
me by email.

We wish to review your source code, even if it is not functional, to catch
potential legal issues early.

For example, to release your program properly under the GPL you must include
a copyright notice and
permission-to-copy statements at the beginning of every file of source code. 
This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch
potential omissions such as these.



Regards,



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?func=detailitem&item_id=5250>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

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