Well, if you talk about copying code and sneaking it into another codebase then it's not too much to ask whether you've observed the author's copyright, is it? A simple yes or no will do.

Well, the problem is that Devel::Trace does not seem to actually have a copyright or license attached to it at all. How can you honor what does not exist?

I also have to agree with Moron that you are jumping to conclusions. Open Source (IMO) has grown and flourished the way it has because people share code and knowledge freely. I think it is understood that if you release your code open source, the possibility exists that people will use it in ways you never intended, which can include "sneaking it into another code base". And if you put code up on CPAN (and it gets mirrored all over the globe) then it is ridiculous to expect that you can retain any control what so ever over that code and how it is used.

I also think you should read Moron's post a little closer.

... just copy the parts or even ideas you need from the module rather than treating its use as an all-or-nothing proposition and suddenly the developer is king again - I used that method to sneak Devel::Trace into a Q/A environment.

I am of the opinion that "just copying the parts or even ideas you need from a module" is exactly in line with the spirit of open source development. Giving credit to the original author is always good manners, however, not always possible (or advisiable) in large corporate environments (especially the politically charged ones Moron seems to be in).

In short, I think you are nitpicking, and need to take a step back.

-stvn

In reply to Re^8: Why non-core CPAN modules can't be used in large corporate environments. by stvn
in thread Why non-core CPAN modules can't be used in large corporate environments. by Moron

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.