Monday, February 27, 2006

Amgen Tour of California

While I am busy trying to help one of the biggest outsourcing companies in the world to sell Magnolia to one of the greatest airlines of the world for their new intranet, here is what current users say:

Thanks, you guys made my day Magnolia! We just finished up the Amgen Tour of California, http://www.amgentourofcalifornia.com, and everyone loved it!

We were very impressed with how Magnolia handled under the load, even before I got caching working. We averaged about 580 hits a second, although that was an overall average and we probably had about 4 times that during lunchtime. This was all running on a single server per magnolia instance, an intel xeon 3.0 ghz processor with 2 Gb of ram.

Again, thanks for a steller product that really worked out! Feel free to contact me (...) if you want more info to maybe put on the magnolia website.

Is it worth 80h weeks? Maybe not, but it sure feels great to know that we make somebody's day out there.

Sunday, February 26, 2006

The Jackrabbit vibe

Too funny what other things are named Jackrabbit:

The Jack Rabbit Vibrator is an all time classic vibe. This wonderful and fun vibrator is loved by women around the world!
Luckily they don't carry a model named "Magnolia".

The JCR shell

Did I mention we need a JCR shell? John just wrote one. Can't wait to see it announced on the Jackrabbit list...

Magnolia training rocks - and so does Magnolia

Tom Jensen of Boise Cascade has writen a very positive review for our Magnolia trainings:
I just finished up yesterday at the training for Magnolia down in Laguna Beach, CA. I was glad I went and felt it well worth the time and money to go there. It was so nice to have a knowledgeable instructor (Giancarlo) to help understand Magnolia and how it relates to the JCR. In the past I've thought it a bit odd to have training for an open source project. I thought that I was a wimp if I couldn't just understand the complete concept of the software from reading any docs on it and looking through the code. The training not only will have saved me many hours of head scratching it has helped me to get the vision of what was intended with Magnolia and how to better use it along with the underlying repository.

I am very happy that Tom choose Magnolia. During the evaluation process it was openCMS vs Magnolia in the finals, and when the decision was made, Tom told me that it was pretty clear: they had the users test the two systems for a day, and while users were having a hard time figuring out how openCMS was supposed to work, the opposite was true when it came to Magnolia - they simply could use it without asking questions. The difference must have been striking. Tom sent me he following note:

This is a great product and I'm looking forward to continuing using it. It is not only a simple, intuitive program for end users (content creators) to use but is pretty straight forward in template creation.

Thats exactly what we intended to deliver from the start - looks like we pretty much succeeded.

Friday, February 10, 2006

Magnolia in the press

The first part of my article about open source community evaluation - and why it matters for your enterprise - has been published as a cover story in the Enterprise Open Source Journal this week. (See page 60 for my article). The theme of this edition is "Demystifying open source" - a great subject and about time bring to our attention, too.

What I like most is that the same issue mentions Magnolia as one of the 10 popular open source CMS systems - even if Ric Shreves has gotten some things wrong in the article:
  1. the licensing is not dual mode but we have several products, some commercial, some open source
  2. the community is quite extraordinary, with 200 people subscribed to the developer list and some outstanding external (to obinary) core members like Fabrizio (who is also committer for displaytag and Maven) and Alexandru (who has been contributing to a number of open source projects)
  3. there are no modules because the way magnolia works, functional modules are rarely needed. Since the data management is completely dynamic (no database tables to create and rows to add) you can simply define a data unit (paragraph) and are read to rock.