Path: chuka.playstation.co.uk!news From: Toby Hutton Newsgroups: scee.yaroze.freetalk.english Subject: Re: Plagiarism... Date: 24 Jul 1998 11:25:12 +1000 Organization: PlayStation Net Yaroze (SCEE) Lines: 26 Sender: thutton@TECH10 Message-ID: References: <35B35498.6FCD@saqnet.co.uk> <01bdb3f5$ba7178c0$f30b0a0a@Angela1.intelligent-group.com> <35b4d4f0.1141862@news.playstation.co.uk> <6p2n6l$46017@chuka.playstation.co.uk> <35B73217.7281@mdx.ac.uk> NNTP-Posting-Host: TECH10.mel.cybec.com.au X-Newsreader: Gnus v5.3/Emacs 19.34 Most of what I'll say here applies to software development in general, not just Yaroze programming. It's not an issue of whether or not to share code (of course it's great if you give out your code, that's how other people can learn!) but more an issue of giving credit where it is due. You don't have to give credit for ideas, unless they're patented I suppose. But if you're using someone else's code and they requested that you credit them, or that you allow the modified code to also be freely available, or whatever, then you should respect their request. If you're going to release your code, and you want to protect it, perhaps try reading the GPL (http://www.gnu.org/copyleft/gpl.html) and see if it suits you. It suits a lot of other people. A similar, but less restrictive licence is the BSD licence. For most people though, in the case of Yaroze code in particular, just releasing your code to the public domain (ie. *anyone* can use it for *anything*) is the easiest option and probably the best for code that is simple and the most obvious way to use the Yaroze libraries (as in a tutorial). Well, that's how I sees it. -- Toby.