> well I believe this is actually theft.. if you lift a source > directory from your employer and it magically becomes part of > an OSS project (or your own proprietary project) without > their permission then you have really stolen the code..
... snip ... To debate this issue effectively, one needs to get stuck into semantics (just a little). The biggest problem I have with responding to your argument is with the use of the word "theft". It's the same misnomer that has been pushed by the record industry for the past few years. If we talk in real terms like copyrights, trademarks, patents, contracts and licences, then there is a legal context. All that aside, I think I do see your point anyway, but can't respond without assuming some things. Correct me if I'm wrong, but it comes down to the distinction between what constitutes IP (which is lacking legal context in itself) and what doesn't. There are ideas, skills, source code, algorithms and blurry lines in between. Point in case ... "if you lift a source directory from your employer and it magically becomes part of an OSS project" That is almost certainly copyright violation, probably as a direct result of violating an employment contract. That is, of course, unless the employer permits it (then it isn't as magic). If you learn a technique to _do_ something, then I think that is a skill that belongs to you, in your head. (We might be entering the evil, murky patent territory here, run for it!) Still not a lawyer, - Rog -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
