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

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

[Savannah-register-public] [task #4411] Submission of giFTstep


From: Sebastian Wieseler
Subject: [Savannah-register-public] [task #4411] Submission of giFTstep
Date: Mon, 11 Jul 2005 20:39:06 +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 #4411 (project administration):

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

    _______________________________________________________

Follow-up Comment #1:

Hello.

At first, 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.



At second, host you project on Savannah and Sourceforge at the same time is
not allowed. You had to keep your primary development on Savannah.


At third, as you said, some files lack information about copyright and
licensing. Please include these notices.
In order to release your project properly and unambiguously under the GPL,
please place copyright notices and permission-to-copy statements at the
beginning of every file of source code.

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.

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.


At fourth, the address of the FSF has changed, and is now:

  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Please update your license notices.

Updates versions of the GPL, LGPL and GFDL can also be found at:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt

Please update the copy of the license (usually, the 'COPYING' file) in your
package as well.

You can find some background and a possible migration script at
https://savannah.gnu.org/forum/forum.php?forum_id=3766



And last, we saw that some files are copyrighted by the FSF. Where do these
files come from? If these files are owned by you, have you sign copyright
assignments to the FSF?

Regards,

    _______________________________________________________

Reply to this item at:

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

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





reply via email to

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