On Jul 14, 2005, at 3:15 AM, Allison Randal wrote:
On Jul 12, 2005, at 15:59, Will Coleda wrote:
Hey, Allison - you drafted up the project plan for TPF grant for
parrot, neh?
Yup. With a good deal of input from Dan, Leo, Patrick and others.
Are you the defacto Project Manager for parrot? Or is that
position unfilled?
Indeed I am. Parrot and Perl 6. Jesse Vincent has also taken on the
role of assistant project manager lately.
Allison
MUahahahahaha, my trap has been sprung! Perfect. I've been looking
for you since before we lost Dan. =-)
Had I know this at the conference, I would have had a much longer
conversation with you. =-)
I have a .. few.. questions for you. Hopefully none of them are
*overly* snarky. Some progress has been made dealing with issues like
this since I originally started bringing them up, but I think there's
still room for improvement.
- Where is parrot's current project plan?
- Does it have any more details than the high level grant plan that
was used to fund leo?
- How does the monthly release cycle fit into this plan?
- How do we tie in the items that are in RT and docs/ROADMAP to the
plan?
- Given current "staffing" and work remaining, what is your best
guess on a 1.0 release?
And a few observations (some of which overlap)
- without a detailed description, we won't know when we're done. (The
high level plan obviously helps here, but it's not "pass this test
suite and we're done.").
- Someone I respect very much *cough* said, "but you need a bunch of
small, achievable goals". I don't think parrot currently has this. I
*think* that having a project plan will help here, but having a
project -manager- would be even better.
- RT is slow. painfully slow. And not just for leo (for whom it
should be very very fast and stay out of his way.).
- Yes, I know you can't map a corporate PM mentality onto an open
source project and have it stick. But I think there's a lot to be
used from more formal methodologies.
- The Architect is not necessarily the Project Manager. The roles
have been conflated, I think, because most people don't know parrot
has (had?) a PM.
- We need to expose the process along with the code: because of the
nature of our workforce, we need to make it much easier to pick and
choose things to work on.
- When possible, things should be on parrotcode.org; even better if
it's just something from svn-latest that's been automatically web-ified.
