Thanks Michi to speak about this kind of issues. Comments are welcome. Christophe
-----Original Message----- From: Michael Wechner [mailto:[EMAIL PROTECTED] Sent: Fri 3/18/2005 11:10 AM To: [EMAIL PROTECTED] Cc: Subject: Re: Why not using Magnolia Michael Aemisegger wrote: > 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? I don't think so this thread was about why using which CMS, but rather why do various such projects within Apache exist. > > > I can't tell for sure whether the licenses of Apache and Magnolia can > go together. AFAIK Magnolia uses LGPL and this might not work out to all ends in the combination with the Apache license. Also AFAIK Obinary (who started Magnolia in the first place and I guess still owns the copyright) is creating new software which seems to be based on so-called collaborative source licenses which are not OSI certified and can cause conflicts. I can understand why "companies" are heading into this direction, but I wouldn't rely on such software and "communities", because of specific lock-ins. > 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. all projects could gain from each other, which is what we try at OSCOM ;-) > 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. I don't this is abour technical issues, but about communities and licenses. Thanks Michi > > -- Michael Wechner Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED]
