Return-Path: owner-LDP-L@cornell.edu
Received: from listproc.mail.cornell.edu (LISTPROC.MAIL.CORNELL.EDU [132.236.56.14]) by keos.cs.Helsinki.FI (8.6.10/H46) with ESMTP id HAA05537 for <LARS.WIRZENIUS@CS.HELSINKI.FI>; Tue, 25 Jul 1995 07:01:19 +0300
Received: from localhost.mail.cornell.edu (localhost [127.0.0.1]) by listproc.mail.cornell.edu (8.6.9/8.6.9) with SMTP id XAA00979; Mon, 24 Jul 1995 23:58:35 -0400
Received: from cornell.edu (cornell.edu [132.236.56.6]) by listproc.mail.cornell.edu (8.6.9/8.6.9) with SMTP id XAA00944 for <LDP-L@listproc.mail.cornell.edu>; Mon, 24 Jul 1995 23:58:06 -0400
Received: (from daemon@localhost) by cornell.edu (8.6.9/8.6.9) id AAA22470 for LDP-L@listproc.mail.cornell.edu; Tue, 25 Jul 1995 00:00:27 -0400
Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by cornell.edu (8.6.9/8.6.9) with SMTP id AAA22456 for <ldp-l@cornell.edu>; Tue, 25 Jul 1995 00:00:25 -0400
Received: from cleon.cc.gatech.edu (root@cleon.cc.gatech.edu [130.207.9.12]) by burdell.cc.gatech.edu (8.6.12/8.6.9) with ESMTP id AAA22743 for <ldp-l@cornell.edu>; Tue, 25 Jul 1995 00:00:22 -0400
Received: (from gregh@localhost) by cleon.cc.gatech.edu (8.6.10/8.6.9) id WAA24870 for ldp-l@cornell.edu; Mon, 24 Jul 1995 22:01:47 -0400
Message-Id: <199507250201.WAA24870@cleon.cc.gatech.edu>
Date: Mon, 24 Jul 1995 22:01:47 -0400 (EDT)
Reply-To: LDP-L@cornell.edu
Sender: owner-LDP-L@cornell.edu
From: gregh@cc.gatech.edu (Greg Hankins)
To: Linux Documentation Project writers  <LDP-L@cornell.edu>
Subject: HOWTO copyrights
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-To: ldp-l@cornell.edu
X-PH: V4.1@cornell.edu (Cornell Modified) 
X-Mailer: ELM [version 2.4 PL24 PGP2]
X-Listprocessor-Version: 7.2(a) -- ListProcessor by CREN
Content-Length: 3139
Status: RO
X-Status: 

This is mainly for the HOWTO authors:

I have been talking with Adam privately about the HOWTO copyright.
Adam said that 2 small changes made to the copyright would be
acceptable to his recent "announcement".  I'd like input from all HOWTO
authors before anything is changed (*if* anything is changed).
Although I'm still not sure I like Adam/Yggdrasil's approach to the
matter, I can't see any practical reasons not to make changes:

adam@yggdrasil.com (Adam J. Richter):
>        I see that the copyright on the HOWTO's has changed recently.
>There are two issues that would have to be resolved for the new
>copyright (#1 also applies to the old copyright):
>
>                1. The business about the "the author would like to
>                   be notified" should probably be clarified to make
>                   sure that it's clear that it's an optional request
>                   (it's OK to say that it's rude not follow the request,
>                   or exert similar non-legal social pressure).

I don't see why this can't be clarified.  Adam made the point, that if it is 
arguable that something needs to be clarified, then by definition it should be
clarified.  Adam is concerned that it be made clear that there is no legal 
obligation to notify authors of any distribution of works.

adam@yggdrasil.com (Adam J. Richter):
>                2. The business about not be able to add further
>                   restriction would have to include something like
>                   "except for restrictions contained in the GNU
>                   General Public License as published by the
>                   Free Software Foundation (Cambridge, MA)" to
>                   ensure that howto excerpts can always be integrated
>                   into GPL'ed code.  Other than that, the "restriction
>                   on restrictions" is OK.
>
>        For example, the GPL requires that distribution of object
>code can only be done with source code or with certain arrangements
>for providing the source code.  This is a non-issue for plain text,
>but if excerpts are incorporated into code it becomes relevant.  It
>also becomes relevant in typesetting systems that border on being
>programming languages.  There are probably other examples.  By
>simply pointing to the GPL when refering to the allowable minimum
>restrictions, you are granting the minimum set of additional rights
>that is needed.
>
>        Just to be clear: I'm not asking you to add these restrictions
>to the HOWTO's, just allow them to be added in derivative works.

Another small change could easily be made to incorporate this into the
current copyright.  Again, I don't see any practical reason not to do this.

What do you think?

Greg
(HOWTO coordinator)

-- 
Greg Hankins (greg.hankins@cc.gatech.edu)  |  Georgia Institute of Technology
Computing and Networking Services          |  College of Computing, room 213
+1 404 853 9989                            |  Atlanta, GA 30332-0280 
<A HREF="http://www.cc.gatech.edu/staff/h/Greg.Hankins/">Greg Hankins</A>
<A HREF="http://www.cc.gatech.edu/staff/h/Greg.Hankins/pubkey.asc">PGP key</A>
