<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Eclipse Helios in the News</title>
	<atom:link href="http://aniszczyk.org/2010/06/25/eclipse-helios-in-the-news/feed/" rel="self" type="application/rss+xml" />
	<link>http://aniszczyk.org/2010/06/25/eclipse-helios-in-the-news/</link>
	<description>work. life. open source. diatribes.</description>
	<lastBuildDate>Fri, 03 Feb 2012 17:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Scott</title>
		<link>http://aniszczyk.org/2010/06/25/eclipse-helios-in-the-news/comment-page-1/#comment-2045</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 25 Jun 2010 22:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://aniszczyk.org/?p=2565#comment-2045</guid>
		<description>Andrew is right, of course...that it takes different (not less) skills to right good documentation, examples, tutorials, etc.  &lt;br&gt;&lt;br&gt;My comment is that whatever the skills required, the actual application of those skill requires one thing:  project resources (people time == $$).  If the commercial members continue to starve the &#039;commons&#039; EF projects for resources (i.e. that they don&#039;t own, but they depend upon), this simply cannot improve.  &lt;br&gt;&lt;br&gt;Putting additional/other &#039;requirements&#039; on committers and contributors won&#039;t work...because requirements mean nothing if the problem is that there is no visible means of support for anyone&#039;s time</description>
		<content:encoded><![CDATA[<p>Andrew is right, of course&#8230;that it takes different (not less) skills to right good documentation, examples, tutorials, etc.  </p>
<p>My comment is that whatever the skills required, the actual application of those skill requires one thing:  project resources (people time == $$).  If the commercial members continue to starve the &#39;commons&#39; EF projects for resources (i.e. that they don&#39;t own, but they depend upon), this simply cannot improve.  </p>
<p>Putting additional/other &#39;requirements&#39; on committers and contributors won&#39;t work&#8230;because requirements mean nothing if the problem is that there is no visible means of support for anyone&#39;s time</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Niefer</title>
		<link>http://aniszczyk.org/2010/06/25/eclipse-helios-in-the-news/comment-page-1/#comment-2044</link>
		<dc:creator>Andrew Niefer</dc:creator>
		<pubDate>Fri, 25 Jun 2010 20:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://aniszczyk.org/?p=2565#comment-2044</guid>
		<description>Documentation is real work that takes real time.  The last time I worked on a commercial product, there were people whose full time job was writing documentation.  When documentation is written by the developers you then have a trade off with writing code.&lt;br&gt;&lt;br&gt;It takes a different skill set to write good documentation, I think fixing this for real requires contributors who focus on the documentation.</description>
		<content:encoded><![CDATA[<p>Documentation is real work that takes real time.  The last time I worked on a commercial product, there were people whose full time job was writing documentation.  When documentation is written by the developers you then have a trade off with writing code.</p>
<p>It takes a different skill set to write good documentation, I think fixing this for real requires contributors who focus on the documentation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

