Coming up: Parrot 0.9.1 # help wanted!

[Andrew Whitworth]

On Fri, Feb 6, 2009 at 7:04 AM, kjstol <parrotcode at gmail.com> wrote:
> Tasks
> =====
> The following tasks are due for the 0.9.1 release. (the resources assigned
> to these tasks are listed in [square brackets].) Preferably, the status of
> the tasks is updated on the tasklist of the Roadmap, but any signal to me
> would suffice if that would be more convenient (and I'll update the Roadmap
> accordingly) First, there's 2 critical tasks:

For the record, I have a few spare tuits this week. I have a few misc
cleanup tasks I'm keeping occupied with and I've always got writing to
do in various books and docs, but if anybody has a project that needs
more emergency manpower, please let me know.

> No status (excluding critical):
> =====================
> * pdd26-ast, user docs (rescheduled from 0.9.0) [pmichaud,tene]
> * pdd19-pir, user docs (rescheduled from 0.9.0) [whiteknight,tene]
> * parrot user documentation, objects, pmcs, dynops, etc (rescheduled from
> 0.9.0) [allison]
> * pdd23-exceptions, describe reality, user docs, exception types [tene]
> * windows porting, windows subprocesses [allison,particle]
> * mmd & subclasses (resolve mmd tickets) [allison]
>
> Allison, particle, pmichaud, Tene, Whiteknight: what is the status of these
> tasks?

I haven't actually talked with Tene about the PDD19 task. The task is
a little vague though, what kinds of documentation do we want to have
when the smoke clears? I've been trying to add lots more PIR-related
info to docs/book/. Are we interested in maintaining docs/user/pir/*
also, or is docs/book/* sufficient? In other words: how many different
forms of PIR documentation do we want to have, and which forms are
higher-priority?

docs are also a great place for for new users to get involved, so any
lurkers reading this can feel free to jump in here and get involved.
Patches welcome!

Also, I could be very helpful with the Windows porting task, if I had
more of a clear picture about what is needed.

> Thank you very much!

kjs++

--Andrew Whitworth