Friday, November 28, 2003


Last night I was stranded without my laptop at home. Using .mac, I was able to sync all my bookmarks and addresses to the iBook of my wife, it worked like a charm. Great stuff! Sometimes small things are great things.

Wednesday, November 26, 2003

craziness abounds

I am very much absorbed at the moment with Magnolia. Lots of traffic on our mailing list. 2500 downloads in the first seven days. Also, I joined LinkedIn upon invitation of R.
To many things going on at the same time. 2 weeks until I am off to New Zealand, 10 days since we posted Magnolia , and LinkedIn starts to be fun. Any questions?

Tuesday, November 18, 2003

Mailing-list vs. Forums - my thoughs from Magnolia-dev

The following is a mail I posted on Magnolia-dev - why I prefer mailinglists over forums
we have thought about this (note: i.e. Forums). The main reason we do not like forums is that email is right there, always with you, whereas you have to visit a site to work the forum.

If it is just for archives, we can provide these.

However, we are open to discussion on issues like this, and as a matter of fact could set up a forum in less than a minute if people would really prefer that.

Personally, while this might seem old-fashioned, I love the fact that I have e.g. 30'000 emails from the webobjects developer list right here cached and indexed in my mail client, always with me wherever I go. Its a huge knowledge store, and its faster than any forum plus I do not need to be online to find an answer.

Also, you have options like digest and index if you just want to reduce the daily mail doses, you can filter to your heart's content ( I have rules that copy certain mails to certain subfolders within my mailing lists) etc.

All in all I believe you have more control, faster access and faster response times with a mailing list than with a forum, and I do not really see any advantages by using a forum other than archives, which we can provide as well.

To have both (mailing list and forum) seamlessly integrated would be sweet. However, in Java, I have only seen one open source solution that tries that, and decided not to integrate it into Magnolia (which of course would be the ultimate goal). To have such a tool for Magnolia would be great, not the least because it would store content in JCR, and this will give you a lot of nice options to retrieve that content, once level 2 functionality (e.g. arbitrary search; versioning) will be there.

Monday, November 17, 2003

Magnolia 1.0 released

We have finally released Magnolia 1.0 and the downloads are mounting. Rank 1014 on sourceforge last Saturday!
We have just released Magnolia, the free, open source, J2EE compatible content management system, last Friday evening. Of course, these are exciting times. While I wait for the sourceforge stats to be updated, this Sunday we had 1000 unique visitors to (which is 10 times the normal daily visits), and since we added Magnolia to versiontracker (only the OSX section) last night, we have 300 downloads this morning on VT alone.

Also people start writing about Magnolia in their Blogs, like Gregor ( who finds the first impression spartanic. That is excellent, because I hate over-bloated user interfaces. Anyway, he likes the way users are able to move content around - one feature I personally love as well.

So lets see where this new journey leads us to.

Oh, the new stats are there now: 125 downloads on sourceforge last Saturday, that brings the known total to roughly 500 at the moment. And we are on rank 1014 (last Saturday). I just can't wait to see the Sunday stats :-)