taskSavannah Administration - Tasks: task #9791, Submission of ForgePlucker

 
 

task #9791: Submission of ForgePlucker

Submitter:  Eric S. Raymond <esr>
Submitted:  Thu 15 Oct 2009 04:55:55 AM UTC
   
 
Should Start On:  Thu 15 Oct 2009 04:00:00 AM UTC Should be Finished on:  Sun 25 Oct 2009 04:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  nicalvaro Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 20 Nov 2009 12:18:45 PM UTC, comment #6: 

I see you have your project hosted on GNA! I will close this application out then.

http://gna.org/projects/forgeplucker/

-Deleted Account- <nicalvaro>
Wed 04 Nov 2009 11:26:14 AM UTC, comment #5: 


> So as long as they don't remove my copyright, whether they read
> the COPYING file actually matters very little to me; anyone who
> reads "new BSD license" will know what I want without having to
> read that file.


Actually what you want seems unclear to me :(. If you are only interested in the copyright notices being preserved. I can recommend the GNU All-Permissive license. There is also the WTFPL, but I don't know exactly how to use that.

http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html

> But there's an easy solution to this "problem".  I can say "BSD
> license", include an URL to the canonical BSD license at OSI
> and remove COPYING entirely.  For your purposes, this might be
> better.


Remember that the orignal BSD License is incompatible with the GNU GPL. I can't accept that then.

What I want is compliance to ensure that the software is free software.

-Deleted Account- <nicalvaro>
Sat 31 Oct 2009 03:07:35 PM UTC, comment #4: 

It just recently clicked in my head that the big reason why we require a clear and precise license notice is that many projects have a file called COPYING and so this will create a mess when there is a project that includes your code or vice versa. Does that to you justify the need for the full modified BSD license notice? If not I still have not received your indication of why. Have you already submitted it to licensing@gnu.org?

For the record, I privately sent you the below message.

> Yes, please send me your explanation. I will send the message to
> licensing and cc you and savannah-hackers. How does that sound?
>
> There are a few things I was thinking about that to them make it
> essential to have the full license. If you see the GNU GPL license
> notice you will see that there are three things defined. There is no
> warranty, where you can get the license if it was not given to you, and
> which license the program is under. Free software allows you to copy
> any part of the code. Since the code and license are separate it's easy
> to forget to copy the license.


-Deleted Account- <nicalvaro>
Fri 23 Oct 2009 11:16:50 PM UTC, comment #3: 

You could define it differently your project differently. Why leave it to the suggestion that proprietary applications could not become free software with this application?

The term seems more ambiguous, since SourceForge and Berlios are neither under any free software license nor available for the public. Looking at what Savannah seems to call itself on the front page would suffice for everything, I think. A software forge.

So why not revise to this:

"ForgePlucker intends to produce simple tools to break projects out of the data jails that too many software forge sites have become."

This site cares about the 4 freedoms as a whole; so if you are to set software apart from the non-free you must write what best describes that. So you could switch "software forge" with "free software hosting" to be acceptable.

For the notice, Savannah wishes to play safe than sorry. Copyright is a complicated issue. If you wish to use that as your licensing notice, I was told we can ask -email is unavailable- . That will obviously take some more time though.

-Deleted Account- <nicalvaro>
Thu 22 Oct 2009 09:11:56 PM UTC, comment #2: 

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.

-Deleted Account- <nicalvaro>
Thu 22 Oct 2009 10:22:38 AM UTC, comment #1: 

Hi, I am evaluating your project.

1) Note that Savannah supports projects of the Free Software movement, not projects of the Open Source movement.

We are careful about ethical issues and insist on producing software that is not dependent on proprietary software.

While Open Source, as defined by its founders, means something pretty close to Free Software, it's frequently misunderstood.  For more information, please see
http://www.gnu.org/philosophy/free-software-for-freedom.html.

Would you be willing to speak about free software on Savannah and not open source?

2) In order to release your project properly and unambiguously under the Modified BSD License, 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-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.

-Deleted Account- <nicalvaro>
Thu 15 Oct 2009 04:55:55 AM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.


Registration Administration


While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):



Registration Details


  • Name: ForgePlucker
  • System Name:  forgeplucker
  • Type: non-GNU software & documentation
  • License: Modified BSD License (No other licenses are involved. )





Description:

ForgePlucker intends to produce simple tools to break projects out of the data jails that too many open-source hosting sites have become.  The proof of concept can recover the state of bug-trackers on Berlios or Savannah, and we expect to support that capability on Gna! and SourceForge very soon.  Over time, we will support more and more complete extraction of more sorts of project state, including repositories, mailing lists, developer permissions, task lists, and static webspace. Eventually we look forward to developing a standardized forge-to-forge project interchange format and building importers for it.


Other Software Required:

Code is pure Python with no dependencies other than the Python standard library.


Tarball URL:

http://savannah.gnu.org/submissions_uploads/foregeplucker.tar.gz


Eric S. Raymond <esr>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by nicalvaro (Posted a comment)
  • -email is unavailable- added by esr (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-11-20 nicalvaro StatusNone Cancelled
        Assigned toNone nicalvaro
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code