I think that you should invest some time in documentation of the project it self, what will be much more easier to integrate new developers to the development of Parrot (in any area of the project, not only the VM or Perl6).
in reply to Time to change the (Perl 6) guard!
Today if someone get the Parrot source it doesn't know what does what, and how to work in something that it want to add or fix, and bingo, you lost some potential developer. If understand the project be a intuitive thing, we can work faster in the exactly point that we need.
For example, get the Perl5 sources, we have a lot of .c files, directories, libraries, specific OS versions, etc...
But we doesn't have a main document that exaplain what is what in the source tree! Will be much more interesting to have in the top of each .c file of the Perl CORE, some text that says, this files is for bla bla bla. We also should have some list of the pourpose of each directory of the distribution, like know that ./ext are the modules that need to be compiled, and ./jpl is just a sub project that integrates Perl and Java, etc...
For who knows Perl and hack it this is silly, we think that is easy to "hack" and look all the sources. Well, for someone that work with Perl for years, yes, is silly. But let's say that you got Perl today, for the 1st time, and want to add/change/play with the sources? A good documentation will be good, and this is what we need to do with Parrot, be able to play easier with it just from the 1st time.
Graciliano M. P.
"Creativity is the expression of the liberty".