Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Very good suggestions; I wouldn't have a problem with any of them.

I also want to strongly applaud your first "if":  [if] the evidence is irrefutable.

In the case of jesuashok and madtoperl, the evidence is irrefutable, as anyone who reads any of the pirated material will quickly see.  But I'm glad you make the point, because it might not always be so obvious, and I would hate for anyone innocent to be unjustly accused of plagiarism, just because something they posted was coincidentally close to existing code or commentary, or because they had reposted their own work here at Perlmonks.

Ironically, this is exactly what jesuashok accused TwistedRaisin of doing, in this thread in the Perl Poetry section, saying "I found this same poem in twistedraisin".   Clearly, of course, it's the same author in both cases, but such a fact might not always be so obvious, and even if we are quick to suspect plagiarism, we should be slow and methodical before accusing, lest we falsely condemn.

As far as code is concerned, it's very easy to coincidentally write similar or even identical code, especially if the code fragment is short, contains common/standard variable names, etc.  We shouldn't assume a subroutine has been pilfered, for example, just because it bears the same name as the original.

So I would urge caution in looking for plagiarism.  SamCG was appropriately careful in the way he handled his concerns about madtoperl's first poetry submission, asking simply "It's very remniscent of listen a lovely poem by Sharon Hopkins. Have you read it?"

Let's all be equally careful not to falsely accuse.


In reply to Re^2: How should Perlmonks deal with Plagiarism? by liverpole
in thread How should Perlmonks deal with Plagiarism? by liverpole

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others avoiding work at the Monastery: (5)
    As of 2021-01-21 19:17 GMT
    Find Nodes?
      Voting Booth?