On 4 Apr 2013, at 18:03, Barry Warsaw <ba...@python.org> wrote: > On Apr 04, 2013, at 06:30 PM, Antoine Pitrou wrote: > >> In http://bugs.python.org/issue17618, I proposed adding a base85 >> implementation to Python. Mercurial already has one (under the GPL), so >> I wrote to the authors (Brendan Cully and Mads Kiilerich) and got their >> informal approval for relicensing and inclusion in Python. >> >> My question is the following: does anything formal need to be done to >> validate the relicensing? If yes, what? > > That's a good question. In optimism for a positive pronouncement, I'm > preparing a 4.0 version of flufl.enum, which is currently LGPLv3+. I intend > to do the next release under an ASLv2.0 license in order to be compatible with > the contributor agreement. It's too much of a PITA for me to do dual licenses > and since ASLv2.0 is GPL-compatible, that seems fine enough for me. > > Is that enough for contribution to Python? >
If the copyright is owned by you then you can donate the code to Python under the Apache license (as per the contributor agreement) *and* release it separately under *whatever* license you want. No need to change the license. Michael > -Barry > _______________________________________________ > python-committers mailing list > python-committers@python.org > http://mail.python.org/mailman/listinfo/python-committers -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
