Giancarlo Berner wrote:
> Sorry, Andy, me again :-)
>
> - Just to clarify: The migration tool ("Packager") is a private
> initiative by Ralph Hirning and has NOTHING to do with Magnolia.
> Magnolia has though integrated the Packager into the EE and I am sure
> they are paying Ralph some royalties. Magnolia CAN NOT give the tool
> away, not even for free!
Fair enough and I apologize if I got that wrong. Still the website that
sells the tool says:You can buy a Magnolia Packager migration license to automatically migrate content created in Magnolia 2.1.5 to Magnolia 3.0 for only € 58 (incl. tax). Which means for me that it is sold by Magnolia Ltd. Still they could create or at least document the migration path because they, the core developer team, has the knowledge to do so. > - Most major Open Source projects are driven by a company or "Sponsor" > (even JBoss!) Someone has to be in charge of quality, continuity and > marketing. Don't start with JBoss. I lost money while working for JBoss but open-source does not need a sponsor per se just look at Apache. > - The reason for the non-compatibility issue is primarily in the > repository, not Magnolia. Changes in the JCR API have broken the > compatibility, which also reflects in Magnolia's release numbering > (from 2 to 3). Well, that is fine with me but just losing some of the community because there is no migration path is bad. > - I know you contributed to Magnolia and it was highly appreciated. > And we all would be glad if we could keep on relying on your knowledge > and expertise! > - Sorry, but you are confusing Magnolia CE and EE. Magnolia > International is NOT making money on the community. It's making its > money on projects and professional services for large scale > enterprises (like JBoss, MySQL, and many more). In fact, the community > profits from that since many enhancements find there way into the CE. > BTW: CE and EE have the same core code base... I did not say otherwise. What I was referring to the confusion with the packager. On the other hand leaving out a migration path screams like someone wants to sell support and/or training because some CC users already mad the investment. > - Now-a-days it's easy to measure download traffic. While the 37'000 > (about a quarter of 150'000) is my pure assumption, the 150'000 > downloads are figures from Magnolia Well, I can tell from JBoss that downloads does not lead to production installations. I would set the numbers lower. > - Don't worry about the "commercial entity" behind Magnolia. The > responsibility of the product lies in the hands of a bunch of highly > skilled Java developers. You can turn it as you want: Magnolia is a > pure Open Source project with some branches pointing into some > commercial solutions. As long as it's Open Source and for free, enjoy it. Nope, otherwise we would not have this discussion. Unfortunately patents, trademarks and reduction in the documentation gives commercial entities a way to take advantage of open-source users. Nothing is free and for sure not open-source otherwise I would be out of a job. > Thanks for your personal advise :-) After 30 years of IT I don't > "believe" in anything anymore. My passion counts for the Content > Repository for Java Technology, which finally has the hierarchical > model I was waiting for (and unsuccessfully trying to develop myself). > Magnolia is just a perfect fitting application on top of it. The > beauty lies in the combination of both! Once you did a large scale Web > initiative and follow how a team can easily maintain it, you will > understand what I mean ;-) Could be but I am a small, very small Magnolia site and time and money is short. If I decide for an open-source application then I am very sensitive how it plays out. Just check out this blog: http://weblogs.java.net/blog/schaefa/archive/2007/05/openjdk_who_is.html > > If you are up for a few drinks, let me know (gberner at xumak dot > com). I hope to join one of the LA-JUG or OC-JUG events soon. I am at the LA-JUGs. -Andy ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
