--- On Mon, 7/12/10, Jake b wrote:
> I'm starting a new python code
> project. What license do you suggest? I
> am searching, but I'm not finding a simple comparison of
> licenses. So
> I don't know which to use. Maybe MIT or Apache or LGPL or
> BSD?
>
> Are there certain licenses to avoid using
On Mon, 12 Jul 2010 17:00:22 -0500, Jake b wrote:
> I'm starting a new python code project. What license do you suggest? I
> am searching, but I'm not finding a simple comparison of licenses. So I
> don't know which to use. Maybe MIT or Apache or LGPL or BSD?
http://www.dwheeler.com/essays/gpl-co
Jake b writes:
> I want:
> 1] Pretty much let anyone use it. Users do not have to include source
> code, as long as I get credit. (which I think normallly is a textfile
> with project url + name?)
The simplest effective license that requires nothing more that
attribution is “under the terms of t
On Mon, Jul 12, 2010 at 6:00 PM, Jake b wrote:
> I'm starting a new python code project. What license do you suggest? I
> am searching, but I'm not finding a simple comparison of licenses. So
> I don't know which to use. Maybe MIT or Apache or LGPL or BSD?
Fair warning: I like and use the GPL a l
I'm starting a new python code project. What license do you suggest? I
am searching, but I'm not finding a simple comparison of licenses. So
I don't know which to use. Maybe MIT or Apache or LGPL or BSD?
Are there certain licenses to avoid using because of interaction
problems between libraries us
