Backgrounder FAQ

License

Daisy is licensed using the Apache License 2.0, which is a BSD-style license. Basically, this license grants the user of Daisy the right to do anything he or she wants with the software, both in a commercial and non-commercial context. Daisy can be redistributed inside for-pay software, and the Daisy source code can be ripped into pieces and be used inside another CMS or web application. There's no license fee involved, so Daisy is both free and open source. The only requirement laid out in our license is that no-one can use the Daisy name to endorse his own endeavours without our consent, and that derivative projects based on Daisy should be crediting us.

Apache Daisy? daisycms.org?

Apparently, quite a few folks misunderstand the relation between Daisy and Apache, or Daisy and Apache Cocoon. Daisy borrows the license of The Apache Software Foundation, but nothing else. Outerthought, the main Daisy contributors, however also contributes to Apache, most notably through its collaboration inside the Apache Cocoon project community. Outerthought has, amongst other things, donated the Cocoon Form handling framework to Cocoon, which obviously is also being used inside Daisy.

Hence, Daisy is not an Apache project. It is hosted on project infrastructure sponsored by Outerthought. The intellectual property rights of the initial Daisy releases is owned by Outerthought and Schaubroeck, and future versions' IP will be owned by both these parties and Daisy's future contributors.

Who is paying for Daisy? What's driving its agenda? How can I get new stuff added fast?

Daisy's initial release (October 2004) has been funded by Schaubroeck, a Belgian e-government solution provider and a customer of Outerthought. Copyright is owned jointly by Outerthought and Schaubroeck. We invite other parties, interested in funding continued development of Daisy, to contact Outerthought.

While Outerthought supports the Daisy open source project and its community of users and contributors to the best of its abilities, we are a company and paid work gets done first. This business model has proven successful in the past for both us and the open source projects we maintain. Outerthought is fully committed to making Daisy happen as a long-term endeavour, and we hope people will feel invited to be a part of it. Needless to say, we welcome bug reports, comments, patches and other contributions: see you on the mailing list!

Why Daisy? Why yet another CMS?

We believe that Daisy is unique in many perspectives, more specifically because of its hierarchy-freeness, the rich-text editor which adapts itself according to changes in the document type schemes, its query capabilities, its centralized ACL system and its clear separation between repository server and front-end application. Daisy is a content and/or information management system with powerful website-publishing capabilities, rather than a website management system.

We don't want to do lengthy comparisons between Daisy and other CMS systems, since we believe such comparisons should be made with specific project requirements in mind. We invite users to install Daisy alongside another CMS and see what fits them best.

Why didn't you contribute to product xyz instead?

When we started development of Daisy, the state of Java-based CMSes was such that we did not felt them being appropriate for commercial applications - business projects with business contracts and business warranties. We freed our minds, swallowed the red pil, and in hindsight can only conclude that this was the best decision would could have made.