What a bad example

i've been watching the project since its inception, have contributed several patches. i think
its more than just the architecture abstractions, although that was definitely a strong sign
of some of the issues. it was also poor technology choices (wx, chandlerdb) in addition to
poor management that lead to this road, imo. and inexperience with python, mucky internal api
(verbose xml initially).. it had the feel of abstracte java apis in python.. much of which was
cleaned up at with philiby eby working (peak, setuptools) as a contractor with them, but the
writing was on the wall.

in general watching chandler and osaf, was like watching a slow moving train wreck.

there server side story is much better (servlet cal-dav repo w/ sharing and  web ui), and was
built fairly rapidly by a small team.