Question for all, but mainly Andy:
I've been contacted by a party interested in using the Python implementation
of TT2, who requests that its copyright and licensing status be made less
ambiguous throughout the source. He suggests a LICENSE file at the top
level and a brief copyright notice in
On Sep 18, 2008, at 0:34, Sean McAfee wrote:
My first thought was to insert a notice into each Python source file
that referred to the Perl implementation, but it's probably less
than ideal to refer to Perl's license from a Python source
distribution, even indirectly. Perhaps, then, I
Hi Sean,
Perhaps, then, I should use Perl's Artistic License as my
LICENSE file, and refer to that throughout the source.
That sounds good to me. And it reminds me that I need to do the same thing
for TT. AL2 specifically, as it supercedes AL1.
