You are viewing an old version of this page. View the current version.
Compare with Current |
View Page History
Zend Framework Proposal Process
If you do not have a Zend Framework account, please sign up to take full advantage of our site's features.
Developers who wish to contribute to Zend Framework should read the Zend Framework Contributors Guide for getting started pointers, issue tracker guidelines, coding standards, and more.
To submit a proposal, you must first have an account and login.
Status1. New ProposalsUnable to render {children}. Page not found: New Proposals.
2. Proposals Under ReviewUnable to render {children}. Page not found: Proposals Under Review.
3. Reviews PendingUnable to render {children}. Page not found: Reviews Pending.
4. Laboratory ProposalsUnable to render {children}. Page not found: Laboratory Proposals.
5. Incubator ProposalsUnable to render {children}. Page not found: Incubator Proposals.
6. Core Component ProposalsUnable to render {children}. Page not found: Core Component Proposals. |
ProcessImages speak more than words, so here is the process in a nutshell. More information is also available for knowing what to expect when submitting a proposal. or in the full text below.
|
Contribution Process
The first step in contributing to the Zend Framework is to validate your idea with Zend and the community. This can be done by contacting one of the Zend developers or by sending an email to the mailing list. Regardless of the channel you choose to initiate the discussion, all suggestions should be discussed on the mailing list.
When contributing the implementation for a proposal, contributors are expected to continue supporting their projects, including fixes and documentation.
After discussing your idea informally with the community, please submit a proposal. The Zend Framework Proposal Process begins by placing your proposal in the Wiki using a built-in template. Once your proposal is in, we will add an issue tracker linked from the proposal that can hold issues that need addressed derived from community and coreteam comments posted to the proposal Wiki page. The issue tracker will show the release status of the proposal with three steps: laboratory, incubator, and core. When submitting a proposal for the laboratory, first submit a Contributor License Agreement. Most proposals will make it to the laboratory once they are organized.
Once in the laboratory, you will have a SVN project, Issue tracker, and the Wiki page for the proposal to support rounding the proposal off. Documentation goes into DocBook format in SVN as normal and not in the Wiki. Although you may prototype it there, the proposal will not move into the laboratory until documentation has begun in earnest in the correct format.
Some proposals will stay in the laboratory for some time, so this gives you a good workspace with everything you need to flourish.
Once the proposal has become code, has unit testing, and reasonable docs it can move upwards and onwards if the timing is right, and the proposal is accepted into the main framework.
For proposals in incubator and core, we combine them into the main single project so that we can track the shipped framework as a whole in one place. Until then we isolate them so they have sufficient freedom to mature into successful components.