--- "Noel J. Bergman" <[EMAIL PROTECTED]> wrote:
> > There seems to be only one active developer: he is
> > working on JamesNG, trying to migrate away from
> the
> > Avalon beast.
> 
> Actually, no.  Development outside of the ASF
> infrastructure is not
> development.  I'd be fairly happy to see him as an
> active developer, working
> with the others.

Any development is development, particularly when no
commits are happening on the main code base.  I'm sure
he'd use the ASF infrastructure, if he were given a
branch to go crazy on.

> > if the dart-throwers were burning up their
> keyboards cranking
> > out new features, integrating submitted patches,
> making more
> > than typo-level fixes to the website, figuring out
> a versioning
> > strategy, or at the very least read up on
> lightweight containers
> > etc.
> 
> Lightweight containers is a fairly low priority
> compared to the many
> features that are pending.

Man, with comments like that no wonder there's gonna
be  a code fork.

Lightweight containers are not about containers but
the contained objects.  I'd argue that a pico-based
(or any other ligthweight container-based)
implementation would hugely benefit the project and
energize development by recruiting new talent.  I have
walked-through and debugged a fair bit of the SMTP and
configuration stuff in James with Eclipse (yes, I
admit it, I'm a recent IDE-convert) and have found
some really strange inheritance hierarchies.   All
this Avalon stuff really makes one's head spin. 
Trying to provide alternate implementations for some
components being a pain usually reflects the lack of
well-thought-out interfaces.  In the case of James,
it's probably a lot more about evolution, then
original poor design.

Gabor


Gabor Kincses
Running Mandrake Linux 10.0


                
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to