home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!mintaka.lcs.mit.edu!hal.gnu.ai.mit.edu!gfm
- From: gfm@hal.gnu.ai.mit.edu (George Francis McBay)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: C-NET
- Message-ID: <1992Sep3.231821.14381@mintaka.lcs.mit.edu>
- Date: 3 Sep 92 23:18:21 GMT
- References: <Les_Jenkins.04ct@lppl.mi.org>
- Sender: news@mintaka.lcs.mit.edu
- Organization: /etc/organization
- Lines: 20
-
- In article <Les_Jenkins.04ct@lppl.mi.org> Les_Jenkins@lppl.mi.org (Les Jenkins) writes:
- >those things and, quite personally, if I had the talent to write a bit of
- >code others would like to use and released it to the PD only to have Ken
- >cut and paste it into his commercial software, I'd be quite P.O.ed about
- >it.
-
- Not to sound like a flame, but if you DID release something like
- that as 'PD' and he used it, it would be your own damned fault, and he (Ken
- Pletzer (sp?)) or anyone else could use it however they wanted. Noone is
- fighting over the morality of what he did, as far as I can see. It is really
- anti-social to include large source chunks written by others without giving
- them credit, even if the code is PD. But if the code is 'public domain' it
- is LEGAL to do this. This whole argument stems from the fact that a good
- number of computer users cannot distinguish public domain for freely
- distributable. Even in nation magazines, they are often confused (usually
- EVERYTHING released freely is labeled 'public domain' when it shouldn't be)
- There are alternative ways to release source code, one of the best, if you
- don't want to be paid for usage, is GNU COPYLEFT, this insures that noone
- else can use your code and then charge for the resulting product. (Well, it
- at least makes that illegal...)
-