Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

particle (3326)

particle
  (email not shown publicly)

Journal of particle (3326)

Tuesday November 18, 2008
04:54 PM

Parrot Developer Summit 2008 Recap

[ #37905 ]

Much of my volunteer time over the past few weeks has been devoted to the organization of Parrot Foundation's first Parrot Developer Summit, which took place this past weekend in Mountain View, CA. Our primary objective was to write a roadmap to the release of Parrot 1.0 and beyond. Secondary objectives included review and discussion on support and release policies, updates on parrot subsystems and milestones, review of Parrot Foundation topics, and knowledge transfer between attendees.

To achieve these goals, we brought together Parrot Foundation directors, core Parrot developers and high-level language designers to spent two days in conference. During the meetings we used a number of agile techniques, and achieved amazing results. You can find our vision outlined in chromatic's journal, and further discussed in this parrot-dev mailing list thread.

Notably, a roadmap for Parrot has been made available on the parrot.org wiki, which will be updated as work progresses. This roadmap is a detailed and organized description of tasks which must be completed to achieve our goals, and it serves as an excellent place to judge the Parrot team's progress against release milestones. This document is a first for Parrot, and I hope it shows the maturity of the project team, and our commitment to meeting our published milestones. It allows our contributors to focus on the tasks remaining, and is an invaluable communication tool for the community.

Without the sponsorship of our advisory board members, the facilites provided by Google, and the support of the Parrot Foundation membership, this summit would not have been possible. Thanks all for your contributions, enthusiasm, and support.

~jerry

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.