Forgot your password?
New user?
Document Actions
Framework Team FAQ
Answers some common questions about the role of the framework team.
- Q: What does the framework team do?
- The framework team is responsible for recommending code for inclusion in a Plone release to that release's manager. In the release cycle, they drive the PLIP and bundle code review cycle. The voting members do the formal duty of collecting information from the community about bundles offered for review, and making the formal decision by voting whether to recommend them to the release manager. One member of the group is chosen from within the group as the framework team lead and is responsible for communicating all decision of the team onto the plone-devel list.
- Q: Who is on the team?
- Anyone who wants to review code and is interested in actively participating with shaping the technical vision of Plone's future. Each release, a small group in a similiar timezone is chosen to cast the actual votes on proposals (PLIP + bundle) on the advise of the larger team.
- Q: How/when are the voting members chosen?
- Currently, voting members are chosen arbitrarily on a rigorous *wink*
criterion of general interest, recent contribution, timezone and who
the former voting members thought would do a good job. As the
framework team is dedicated to evolving process, this is open to become
a more formalized democratic process.
New voting members are active after the first alpha of a new release and remain active until the first alpha of the next major release. - Q: Sounds groovy! How can I participate? (I just can't get enough e-mail from Martin...)
- Thought you would never ask... the new voting member probably
have some ideas, but here are some broad strokes that go from early in
the release cycle to late:
- Participate in / start technical discussions of possible PLIPs on plone-devel (preferably with prototype code). This also includes discussions of use-cases and end-user needs.
- Join framework-team and participate in discussions of refining development process and codification of developer best practices.
- As plips come in, help plippers make bundles and prepare their code for review.
- As bundles get ready for review, review code and report your findings to the voting members.
- take off your framework-team hat and help get that release out!
