Hi Framework team: I just realized that I sent this out without a very critical element: a timetable.
If we do the FWT selection as in the past, we'll set a date to close nominations, then will have a discussion and voting on a mailing list restricted to framework team members and alums who are not nominees. So, we need some agreement among those interested in participating in the selection as to when nominations should close. May I suggest we close nominations at the end of the first week of June and aim to review the nominations the next week? Discussion welcome! BTW, I'm just stepping up to facilitate the process, and will not be a voting member of the selection team. I hope there are no objections, but if there are, that's also open for discussion. ;) Steve On Sat, May 22, 2010 at 6:24 PM, Steve McMahon <[email protected]> wrote: > Plone 4.0 is on it's way, and the Plone development team is beginning > planning for future releases in the 4.x series. Would you like to help > choose what goes into Plone 4.1, 4.2 ...? > > The Plone Framework team is now receiving applications and nominations for > membership in the Plone 4.x Framework Team. > > The 4.x Framework Team will be responsible for evaluating Plone > Improvement Proposals (PLIPs) and implementations for Plone 4.1 and > subsequent +0.1s. PLIP evaluation consists of considering the benefits and > risks associated with a PLIP and casting a reasoned and explained +/- 1 vote > on each proposal. Framework Team members also follow PLIP implementation, > and make acceptance recommendations to the Release Manager. > > Qualifications include: > > - An awareness of community strategic discussions about Plone's > development; > > - Ability to make a long-term commitment. Plone 4 will be around for > some time, and we want most of the team will stay together to work on > the entire 4.x series; > > - A good understanding of Plone's architecture and UI: enough to weigh > risks and benefits of PLIPs; > > - Time to keep up with discussions on the Framework Team mailing lists; > > - The ability to occasionally budget a significant amount of time for > evaluating PLIPs or implementations in detail as deadlines approach; this > is > not as big a time sink as with a .0 release, but is still significant; you > should also be available for scheduled conference calls, as often as weekly > during the more intense periods; > > - The ability to work with SVN well enough to test PLIP integration and > implementation for final evaluation (mr.developer has lessened the need for > this, but it's the kind of skill Framework team members have); > > - The personality to get along well in a flexible, give-and-take, group > process and to accept and support group decisions. > > New Framework Team members will be chosen by existing Framework Teammembers > and involved FWT alumni. Considerations will include many criteria > beyond the simply technical. The new team must be balanced in skills and > likely to work well together. > > Please note that the Plone 4.x Framework Team will continue to work on > enhancing Plone 4.x during the development of Plone 5. > > If you're interested or would like to nominate someone, please send an > introductory note, explaining you or your nominee's interest and > qualifications, to [email protected]. Postings from > non-subscribers are rejected, so if you're not a subscriber, send your > message to [email protected] with a request for forwarding. > >
_______________________________________________ Framework-Team mailing list [email protected] http://lists.plone.org/mailman/listinfo/framework-team
