We had some internal planning sessions on Daisy's future, which I transcribed into an updated roadmap document. Community-wise, there's 120 list subscribers on the Daisy mailing list so far, and about 10 downloads per day of the new 1.3M1 release.
Daisy is 7 months old now - counting from where its public life began. We're trying to make a two-fold difference with Daisy: first of all, we want Daisy to be a compelling CMS framework with innovative design concepts, solid production-quality code and lots of nifty features. Looking at our current feature set, I think it's safe to say that we're leaving lots of the established players behind us - we might be missing on some of the eye-candy but that's irrelevant for now: if they have to choose, people prefer stuff that works anytime over stuff that just looks good. The strong separation between repository and editing/publishing web application seems to be hitting a sweet spot with a lot of its adopters. The second difference we want to make, is to show the world that serious open source development can be done, without commercial-unfriendly dual licensing, and without VC funding, by a small, yet committed company, actively seeking both volunteer and commercial co-ownership of a shared codebase.
BTW, did you know that the aggregated Daisy documentation is almost 100 printed PDF pages so far?
TrackBack URL for this entry:
http://blogs.cocoondev.org/MT/mt-tb.cgi/2305
Sadly enough, in my experience, users prefer stuff that looks good over stuff that works ... :(