At 08:40 22/2/01 -0500, Ted Husted wrote:
>[EMAIL PROTECTED] wrote:
>> In any case - I hope Ted will include the 2 proposals in the final vote,
>> and I'll let the majority decide what will be the goal and rules for this
>> project.
>
>As near as I can figure we have already covered that ground, and the
>current proposal already reflects what the majority of people
>contributing to this list have decided.
I am kinda confused ;)
A few days ago I indicated the 4 paths I saw were
1. component repository (ie ToolForge+CJAN)
2. vetted/tested/approved components (ie Avalon+CJAN)
3. base util (Something similar to AUT - Apache Utility Toolkit).
4. gathering
(3) is easily doable within current apache model. I believe Costin wants to
work in (1) and Avalon covers enough of (2) that I don't see it worth
creating a new project for. So what am I saying? ;) I am +1 for all but (2)
which I am -1 on at the moment.
>From what I gathered our plan of attack was (1). ie Our first module would
be the DBPool. We would extract it from somewhere (say turbine) refactor
it. Then push it back into turbine with a wrapper that integrates it into
the turbine framework. We would then try to integrate it into struts and
anyone else that uses DB pools. Then we would pick another component and do
the same. Have I got this correct/wrong?
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
