1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Seemant Kulleen wrote: |
5 |
> If you can really show some way that GPL3 provides a compelling case |
6 |
> to move to it, then we can start talking about that. |
7 |
> |
8 |
|
9 |
I wasn't aware that gentoo practiced copyright assignment. You might |
10 |
want to make the disclaimers clear - if somebody submits a patch on |
11 |
bugzilla and doesn't expressly assign copyright they would legally |
12 |
retain it unless it were a clear condition of using the site. Also, it |
13 |
would help avoid people submitting patches that aren't |
14 |
GPL-2-only-compatible from other projects. But then again, I'm not a |
15 |
lawyer... :) |
16 |
|
17 |
I guess one reason to move would be that it is the goal of the FSF for |
18 |
this to become the "default" GPL. So, if there was a compelling case |
19 |
for adopting the GPL at all (one presumes there was since we're GPL |
20 |
currently), then there is a case for migrating to GPL v3 by that virtue |
21 |
alone. Does that mean that we HAVE to? Certainly not. |
22 |
|
23 |
I'd ask the question why we're GPL at all? If the reason is because we |
24 |
generally agree with the principles of free software and copyleft, then |
25 |
the GPL v3 is only an improvement over the GPL. If we don't really like |
26 |
copyleft as an organization then it would make more sense to just adopt |
27 |
BSD, rather than stick with a copyleft license that just has a few |
28 |
loopholes in it. |
29 |
|
30 |
In terms of pros/cons with GPLv2 you'd have compatibility with GPL3 and |
31 |
GPL2+ licenses, as well as the the Affero GPL. There is of course the |
32 |
closing of the tivoization loophole, and that can be considered a pro or |
33 |
a con depending on your personal beliefs. However, if you really are |
34 |
pro-tivoization, then why use the GPL at all? |
35 |
|
36 |
Oh, there exists another option - we could also relicense as GPL2 or 3 - |
37 |
that gets rid of the "what if it changes to something bad" issue while |
38 |
allowing others to adopt the code under either license. |
39 |
-----BEGIN PGP SIGNATURE----- |
40 |
Version: GnuPG v1.4.7 (GNU/Linux) |
41 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
42 |
|
43 |
iD8DBQFGkSnKG4/rWKZmVWkRApvIAJ98Oj9+pNvRnHXYVeNAElNQ8dUeYwCfeQNN |
44 |
s0QRFW/n1ZNhZm1RabgNaQk= |
45 |
=w0HP |
46 |
-----END PGP SIGNATURE----- |