We?
Yes, we. One of the huge strengths of Perl (in my opinion) is the community behind it. Once you start breaking things down into "the cool kids" and "losers" (as you're doing above), that community is divided into the haves and the have nots. I think brain d foy has a good point: I don't think as many people are attempting to bully the perl6 process, but I do think that people want a more transparent view into the overall progress of the project. I count myself in the latter group.

To further expound on the problem as I perceive it, I'm going to go looking for a project summary. I'd assume that an at-a-glance summary would be located here. I'd be wrong. I'll keep looking. Only because I remember the fervor surrounding apocalypses, exegeses, and synopses when this whole thing started, I thought that that might be a good place to start looking for at least the design documents. There are eight apocalypses (number non-contiguously might I add, implying that there are some missing), six exegeses (again numbered non-contiguously), and twelve synopses (more of the same). Okay, so we don't seem to have a complete design available to the public. But maybe there's hope. Maybe there's something like this (admittedly a little out of date) for perl6. A line by line list of tasks and their associated completion. I don't think I'm that bad at searching, but I didn't find it.

How can anyone know what to work on without a list of items trying to conform to a seemingly incomplete specification? Especially when coordinating with people solely via e-mail often many timezones apart. Maybe it works for you, but it seems to me that it'd be a reciepe for miscoordination and duplication of effort. I don't mean to be hard on a purely volunteer workforce for something that I'm sure to get great utility and enjoyment out of, but that's what I (and probably a lot of others not "in the know") see. It's also hard for me to try to contribute to something that I see as being that chaotic. I want to help, I really do. The whole things seems way too overwhelming. You guys are obviously better at keeping many more balls in the air than I am. Lower the barrier to entry and not only will you help yourself in so far as becoming a little more organized and efficent, but perhaps lurkers like me will come out of the woodwork and lend a hand.

thor

The only easy day was yesterday

In reply to Re: No, "We" Don't Have to Do Anything by thor
in thread No, "We" Don't Have to Do Anything by chromatic

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.