Mark R. Diggory wrote: ...
What about a "home"? Where will depot live as a tool? For example, is it appropriate as a Jakarta Commons Component? Growth will occur if the project is situated in the proper location such that users can find and will use it.
Hmmm... the initial idea was to go top level, but is it shooting too high? (I'm thinking out loud) Having as a goal to go to Jakarta Commons and thus using the Sandbox may be an idea.
Or is just telling people in the right forums enough?
Already seeing successful reuse of Jakarta Commons Components throughout Apache. Depot, as a Jakarta Commons Component would open doors for much reusage throughout Apache as many projects are already using commons components and feel very comfortable with using them. If Depot were a Commons Component, users who already feel familiar with the Commons package layout would feel less apprehensive in terms of picking it up and introducing it as a dependency.
I have already seen that some projects are interested in using Depot but are afraid of the dependency. In particular from Cocoon I have heard the question if it's them needing us or viceversa. Probably going in Jakarta Commons would ease this.
On the other hand Jakarta Sandbox is seen equally unstable, so I'm not sure it will be so different.
More Dependencies = More Involvement.
I agree. That's why I want to propose it to Cocoon, and publicize it more.
I'd say we try to do this last push and see how it goes. The points I highlighted have to be done in any case, so eventual destination changes can still be done later on.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
