Picking a license

Ed Keith e_d_k at yahoo.com
Thu May 13 21:37:31 EDT 2010


--- On Thu, 5/13/10, Brendan Abel <007brendan at gmail.com> wrote:

> From: Brendan Abel <007brendan at gmail.com>
> Subject: Re: Picking a license
> To: python-list at python.org
> Date: Thursday, May 13, 2010, 7:30 PM
> While I think most of the
> disagreement in this long thread results
> from different beliefs in what "freedom" means, I wanted to
> add, that
> most of the responses that argue that the MIT license
> permits the user
> more freedom than the GPL, suffer from the broken window
> fallacy.
> This fallacy results from the short-sided-ness of the user
> base, as it
> is only considering the first generation of derivative
> works.
> 
> I agree, that under an MIT license, the first generation of
> derivative
> works have more freedom.  But any extra freedom gained
> here comes at
> the direct expense of all future generations of derivative
> software.
> 
> Under a GPL license, it is true that the first generation
> will have
> less freedom to distribute their software as they would
> like.  But it
> also ensures that all subsequent generations of derivative
> works have
> the freedom to access all previous derivative works.
> 
> I also want to add that I think the GPL v3 has exceeded
> this
> fundamental concept.  GPL v2 really embodies this
> meaning of "freedom".
> -- 
> http://mail.python.org/mailman/listinfo/python-list

I ALWAYS give my client my source code. But I do not want to bind them to the requirements of the GPL, I want them to be free do do what they want with the program, so I never incorporate any GPLed code in my projects.

   -EdK

Ed Keith
e_d_k at yahoo.com

Blog: edkeith.blogspot.com





      



More information about the Python-list mailing list