compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (30)

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

h2. Information
<h2>Information</h2>

* Date: 26 October 2011, 17:00-18:00 UTC
* [Agenda|2011-10-26 Meeting Agenda]
* Moderator: Matthew Weier O'Phinney (nickname weierophinney)
* Next meeting: [Wednesday, 9 November 2011, 17:00 UTC|2011-11-09 Meeting Agenda]
<ul>
<li>Date: 26 October 2011, 17:00-18:00 UTC</li>
<li><ac:link><ri:page ri:content-title="2011-10-26 Meeting Agenda" /><ac:link-body>Agenda</ac:link-body></ac:link></li>
<li>Moderator: Matthew Weier O'Phinney (nickname weierophinney)</li>
<li>Next meeting: <ac:link><ri:page ri:content-title="2011-11-09 Meeting Agenda" /><ac:link-body>Wednesday, 9 November 2011, 17:00 UTC</ac:link-body></ac:link></li>
</ul>

h2. Summary

h3. ACL / RBAC
<h2>Summary</h2>

There have been some calls to either remove Zend\Acl, replace it, or add an alternative. The discussion centered around these questions, and goals for ACLs in ZF2.
<h3>ACL / RBAC</h3>

* Zend\Acl certainly works now, but should be refactored to use SPL data structures, interfaces, and iterators internally, target for beta3 at the latest.
* Eventually (v2.1) an alternative RBAC implementation should be developed, but we need a comprehensive proposal. Ralph says if we do the refactor, getting RBAC behavior out of what we have may be relatively easy.
<p>There have been some calls to either remove Zend\Acl, replace it, or add an alternative. The discussion centered around these questions, and goals for ACLs in ZF2.</p>

h3. RFC vs Proposal
<ul>
<li>Zend\Acl certainly works now, but should be refactored to use SPL data structures, interfaces, and iterators internally, target for beta3 at the latest.</li>
<li>Eventually (v2.1) an alternative RBAC implementation should be developed, but we need a comprehensive proposal. Ralph says if we do the refactor, getting RBAC behavior out of what we have may be relatively easy.</li>
</ul>

This was raised last minute by Mike Willbanks (nickname lubs), out of some confusion regarding the difference between proposals and RFCs.

* Rewrite/refactor of existing components, or new architecture == RFC, New component == Proposal
* lubs asked about Service components... Matthew says, 'I think with that stuff, it may be good enough to simply throw out on the ML and on the wiki, "Hey, I'm working on this" and do it in a branch of your own.'
* DASPRiD will email the CR-Team to organize a meeting to discuss timelines and processes. (done)
** Matthew: "we _need_ to get the proposal process working again. It's halted right now."
* We will reach out to current proposal authors to update their proposals for 2.0.
* robertbasic proposes we make the CR teams work more transparent / visible, "say, a digest blog post + ML thread once in a while"
<h3>RFC vs Proposal</h3>

h3. Module Installation / Distribution
<p>This was raised last minute by Mike Willbanks (nickname lubs), out of some confusion regarding the difference between proposals and RFCs.</p>

This conversation centered around Evan Coury's (nickname EvanDotPro) [module distribution and installation RFC|RFC - Module Installation and Distribution].
<ul>
<li>Rewrite/refactor of existing components, or new architecture == RFC, New component == Proposal</li>
<li>lubs asked about Service components... Matthew says, 'I think with that stuff, it may be good enough to simply throw out on the ML and on the wiki, &quot;Hey, I'm working on this&quot; and do it in a branch of your own.'</li>
<li>DASPRiD will email the CR-Team to organize a meeting to discuss timelines and processes. (done)
<ul>
<li>Matthew: &quot;we <em>need</em> to get the proposal process working again. It's halted right now.&quot;</li>
</ul>
</li>
<li>We will reach out to current proposal authors to update their proposals for 2.0.</li>
<li>robertbasic proposes we make the CR teams work more transparent / visible, &quot;say, a digest blog post + ML thread once in a while&quot;</li>
</ul>

* Removal of modules should also remove application.config.php entry somehow (RFC will be updated)
* Zend is open to the idea of hosting a community module pyrus channel; details to be figured out later.
* Module installation / distribution is waiting on CLI work from robertbasic and mattcockayne (CLI will be a topic of the next meeting)

h2. Log
<h3>Module Installation / Distribution</h3>

<p>This conversation centered around Evan Coury's (nickname EvanDotPro) <ac:link><ri:page ri:content-title="RFC - Module Installation and Distribution" /><ac:link-body>module distribution and installation RFC</ac:link-body></ac:link>.</p>
{html:output=html}
<ul>
<li>Removal of modules should also remove application.config.php entry somehow (RFC will be updated)</li>
<li>Zend is open to the idea of hosting a community module pyrus channel; details to be figured out later.</li>
<li>Module installation / distribution is waiting on CLI work from robertbasic and mattcockayne (CLI will be a topic of the next meeting)</li>
</ul>


<h2>Log</h2>

<ac:macro ac:name="html"><ac:parameter ac:name="output">html</ac:parameter><ac:plain-text-body><![CDATA[
<style>
pre.log {
Oct 26 17:53:29 &lt;weierophinney&gt; We're approaching 18:00 UTC, so we should wrap up
</pre>
{html}
]]></ac:plain-text-body></ac:macro>