The wikibook stands to give /everyone/ with a browser a source of third party docs that don't fall under your jurisdiction and that can be changed or updated without "special access" or doc patch known-how

You make this sound like an act of rebellion against us as your oppressors, a little dramatic don't you think? And honestly, the whole "under your jurisdiction" comment and the censorship it implies is ridiculous.

You were have been banned from #moose for repeatedly being a troll and causing trouble. I personally stuck my neck out for you several times and got you unbanned but you just went right back to the same behavior that got you banned initially. Your exclusion from the community is self-inflicted, you simply pissed off the wrong people (the ones with ops).

As for access to the docs, we have Moose mirrored on github and happily accept branches from anyone as long as they are accurate and correct. Yes you need to know git in order to contribute, but this is how open source works often times. And if you really can't/don't want to go through git, we would happily accept old-school patches or even just simple corrections via the mailing list/IRC/RT.cpan (it might take longer for people to get around to applying them though).

There is no real barrier to contribution here, only one you have erected yourself through your continued troll-ish behavior.

I would still assert that it has strong assets, and that I still update it every now and then. I really like the great concentrated doc for has(),

This may very well be true, but it would be so much nicer if you would contribute to the official docs instead so that we can have one central place for this information. But alas, if you feel the need to be a martyr, go for it.

-stvn

In reply to Re^8: Resources for Moose by stvn
in thread Resources for Moose by sherab

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.