bug-wget
[Top][All Lists]
Advanced

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

Re: [Bug-wget] wget2.0 / niwt / refactoring


From: Tim Ruehsen
Subject: Re: [Bug-wget] wget2.0 / niwt / refactoring
Date: Mon, 13 Aug 2012 17:53:44 +0200
User-agent: KMail/1.13.7 (Linux/3.2.0-3-amd64; KDE/4.8.4; x86_64; ; )

Am Monday 13 August 2012 schrieb Micah Cowan:
> On 08/13/2012 02:01 AM, Tim Ruehsen wrote:
> > And now back to Micah and Niwt. How can we join forces ?
> > It should make sense to share code / libraries and  parts of the test
> > code.
> 
> It should be noted that I chose a MIT/2-clause BSD-style license for
> Niwt, so any sharing would necessarily be one-directional (towards Wget,
> not the other direction), much as it has been for the Curl project.
> 
> (I am a believer in the GPL; however, in a project made up almost
> entirely of small, trivially-rewritten programs, a BSD-style license
> made the most sense to me. If someone wants to redistribute a version
> where one component had to link against proprietary code, I didn't see
> any value in restricting that, since they could simply write a
> replacement in most cases within days. Likewise, should anyone
> distribute improvements without source code, it wouldn't take long to
> reimplement them.)

Your arguments for a BSD-style license for Niwt make sense to me.
Nevertheless, for the moment I am the only copyright holder for the Mget code. 
I could double license it or change the license for single source files.
For the moment I can't see a real reason why we shouldn't exchange code, or 
work together on at least some parts (e.g. library routines).
(The oneway problem might arise someday in the future...)

At least I am very interested to join forces while trying to respect your 
caveats.

Tim



reply via email to

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