Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!apple!agate!eris.berkeley.edu!mwm From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Newsgroups: comp.sys.amiga.tech Subject: Re: Getty/UUCICO will be Freeware Message-ID: <1989Oct28.051928.944@agate.berkeley.edu> Date: 28 Oct 89 05:19:28 GMT References: <8910262315.AA23551@postgres.Berkeley.EDU> Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44) Reply-To: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Organization: Missionaria Phonibalonica Lines: 40 In article <8910262315.AA23551@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes: < Apparently the UUCico code still has a lot of GNU code in it, < which means nobody can legally *sell* it. Matt, I'm surprised at you. The GNU Public License isn't any denser than most technical documentation, and I know you can deal with the latter. The GPL doesn't prevent you from legally selling their code. It does say that if you distribute it (no matter how, or what you charge for it), you can't prevent those who have a copy from redistributing it, and you have to be willing to make source available to everyone who got it from you (directly or indirectly; distributing source means you don't have to deal with this at all). In other words, it doesn't turn into a real commercial product very well. Doing it as shareware should work just fine. < Thus, since it is as such, and since I want to distribute Getty < with my fixed UUCico, Getty will be made Freeware. Unless your Getty has code covered by the GPL in it, bundling it with the UUCico doesn't extend the GPL to cover it. This is stated explicitly in the GPL. < By the way, I've rewritten much of UUCico... completely rewrote < the G protocol (which is an aweful protocol by the way :-( Yich). To true. < The implementation was even worse (it was the original GNU code). Actually, it was originally UUPC, which was PD.