Skip to end of metadata
Go to start of metadata

<h1>Tools Supporting our Development Effort</h1>

<p>The Zend Framework team uses the following tools to support our effort:</p>

<ul>
<li><ac:link><ri:page ri:content-title="Subversion Standards" /><ac:link-body>Subversion</ac:link-body></ac:link> (SVN) - File and directory version control system. <a href="http://subversion.tigris.org">Vendor</a></li>
<li><ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[Confluence]]></ac:plain-text-body></ac:macro> - Wiki integrated with JIRA <a href="http://www.atlassian.com/software/confluence/">Vendor</a></li>
<li><a href="http://framework.zend.com/code">WebSVN</a> - SVN changeset browser, search and statistic tool.<br />
delivers a unified web-based view of source repositories with robust navigation, search, historical reporting, configurable file annotation and diff views, change-set analysis, RSS feeds. <a href="http://websvn.tigris.org/">Vendor</a></li>
<li><a href="http://framework.zend.com/issues">JIRA</a> - Bug Tracking, Issue Tracking, Project Management (same username as SVN) <a href="http://www.atlassian.com/software/jira/">Vendor</a></li>
<li>Crucible - Online peer code-review tool. <a href="http://www.cenqua.com/crucible/">Vendor</a></li>
</ul>

<p>They are either open-source or provided by companies that openly and <strong>freely</strong> promote open-source projects. We also run a variety of back-end systems such as Zend Platform, Apache, MySQL, ApacheDS and Apache Tomcat. During development we use PHPUnit for our unit testing effort.</p>

<h2>Why these tools?</h2>

<p>When we were looking at how the Zend Framework project was progressing, we found that we needed better project tracking, more features to meet our requirements and complexity, and systems that worked very well together, yet were each top of their class.</p>

<p>We decided upon these guiding goals:</p>

<ol>
<li>The toolset must make us more efficient</li>
<li>We want the best toolset available</li>
<li>We are not going to hack the toolset and write code for it</li>
<li>The issues of CLA management, tracking and use must be workable in each and every tool</li>
<li>No religion (OS, language, or other) should get in the way of meeting our requirements</li>
</ol>

<p>Then we did a scan of systems, tried many out, and went with this toolset. Pieces of it are seen all over the open-source world, and we are integrating it all as well or better than most.</p>

<h2>Why aren't these PHP tools? Or Python? Or Perl? Or ...</h2>

<p>See our guiding goals above. </p>

<p>This isn't about the language, it is about the toolset supporting our project so that we can achieve our goals. Even if something is written in PHP, the best web development language in the known universe, that doesn't mean the <strong>product</strong> written in PHP meets our requirements. And where would we draw the line if we over-wrote our requirements? Apache isn't written in PHP, neither is MySQL. So we cut this line of thinking out of the equation and found the tools for our needs.</p>

<p>We are building a framework for PHP as an open-source group and must focus on that goal. Others can focus on writing the best Wiki, the best issue tracker, and the best revision control system.</p>

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