Picking a license

Delaney, Timothy (Tim) tdelaney at avaya.com
Thu May 20 18:42:56 EDT 2010


From: Ben Finney

> This thread is already off-topic and too long. I'm conflicted about my
role in that;
> I have endeavoured only to address falsehoods that IMO were not
otherwise being addressed.
>
> So I'll try to keep this brief.
>
> Ethan Furman <ethan at stoneleaf.us> writes:
>
>> This doesn't make sense to me, but I'm willing to learn -- how do you

>> do this in practice? Are you really selling the software
>
> Perhaps in private email we can discuss what you mean by "really
selling the software";
> it's too off-topic here. By my understanding of that term, yes, I am
selling software.
>
>> or rather selling things like setup, support, new code (or time to 
>> code), etc?
>
>All of the above, depending on the project.

Considering that's one of the only two interesting things that have come
out of this
discussion, if you're willing to discuss that in public (in another
thread) I'd be very
interested in reading it.

BTW, the other interesting thing is the inadvertent license violations
where I tend to
think Pat has the right interpretation, but am not sure.

For the record, I tend to be in favour of permissive licenses both for
releasing my own
code and using others' (not least because I am employed by a company and
it makes my work
easier), but there are good reasons for using any license so long as you
understand the
consequences of your decision.

Tim Delaney



More information about the Python-list mailing list