Skip to end of metadata
Go to start of metadata

<p><em>This email was sent Feb 5 2011 to both the contributors and fw-general mailinglist</em></p>

<p>Howdy!</p>

<p>Since 2007 the Zend Framework project has evolved based on proposals.<br />
The proposal process allows each community member to contribute to the<br />
Zend Framework, while ensuring that everybody from the community has a<br />
say in what the component that is being proposed should look like, and<br />
whether or not they think it can be included into the framework.</p>

<p>We, the Zend Framework Community Review Team (just call it cr-team),<br />
however notices that there are a lot of old, abandoned proposals, and<br />
recognize this diverts attention from that proposals that are actually<br />
worth a look. Therefore we have decided to archive all the seemingly<br />
abandoned proposals and have set the gauge on four months.</p>

<p>If your proposal is archived while you're still planning on putting it<br />
forward soon, you can feel free to restore it. This can be done by<br />
logging in to the wiki, edit the page (under 'page operations'), and<br />
drag the respective page to the category it should be in. This usually<br />
will be 'Ready for review' or 'New'.</p>

<p>Just as a reminder, the proposal process works as follows (guess what,<br />
it's just four simple steps <ac:emoticon ac:name="laugh" />):<br />
1. You think of a great, new, shiny component.<br />
2. You write a proposal, as long as you aren't done with that you can<br />
save it in the category 'new' (default).<br />
3. Once the proposal is ready, you can move it to 'ready for review'<br />
and announce it to the community on the mailinglists and irc<br />
(#zftalk.dev - <a class="external-link" href="http://www.zftalk.com">http://www.zftalk.com</a>).<br />
4. When that is done you can move the proposal to 'ready for<br />
recommendation', and contact us. We will then review it. After that's<br />
done, it can usually be moved to the Zend Framework Incubator,<br />
followed by trunk (don't worry, we'll guide you through that!).</p>

<p>For more details see
<a class="external-link" href="http://framework.zend.com/wiki/display/ZFPROP/Proposal+Process">http://framework.zend.com/wiki/display/ZFPROP/Proposal+Process</a></p>

<p>Please be aware that your component, if accepted, will have to meet<br />
the ZF 2 coding standards before it can be moved to trunk. This<br />
primarily means you should use namespaces, and may have to rename some<br />
classes.</p>

<p>If you have any questions based on this email or otherwise intended<br />
for the CR-Team, please send an email to zf-crteam@zend.com .</p>

<p>Kind regards,</p>

<p>On behalf of the CR-Team,</p>

<p>Dolf Schimmel<br />
– Freeaqingme</p>

<p>P.s. this e-mail was cc'ed to fw-general because not everybody may be<br />
subscribed to zf-contributors.</p>

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