X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2510" "Tue" "18" "July" "1995" "14:34:45" "-0300" "David Carlisle" "carlisle@CS.MAN.AC.UK" nil "56" "Re: latex/1600: LaTeX2e licensing terms" "^Date:" nil nil "7" nil nil nil nil] nil) Received: from MZDMZA.ZDV.UNI-MAINZ.DE (vzdmzj.zdv.Uni-Mainz.DE [134.93.8.16]) by trudi.zdv.Uni-Mainz.DE (8.6.12/8.6.12) with ESMTP id PAA16909 for ; Tue, 18 Jul 1995 15:37:47 +0200 Received: from DIRECTORY-DAEMON by MZDMZA.ZDV.UNI-MAINZ.DE (PMDF V5.0-3 #4432) id <01HT0R78E62O9BVIB5@MZDMZA.ZDV.UNI-MAINZ.DE> for schoepf@goofy.zdv.uni-mainz.de; Tue, 18 Jul 1995 15:37:35 +0100 Received: from listserv.gmd.de (listserv.gmd.de) by MZDMZA.ZDV.UNI-MAINZ.DE (PMDF V5.0-3 #4432) id <01HT0R76GE1C8WWAIK@MZDMZA.ZDV.UNI-MAINZ.DE> for schoepf@Uni-Mainz.DE; Tue, 18 Jul 1995 15:37:35 +0100 Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v0.1a) with SMTP id DD0A8270 ; Tue, 18 Jul 1995 15:37:33 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE by VM.URZ.UNI-HEIDELBERG.DE (LISTSERV release 1.8b) with NJE id 3456 for LATEX-L@VM.URZ.UNI-HEIDELBERG.DE; Tue, 18 Jul 1995 15:37:03 +0000 Received: from DHDURZ1 (NJE origin SMTP@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 7599; Tue, 18 Jul 1995 15:35:09 +0000 Received: from m1.cs.man.ac.uk by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with TCP; Tue, 18 Jul 1995 15:35:07 +0100 (CET) Received: from r8h.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL5l) id AA04910; Tue, 18 Jul 1995 14:34:47 -0300 (BST) In-reply-to: <199507181202.IAA06872@mole.gnu.ai.mit.edu> (message from Richard Stallman on Tue, 18 Jul 1995 08:02:21 -0400) Reply-to: Mailing list for the LaTeX3 project Message-id: <9507181334.AA21284@r8h.cs.man.ac.uk> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Date: Tue, 18 Jul 1995 14:34:45 -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: 1697 Richard Stallman writes: > The explicit description of the file types is a big improvement. Getting there (slowly;-) > A copyright is an abstract legal entity....... > I've reported this problem before--would you please fix it, so I > don't feel my efforts to help are being ignored? OK point noted. We should refrain from using `copyright' as a catch all for `conditions for modification/distribution'. > 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. This looks sensible to me, the wording needs to make it clear that the `complete list of exceptions' is only a complete list as far as the original LaTeX distribution is concerned. Some people may choose to distribute some other file and say it is distributed under the LaTeX distribution conditions as expressed in legal.txt. In this case of course the `complete list' may not cover this other software. This is why the list of file extensions is headed by a note that it *only* covers the standard LaTeX distribution. > If the file [cfgguide] contains advice, please delete all mention of > it from here, and mention it at the end of the section instead. It contains advice, I thought this was clear but if you need to ask then presumably it wasn't clear enough. Your proposed wording looks reasonable, but we would need to think before committing ourselves to any changes, this is just an `instant reply' to your points. > 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. Actually the current situation is that the only cfg file in the distribution has no header at all. It has my name and a date in a comment, but it was not the intention to place any legal restriction on this file, although cfgguide.tex contains some advice/instructions on the type of thing the file is intended to be used for. Again If you felt the need to ask about this then perhaps the wording was not sufficiently clear. David