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

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

[Savannah-register-public] [task #9791] Submission of ForgePlucker


From: Nicodemo Alvaro
Subject: [Savannah-register-public] [task #9791] Submission of ForgePlucker
Date: Thu, 22 Oct 2009 21:11:56 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009090216

Follow-up Comment #2, task #9791 (project administration):

I apologize for not personalizing that pre-written note. It was an
oversight.

"ForgePlucker intends to produce simple tools to break projects out of the
data jails that too many open-source hosting sites have become."

The first sentence of your description made me think of the Open Source
movement. I do not think this is good for Savannah to refer to other sites and
Savannah itself as open-source hosting sites.

The Savannah policy on speaking of free software is in the requirements.

https://savannah.gnu.org/register/requirements.php

> To protect my code, I deem it sufficient to have a COPYING file which is 
> included by reference.  I know what the GPL FAQ says, but you should
> not inappropriately generalize that advice to other licenses.

In your script 'bugplucker.py' you have:

"This code is Copright (c) 2009 by Eric S. Raymond.  New BSD luicense
applies"

^Spelling errors. license. copyright

Karl has told me that in order to give permissions each source file needs to
have a copying permissions notice.

http://lists.gnu.org/archive/html/savannah-hackers-public/2009-10/msg00039.html

"New BSD" is vague and could refer to the many other Modified BSD licenses
when it comes out. From what I've seen in the license list, there are too many
to know which one is referred to. Sylvain claimed that the license you used is
unique.

Here are some of the many variations of the BSD license.
http://www.freebsd.org/copyright/freebsd-license.html
http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5
http://labs.metacarta.com/license-explanation.html#license

Our guidelines in the wiki state in the Other Licenses section:

"If the license is small (such as the mBSD/MIT/Expat license), instead of a
license notice, include it entirely at the top of all your files."

It was asked of you in the registration checklist when you applied if you had
placed license notices in all your files.

I hope that explains everything.

    _______________________________________________________

Reply to this item at:

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

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





reply via email to

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