Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!ico!isis!aburt
From: aburt@isis.UUCP (Andrew Burt)
Newsgroups: comp.sources.d
Subject: Re: Copyrights, again (Was: Re: v22i001:  RFC 931 TCP Authentication server, Part01/02)
Message-ID: <3551@isis.UUCP>
Date: 7 May 90 04:03:13 GMT
References: <2467@litchi.bbn.com> <15122@s.ms.uky.edu> <1696@utoday.UUCP>
Reply-To: aburt@isis.UUCP (Andrew Burt)
Organization: Math/CS, University of Denver
Lines: 25

In article <1696@utoday.UUCP> greenber@.UUCP (Ross M. Greenberg) writes:
>"If you don't like it, don't use it."  You are on the other end of the
>food chain, Sean, as a consumer and not as a producer.

In general:

Copyrights and other flame war fodder aside, but "the customer is always
right" is a prudent attitude to take.

In specific:

Perhaps an agreeable solution would be to place the LONG copyright
notice at the END of the file, with a one line pointer to it at the
beginning.  (Same for revision histories, etc.)

Some of us do read code at 2400 bps or slower, and the copyright doesn't
add anything to enjoyment of code (it detracts) and moving it to the end
won't fail to prevent any illegal acts that having it at the front would.

DEC, Berkeley, etc., are you listening?
-- 
Andrew Burt 				   			uunet!isis!aburt
								or aburt@du.edu

                            "Kwyjibo on the loose!"