> The sticking point seems to be that they want permission to re- > license the code themselves, namely under the PSF license. We want to > make it easy to give them this permission when the time comes. How to > best go about doing this I'm not totally sure, but choosing an > acceptable license is a step in the right direction.
You can simply use a contributor agreement which stipulates a conditional dual-license condition which activates if/when Cython ever becomes a standard Python module. This is pretty trivial to put together, and will prevent the need to track down all the contributors over Cython's history and get permission from them later. Given such an agreement, there would be no limitation to Cython's current license, so long as it's free software. _______________________________________________ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
