X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["3365" "Wed" "19" "July" "1995" "09:47:34" "-0300" "David Carlisle" "carlisle@CS.MAN.AC.UK" "<9507190847.AA22142@r8h.cs.man.ac.uk>" "78" "Re: latex/1600: LaTeX2e licensing terms" "^Date:" nil nil "7" "1995071912:47:34" "latex/1600: LaTeX2e licensing terms" nil "<9507181334.AA21284@r8h.cs.man.ac.uk>"] nil) Received: from MZDMZA.ZDV.UNI-MAINZ.DE (vzdmzi.zdv.Uni-Mainz.DE [134.93.8.15]) by trudi.zdv.Uni-Mainz.DE (8.6.12/8.6.12) with ESMTP id KAA07318 for ; Wed, 19 Jul 1995 10:49:42 +0200 Received: from DIRECTORY-DAEMON by MZDMZA.ZDV.UNI-MAINZ.DE (PMDF V5.0-3 #4432) id <01HT1VFH3MJK9BVIVS@MZDMZA.ZDV.UNI-MAINZ.DE> for schoepf@goofy.zdv.uni-mainz.de; Wed, 19 Jul 1995 10:49:34 +0100 Received: from listserv.gmd.de (listserv.gmd.de) by MZDMZA.ZDV.UNI-MAINZ.DE (PMDF V5.0-3 #4432) id <01HT1VF0EQ6O8WWBZJ@MZDMZA.ZDV.UNI-MAINZ.DE> for schoepf@Uni-Mainz.DE; Wed, 19 Jul 1995 10:49:16 +0100 Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v0.1a) with SMTP id BED6EB89 ; Wed, 19 Jul 1995 10:49:11 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE by VM.URZ.UNI-HEIDELBERG.DE (LISTSERV release 1.8b) with NJE id 4325 for LATEX-L@VM.URZ.UNI-HEIDELBERG.DE; Wed, 19 Jul 1995 10:48:49 +0000 Received: from DHDURZ1 (NJE origin SMTP@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 9393; Wed, 19 Jul 1995 10:47:37 +0000 Received: from m1.cs.man.ac.uk by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with TCP; Wed, 19 Jul 1995 10:47:35 +0100 (CET) Received: from r8h.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL5l) id AA18353; Wed, 19 Jul 1995 09:47:35 -0300 (BST) In-reply-to: <9507181334.AA21284@r8h.cs.man.ac.uk> (message from David Carlisle on Tue, 18 Jul 1995 14:34:45 BST) Reply-to: Mailing list for the LaTeX3 project Message-id: <9507190847.AA22142@r8h.cs.man.ac.uk> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Date: Wed, 19 Jul 1995 09:47:34 -0300 (BST) From: David Carlisle Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: latex/1600: LaTeX2e licensing terms Status: R X-Status: X-Keywords: X-UID: 1699 I replied yesterday to a message of Richard Stallman's but it turns out that listserv rejected his message as he is not on the list so Richard asked me to forward his message... =========================================== The explicit description of the file types is a big improvement. I have these comments about the change. 1. Some of the things you say about "copyright" or "copyright notice" make no sense--you must be talking about something else, such as the copying conditions or the notice of copying conditions. A copyright is an abstract legal entity. It either exists for a given work or it doesn't; there aren't any other degrees of freedom. A copyright notice says "Copyright YEAR NAME" and nothing more. A file like legal.txt does not contain a copyright; it contains a statement of conditions for copying and modification. It cannot possibly be overridden by the copyright of an individual file, but could be overridden by the copying conditions of that file. I've reported this problem before--would you please fix it, so I don't feel my efforts to help are being ignored? 2. Regarding this paragraph: * It is allowed only if the copyright notice in the file does not expressly forbid it. If the section below "COPYRIGHT ON INDIVIDUAL FILES" is intended to restate this in more detail, please say so explicitly, like this: * It is allowed only if the stated conditions in the file do not expressly forbid it. See below, under "TERMS FOR INDIVIDUAL FILES", for a complete list of classes of files which are exceptions. I think that is the intention, but the fact that it isn't stated explicitly here suggests that maybe that isn't the intention. People will not feel confident they understand properly. 3. Some of this is unclear: * Files with extension `.fd'. The modification restrictions on these files are relaxed. Under certain conditions it is allowed to modify the file without changing the name. See the head of any of the .fd files for details also the documentation in cfgguide.tex has information on when it makes sense to modify or generate such files. * Files with extension `.cfg'. These files may be edited. The documentation in cfgguide.tex has information on when it makes sense to modify or generate such files. a. Does cfgguide.tex contain legal conditions, or advice? It is not really clear from this wording; mentioning the file right next to a statement about legal terms suggests that it states legal terms too, and people will wonder what they are. If the file contains advice, please delete all mention of it from here, and mention it at the end of the section instead. Say this: You can find advice about when it is useful to modify or generate .fd or .cfg files in the file cfgguide.tex. That avoids uncertainty. b. "These files may be edited" is not quite clear. Does it mean, "You have permission to modify these files as you wish as long as you preserve the copyright notice and permission notice"? If so, please say that, to be more concrete. c. "The modification restrictions on these files are relaxed" is not specific. It says that the conditions for modifying these files are more lax, but it doesn't say precisely what they are. Would you please be specific?