i am currently testing out zimbra on debian, as well as looking at some alternatives like openxchange, opengroupware, and a few other projects.
QUESTION: what is the overall goal for zimbra ... are you guys tightly focused on a messaging server solution (like hula-project for example) or will you be trying to expand into the 'groupware/collaboration' and 'application server' problem domains?
the reason i ask is that as i watch a lot of these projects, i am noticing one of two things:
a) the problem the project is trying to solve is not well understood by its developers, so they start out with a scope that seems well defined like 'messaging server', but then ms exchange envy sets in and they quickly bolt on 'groupware applications' and end up reinventing their applications server.
b) the core developers understand that a mail frontend is just another 'application' and end up not picking an established application framework but reinventing their own (like opengroupware for example).
there are a whole other set of questions that either observation poses (namely along the lines that if either option has been chosen, it is the wrong one usually), but i'm just curious where we are starting from and what we are aiming for with zimbra.
any input on this topic would be greatly appreciated.