... a single person is able to chase away one of the most capable persons in our community.

That's a very selective reading of things. I explained my goals for Perl 5. I asked Rafael specific questions and offered to discuss technical details and to accept any correction for mistakes I've made.

What should I have done differently?

{Picking} on a release schedule or backwards compatability is not nice when you compare a project that has built up a huge history against a project that has no real production uses yet.

Plenty of other projects have regular release schedules and deprecation cycles, including the Linux kernel, OpenBSD, Fedora, Ubuntu, GNOME, Wine, and Samba. I chose to discuss Parrot and Rakudo because I work on those projects and feel more qualified discussing my personal experiences there than on projects to which I do not contribute regularly.

Some people obviously missed the respect for Raphael's decisions. He was chosen to make them.

If I recall correctly, he replaced hv, who resigned under some pressure (most of it not public) for not releasing a new version of Perl.

In reply to Re^3: When comment turns into disaster by chromatic
in thread When comment turns into disaster by Tux

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.