On Sun, 20 Oct 2002, Aaron Bannert wrote:

> On Mon, Oct 21, 2002 at 12:17:51AM +0100, Stephen Colebourne wrote:
> > The problem here is that jakarta-commons project names are intended to be
> > 'bland' (See the commons charter). Thus we have names such as lang,
> > collections, io. These are names that might equally apply to other
> > programming languages.
> >
> > My opinion is that putting code from different languages into the same CVS
> > is just going to hurt.
>
> Maybe it's more important to create a new Commons that is acceptable
> for full integration to/from the original Jakarta Commons, than
> to worry about namespace collisions. I tend to think that any
> namespace-collision-strategy that we come up with will be more confusing
> to our users, and I think the collaboration between the (successful)
> original group with the ASF-wide initiative would be very fruitful.
>
> What would it take to make these two groups into one?

Right now? Provide a good split-pane of the difference between Jakarta
Commons and Apache Commons as far as the projects themselves are
concerned.

Then hopefully, turn the negative parts of moving to Apache Commons into
positives, or at least show how they're less than the negatives of staying
at Jakarta Commons. Do some marketing :)

I think we're all happy to sign-up, once we have a real understanding of
what the contract says and what it's gonna mean.

One of the problems with this I figure is that Apache Commons is currently
a nothingness, just a term for a vague concept, so the first step is to
iron out what life will be like as a Java project in Apache Commons, then
do the above.

None of us are really going to budge at the moment if the chance still
exists that we join and then find out that some beaureacrat is demanding
that we release all our code in perl/c++ and tcl too. [a hypothetically
stupid situation]. I do however expect a lot of us to be listening in
though and try to help you get Apache-Commons/Java to the point of being
useful to Jakarta Commons, but I doubt any of us will commit.

Hen

Reply via email to