I very much like this idea. When we look at the roadmap, it's almost comical how few priority items are listed there, and what strange items are deemed to be milestones. When we look at the 2.0 milestone for instance, I think there are a lot more items than just "testing sprint" that we should be focusing on if we expect 2.0 to be "production ready".
We're working on a schedule comprised of best guesses from over a year ago. Some items on the roadmap at PDS slipped considerably. Some fell off the roadmap entirely. Several new items need to be added. An occasional, dedicated roadmap planning meeting would go a long way towards makings sure the roadmap represents an accurate list of prioritized goals, and not just a very small arbitrary subset of obscure tickets. I don't have an opinion on the timing, whether we have an annual PDS-like meeting where we plan a year in advance or bi-annual meetings where we plan for the next stable release would both be fine. Most important is that we have something to keep us on track. --Andrew Whitworth On Wed, Dec 2, 2009 at 11:34 AM, Will Coleda <[email protected]> wrote: > Based on some discussion in IRC today, I'd like to suggest augmenting > our parrotsketch process to include more long term roadmap planning. > > Our roadmap is currently based on the Parrot Developer Summit of 2008 > with some minor modifications along the way, but I don't think we've > had had a cohesive roadmap update since then (Though we have had > several incremental updates!) > > I propose that we take the parrotsketch the week after each stable > release specifically to address the plan for the next stable release; > This won't mean that things are set in stone for the release, but it > will give us a chance to insure that we have a cohesive plan. > > Obviously, we are doing this now on a small scale every week, but > having a meeting devoted to this on a regular basis will, I think, > improve the process. We can also advertise these in advance to insure > that anyone who isn't a core committer has a chance to speak up so > that we can be sure our non-dev parrot users are heard. > > I would also recommend that we take over next week's parrotsketch for > the same type of meeting, to conduct any last minute steering in time > for 1.9 and 2.0). > > The results of these meetings should be available at > https://trac.parrot.org/parrot/roadmap (as our updates have been as we > go.); Additionally, each of the roadmap items should have supporting > docs (what's the purpose), and tickets (are we done yet?) so that our > tasks are clear and our progress is measurable. > > Feedback? > > -- > Will "Coke" Coleda > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
