m0 team plan

Hi all.  Thanks for taking an interest in helping produce a spec and implementation for M0.  Now that there's a stub pdd in the m0-spec branch of parrot.git, here's how I'd like to make it into something implementable and useful.

I split the pdd into several sections that describe the various aspects of M0, e.g. memory model, types, ops, etc.  Over the next couple weeks I'd like to get volunteers from among you all to adopt individual topics and propose what those aspects of M0 should look like.  Adopting a topic doesn't mean you're on your own, just that you'll take the lead in researching and writing something that will make a good starting point for further discussion.  I'd be disappointed if some aspects of M0 didn't spill over into #parrot and parrot-dev.

Consider this a loose organization.  Anyone is free to improve any part of the design when they feel they have something useful to add.  It's important to eventually reach something stable, but throwing a random idea into the pdd (with a note that it's a random idea) is just fine.  Please, however, focus primarily on ideas that you expect to see in the first prototype of the M0 VM.  Pie in the sky features that we want to see in Parrot 6.0 should until we have a working prototype.

I'd also like to start a regular (weekly at first) conference call to discuss the week's work.  My plan is for this to be a time for high-bandwidth discussion so that we can efficiently discuss the week's accomplishments, improve the spec and assign topics for the next week.  If this process goes well I'd also like to use it to get a full spec for Lorito.

Thanks for participating.  I'm excited to finally turn M0 and Lorito into a reality.

Christoph