I'm having a really big problem making productive contributions, help me.

I initially wrote a feature request for Catalyst::Plugin::Params::Nested. It was rudely disregarded three hours later with a blanket statement requesting a patch, and tests. I did this. It took almost a week without response for me to get the patch accepted. I had to cross post to the mailing list to get action. And, all this time I had my module on github waiting without any review .

This week, again I started with a feature request. No response, so I wrote the patch, added the tests, and fixed the pod.

Alas, my issue is with the community gatekeepers. Today, I was able to connect to IRC - I was unbanned and un-klinned - I /join irc.perl.org#catalyst, and instantly I find this

11:22 [perl] -!- You were killed by apeiron [apeiron@shadow.cat] [(and + stay dead.)] [Path: ] 11:22 [perl] -!- ERROR Closing Link: 64.200.109.13 (Killed (apeiron (a +nd stay dead.)))

I want to take this opportunity to point fingers at Matthew Trout. This guy is a despot. I'm not going to dance around the issue here. The people that are holding this ban in #perl, and irc.perl.org, are using nothing but coercion on ops. Aperion is employed by Matt. I would challenge anyone to speak to Aperion. I don't even know that guy. I don't think I've ever talked to him -- yet he mirrors Matt's actions entirely. Ask him about me, someone should dig into his reasoning. I would request that some people turn their attention to community moderation. Matt trash talks my modules and my code incessantly behind my back. He can't speak to me with a civil tone. I haven't spoke to the guy in years but I still have some mighty refreshing logs from those days.

I'm just seriously asking people weight his control and influence. When I want to contribute but I'm klinned from irc.perl.org, and #perl on irc.freenode.net you can just about expect me to fork. And, when I fork out of necessity I don't want to hear any crap about not having tried. I tried. I even got a list with four ops on freenode that agree with me. Matt is abusing his power, and his emotions don't cloud his reason -- his very personality is totally devoid of it to begin with. He simply makes for a very poor authority.

[12:58] mst &#9474; Phurl: yeah, do note that the author of +that module is banned from, well, everywhere [12:58] mst &#9474; Phurl: the guy who wrote ::ASP_NET [12:58] Phurl &#9474; what module? the asp one? [12:58] Phurl &#9474; it sux [12:58] mst &#9474; right [12:59] mst &#9474; he's a known troll [12:59] Phurl &#9474; god [12:59] Phurl &#9474; even the synopsis is bad >_< oh man, harsh. [13:00] mst &#9474; please don't think anything produced by +that fucktarded sack of shit is "normal" Moose code :)
Here he does it again, #perl Oct 6, 2010
20:46 < mst> fdaemoins: do NOT use nextgen.pm 20:46 < fdaemoins> why is that? 20:47 < mst> fdaemoins: because the author couldn't find his arse with + both hands 20:47 < mst> fdaemoins: nextgen is bsaically "Modern::Perl done very b +adly" 20:47 < fdaemoins> mst: that seems crude, care to elaborate the proble +m with the /code/, or are you suggesting we should judge the tools we + use by the authors that write them? 20:48 < fdaemoins> because I hear you're a pretty fucking big arse hol +e too. 20:48 < fdaemoins> I'm sure the author would gladly address your conce +rns. 20:49 < mst> I judge the tools by their likely future stability 20:49 < mst> since Evan is known for breaking shit with no notice, and + nextgen's enforcing of 'use Moose' onto every package is insane anyw +ay, I wouldn't go within a mile of it for production code 20:49 < fdaemoins> it's on git hub, you can fork it.. 20:50 < mst> I don't want to fork it. I want to use something written +by a competent programmer and community member in the first place. 20:50 < mst> use Modern::Perl and/or Moose and/or MooseX::Declare norm +ally 20:50 < fdaemoins> No. 20:51 < fdaemoins> Don't tell me what to do just because you hate auth +or... If you were capable of having this conversation in a sane fashi +on, you probably wouldn't have banned him from #perl to end this deba +te before it starts.


Evan Carroll
The most respected person in the whole perl community.
www.evancarroll.com

In reply to Someone take control of Magnet. by EvanCarroll

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.