Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!wuarchive!texbell!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.sources.d Subject: Re: What does "free" mean, eh? (Re: Scareware) Message-ID: Date: 7 Mar 90 15:34:53 GMT References: <14010@s.ms.uky.edu> <125816@midas.UUCP> <635@magnus.Hotline.Com> <34812@watmath.waterloo.edu> <10612@hoptoad.uucp> <18111@rpp386.cactus.org> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 26 In article <18111@rpp386.cactus.org> jfh@rpp386.cactus.org (John F. Haugh II) writes: > the only difference between FSFware and "Freeware" is you can't steal > FSFware and pretend you wrote it. that's about the only practical > difference. You can't "steal" many of my freeware programs and pretend you wrote them, but I don't require that you make any program you incorporate them in freeware as well. For example, I require that anyone using my Amiga file requestor credit me (as in, file requestor by Peter da Silva somewhere in the docs), but otherwise they're free to use it for any purpose. Other stuff I've written is completely PD, but DP and freeware aren't synonymous. FSFware, on the other hand, may not be used in commercial software (well, you can if you want... but you have to give away the source). That's a big difference. > both have their place. something small and easily re-implmentable i'd > rather do as PDware. but a large offering would certainly be FSFware. Not real freeware? > as for "donations", i believe they are happy with code contributions as > donations. They effectively *require* code contributions. Any product distributed using any FSF code must be placed under the FSF General Public License. -- _--_|\ `-_-' Peter da Silva. +1 713 274 5180. . / \ 'U` \_.--._/ "I've about decided that the net is not the place to do the right v thing. It might violate a charter somewhere ..." -- Spenser Aden