as you may have noticed, I haven't been active in the ZooKeeper project
anymore for a couple of months. I'm a full time student again since march so
that any further activity in Hadoop/ZooKeeper would need to be auto-motivated.

Since I don't want to just fade away and I'll still give a talk about
ZooKeeper on the BerlinBuzzWords conf (Berlin, june 6/7), I listed the reasons
why I wouldn't like to work on the current ZooKeeper code base anymore.

A tentative brain dump of part three is listed below. I appreciate any
comments that could help me to give a balanced presentation of the ZooKeeper
project.

If I'd need a ZooKeeper implementation right now I'd probably do a minimal-
feature rewrite in Scala + Akka. I do appreciate ZooKeeper as an invaluable
proof-of-concept implementation and pioneer. But as in american history there
should come others after the pioneers that don't look like Clint Eastwood
anymore and build more tidy things.

The list:

* The code is tightly coupled
* most so called "Unit-Tests" are actualy integration tests. They run the
whole application and test one specific functionality.