Giancarlo Berner wrote: > Hi Andy > > I have no problem if you criticize company policies. In fact, I do > that quite often too when consulting :-) But what I do not like is > that you are publishing comments and blaming others, but yourself did > not do the homework. That is simply not fair towards all developers > and definitely against all rules of Open Source projects. If you had > just spent a few more minutes researching you would have realized that > Magnolia is still an Open Source project and it's still for free and > can be downloaded any time. > Didn't you profit for 2 years from using Magnolia? And I assume > Magnolia is helping you generate business. So the Community (and the > Magnolia core developers) deserve a little more respect! Of course I did but did not Magnolia profit by having Magnolia deployed on JBoss? I know it is not deployed by default but many are using it that way including me. I have great respect of any open-source contributor but I am not happy when I feel tricked by open-source project where an open-source project is used to lure users and then take advantage of them. And no I don't make money using Magnolia. It just helps me having a company website but so far the only thing is having a face on the Internet and distributing my presentations for free. > Most companies (even Day Software, who does most of the work for the > Content Repository standardization) who provide Open Source products > at such a high quality as Magnolia have to make money somehow. 90% of > the Magnolia development (and being 2 years on the list you definitely > should know that) is still done by the pure Magnolia core team (let me > take the opportunity to thank Boris, Sameer, Philipp, Gregory and the > whole Magnolia team for a great product!) AND NOT THE COMMUNITY! The > Community is extremely helpful in exploring and maturing the product, > but the development requires deep understanding of Java (incl > patterns) and especially the repository API. That will have to be done > by the Magnolia Team. Well, you cannot separate the one from the other. Contributing does not mean coding per se but can be any form of contribution by the community. If only coding with be a contribution then Magnolia would not be open-source, I guess. > You were (or still are?) a very valuable member of the community and > I'm sure many users out there are thankful for your advise. But there > are also many COMPANIES testing and implementing Magnolia. These > companies have different needs. The real good news for the community > is, that these companies are ready to pay a certain some for support, > training, security and more. Keep in mind that this money is > absolutely essential to keep the Magnolia core team alive! Better yet: > a lot of enhancements required by these companies (and paid for!) are > finding there way into the community edition! So take a few hours and > upgrade to Magnolia 3.0. You hardly will regret the effort! I am not that sure. How difficult can it be for the core Magnolia team to create a basic conversion tool or a good documentation tool. I don't mind to pick it up but I am not going to start from scratch. Again I could have my website up and running with plain JSP for the same amount of time. Magnolia is a pet project for me which I don't mind but I would rather focus on productive things than writing a stupid migration tool. > Andy, coincident? I joined the LA-JUG recently, so perhaps we can > continue this discussion along with a glass of wine :-) Just ping me > at gberner at xumak dot com. I will gladly help you migrate your web > site. I take the Presidente Margaritha. No, it is not a coincident but IT world is really small. Let's talk about it. > Hoping you will remain a member of the Magnolia Community ;-) > Giancarlo > > BTW: Magnolia DOES NOT MAKE MONEY on the Packager's 58 Euro. It is a > private initiative by Ralph Hirning. The Packager is part of the > Magnolia Enterprise Edition. Ok, I did not know that which mean that they Magnolia did not a good job on explaining that. Still I am disappointed that Magnolia Ltd. did not provide either a documentation how to migrate or even better a basic tool. I don't need to convert JSP or others but I am not going to spend hours dealing with the repository because I then also need to know the inner working of Magnolia. And shelling out 58 euros just feels wrong and I am not going to do that.
---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
