licensing

[daonb]

Hi all,
The good news is all the three projects I found have a license, bad
news is they have 3 different licenses: AGPLv3, MIT and GPLv2. If we
want to exchange code we have to use compatible licenses, so I suggest
we choose a same license for all the projects.

From what I know, the license is important not just from the legal
POV, but as a declarative mean used to set the ground rules of the
community. As we clearly have different opinion about which license to
use, I asked Jacob Kaplan Moss for his opinion:

[4:27] jacobkm: daonb__: in my opnion, the Python community basically
accepts common permissive licenses, so BSD, MIT, Apache, MPL (and the
Python license, of course, but it's only applicable to Python itself).
[4:28pm] jacobkm: daonb__: of those, I think the BSD/MIT are the best
choice for users new to licensing, and the Apache and MPL licenses
good for those who understand patent clauses and why they might
matter.
[4:53pm] daonb__: jacobkm: the 3 django-gov projects I found use
GPLv2, AGPLv3 and MIT. guess two of them will have to re-license
[4:54pm] jacobkm: daonb__: look, licensing, at the root of things, a
personal choice; I don't begrudge anyone who makes different choices
than I do. But *I* am not going to use any GPL'd code in combination
with my own, and I wouldn't touch AGPL'd code with a ten foot pole.

What do you say?

Benny

[daonb]

We're growing fast - two new projects from Peter Krantz, both using
GPLv2.

We really need to decide on a common license so we can freely exchange
code.

Best,

Benny