, though we are rather fond of them for obvious reasons.
Submitted by jkeenan on Mon, 01/03/2011 - 16:38
In my last post, On Roadmaps and Teams, Part One, I argued that the only goals we should put on our roadmap are those which:
- we, the Parrot Project as a whole, are absolutely committed to deliver; and
- for which we have a team committed to delivering those goals.
There are many things which would be great to have in Parrot, and the more developers we have, the more of them we can achieve. But roadmap goals are different from all other goals in that the Parrot Project as a whole is promising to deliver on them; and the Project has organized teams of developers working to deliver on those promises. If we can't organize a team to work on a particular goal, then that goal does not qualify for placement on the roadmap.
As I hinted at the end of my last post, I'm taking a strong stand on this because otherwise we will never create a virtual machine that other software developers will be enthusiastic about using. Note the word 'other' in the previous sentence. In this context, 'other' developers mean people who don't want to 'work on' Parrot, who couldn't care less what's 'inside' Parrot, but who want to 'use' Parrot as the basis for dynamic languages and other applications.
Submitted by jkeenan on Fri, 12/31/2010 - 01:16
I agree with most of what Christoph Otto posted earlier this month on roadmap items. But I think the relationship between roadmap items and the teams of Parrot developers who will work on those items needs a sharper focus. Here are my thoughts:
- The Parrot Developer Summit to be held on the weekend of Jan 29-30 must set roadmap items for next 4 supported releases.
- Roadmap items are those we pledge, to ourselves, our users and the world, to deliver in the specified releases on the specified dates.
- Roadmap items should therefore be few in number and have strong support among our developers. Few enough that we can under-promise and over-deliver.
- We need to draw a sharp distinction between roadmap items and everything else. Absolutely no "wishlist" or "nice to have" items may go on the roadmap. None whatsoever! There is no such thing as a "secondary" or "second-tier" roadmap item.
- Because of our high degree of commitment to roadmap items, we cannot consider anything for placement on the roadmap unless it has a team of people committed to implementing it.
So what do we mean by 'team' with respect to roadmap items?
Submitted by Whiteknight on Tue, 12/21/2010 - 17:59
On behalf of the Parrot team, I'm proud to announce Parrot 2.11.0 "At The ROFLBBQ." Parrot is a virtual machine aimed at running all dynamic languages.
Submitted by tcurtis on Tue, 11/16/2010 - 20:24
On behalf of the Parrot team, I'm proud to announce Parrot 2.10.0 "Pesquet's". Parrot is a virtual machine aimed at running all dynamic languages.
Parrot 2.10.0 is available on Parrot's FTP site, or follow the download instructions. For those who would like to develop on Parrot, or help develop Parrot itself, we recommend using Git on our source code repository to get the latest and best Parrot code.
Submitted by jkeenan on Sat, 10/23/2010 - 00:41
Last week I helped organize a gathering of Parrot developers, old and new, in Portland, OR. We shaped the discussion more around the people of the Parrot project rather than the technology or the code. Since my return to New York City my time available for Parrot has been tied up with diagnosing problems impeding Parrot's build on small resource machines. So I haven't had time to write up my reactions to the gathering.
Submitted by cotto on Tue, 10/19/2010 - 22:44
On behalf of the Parrot team, I'm proud to announce Parrot 2.9.1. Parrot
is a virtual machine aimed at running all dynamic languages.
Submitted by jkeenan on Sat, 10/16/2010 - 23:32
Summary of Pacific Northwest Parrot Developers Gathering
Saturday, October 16, 2010
Part One Discussion
Please see the list of discussion questions posted here.
Submitted by jkeenan on Sat, 10/16/2010 - 22:58
As the first of what will be multiple blog posts or posting to parrot-dev about this gathering, I am posting below the agenda I composed:
Agenda for Pacific Northwest Parrot Developers Gathering
Saturday, October 16, 2010
Lucky Labrador Brewing
915 SE Hawthorne Blvd
Portland, OR 97214
Part One, 1100-1300.
Questions for Current Parrot Developers
Submitted by jkeenan on Wed, 10/13/2010 - 03:29
I'm on vacation in the Pacific Northwest -- a vacation that has Parrot droppings all over it. The high point will be the Saturday, October 16 Pacific Northwest Parrot Developers Gathering I previously blogged about. You are welcome to drop in at Lucky Labrador Brewing, 915 SE Hawthorne Blvd, Portland OR.