On Wed, Dec 2, 2009 at 12:03 PM, Patrick R. Michaud <[email protected]> wrote: > I'm very worried about this part of the proposal -- I think the > issues we have at present are too large to be adequately addressed > in a 1-hour IRC meeting next week. Preparing the roadmap at PDS 2008 > took us a lot longer than that (1.5 days of in-person meetings), and > I think many of the issues today -- especially with respect to possible > policy and procedure changes -- will need as much discussion this > year as they did then.
We should schedule something for sometime. Everybody is constrained and even with the convenience of IRC over in-person meetings it's going to be hard to schedule anything that's much longer than 1 hour that the majority of our interested devs will be able to attend. If 1 hour at #ps time is not sufficient (and I don't argue this point), then how long do you suggest it will take? > Speaking a little more broadly, I think that holding planning meetings > /after/ a supported release is getting things in the wrong sequence. > When a supported release is issued, we should _already_ have our detailed > plan in place for the next supported release, so that we're sure to have > included any deprecations that are likely to occur and so that the > Parrot user community knows what to expect in the next supported release. +1 from me. --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
