|P is for Practical|
I was speaking specifically to the idea that the world outside the Perl community needs the marketing.
You seem to think that all (or most of) the Perl 6 contributors come from the Perl community. That doesn't match my experience. About a third of the people in #perl6 who voice their interest in helping with Perl 6 don't know perl 5 (or the community) very well.
A core of tutorials and projects could go miles to getting the mid-level devs like me more engaged. It would be a huge amount of work for whoever took it on though and it might be early even for that.
I've started with the documentation work with the 5 to 6 blog series, and now a Perl 6 book (work in progress) (together with others). I'd love to get more feedback on either, or ideas for good examples to use.
(Off-topic: finding good (short, instructive, non-contrived and practical examples is quite hard, and takes up much time).
From a technical point of view, the time for porting modules to Perl 6 has almost come. Pure perl modules that don't rely much on IO work fine. For example I ported Date::Simple to Perl 6 in about a day - no huge difficulties due to missing features or stability.
For modules that mostly implement algorithms, now is actually a good time :-)
But you're right, for the average Perl 5 hacker it's probably too much effort right now, due to missing docs and module infrastructure.
Perl 6 - links to (nearly) everything that is Perl 6.
In reply to Re^8: A wholly inadequate reply to an Anonymous Monk