Hi,
Since we have so many road blocks on our track ahead... why don't we
simply start a rewrite?
Before we all throw in our -1's, let's just think about it for a minute...
Truely, coding the current stuff is _no_fun_. How do we expect this
project to gain track if nobody is volunteering for coping with this pain?
We have _not_enough_long_term_committers able and willing to deal with
legacy stuff. The world has _moved_on_. Can't we build something which
is comprehensible? The whole backend repository architecture and how
things are propagated, well, I don't get it and I think it'd better be
replaced. And I don't even figure out how to replace stuff there.
Whenever I look at this stuff I start with... putting it away.
Many important features from the last couple of months could (IMHO) not
be integrated seamlessly. Because current JAMES is not easily extensible
and generally does not welcome changes. We have some cool ideas like
async handlers etc. And people invest their time trying to fit it into
the current architecture, where this energy is better spent writing even
more cool features and making the server unbreakable. We have tight
integration with JavaMail. This alone has probably cost us so much time.
(Re-reading the last paragraph, it seems a little bit like a rant to me,
don't you think? But I feel better now. Anyway...)
Yes, we have a responsability, to make things easy for our users,
support migrations, be defensive with changing APIs and so on. But how
does that help if we are unable to push this dinosaur forward? Or
foremost responsability is to make this a fun place to be, make people
contribute and hand out fine releases. I think we have come to a
situation where we might be better off with creating something new from
scratch.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
