Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d5ZB48mKYG2jsBgL" Content-Disposition: inline Return-path: <[log in to unmask]> Envelope-to: [log in to unmask] Delivery-date: Tue, 16 Jul 2002 10:56:22 +0200 Received: from pop.kundenserver.de [212.227.126.167] by localhost with POP3 (fetchmail-5.6.5) for frank@localhost (single-drop); Tue, 16 Jul 2002 11:00:15 +0200 (CEST) Received: from [134.100.9.61] (helo=rzdspc1.informatik.uni-hamburg.de) by mxng09.kundenserver.de with esmtp (Exim 3.22 #2) id 17UO7z-000260-00 for [log in to unmask]; Tue, 16 Jul 2002 10:56:15 +0200 Received: from sun.dante.de ([log in to unmask] [134.100.9.52]) by rzdspc1.informatik.uni-hamburg.de (8.12.5/8.12.5) with ESMTP id g6G8uC4Y009270 for <[log in to unmask]>; Tue, 16 Jul 2002 10:56:12 +0200 (CEST) Received: from rzdspc1.informatik.uni-hamburg.de ([log in to unmask] [134.100.9.61]) by sun.dante.de (8.12.5/8.12.5) with ESMTP id g6G8uBBn007662 for <[log in to unmask]>; Tue, 16 Jul 2002 10:56:11 +0200 (CEST) Received: from apocalypse.deadbeast.net (pcp942041pcs.cstltn01.in.comcast.net [68.57.244.226]) by rzdspc1.informatik.uni-hamburg.de (8.12.5/8.12.5) with ESMTP id g6G8u74Y009225 for <[log in to unmask]>; Tue, 16 Jul 2002 10:56:08 +0200 (CEST) Received: by apocalypse.deadbeast.net (Postfix, from userid 1000) id 3451A3D9D; Tue, 16 Jul 2002 03:56:02 -0500 (EST) Message-ID: <[log in to unmask]> Mail-Followup-To: [log in to unmask], Frank Mittelbach <[log in to unmask]> References: <[log in to unmask]> <[log in to unmask]> <[log in to unmask]> <[log in to unmask]> <[log in to unmask]> <[log in to unmask]> <[log in to unmask]> In-Reply-To: <[log in to unmask]> User-Agent: Mutt/1.4i Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) From: Branden Robinson <[log in to unmask]> To: [log in to unmask], Frank Mittelbach <[log in to unmask]> Subject: Re: Motivations; proposed alternative license (was Re: LaTeX PublicProject License, Version 1.3 (DRAFT)) Date: Tue, 16 Jul 2002 03:56:02 -0500 --d5ZB48mKYG2jsBgL CONTENT-TRANSFER-ENCODING: quoted-printable Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 15, 2002 at 11:45:52PM +0200, Frank Mittelbach wrote: > I don't have a proposition for that. but LPPL wasn't written originally (= or > ever) to enforce things legally, it was written to codify what the majori= ty of > the LATeX community understood as an important set of goals Uh, well, in that case I suggest drafting a Statement of Principles. The entire raison d'etre of a copyright license is to "enforce things legally". Perhaps you should contrain the LPPL's scope to whatever ends you want to achieve with that means. > but again, there is one major miss-statement in your sentence. we don't > restrict people from modifying files, we only ask them to do it in a way = that > is helps everybody (including them in the long run). A requirement to rename *is* a restriction. > the fact that in the "free software world" but outside LaTeX the importan= ce > of the goals aren't seen, as well as the fact that codifying those goals > improved the situation within the LaTeX community a lot makes us believe = that > our approach in that particular situation is better. You're certainly entitled to that belief, but sympathy doesn't render a license "free" under the Debian Free Software Guidelines; only its terms can do so. > i understand that there are a large number of people (who work with other= type > of free software) that do not like the fact that we preserve some rights = of > the users of LaTeX Can you enumerate what rights of the user you are preserving by forbidding them from distributing modified files without changing the filename? > It is certainly (a bit) more work to rename a file rather than to > simply change it, but while I concur with you that for stuff which is > essentially local to my environment this is fine (and thus something > like GPL or whatever is appropriate) for the benefit of LaTeX as a > freely extensible and changeable system for exchange of information it > is not. I hope you'll agree with me that this statement is a subjective analysis. > > Requirements of notification of modification in original source code a= nd > > in program diagnostic output are perfectly acceptable under the DFSG; > > badging or watermarking the generated document while forbidding the > > removal of same would not be. >=20 > sorry, you lost me. what exactly is there that would not be acceptable? Asserting intellectual property right in the output of LaTeX would not be acceptable[1]. Such an assertion would be logically required if you put some indicator of modified-LaTeX status into users' output and forbade them from removing that indicator. (This is not the same thing as requiring preservation of modification notices within a LaTeX source file, upon which the LaTeX Project presumably does have a copyright.) > > There may be other means of notifying the user that he's running a > > hot-rodded component; we'd be more than happy to work with you to think > > of some. >=20 > if you manage to do that I would have no qualms to change to different sy= stem > or license, but not if that means the user has to read through potentially > thousand of source files to find a file that makes his document work > differently on his site than on others. I'm sure there are lots of ways. One possibility that springs to mind that would not run afoul of the DFSG would be to require the existence of a "flag file" in modified distributions of LaTeX. The LaTeX engine could look for this file at some convenience stage in its execution and spew a warning to standard output or standard error[2]. I'm not a very sophisticated TeX user, but I'm in the habit of reading the warnings it gives me. I've learned to ignore overfull and underfull hboxes, but maybe real TeXperts have such self-confidence that they ignore everything. :) In any event, it's the user's responsibility to read the output the program gives him. [1] In the general case; this is of course not true when LaTeX is used to output, say, its own source code. [2] You could not forbid people from removing the code that searched for this flag file without violating clause 3 of the DFSG, but the requirement of the existence of the "flag file" in distributions of LaTeX would be unaffected, and it is pretty easy to tell people how to find such a file without involving the LaTeX executable. --=20 G. Branden Robinson | Communism is just one step on the Debian GNU/Linux | long road from capitalism to [log in to unmask] | capitalism. http://people.debian.org/~branden/ | -- Russian saying --d5ZB48mKYG2jsBgL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj0z36IACgkQ6kxmHytGonyQAQCfS/eAdWKh1YQbLA46avG87zZ8 JoIAnRZl6CzlKgjOGMY44kbv7Qwmnvnx =gqnR -----END PGP SIGNATURE----- --d5ZB48mKYG2jsBgL--