This is not your regular industry project.
If you want results, look at Parrot. They've been releasing often and have been making pretty impressive progress. And judging from the mailing lists, some language implementations targetting it went from experimental to "I can't believe it but this is mostly complete" in astonishingly short time. So once there's a sketch to look at for the implementation of Perl6 I'm pretty sure it will get done much sooner than anyone looking in from the outside would expect. I assume this part of the project will have little to learn from the industry.
The Perl6 language specification part of the process on the other hand is a different kind of beast entirely. It's much more comparable with, say, a W3C TR. Not surprisingly, some of those have been known to take a while to completion as well. Fundamental design in a previously unmapped area is not something you can really plan out; in fact, Perl6 is an exception in that it does have a roadmap (that is, the Camel book chapter order).
Makeshifts last the longest.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.