View Source

<p>The below are suggested topics for the meeting occuring at 17:00 UTC on Wednesday, 17 Aug 2011. If you have additions, please edit the page to add them.</p>

<h2>Suggested format for meetings</h2>

<ul>
<li>Pulling a page from the Symfony project: <a class="external-link" href="http://symfony.com/doc/2.0/contributing/community/irc.html">http://symfony.com/doc/2.0/contributing/community/irc.html</a></li>
<li>Basically:
<ul>
<li>Post a topic, with a URL containing details, to a specific page in the wiki (alternately, information could be placed in that agenda page directly, as is being done with this one). Topics should contain specific questions and actionable items.</li>
<li>For each meeting: a doodle.com page is setup, allowing contributors to vote on topics</li>
<li>X number of topics will be chosen based on voting, each receiving Y number of minutes of discussion</li>
<li>One person is a moderator, and announces start of discussion on each topic, and ensures limit of Y is not exceeded. Also, that person records decisions and/or actionable items discovered during the meeting.</li>
<li>Logs are posted within 24 hours of the meeting and a link provided to the mailing list (and potentially the ZF2 blog)</li>
</ul>
</li>
<li>Decisions:
<ul>
<li>Does the above proposal meet the needs of contributors?</li>
<li>How many minutes do we meet?</li>
<li>How many minutes per-item, and how many items per meeting?</li>
</ul>
</li>
</ul>


<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{vote:Suggested format for meetings
|visibleVoters=true|locked=true}
Yes - Let's discuss this
No - Do not discuss this
{vote}]]></ac:plain-text-body></ac:macro>

<h2>ZF2 Process</h2>

<ul>
<li>Does the ZF1 process work for ZF2 development?
<ul>
<li>i.e., write proposal, get community feedback, post to CRT, get recommendation, proceed</li>
<li>Do existing practices continue to apply? E.g. coding standards, testing and<br />
documentation requirements, etc.</li>
</ul>
</li>
<li>Should proposals (if we're doing them) be done in the main ZFPROP namespace, or in ZFDEV2, or somewhere else?</li>
<li>Do refactors need proposals?</li>
<li>Should maintainers indicate when/where they are refactoring?</li>
<li>How do we handle orphaned components?</li>
</ul>


<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{vote:Does the ZF1 process work for ZF2 development?
|locked=true}
Yes - Let's discuss this
No - Do not discuss this
{vote}]]></ac:plain-text-body></ac:macro>

<h2>Milestones</h2>

<ul>
<li>We identified the following milestones early:
<ul>
<li>Autoloading &amp; Plugin Loading <ac:link><ri:page ri:content-title="DONE" /></ac:link></li>
<li>Exceptions <ac:link><ri:page ri:content-title="DONE" /></ac:link></li>
<li>Testing <ac:link><ri:page ri:content-title="In Progress" /></ac:link></li>
<li>MVC <ac:link><ri:page ri:content-title="In Progress" /></ac:link></li>
<li>Documentation <ac:link><ri:page ri:content-title="In Progress" /></ac:link></li>
<li>I18n/L10n <ac:link><ri:page ri:content-title="?" /></ac:link></li>
</ul>
</li>
<li>Are these still relevant?</li>
<li>Do we need additional milestones? Can we remove any?</li>
<li>Should we break any of these into more fine-grained items?
<ul>
<li>E.g., potentially break MVC into &quot;core HTTP functionality&quot;, &quot;HTTP client&quot;, &quot;Routing&quot;, &quot;Front Controller and Dispatcher&quot;, &quot;Common Action Controller functionality&quot;, &quot;Server components&quot;, etc.</li>
<li>or would those be considered &quot;sub-tasks&quot; of that milestone?</li>
</ul>
</li>
<li>How do we want to track progress on each milestone and set of tasks/subtasks?
<ul>
<li>JIRA's !GreenHopper product looks interesting</li>
<li>Manually via a wiki page? or via tasks in JIRA?</li>
</ul>
</li>
</ul>


<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{vote:Milestones
|locked=true}
Yes - Let's discuss this
No - Do not discuss this
{vote}]]></ac:plain-text-body></ac:macro>