commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk Verbeeck <>
Subject Re: [Vote] ARMI to move
Date Wed, 09 Jan 2002 17:57:43 GMT
My vote: +1 to add it to commons

If you think the API is stable enough to give it to the public, go for
We have a place for reusable components and that is commons.
But I understand if you want to go back to your Avalon roots.

These discussions are common on commons ;-)
Do we use this component or that other one; accept this or that
style/component/coding method. Don't listen too much to those

The bottom line is as always, is the code good enough ? The answer must
be yes otherwise it wouldn't be accepted into Avalon.

For the support part, maybe you can ask some Avalon committers for their
unofficial support / votes.
New components must get a chance in the real world (outside the sandbox)
and if the code is used in Avalon there will be somebody the support it. 

Dirk Verbeeck

Paul Hammant wrote:
> Folks,
> > 2) Take it back to excalibur and just shove it in (where it becomes a
> > tool amngst many that already have a community).
> Actually I don't think this is so rude after all.  It is not like ARMI
> was commissioned or solicited for. I'll go back to where I came from,
> with the official vote being one for and one against.
> - Paul H

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message