Skip to end of metadata
Go to start of metadata

<p>This IRC Meeting is planned for 20:00 UTC on Wednesday, 20 June 2012.</p>

<ac:macro ac:name="html"><ac:plain-text-body><![CDATA[<iframe src="http://free.timeanddate.com/countdown/i340waf4/cf12/cm0/cu4/ct0/cs0/ca0/cr0/ss0/cac000/cpc000/pcfff/tcfff/fs100/szw320/szh135/tatTime%20left%20to%20Event%20in/tac000/tptTime%20since%20Event%20started%20in/tpc000/mac000/mpc000/iso2012-06-20T20:00:00" frameborder="0" width="180" height="72"></iframe>]]></ac:plain-text-body></ac:macro>

<p>Please feel free to add topics, according to the template on the <ac:link><ri:page ri:content-title="IRC Meetings" /><ac:link-body>parent page</ac:link-body></ac:link>.</p>

<h2>Documentation</h2>
<p>It is hoped that from beta5 and beyond, we can start pulling the documentation into line. Currently there is no one person (or persons) who are ensure consistency and quality of the docs, which is particularly important for the manual.</p>

<p>Matthew has proposed a standard here: <a class="external-link" href="http://framework.zend.com/wiki/display/ZFDEV2/Proposal+for+Documentation+in+ZF2">http://framework.zend.com/wiki/display/ZFDEV2/Proposal+for+Documentation+in+ZF2</a></p>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Documentation - Should we discuss this? (Log In to vote.)
Choices Your Vote

Yes

No

]]></ac:plain-text-body></ac:macro>

<h2>Which Components to Ship</h2>
<p>Rob Allen has raised the question on the mailing list regarding which components should ship with Zend Framework 2.0 release. Defining what we are aiming for now helps to focus our efforts and gives us a clear end point to aim for. </p>

<p>Rob Allen's mailing list thread can be found here: <a class="external-link" href="http://zend-framework-community.634137.n4.nabble.com/Which-components-to-ship-td4655245.html">http://zend-framework-community.634137.n4.nabble.com/Which-components-to-ship-td4655245.html</a></p>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Which Components to Ship - Should we discuss this? (Log In to vote.)
Choices Your Vote

Yes

No

]]></ac:plain-text-body></ac:macro>

<h2>Adopting PSR-1/PSR-2 coding standards</h2>
<p>Now that PSR-1 and PSR-2 has been ratified, we should formally adopt our usage of them within ZF2. Martin Keckeis started a discussion on the mailing list thatcan be found here: <a class="external-link" href="http://zend-framework-community.634137.n4.nabble.com/PSR-1-and-PSR-2-proposel-are-out-td4649662.html">http://zend-framework-community.634137.n4.nabble.com/PSR-1-and-PSR-2-proposel-are-out-td4649662.html</a></p>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Adopting PSR-1/PSR-2 coding standards - Should we discuss this? (Log In to vote.)
Choices Your Vote

Yes

No

]]></ac:plain-text-body></ac:macro>

<h2>Replace the Plugin Broker + PluginClassLocator system with the ServiceManager</h2>
<p>Matthew has raised a topic on the mailing list requesting to replace the plugin broker system with the service manager: <a class="external-link" href="http://zend-framework-community.634137.n4.nabble.com/Proposal-replace-the-plugin-loader-with-the-service-manager-tp4655378.html">http://zend-framework-community.634137.n4.nabble.com/Proposal-replace-the-plugin-loader-with-the-service-manager-tp4655378.html</a></p>

<p>Please read the above link and come ready to discuss (and hopefully vote on) this potential change.</p>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Replace the PluginBroker with the ServiceManager - should we discuss? (Log In to vote.)
Choices Your Vote

Yes

No

]]></ac:plain-text-body></ac:macro>

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

    <p>For Documentation, I can give a quick update: Jonas Marien is already starting to update documentation for components that are currently tested and shipped to ensure they reflect new naming conventions (namespaces, class name changes, etc.). This work is in progress, and can likely benefit from more contributors.</p>

    <p>RE: PSR-1 and PSR-2: I think we should simply vote during the meeting; we're already doing most of these practices, and the only substantive change from our current CS is having a "use" statement for each import (something I've been doing in all new code anyways).</p>

    <p>RE: SM as plugin broker: based on the response in the ML, this seems like mostly a quick vote.</p>

    <p>As such, I think we should go through those three topics quickly, and then move to the "which components to ship" topic and come up with a plan for beta5 quickly.</p>