Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!husc6!purdue!spaf From: spaf@cs.purdue.EDU (Gene Spafford) Newsgroups: news.misc Subject: Changes to A Primer on How to Work With the Usenet Community Message-ID: <5931@medusa.cs.purdue.edu> Date: 30 Jan 89 07:02:41 GMT Expires: 30 Apr 89 07:02:41 GMT Organization: Dept. of Computer Sciences, Purdue Univ. Lines: 92 Supersedes: <5066@medusa.cs.purdue.edu> This posting contains a listing of differences between the version of the article (referenced in the "Subject:" line) just posted to the news.announce.newusers group, and the version posted a few weeks ago. It is intended to enable experienced users to track changes to the regularly posted Usenet documents. *** old/etiquette.n Mon Oct 10 21:55:14 1988 --- src/etiquette.n Mon Jan 30 01:27:23 1989 *************** *** 5,7 Original-from: chuq@sun.COM (Chuq Von Rospach) ! [Most recent change: 10 October 1988 by msb@sq.com (Mark Brader)] --- 5,7 ----- Original-from: chuq@sun.COM (Chuq Von Rospach) ! [Most recent change: 29 January 1989 by Mark Brader ] *************** *** 116,118 shouldn't post to groups you do not read, or post to groups you've ! only read a few articles from -- you may not be familar with the on-going conventions and themes of the group. One normally does not join --- 116,118 ----- shouldn't post to groups you do not read, or post to groups you've ! only read a few articles from -- you may not be familiar with the on-going conventions and themes of the group. One normally does not join *************** *** 206,207 Be Careful About Copyrights and Licenses --- 206,221 ----- + Check the Headers When Following Up + + The news software has provisions to specify that follow-ups to an + article should go to a specific set of newsgroups -- possibly + different than the newsgroups to which the original article was + posted. Sometimes the groups chosen for follow-ups are totally + inappropriate, especially as a thread of discussion changes with + repeated postings. You should carefully check the groups and + distributions given in the header and edit them as appropriate. If + you change the groups named in the header, or if you direct + follow-ups to a particular group, say so in the body of the message + -- no everyone reads the headers of postings. + + Be Careful About Copyrights and Licenses *************** *** 208,217 ! Once something is posted onto the network, it is effectively in the public ! domain. When posting material to the network, keep in mind that material ! that is UNIX-related may be restricted by the license you or your company ! signed with AT&T and be careful not to violate it. You should also be ! aware that posting movie reviews, song lyrics, or anything else published ! under a copyright could cause you, your company, or the net itself to be ! held liable for damages, so we highly recommend caution in using this ! material. --- 222,235 ----- ! Once something is posted onto the network, it is effectively in the ! public domain unless you own the appropriate rights (most notably, ! if you wrote the thing yourself) and you post it with a valid ! copyright notice. Of course, the *information* becomes public, so ! you mustn't post trade secrets that way. When posting material to ! the network, keep in mind that material that is UNIX-related may be ! restricted by the license you or your company signed with AT&T and ! be careful not to violate it. You should also be aware that posting ! movie reviews, song lyrics, or anything else published under a ! copyright could cause you, your company, or the net itself to be ! held liable for damages, so we highly recommend caution in using ! this material. *************** *** 276,277 Read all follow-ups and don't repeat what has already been said Be careful about copyrights and licenses --- 294,296 ----- Read all follow-ups and don't repeat what has already been said + Double-check follow-up newsgroups and distributions. Be careful about copyrights and licenses -- Gene Spafford NSF/Purdue/U of Florida Software Engineering Research Center, Dept. of Computer Sciences, Purdue University, W. Lafayette IN 47907-2004 Internet: spaf@cs.purdue.edu uucp: ...!{decwrl,gatech,ucbvax}!purdue!spaf