Morgan Delagrange wrote:
>
> Hi all,
>
> Maybe it's time for a reset here? Instead of worrying
> so much about other subprojects, why don't we focus on
> creating good stand-alone libraries? After all, we
> can't force anybody to adopt our libraries if they
> don't want to. Even if only some projects adopt our
> libraries within their framework, I'd say we've still
> made progress and provided more accessible
> distributions. Practically every Java project in
> Apache (including Struts, Avalon, and Turbine) is
> organized at the framework level, and I think it's
> time for more discrete packaging.
>
> I propose that we move forward with a dedicated set of
> committers in a fashion similar to Taglibs and not
> attempt to please every subproject. In fact, trying
> to meet everyone's needs simultaneously would probably
> lead to disaster. If this is a good idea, our
> components will converge with their frameworks in
> time.
>
> We've got lots of good ideas, such as more focused
> documentation and more minimal and explicit
> dependencies. By getting mired in the minutiae, we're
> going to lose sight of the single important goal,
> which is to produce quality stand-alone components.
>
> How about we pick one or two components, gather some
> likely starting candidates for a baseline, and have a
> cook-off? Really, if we don't work in a small group,
> it's going to be group-vs.-group-vs.-group,
> my-framework-is-better-than-your-framework, and
> nothing will be accomplished.
>
> - Morgan
>
+1000.
I guess we have to
-pick up 2 or 3 components from the list already discussed,
-populate the CVS
-write some kind of spec (what this is supposed to do, APIs etc) from
what's already there and what can be done to make it more generic (wider
users scope)
-maybe propose these spec to an extended group of people for tuning...
During the process we will tune the "library guidelines" in terms of doc
requirements, testing etc.
as test project sounds like connection pool is a good candidate.
Fede
