I didn’t notice that the author mispelled your product name, forgive me for my mistake. Indeed you answered my question, saying that it is still to early to measure economic results due to opensourcing, considering that you did it less than five months ago.

I commented the article because innacurate, pretending to drive conclusions from a series false assumptions (Other Open Source CMS have problem with getting things fixed, no commercial support available, etc).

I’m really enjoying the conversation with you and I would be happy to write more about it, if interested let me know.

Your google query probably didn’t return very many results because the author of the article misspelled our product name - It’s actually SilverStripe (one word).

Googling “SilverStripe CMS” returns 82,400 results

We chose the BSD license, rather than GPL, because it makes SilverStripe a good choice for commercial projects where you want to use SilverStripe as the framework for your own product. Our goal with open-sourcing SilverStripe was to push its usage as widely as possible.

With regards revenue from open-sourcing, it’s obviously early days yet, but we are starting to get revenue from sources directly tied to our open-sourcing, and it’s looking like this will grow.

I can’t comment on the author’s junkyard dog metaphors, but I can say that we started building SilverStripe because we were disappointed with the CMSes out there - not just open-source ones, but proprietary ones too. I think that a project of this nature does need a clear vision that the developers stick to (in our case, keeping the authoring system simple to use without forcing all sites to come from a cookie cutter). While this could happen in projects that are open-source from the start, it did help to have the development team in the same room during the formative period of the project.

Anyway, glad to hear that you gave our project a look in, I hope this answers some of the questions you had.