Merging network and network-bytestring: license question

Ivan Lazar Miljenovic ivan.miljenovic at gmail.com
Thu Oct 28 21:51:41 EDT 2010


On 29 October 2010 12:41, wren ng thornton <wren at freegeek.org> wrote:
> On 10/28/10 1:34 PM, Johan Tibell wrote:
>>
>> Hi,
>>
>> While looking into merging the network and network-bytestring
>> packages, I noticed that their licenses differ slightly. I've attached
>> both licenses in the end of this email for reference.
>>
>> How do I merge the two licenses? I own the copyright on
>> network-bytestring, so I could change that license to be the same as
>> the one used for network. Is this the right way to go? Is it possible
>> to move the whole resulting library to the two-clause BSD license,
>> which is more common on Hackage? Would that mean getting approval from
>> everyone who has ever contributed to the code base?
>
> Why not just stick with network's BSD3 (modifying "the university" to "the
> copyright holders" or what have you)? This is the first I've heard of the
> BSD2, is there any particular reason you wish to omit the third clause
> (thereby allowing people to use your name to promote derivative works)?

I personally think that that third clause is useless; who is really
going to bother trying to use my name to promote derivative works?

It probably doesn't matter much for Haskell code, but KDE SC software
is not allowed to be licensed under the BSD-3 license:
http://techbase.kde.org/Policies/Licensing_Policy/Draft#BSD_License

-- 
Ivan Lazar Miljenovic
Ivan.Miljenovic at gmail.com
IvanMiljenovic.wordpress.com


More information about the Libraries mailing list