Skip to end of metadata
Go to start of metadata

<p>This IRC Meeting is planned for 20:00 UTC on Wednesday, 16 May 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-05-16T20: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>Beta 4 Status Report </h2>

<p>What will be in beta 4? What will not make it into b4? Are there already plans for beta 5? Quick roundup (not discussion) about what has to be planned and what is already in schedule.</p>

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

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

Yes

No

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

<h2>Composer as a possible solution for autoloading in ZendSkeletonApplication</h2>

<p>In the last two weeks, Marco Pivetta (nick: ocramius) has been experimenting composer-based installations of the ZendSkeletonApplication (<a href="https://github.com/zendframework/ZendSkeletonApplication">https://github.com/zendframework/ZendSkeletonApplication</a>). Composer (<a href="http://getcomposer.org/">http://getcomposer.org/</a>) has turned out being an extremely flexible and easy to use installation method in contexts where modules share dependencies or have too many of them. GIT submodules are slow and cause the developer to focus more on autoloading than actually needed.</p>

<h4>Advantages:</h4>
<ol>
<li>simpler autoloading: `require_once 'vendor/autoload.php';` does all the work, eventually also loading ZendFramework</li>
<li>Installing modules is reduced to "requiring" them in `composer.json` and then enabling them in `config/application.config.php`</li>
<li>submodules and libraries are in sync. Conflicts between dependencies and their versions are eagerly detected by the composer installer</li>
<li>faster installation and smaller project directories (no duplication of dependencies)</li>
<li>one copy of dependencies per project. This makes your projects independent from global installations. (this is also a cons)</li>
</ol>

<h4>Disadvantages:</h4>
<ol>
<li>"freezing" the Skeleton application to a precise ZF2 revision is currently not possible until it has been tagged. This makes composer usage very tricky until RC stage is reached, and thus branch "master" in zf2 will be fairly stable.</li>
<li>yet another tool to learn? Could be simplified with a provided script in the skeleton, but it is one command more to have a running application (`git clone --recursive` vs `git clone && cd checkout-dir && ./install.sh`?).</li>
<li>one copy of dependencies per project (opcode cache troubles)</li>
</ol>

<p>Focus of discussion would be </p>
<ol>
<li>Q&A about composer functionality</li>
<li>using composer as a default for autoloading in the ZendSkeletonApplication</li>
<li>if accepted as autoloader for the skeleton application, at which point in time this should become true (see "tagging" issue at disadvantages (1)).</li>
</ol>

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

ZendSkeletonApplication with autoloading provided by Composer - Should we discuss this? (Log In to vote.)
Choices Your Vote

Yes

No

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

<h2>Rename Zend\Module to Zend\ModuleManager</h2>

<p>We have Zend\EventManager, Zend\ServiceManager (coming soon), and<br />
talks about renaming Zend\Module to Zend\ModuleManager. So my question<br />
is, if we're suffixing these with Manager, why these components? Do we<br />
also rename Zend\Cache to Zend\CacheManager, Zend\Log to<br />
Zend\LogManager, Zend\Session to Zend\SessionManager? Where do we draw<br />
the line?</p>

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

Rename ZendModule to ZendModuleManager - Should we discuss this? (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. May 16, 2012

    <p>Yesterday I did a quick test with Composer, Zend Framework and Doctrine and I must say it is quite easy and fast to setup an application.</p>

    <p>1. Install composer (getcomposer.org)<br />
    2. Create a composer.json file with the following content:</p>
    <ac:macro ac:name="code"><ac:default-parameter>xml</ac:default-parameter><ac:plain-text-body><![CDATA[
    {
    "require":

    Unknown macro: { "zendframework/zendframework"}

    }
    ]]></ac:plain-text-body></ac:macro>
    <p>3. Open a command prompt and change your working directory to the directory where composer.json is located.<br />
    4. Call "php path/to/composer.phar install"<br />
    5. You're done.</p>

    1. May 16, 2012

      <p>I was quite surprised too. I had some problems with Git submodules with DoctrineModule. With composer it was fast and easy. Plus I can quickly figure out where is Doctrine source code (whereas I had to navigate through a lot of folders before).</p>