<?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"
	>
<channel>
	<title>Comments on: Where are my features?</title>
	<atom:link href="http://blog.openx.org/06/where-are-my-features/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.openx.org/06/where-are-my-features/</link>
	<description>OpenX Community News</description>
	<pubDate>Sun, 05 Jul 2009 02:31:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Diana Sabey</title>
		<link>http://blog.openx.org/06/where-are-my-features/#comment-21530</link>
		<dc:creator>Diana Sabey</dc:creator>
		<pubDate>Sat, 15 Dec 2007 06:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/06/where-are-my-features/#comment-21530</guid>
		<description>We really appreciate the fact that you enjoy the product so much.  It's important to us that we get feedback from the community so we can add the features you want.  Openads 2.4 was an important step for stabilising the product and being able to add big features more effectively. Now that it's out, we're developing key features the community has been asking for.

We are also working on a new version of the website. The changes will make it easier for the Openads Community to be involved in deciding which features make it into the product. For example providing a clearer way to suggest, promote and discuss new product ideas.

Thanks! 
-- Diana</description>
		<content:encoded><![CDATA[<p>We really appreciate the fact that you enjoy the product so much.  It&#8217;s important to us that we get feedback from the community so we can add the features you want.  Openads 2.4 was an important step for stabilising the product and being able to add big features more effectively. Now that it&#8217;s out, we&#8217;re developing key features the community has been asking for.</p>
<p>We are also working on a new version of the website. The changes will make it easier for the Openads Community to be involved in deciding which features make it into the product. For example providing a clearer way to suggest, promote and discuss new product ideas.</p>
<p>Thanks!<br />
&#8211; Diana</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: danz</title>
		<link>http://blog.openx.org/06/where-are-my-features/#comment-20678</link>
		<dc:creator>danz</dc:creator>
		<pubDate>Tue, 11 Dec 2007 11:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/06/where-are-my-features/#comment-20678</guid>
		<description>I wanted to thank you guys for making a great product. I know you have gone though and really improved in 2.4 however some of those desired features have turned out to what prevents some of my clients from selecting openads and going with a pay alternative. I understand your looking to raise fun and was wondering if you could sell plugins for openads to bring these features the community have been asking for and charging a fair rate for them. I know if that were the case I would not have to use another app I do not believe in. Keep up the good work and hope to see those features, even if we have to pay for them!</description>
		<content:encoded><![CDATA[<p>I wanted to thank you guys for making a great product. I know you have gone though and really improved in 2.4 however some of those desired features have turned out to what prevents some of my clients from selecting openads and going with a pay alternative. I understand your looking to raise fun and was wondering if you could sell plugins for openads to bring these features the community have been asking for and charging a fair rate for them. I know if that were the case I would not have to use another app I do not believe in. Keep up the good work and hope to see those features, even if we have to pay for them!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Switzer</title>
		<link>http://blog.openx.org/06/where-are-my-features/#comment-6801</link>
		<dc:creator>Scott Switzer</dc:creator>
		<pubDate>Mon, 17 Sep 2007 16:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/06/where-are-my-features/#comment-6801</guid>
		<description>Now that we have 2.4 stable out the door, our focus is to transform Openads into a platform that is easily accessible by developers to build plugins, as well as use the data via web services in other applications.

Over the next couple of months, quite a bit of energy will be spent on the developer site (developer.openads.org).  The documents that you recomment are a great start.  Any other suggestions are welcome!

Cheers,
Scott</description>
		<content:encoded><![CDATA[<p>Now that we have 2.4 stable out the door, our focus is to transform Openads into a platform that is easily accessible by developers to build plugins, as well as use the data via web services in other applications.</p>
<p>Over the next couple of months, quite a bit of energy will be spent on the developer site (developer.openads.org).  The documents that you recomment are a great start.  Any other suggestions are welcome!</p>
<p>Cheers,<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: swilson</title>
		<link>http://blog.openx.org/06/where-are-my-features/#comment-6351</link>
		<dc:creator>swilson</dc:creator>
		<pubDate>Wed, 12 Sep 2007 18:02:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/06/where-are-my-features/#comment-6351</guid>
		<description>Recruiting good talent to work on an open source project is difficult, but there are ways of increasing your chances.  First, lower the barrier for developers to start hacking away on the code.  As it is, I can find very little information about the overall structure of the OpenAds 2.[34] codebase.  The location of the SVN repo has to be searched for instead of being clearly stated.

I suggest several documents be created:
&lt;em&gt;Architecture Overview&lt;em&gt; - Detail the different components of OpenAds and examine what technologies are used and why.
&lt;em&gt;Getting started guide&lt;/em&gt; - Describe the process of getting a development version of OpenAds installed on a server.
&lt;em&gt;Making your first Plugin&lt;/em&gt; - Starting with a simple example, build a plugin to modify the behavior of OpenAds.

The end user documentation is great and should be used as a model for the developer documentation.  As you've stated above, you've been hard at work creating a great, stable product and the audience for developer documentation is currently small.  However, with that audience will only grow if they understand the code.  I, for one, look forward to mucking about with it's internals!

-swilson</description>
		<content:encoded><![CDATA[<p>Recruiting good talent to work on an open source project is difficult, but there are ways of increasing your chances.  First, lower the barrier for developers to start hacking away on the code.  As it is, I can find very little information about the overall structure of the OpenAds 2.[34] codebase.  The location of the SVN repo has to be searched for instead of being clearly stated.</p>
<p>I suggest several documents be created:<br />
<em>Architecture Overview</em><em> - Detail the different components of OpenAds and examine what technologies are used and why.<br />
</em><em>Getting started guide</em> - Describe the process of getting a development version of OpenAds installed on a server.<br />
<em>Making your first Plugin</em> - Starting with a simple example, build a plugin to modify the behavior of OpenAds.</p>
<p>The end user documentation is great and should be used as a model for the developer documentation.  As you&#8217;ve stated above, you&#8217;ve been hard at work creating a great, stable product and the audience for developer documentation is currently small.  However, with that audience will only grow if they understand the code.  I, for one, look forward to mucking about with it&#8217;s internals!</p>
<p>-swilson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pranav</title>
		<link>http://blog.openx.org/06/where-are-my-features/#comment-844</link>
		<dc:creator>Pranav</dc:creator>
		<pubDate>Mon, 18 Jun 2007 17:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/06/where-are-my-features/#comment-844</guid>
		<description>What would really help is if the openads dev team can provide some roadmap..Like, this is our focus right now..and then the next priority is on these features etc.

I know that there's a developers section on the site and it has the roadmap related to each milestone..but often times, that fails to give a clear picture on what currently is being worked upon..and what is next.

Keep up the awesome work though,

-p</description>
		<content:encoded><![CDATA[<p>What would really help is if the openads dev team can provide some roadmap..Like, this is our focus right now..and then the next priority is on these features etc.</p>
<p>I know that there&#8217;s a developers section on the site and it has the roadmap related to each milestone..but often times, that fails to give a clear picture on what currently is being worked upon..and what is next.</p>
<p>Keep up the awesome work though,</p>
<p>-p</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harald_K</title>
		<link>http://blog.openx.org/06/where-are-my-features/#comment-783</link>
		<dc:creator>Harald_K</dc:creator>
		<pubDate>Fri, 15 Jun 2007 18:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/06/where-are-my-features/#comment-783</guid>
		<description>That sound very honest to me. I´m excited to here those news. I Hope, your work will now be much more satisfied for you. Sure it will :) 

Best regards 
Harald_K</description>
		<content:encoded><![CDATA[<p>That sound very honest to me. I´m excited to here those news. I Hope, your work will now be much more satisfied for you. Sure it will <img src='http://blog.openx.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Best regards<br />
Harald_K</p>
]]></content:encoded>
	</item>
</channel>
</rss>
