<?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: New leap for open source CMS vendor</title>
	<atom:link href="http://zenofnptech.org/2009/02/new-leap-for-open-source-cms-vendor.html/feed" rel="self" type="application/rss+xml" />
	<link>http://zenofnptech.org/2009/02/new-leap-for-open-source-cms-vendor.html</link>
	<description>Thoughtful and sometimes snarky perspectives on nonprofit technology</description>
	<lastBuildDate>Sun, 31 Jul 2011 12:25:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Tim Sporcic</title>
		<link>http://zenofnptech.org/2009/02/new-leap-for-open-source-cms-vendor.html/comment-page-1#comment-6402</link>
		<dc:creator>Tim Sporcic</dc:creator>
		<pubDate>Fri, 27 Feb 2009 18:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.zenofnptech.org/?p=453#comment-6402</guid>
		<description>Thanks for taking a peek, Michelle. We&#039;ve been working hard on getting the beta out the door, and have not devoted the desired level of attention on the community portal. You&#039;ll see that start to change as we approach GA. We&#039;re very much committed to having an open dialog with our users and the tech community, and we&#039;ll have the tools in place to make it happen.

The &quot;domain specific fields and rules&quot; are a broad way of saying we make use of a full-feature rules engine (Drools) along with dynamic custom field definitions. Customs fields in our platform go beyond basic key/value pairs and can define relationships between different fields, including other custom fields, along with validation rules. Couple this with the rules engine, and we can support some very sophisticated customizations without having to go in and modify code. 

I&#039;m one of the core developers on the platform. I&#039;ve only been at Orange Leap for three months now, but I came here because of the passion and vision of the management team. They &quot;get it&quot; and I&#039;m proud to be a part of it. 

Feel free to email me directly if you have any questions.
 -Tim</description>
		<content:encoded><![CDATA[<p>Thanks for taking a peek, Michelle. We&#8217;ve been working hard on getting the beta out the door, and have not devoted the desired level of attention on the community portal. You&#8217;ll see that start to change as we approach GA. We&#8217;re very much committed to having an open dialog with our users and the tech community, and we&#8217;ll have the tools in place to make it happen.</p>
<p>The &#8220;domain specific fields and rules&#8221; are a broad way of saying we make use of a full-feature rules engine (Drools) along with dynamic custom field definitions. Customs fields in our platform go beyond basic key/value pairs and can define relationships between different fields, including other custom fields, along with validation rules. Couple this with the rules engine, and we can support some very sophisticated customizations without having to go in and modify code. </p>
<p>I&#8217;m one of the core developers on the platform. I&#8217;ve only been at Orange Leap for three months now, but I came here because of the passion and vision of the management team. They &#8220;get it&#8221; and I&#8217;m proud to be a part of it. </p>
<p>Feel free to email me directly if you have any questions.<br />
 -Tim</p>
]]></content:encoded>
	</item>
</channel>
</rss>

