commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: Project Proposal?
Date Fri, 05 Aug 2005 06:37:24 GMT
Out of interest, why and not sandbox? :)

Before that sounds like a witch-hunt, I'm as guilty in that I start
all my stuff at and I can definitely list some reasons why.

Some may be bad:
* Embaressment for dumb ideas :)
* Don't want to be weighed down by a weighty release system.
* Big painful website.
* Might compete with another Commons component.

Some may be good:
* Does the ASF want single-person codebases when an idea doesn't pan out.
* If it fails, I'd then be forking it elsewhere which feels worse than
just starting elsewhere.

What if we had a location within which ASF committers can bring their
half-cocked component ideas? Try to encourage migration to the ASF and
its benefits:

* bandwidth, though and can solve that too. So can
building your own system to the level of Codehaus.
* legal protection.
* better user acceptance.
* community.

If we couple this with:

* much better management of the sandbox, and components that have failed.
* a plan for mature components.

could we pick things up in terms of vibrancy? My biggest worry would
be whether the mailing list becomes a bottleneck.

Half-baked idea (it's late): Each component has its own mail alias
which gets forwarded to particular lists. These lists could represent
the state of maturity of a component. Probably crap, just throwing it

One question I'd like to ask is whether we would accept mature components. 

Take, HttpClient said they were
interested in using it and the thought was to put it in Commons. My
only concern is that I can't see a lot more to do with it code-wise,
so I'm hesitant to dump it in Commons, and yet I think it's a good
tiny component that could do with being more open.


On 8/4/05, James Carman <> wrote:
> Well, I went ahead and started the project over at, but we can move
> it later if need be.  It's a dependency injection framework called
> "syringe."  The project uses the Apache License, Version 2.0.  It's still
> "pending approval" at, so you guys won't be able to see anything
> yet.  It should be approved soon though.

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

View raw message