Version 1 by Ralph Schindler
on May 01, 2012 14:18.

compared with
Current by Ralph Schindler
on May 01, 2012 14:18.

(show comment)
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (27)

View Page History
{toc}
<ac:macro ac:name="toc" />

h2. Information
<h2>Information</h2>

* Date: 25 April 2012, 20:00-21:00 UTC
* [Agenda|2012-04-25 Meeting Agenda]
* Moderator: Matthew Weier O'Phinney (nickname weierophinney)
* Next meeting: 02 May 2012
<ul>
<li>Date: 25 April 2012, 20:00-21:00 UTC</li>
<li><ac:link><ri:page ri:content-title="2012-04-25 Meeting Agenda" /><ac:link-body>Agenda</ac:link-body></ac:link></li>
<li>Moderator: Matthew Weier O'Phinney (nickname weierophinney)</li>
<li>Next meeting: 02 May 2012</li>
</ul>

h2. Summary

h3. ServiceManager Proposal (Was InstanceManager, Was ServiceLocator)
<h2>Summary</h2>

(Entire log file below)
<h3>ServiceManager Proposal (Was InstanceManager, Was ServiceLocator)</h3>

Ralph Schindler, after having created both the ServiceLocator proposal and working component (renamed to Zend\ServiceManager), is offering the Zend\ServiceManager prototype as well as a sample integration in the form of a ZendSkeleton application and Zend\Mvc refactoring up for inclusion in the framework.
<p>(Entire log file below)</p>

Many quetions were asked about how ServiceManager and Zend\Di related to one another: Will SM replace DI, how will configuration work, how will we address the configuration structure issue. ralphschindler addressed each of these in the chat log below.
<p>Ralph Schindler, after having created both the ServiceLocator proposal and working component (renamed to Zend\ServiceManager), is offering the Zend\ServiceManager prototype as well as a sample integration in the form of a ZendSkeleton application and Zend\Mvc refactoring up for inclusion in the framework.</p>

It was then suggested that the component and it's impact on Zend\Mvc be broken down into two phases, the first to get the ServiceManager into the framework as a component, then in a later phase, do the Zend\Mvc refactoring. This was put to a vote, and accepted:
<p>Many quetions were asked about how ServiceManager and Zend\Di related to one another: Will SM replace DI, how will configuration work, how will we address the configuration structure issue. ralphschindler addressed each of these in the chat log below.</p>

bq. Do we accept the ServiceManager RFC?": 10 positives, 0 negatives and 2 neutrals, consensus: 10
<p>It was then suggested that the component and it's impact on Zend\Mvc be broken down into two phases, the first to get the ServiceManager into the framework as a component, then in a later phase, do the Zend\Mvc refactoring. This was put to a vote, and accepted:</p>

*tl;dr*: Zend\ServiceManager tests and library code will be completed and a pull request will be issued.
<blockquote><p>Do we accept the ServiceManager RFC?&quot;: 10 positives, 0 negatives and 2 neutrals, consensus: 10</p></blockquote>

h2. Log
<p><strong>tl;dr</strong>: Zend\ServiceManager tests and library code will be completed and a pull request will be issued.</p>

{html:output=html} <h2>Log</h2>

<ac:macro ac:name="html"><ac:parameter ac:name="output">html</ac:parameter><ac:plain-text-body><![CDATA[
<style>
pre.log {
20:49:10 &lt;weierophinney &gt; kk, folks, let's call it a day.
</pre>
{html}
]]></ac:plain-text-body></ac:macro>