An interesting and relevant essay on this is A Group Is Its Own Worst Enemy (which I saw thanks to dws).

That said, Jarkko maintains CPAN. He lead the 5.8.0 release of Perl. It is clear that he is a member of the "core group" involved with Perl and general Perl infrastructure. It is true that if he (and other members of the core group) took Perl in directions that the users don't want to go, users would go elsewhere. But it is equally true that until users get upset enough about affairs to either join the core group, or to fork Perl, the core group fundamentally does what it thinks is right and everyone else can argue about that as long as they want to. Conversely if a group of users does get upset enough to take decisive action and succeeds, then they will wind up re-creating the same basic core/general division all over again because it is a natural dynamic for human groups as they scale.

So, given this reality, what should we conclude? Well first of all, any conversation here does not mean much unless Jarkko hears about it somehow. Second, it is quite possible that there already is a policy about this kind of thing that Jarkko already works by. Third, the single most effective feedback is direct feedback to Jarkko or (if he functions that way - and if a lot of issues do come up he hopefully does) to the relevant list of people whose discussions he pays attention to. Which probably isn't PerlMonks.

Finally, why would it be good for Jarkko (I don't meant to pick on him, what I am saying applies to anyone with a position of influence in an online community) to decide things in an open manner? Here are some of the top reasons that I see:

  1. Anything he decides gets sanity checked. A lot of obvious problems are caught immediately.
  2. The open forum provides many people who might otherwise be motivated to cause problems an opportunity to participate instead.
  3. Other list members, and archived discussions from the list take the load of responding to people about policy decisions from Jarkko's shoulders.
  4. The forum provides a way for good possible maintainers to identify themselves to Jarkko for when he wants to pass the baton on.
You will note that conspicuous by its absence is any notion of making the process more democratic. Well-run open source projects are meritocracies, not democracies. Wanting a say doesn't give you one. Decisions are made in the end by convincing the right key people, not by voting.

In reply to Re: Re: Re: Commercial Perl Mods on CPAN by tilly
in thread Commercial Perl Mods on CPAN by xanthos

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.