the gpl
This commit is contained in:
parent
b776c58280
commit
1070277ed6
1 changed files with 2 additions and 2 deletions
|
@ -2250,7 +2250,7 @@ for some of GPLv2's terms and/or policy opposition to GPLv3's terms.
|
|||
Given this ``two GPLs world'' is reality, it makes sense to consider GPLv3 in
|
||||
terms of how it differs from GPLv2. Also, most of the best GPL experts in
|
||||
the world must deal regularly with both licenses, and admittedly have decades
|
||||
of experience of GPLv2 while the most experience with GPLv3 that's possible
|
||||
of experience with GPLv2 while the most experience with GPLv3 that's possible
|
||||
is by default less than a decade. These two factors usually cause even new
|
||||
students of GPL to start with GPLv2 and move on to GPLv3, and this tutorial
|
||||
follows that pattern.
|
||||
|
@ -2279,7 +2279,7 @@ internationalization.
|
|||
|
||||
One of lawyers' most common complaints about GPLv2 is that defined terms in
|
||||
the document appear throughout. Most licenses define terms up-front.
|
||||
However, GPL was always designed both as a document that should be easily
|
||||
However, the GPL was always designed both as a document that should be easily
|
||||
understood both by lawyers and by software developers: it is a document
|
||||
designed to give freedom to software developers and users, and therefore it
|
||||
should be comprehensible to that constituency.
|
||||
|
|
Loading…
Reference in a new issue