On one side, I see that such a book would be usefull, but I think the problems weigh much more than the benefits. On one hand, there are the copyright and quality problems. If you simply reprint posts from perlmonks, you won't have copyright problems (as anyone who posts here already implicitly agreed about the public display of the posts), but you will have clarity and quality problems. If you clean up the posts, clarify the wording etc., you will have much work to do and you will also have to ask each author if you can use his post. Or you have to modify every post so much that it isn't really the post anymore, but then you'd simply be writing yet another Camel book, and there are already enough djihads about Camel books out there.

For KMs opinion, that noone should be allowed to make money from his posts, I think that this mindset is a bit too narrow for me - if someone is able to make money from what I release freely, hey, so be it. I didn't post that stuff to make money, but I'm not restricting anybody else from trying to do so. (I'm more into the real "free" aspect of Perl than the GPL "free" aspect obviously).

In reply to (Corion) RE: Perl Monks Cookbook? by Corion
in thread Perl Monks Cookbook? by princepawn

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.