I'd really like to see people start turning the existing design documents into story cards and programmer tests for Perl 6. That'll make it much easier to implement the thing.
So basically go back through the existing Apoc/Exeg's and break it down into a long list of features. Then start building tests for each feature.
I'll give this some thought.
Design decisions have to be broken into individual tasks at some point. Sure, some of them will change as we go along. There's enough there that can be implemented now, though, without waiting for the big thud of specifications. There's plenty of useful work to go around.
Running test cases are *much* easier to implement against than anything else.
(Hey, it's been working fairly well on the Perl XP Training Wiki: http://xptrain.perl-cw.com/).
-- c
