dulwich-users team mailing list archive

[Jelmer Vernooij <jelmer@xxxxxxxxx>]

Just in case you haven't seen this: please consider relicensing your
Dulwich contributions under dual GPLv2+/Apachev2+.

Thanks!

Jelmer

On Sat, Jun 13, 2015 at 01:56:51AM +0000, Jelmer Vernooij wrote:
> Hi there,
> 
> TL;DR: Please check if you're okay with relicensing your Dulwich contributions
> to dual GPLv2+/Apachev2+ and send me a pull request removing your name from
> https://github.com/jelmer/dulwich/blob/master/relicensing-apachev2.txt
> 
> ----
> 
> You're receiving this email because you are one of the contributors to
> Dulwich (https://www.dulwich.io/).
> 
> The current license of Dulwich is GPLv2 or later. I would like to
> change that to version 2.0 of the Apache license for the following
> reasons:
> 
>  * Several permissively licensed projects that use Dulwich or
>    want to use Dulwich have indicated that the GPL is a problem
>    for them.
> 
>  * More consistent with other modules in the Python world and Python
>    itself, where permissive licenses are common
> 
> Since the Apache2 license is incompatible with the GPLv2
> (it is compatible with GPL version 3.0), we would have to dual-license
> under GPLv2 and Apache v2 license - to keep projects that depend on
> Dulwich and are GPLv2 licensed happy.
> 
> For more information, see also the issue on GitHub:
> https://github.com/jelmer/dulwich/issues/153
> 
> The current progress on the relicensing is documented at
> https://github.com/jelmer/dulwich/blob/master/relicensing-apachev2.txt
> 
> If you are be happy to relicense your contribution under dual GPLv2/Apachev2,
> then please send me a pull request on GitHub removing your name from the list
> above, or reply to this email.
> 
> My apologies for sending out another e-mail on this topic. I didn't properly keep
> track of the replies last round, and want to make absolutely sure all code
> is under the correct license.
> 
> Cheers,
> 
> Jelmer



-- 
Jelmer Vernooij <jelmer@xxxxxxxxx> -- https://jelmer.uk/