We’ve been getting quite a lot of feedback and comments the last few days, on the back of the announcement that we’ve raised funding.
Here’s the comment that has interested me most, which was posted on TechCrunch:
Well, then that explains why they haven’t released all the features that users have been begging for over the years like self-signup and PayPal integration. I’m guessing we’ll all have to pay for those features instead of getting them in the OS package. If so, I do hope they crash and burn as all of the support users have given them over the years was to make a better product for all, not to feed ideas for their own startup.
I’ve talked about the evolution of Openads before on our forums, but perhaps it’s a good idea to reiterate a few points, just so that people know where we’re coming from.
I’ve been working on the Openads 2.3 code base for a little over 3 years now - but in a rather circuitous way. When I started, the company I was working for was called Awarez, later renamed to m3, and we were writing something called Max Media Manager, or MMM for short.
MMM was forked from phpAdsNew about 12 months before I joined Awarez, for a very specific purpose - to meet the needs of Awarez’s parent company, Unanimis. So, that’s what we had in mind when we added features to MMM - what does Unanimis need? After all, Unanimis were paying the bills, so we worked on what they needed.
As MMM had come from the open source phpAdsNew, we wanted to give something back to the open source community, if we could - so we kept MMM open source, we made occasional releases, and the staff of Awarez/m3 pitched in whenever they could to help out anyone brave enough to use the incredibly complex and undocumented code base that MMM became over the years. We didn’t have to do this - Unanimis didn’t stand to gain anything from this, after all - but we wanted to.
Of course, the people who used phpAdsNew or MMM requested new features - and self sign-up and PayPal integration are certainly high on the list of most requested. But Unanimis had no need for these features, and we just didn’t have the time in between doing what Unanimis needed us to do for them to put those features into MMM - and with Matteo Beccati as the only person who was volunteering their time to manage the phpAdsNew project, unfortunately the features weren’t able to be put into phpAdsNew, either.
In time, we came to realise that was an opportunity to form a company around the open source products of phpAdsNew and MMM. So, we formed Openads Limited, and we managed to convince Matteo to join forces with us, and now, together, we’ve renamed phpAdsNew as Openads 2.0, and MMM as Openads 2.3.
So, I can understand why people might be asking, “where are the features we’ve requested?” I can understand that they think we’ve had a secret evil master plan all this time to deliberately keep features out of the product so that we can now charge for those features. However, that’s not the truth. Openads the company has only been working, full time, on writing software for you, the open source community, for six months now, and that whole time has been spent working on making sure Openads 2.3 gets the clean up it needs to be released as a solid, stable, fast and well documented successor to the long running and outstandingly successful phpAdsNew (now Openads 2.0) software.
However, as hard as we’ve been working for the last six months on this, we’re not satisfied. The progress we’re making is not fast enough. We want Openads to be better, sooner - but there’s only so much a small team can do in a day. We need to grow our development team if we want Openads to improve more quickly, and to add all those new features people request. To do that, we need money to hire developers. That’s why we raised funds - so we can get more developers on board, and make Openads not just good, but great.
So, we hope that over the next six months, you’ll see the difference from the funding. We’ve heard your requests for features in the past - and we’ve received hundreds of emails over the last couple of days. We’re listening, just like we always have - except that now, our focus is on your needs, and so we’re planning how we can best fit those needs into our development roadmap for Openads right now.

Tags:
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
Comment by Harald_K — June 15, 2007 @ 6:38 pm
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
Comment by Pranav — June 18, 2007 @ 5:47 pm
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:
Architecture Overview - Detail the different components of OpenAds and examine what technologies are used and why.
Getting started guide - Describe the process of getting a development version of OpenAds installed on a server.
Making your first Plugin - 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
Comment by swilson — September 12, 2007 @ 6:02 pm
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
Comment by Scott Switzer — September 17, 2007 @ 4:15 pm
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!
Comment by danz — December 11, 2007 @ 11:37 am
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
Comment by Diana Sabey — December 15, 2007 @ 6:38 am