On Fri, 25 Mar 2005 07:21:50 -0800 (PST)
 Gabor Kincses <[EMAIL PROTECTED]> wrote:
There seems to be only one active developer: he is
working on JamesNG, trying to migrate away from the
Avalon beast.  Unfortunately, this list tends to throw
more darts at the guy (re: groovy), rather than
encouraging him.  This would only be fair IMHO 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.

I agree completely with the sentiment that those who are most idle shouldn't try to block people who are not.


That said, Noel did throw the sharpest darts and he's been the most active in recent time. Using groovy as a container is at best "leading-edge" and I wouldn't expect adopted without extensive discussion, most of which has been constructive. I took away from the last discussion that the biggest work was making James a collection of POJOs, and then we could work on container strategies secondarily. When that's ready, I expect more discussions.

Also, the JamesNG work is done by a non-committer, so this is someone who hasn't worked with the James developers and needs to earn some trust. I think he's doing a good job towards that. For everyone's sake, we don't grant access without a vetting process, otherwise we could end up with an unsupported product that has been run half-way in multiple unmaintainable directions.

This is not a troll.  Just some of the observations, I
have gathered since I had jumped on the James
bandwagon.

Constructive criticism is always welcome.

I have considered James basically a dead project for
some time now.

Correct me if I'm wrong.

I can't bring myself to call James dead since that is a permanent state. The developer community around it is idle, but it is still there and not abandoning it.


--
Serge Knystautas

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



Reply via email to