The question in my mind is what does copyright law have to say on this? We certainly have some very, very strong evidence that copyright infringement has occured. By continuing to host it does that make Perl Monks an accomplice or guilty as well? Why is it everyone wants to pretend this issue does not exist? It's the proverbial elephant in the room!

Personally, I'd be curious to hear what some of our published authors such as TheDamian and merlyn think about all of this.This likely hits closer to home with them and they are likely to give better advice being more familiar (in theory) with copyright law. chromatic has already said the offending material should be removed in node 576948.

In reply to Re^3: How should Perlmonks deal with Plagiarism? (legalese) by Argel
in thread How should Perlmonks deal with Plagiarism? by liverpole

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.