Um, wouldn't these thoughts be better addressed, um, to someone potentially in a position to do something about it?

Besides, this was discussed almost two years ago. (I originally provided a link to the thread but have since unlinked it. After all, what's done is done.) Please don't get me wrong. Merlyn (and any other person involved in the process) should receive fair credit and/or compensation. The thread I didn't link to showed a number of things, including the discomfort several felt about discussing the particulars in such a public forum. While I realize you're not addressing precisely the same issue as that other discussion, I personally wonder if the two aren't more than a little related.

In any event, Camel3 has been put to bed. While changes in attribution might be made in a later edition, that seems highly unlikely. Indeed, a far wiser course of action might be to first find out if the monk in question still has issues with that and, if so, then see what (if anything) he thinks would be an appropriate response at this point in time. (Hint: there is a new version of Perl coming out RSN.)

Would it not be better to focus on trying to affect the future instead of rehashing the mistakes of the past--especially when there may be more to the story than what's been discussed publically?

--f

In reply to Re: Return Merlyn's Name to Programming Perl by footpad
in thread Return Merlyn's Name to Programming Perl by ignatz

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.