This commit is contained in:
donaldr3 2014-03-21 17:29:18 -04:00
parent b776c58280
commit 1070277ed6

View file

@ -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 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 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 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 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 students of GPL to start with GPLv2 and move on to GPLv3, and this tutorial
follows that pattern. follows that pattern.
@ -2279,7 +2279,7 @@ internationalization.
One of lawyers' most common complaints about GPLv2 is that defined terms in One of lawyers' most common complaints about GPLv2 is that defined terms in
the document appear throughout. Most licenses define terms up-front. 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 understood both by lawyers and by software developers: it is a document
designed to give freedom to software developers and users, and therefore it designed to give freedom to software developers and users, and therefore it
should be comprehensible to that constituency. should be comprehensible to that constituency.