<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 01:41:51 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Book Review: Producing Open Source Software]]></title>
      <guid>http://www.phpdeveloper.org/news/16442</guid>
      <link>http://www.phpdeveloper.org/news/16442</link>
      <description><![CDATA[<p>
On the Zend Developer Zone today there's a <a href="http://devzone.zend.com/article/15328-Book-Review-Producing-Open-Source-Software">new book review</a> from <i>Keith Casey</i> covering the <i>Karl Fogel</i> book <a href="http://producingoss.com/">Producing Open Source Software</a>, a guide to organizing and running a successful open source project and its community.
</p>
<blockquote>
By the time I finished the book a few months later, it rocked my professional world and I couldn't wait to jump into the community fully and completely. To be clear, Karl's book is about the difficulties and challenges of building a team to build a project, but almost all of it is relevant in the building communities in general...
</blockquote>
<p>
He goes through some of the topics mentioned in the book and highlights three different themes that stood out to him - Political and Social Structure, Communication and one of the most difficult, Managing Volunteers. 
</p>
<blockquote>
So overall, almost every single idea struck me as both blindingly obvious and often missed. And the single best part about this entire book... about 90% of it applies to any project or technical community. Yes, I don't care if you're working on an Open Source project, an internal project, or a commercial shrink-wrapped application. You can use almost any idea from this book and apply it immediately.
</blockquote>]]></description>
      <pubDate>Wed, 08 Jun 2011 11:07:05 -0500</pubDate>
    </item>
  </channel>
</rss>
