I've seen various posts and actions recently which are totally the opposite. One person making a decision, no discussion to be had, despite many people with vested interests trying to point out that there are better courses of action. An example Regarding the closure of rt.cpan. Fortunately enough push back occurred and something was done about it. From what I understand based on people actually doing the work on perl core/toolchain, rather than making managerial decisions, this has been the case with a lot of the decisions made about perl7, some of the people involved commented on the HN thread linked to earlier, e.g. Christian Walde have documented the situation well. Letting people "just get on with it" isn't always the best idea.

In reply to Re^3: Pumpking resignation by marto
in thread Pumpking resignation by davies

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.