Ok. Here's a plan. [0] Shortly before each stable release, we'll have a more thorough roadmap review; insure that, as a group, our priorities are pointed in a direction that will improve things for our users. We'll continue to do incremental review in parrotsketches, but these meetings will be slightly bigger, and be spread out over a day on the weekend, like our pre-release hackathons; not necessarily at a fixed time, but we'll try to get a good sample of developers online for discussion.
These workshops will be announced in advance, and we'll have a shared document we can all edit ahead of time to make sure everything folks have a concern about is on the list; discussion can occur on list, on IRC, or at the water cooler. If there is a feature that you need for your language that parrot doesn't have on the roadmap, or you think it's prioritized incorrectly, this will be your chance to speak up. These workshops will also be a great time to bring up meta-project discussions, like revisiting the support policy, or even foundation issues. While a major component of them will have to be online, by the very nature of our community, hopefully we can sneak the occasional one in at a YAPC, supplementing the virtual meeting with a partial one with actual physical people. =-) I've created a spreadsheet on google docs at: https://spreadsheets.google.com/ccc?key=0Ahm1zTZwW0VHdFVPSW1BemVEZU82RkFrZDZ5cTdtYXc&hl=en Please login, update it; it's a community document! Having pinged a few people, we're going to target December 13th for the first workshop day - this is in advance of the 2.0 release and will give us a little time to insure that any deprecation notices or announcements needed for that release are available, and will allow us to include pointers to the shiny new roadmap. We'll plan on going over the spreadsheet, discussing items on IRC, and hopefully coming to a consensus about the plan for the upcoming stable release cycle. Please do NOT wait until then to edit the document, or mention things on list; if you have something you need parrot to be doing, get it on the list sooner than later! One big ticket, non-code item that is on the table right now is changing our support policy from a six-month stable cycle to a three month cycle: making 2.0, 2.3, 2.6 and 2.9 stable releases for the upcoming year; two of those will probably end up getting targeted for linux releases, and the more frequently release schedule as we continue to improve at a rapid pace should give some relief to language authors. Other big ticket items include "GC" and "Concurrency"; these need to be fleshed out into more concrete, achievable goals. [0] If you like it, blame chromatic and pmichaud and allison. If not, blame me. (And come up with a better plan. =-) As always, feedback welcome. -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
