Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!hhdist
From: jsims@vuse.vanderbilt.edu (J. Robert Sims)
Newsgroups: comp.sys.handhelds
Subject: Copyright
Message-ID: <9011291937.AA12506@vuse.vanderbilt.edu>
Date: 29 Nov 90 19:37:44 GMT
Lines: 33
To: handhelds@gac.edu
Return-path: <jsims@vuse.vanderbilt.edu>
To: handhelds@gac.edu

If somebody writes a program to be freely distributed, and does not copyright
it, another person can then sell that program for a profit, and not even give
credit to the author.  Another person might also get away with copyrighting the
program, and take all rights to distribution, etc. away from the original 
author.  

The "call me" type permissions gives the author a chance to make some money off
of a group that intends to use it for a purely commercial purpose.  Writing
software and distributing it in the public domain is a great thing for 
everyone; the whole network gets some really top notch software, and the 
author receives recognition.  If I start a company to sell TETRIS, and used
your program, without even giving you credit, wouldn't you be upset?  If 
anyone makes a profit from software, it should be the author.  Companies do
pay attention to copyrights, and you would have legal recourse against those
few that didn't.

Many of the copyrights also state that the program may not be modified, or that
modifications must be clearly marked as such.  I know that I would not want
to be blamed for someone else's defective modification to a program I wrote.
Many programs on this group can easily cause loss of memory, and possibly
damage hardware, especially the non-self contained programs.  The disclaimer of
liability also serves as a warning to users of the program.  I think that these
disclaimers are good to include, especially for the novice user encountering a
complicated program for the first time.  If a novice user loses his memory 
without being warned, he is likely to be quite upset, especially at the author.

The copyright messages really aren't that long.  They may take a significant
amount of space in a newsletter, but you might get by with one set of notations
in the back and reference the appropriate type of copyright for each article.

The real solution, of course, is to shoot all the lawyers.

Rob