<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://kairosnews.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>cbpp</title>
 <link>http://kairosnews.org/taxonomy/term/542/feed/%2A</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Ask not what your open source project can do for you...</title>
 <link>http://kairosnews.org/ask-not-what-your-open-source-project</link>
 <description>&lt;p&gt;I sympathize with &lt;a href=&quot;http://www.sgerald.net/?q=node/6&quot;&gt;Sharon&#039;s plight&lt;/a&gt; about Drupal documentation and &lt;a href=&quot;http://kairosnews.org/give-sharon-a-hand&quot;&gt;Clancy&#039;s concerns&lt;/a&gt;. As with many open source projects, the documentation could be much improved. That&#039;s a given that most open source projects recognize. &lt;/p&gt;
&lt;p&gt;Unfortunately, I&#039;ve seen similar observations about the need for better documentation posted to the Drupal forums many, many times. The solution to the problem is clear--many long term Drupal contributors respond to those that note the documentation problems with the best solution--but those who could provide the solution almost never do. &lt;/p&gt;</description>
 <comments>http://kairosnews.org/ask-not-what-your-open-source-project#comments</comments>
 <category domain="http://kairosnews.org/taxonomy/term/542">cbpp</category>
 <category domain="http://kairosnews.org/taxonomy/term/38">documentation</category>
 <category domain="http://kairosnews.org/taxonomy/term/85">drupal</category>
 <category domain="http://kairosnews.org/taxonomy/term/16">open source</category>
 <pubDate>Sat, 21 Apr 2007 11:00:30 -0400</pubDate>
 <dc:creator>cel4145</dc:creator>
 <guid isPermaLink="false">5053 at http://kairosnews.org</guid>
</item>
</channel>
</rss>
