Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Zend Framework Proposal Process

Unable to render {include} Couldn't find a page to include called: ZFDEV:Page Toolbar
Welcome to the Zend Framework Wiki!

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.

Please add the "milestones" section to your proposals. See example here.

Status


1. New Proposals

Unable to render {children}. Page not found: New Proposals.

2. Proposals Under Review

Unable to render {children}. Page not found: Proposals Under Review.

3. Reviews Pending

Unable to render {children}. Page not found: Reviews Pending.

4. Laboratory Proposals

Unable to render {children}. Page not found: Laboratory Proposals.

5. Incubator Proposals

Unable to render {children}. Page not found: Incubator Proposals.

6. Core Component Proposals

Unable to render {children}. Page not found: Core Component Proposals.

7. Mothballed Proposals

These proposals are superseded by other plans.

Unable to render {children}. Page not found: Mothballed Component Proposals.

Process


Images 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 under the "New Proposals" section, using a built-in template. Look for the example "Sample Zend_Magic Proposal". After the proposal review process completes, and a proposal is approved for the laboratory or the incubator, an issue tracker will be created and linked from the proposal that can hold issues. Community and coreteam comments posted to the proposal Wiki page provide the initial list of issues. The issue tracker will show the release status of the proposal with three possible "locations": laboratory, incubator, and core. Before submitting a proposal, contributors should submit a completed Contributor License Agreement.

Most proposals will make it to the laboratory once they are organized and reviewed. 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. Some proposals will stay in the laboratory for some time, so this gives you a good workspace with everything you need to flourish. In order to promote diversity of approaches in the laboratory, components approved for laboratory development will be given a name of the format: ZF_<category>_<code name>. The category name pertains to the general purpose of the component, and the code name is to distinguish it from other components having the same purpose. Class names for the components should also be named in accordance with this format.

Some proposals for which inclusion in the framework core is currently planned will enter the incubator for initial development. Documentation may be initially developed in the wiki for eventual translation to the DocBook format in SVN. Components accepted for incubation should have milestones outlining the path to achieve "release" quality. The proposed component will not be released with the framework (even as an incubator component) until documentation and unit tests have been completed. Proposed components having been approved for incubator development must be controlled for the potential of "feature creep." All new issues for incubator and core components (e.g., bug fixes, feature requests) should be entered using the issue tracker for the component.

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 framework core.

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.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.