Dear list
I hope you don't mind bothering you with this question again. I've read the thread about Lenya and haven't found arguments that would counteract Magnolia. Why not using Magnolia?
Let me put it short. Magnolia is a J2EE compliant, open source CMS, see http://www.magnolia.info/en/community/about.html
Magnolia is JCR 170 compliant since the birth of the project in 2003 (first slide, now jackrabbit). It has a very nice user interface and a constantly growing user and developer community. And it can be combined with Jetspeed. I did integrate Jetspeed 1.4 with Magnolia 2. See www.pagnolia.ch > Produkt > Demo for a demo site. I planned to migrate to Jetspeed 2 as soon as Jetspeed 2 is production ready.
I might be interested in participating in the project and contribute work, code or experience (well, if needed at all).
I can't tell for sure whether the licenses of Apache and Magnolia can go together. I don't know whether you are interested in using an existing codebase. I cannot tell for sure if the Magnolia community would welcome the Graffito project. But I am sure, that the two projects could gain from eachother. Magnolia could be the CMS part for administering content, Jetspeed could be the presentation and business logic part and Graffito would enrich those two with ready to use JSR-168 compliant mini applications.
-- Cheers, Michael
