in reply to Re^17: Why non-core CPAN modules can't be used in large corporate environments.
in thread Why non-core CPAN modules can't be used in large corporate environments.

Take the (as yet hypothetical) case we are arguing about. A corporate employee takes a piece of free software, removes the copyright and license and integrates the code into his own project. This employee has already shown supreme disregard for the original author's wishes by ignoring the (simple and easy to fulfil) requests in the license statement. Do you think said employee or his company would care if one presented a moral argument telling them that they were not being nice? I doubt that. Luckily there is a bigger stick, which is copyright law and which forces them to comply with the authors wish. Which is why I brought up legal liability (and just to be exact, "sneaking" was a quote from Morons post).
Actually, most open software licenses, including the GPL, allows you to take someones code, remove the copyright, and incorporate it in your own project.

Open software licenses put restrictions on the distribution (and legal precedence has established that 'distribution' means 'crossing the company boundary') of software. Open software licenses can't be applied to the situation you describe - they'd only get into effect if the code from that project is sold, or given away.

Perl --((8:>*
  • Comment on Re^18: Why non-core CPAN modules can't be used in large corporate environments.

Replies are listed 'Best First'.
Re^19: Why non-core CPAN modules can't be used in large corporate environments.
by tirwhan (Abbot) on Dec 08, 2005 at 09:08 UTC

    You're wrong, read section 1 and 2 of the GPL and/or talk to the FSF. If you take a piece of GPL code and copy it into your own project you are modifying the original code. Such modification is only allowed if you retain the license and original copyright notice. This is what this whole subthread is about.

    Removing the copyright is not even permissible under the BSD license, only public domain (arguably) lets you do that.


    Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan
Re^19: Why non-core CPAN modules can't be used in large corporate environments.
by Anonymous Monk on Dec 08, 2005 at 01:39 UTC
    Actually, most open software licenses, including the GPL, allows you to take someones code, remove the copyright, and incorporate it in your own project.
    I'll ignore the subtle legalities (since I'm not a lawyer), but for everyone's sanity, I'd recommend *not* just blindly stripping the license off of code you want to use, even if it will only be used internally. 'Cause it'll only lead to heartache later when a few years down the line someone else wants to distribute that code. He'll assume that the organization owns the code ("Hey, there's no copyright notices! We must have wrote it.") and he won't see that he's got obligations he has to live up to. For a good example of this, see the SCO vs. Linux thing where SCO stripped the BSD license off of some code and later forgot where it came from.