tex4ht=new Array() ; //2007-09-27 13:05:00
tex4ht.fn1x0="
We refer to terms as “permissive terms” or “permissive licenses” if they grant relatively broad copyright permissions with few conditions and are understood to be permissive enough to allow incorporation of code into a larger work, the totality of which is governed by the more restrictive terms of the GPL. Examples of permissive licenses include the modified BSD license and the ISC license (sometimes called the 2-clause BSD license).
";
tex4ht.fn2x0="For simplicity, we refer to versions 2 and 3 of the GNU General Public License simply as “the GPL” when our observations apply to either version. In accord with longstanding free software community usage, we use “GPL’d” to mean “licensed under the GPL”.
";
tex4ht.fn3x0="Though the file-by-file method was widely adopted in the free software community during the past two decades, it is not an ideal method, because ensuring that notices remain correct imposes a heavy burden of individual file change tracking. We recommend that project leaders begin to reconsider the file-by-file approach, as it is error-prone and can lead to inadvertent copyright infringement and improper attribution. Any method that projects choose must be properly reviewed and maintained for accuracy. If the file-by-file method continues to serve as the canonical method for copyright inventory, we believe that substantial improvements are needed in the day-to-day care of the copyright and licensing notices in most projects.
";
tex4ht.fn4x0="For example, “dual licensing” is sometimes used to describe the activity of a business offering a (fee-bearing) proprietary license for a GPL’d product. Arguably this usage is a misnomer; in any event, it is entirely unrelated to our discussion here.
";
tex4ht.fn5x0="";
ol_hauto = 1;