<?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: Alfresco plans to open up</title>
	<atom:link href="http://www.contenthere.net/2008/03/alfresco-plans-to-open-up.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.contenthere.net/2008/03/alfresco-plans-to-open-up.html</link>
	<description>Enter Content Here</description>
	<lastBuildDate>Mon, 09 Aug 2010 05:40:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: NyWebGuy</title>
		<link>http://www.contenthere.net/2008/03/alfresco-plans-to-open-up.html/comment-page-1#comment-638</link>
		<dc:creator>NyWebGuy</dc:creator>
		<pubDate>Thu, 20 Mar 2008 05:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www1.contenthere.net/2008/03/alfresco-plans-to-open-up.html#comment-638</guid>
		<description>I work for Alfresco (although less than six months), and wanted to point something out.  &lt;br/&gt;&lt;br/&gt;&gt;  Because Alfresco doesn&#039;t fix the bugs in the Community Edition and Alfresco partners will not help you implement and maintain it, the Community Edition is too risky to use for most companies to consider.&lt;br/&gt;&lt;br/&gt;We do fix bugs in Community edition, more precisely, we merge in the bug fixes from the Enterprise Version.  We don&#039;t provide an SLA on that, but we do that often.  According to our pingbacks, we have tens of thousands of live systems running community, so thre is definitely value that is being delivered through the Community Version.  &lt;br/&gt;&lt;br/&gt;To clarify the distinction.  The Alfresco Community edition is where all the new features go in. Around release time, we pick a few of these to roll into enterprise, and stabilize them, putting through a rigorous QA process and making it enterprise-ready. &lt;br/&gt;&lt;br/&gt;As far as partners only working with Enterprise version, since we have stabilized it, we have higher confidence in that code base, and thus sell support services around that.  If our partners were to provide services on community, we would have a management nightmare where we would have two release trunks simultaneously.  It would also be harder to service paying customers, on which, after all, is how we make our money.  Just like you would not want to put into production beta software, we don&#039;t recommend putting community into production for large enterprise-level systems (although like I said above, many people do). &lt;br/&gt;&lt;br/&gt;The Community is supported through forums, where engineers and other technical employees, myself included, contribute regularly. &lt;br/&gt;&lt;br/&gt;I definitely think that opening up for more contributions is great.&lt;br/&gt;&lt;br/&gt;Jean</description>
		<content:encoded><![CDATA[<p>I work for Alfresco (although less than six months), and wanted to point something out.  </p>
<p>>  Because Alfresco doesn&#8217;t fix the bugs in the Community Edition and Alfresco partners will not help you implement and maintain it, the Community Edition is too risky to use for most companies to consider.</p>
<p>We do fix bugs in Community edition, more precisely, we merge in the bug fixes from the Enterprise Version.  We don&#8217;t provide an SLA on that, but we do that often.  According to our pingbacks, we have tens of thousands of live systems running community, so thre is definitely value that is being delivered through the Community Version.  </p>
<p>To clarify the distinction.  The Alfresco Community edition is where all the new features go in. Around release time, we pick a few of these to roll into enterprise, and stabilize them, putting through a rigorous QA process and making it enterprise-ready. </p>
<p>As far as partners only working with Enterprise version, since we have stabilized it, we have higher confidence in that code base, and thus sell support services around that.  If our partners were to provide services on community, we would have a management nightmare where we would have two release trunks simultaneously.  It would also be harder to service paying customers, on which, after all, is how we make our money.  Just like you would not want to put into production beta software, we don&#8217;t recommend putting community into production for large enterprise-level systems (although like I said above, many people do). </p>
<p>The Community is supported through forums, where engineers and other technical employees, myself included, contribute regularly. </p>
<p>I definitely think that opening up for more contributions is great.</p>
<p>Jean</p>
]]></content:encoded>
	</item>
</channel>
</rss>
