Re: GPLv3 code in monotone

Am 19.05.11 19:38, schrieb Thomas Keller:
> Am 19.05.11 16:59, schrieb Zack Weinberg:
> 
> Nice to read you! :)
> 
>> I think that migration to GPLv3 remains premature at this time, and we
>> should relicense the v3 files down to v2.
> 
> +1 from me as well.
> 
> We probably need to create a patch release with this change, so
> downstream's license issues are actually reflected properly, right?
> 
> I don't want to "temporarily" make the package GPLv3 and wait for the
> next release to "downgrade" it again to GPLv2... do we actually have
> anything for a 1.0.1 release beside this? I came across a few Win32
> issues lately, but I have no time to look after them.

I have announced downstream that we relicense the two files under GPLv2+
(based on the last paragraph in Stephen's answer here
<http://article.gmane.org/gmane.comp.version-control.monotone.devel/19094>).
I asked whether it is ok to leave the sources as is for now and update
to 1.0.1 that contain the license change once we released that version.

Thomas.

-- 
GPG-Key 0x160D1092 | [email protected] | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

_______________________________________________
Monotone-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/monotone-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3Xe1kACgkQaf7NlBYNEJL4tQCfa3QWagGXTvnps0o7j2Yxx4kW
44gAoLnucSNuUg/+vAyOMRJ0JA3Tbjnt
=IwrX
-----END PGP SIGNATURE-----