[EMAIL PROTECTED] wrote:
> I think both. And more importantly - sharing a community.But one thing
> is easy to verify - the current situation is that code is not shared. And
> my guess is that this is because people don't feel they are part of the
> same community - we have different projects, with different communities.
Jakarta products share a lot of code -- but only at the JAR level. We
all share Ant, and many use XML tools from other ASF projects, Jetspeed
uses Turbine, James uses Avalon. The list goes on.
And some products are trying to expose more code at a lower level for
others to use too. Struts is a good example of that. So is Avalon and
Turbine. In time, more deep sharing will occur. Someone will want to use
something from the Avalon utils and Struts utils in the some other
product, there will be some twiddly problem, and Craig and Peter will
find a nice ad-hoc solution. This will happen a few more times, and
eventually an adhoc library will evolve. Someone will start a list on
the Web site, and more people will start using shared utilities from
different products.
But, realistically, that may take several years.
So rather than wait for evolution, some of us want to start a
revolution, and launch a library subproject. We don't want it to be hard
for people to use the library, so we're saying it should look-and-feel
just like the rest of Jakarta. People are already happily sharing code
at the product level, so let's make the packages look like products, so
they will be happy to share these too.
We can't tell anyone to do anything here, so we have to look at what
people ~want~ to do, especially what they are ~eager~ to do, and work
from there. Based on the poll, it seems that most people want to work on
a Taglibs-style library subproject, and so we need to run with that. It
may not be the optimal use of resources, but it's the only real choice
we have.
-Ted.
