On Wed, 17 Dec 2003, __matthewHawthorne wrote:

> However, I'm not sure that I understand your suggestion about Jakarta
> Commons becoming top level, and then being joined by Apache Commons.  I
> think it should be the other way around -- Jakarta Commons projects
> should become Apache Commons projects.

It's easier for 1 to join N, than for N to join 1. Rather than have us
spend ages trying to modify A-C's rules until we feel like we like the
idea, we can just suggest that we grandfather our rules in and invite the
A-C people in to help us open our minds.

> But in a sense, it can all seem redundant.  If Apache Commons then has
> projects for all languages, there would need to be at least a small
> separation of projects by language, if only for web site listing, or
> coding standards, etc.  So, there would be a Java branch of Apache
> Commons -- which is kind of what Jakarta was in the first place,
> Apache's Java project, right?

This starts getting us into big long email threads about how to architect
a multi-language commons, and I'm not sure we need it yet. Even with a
merger, there would only be 2 additional C projects so not enough to have
a clue what the future will look like.

While we'll have to stop the project being java-centric, just to fit the
components on the website and in the mind, we wouldn't have to find a new
structure. So there wouldn't be a Java branch of Apache Commons, there
would just be Apache Commons. It would be a bazaar of projects which might
then choose the Java language as a categorisation, or might choose
something else.

> So, my point is, I agree that Jakarta Commons might benefit in being
> higher up.  I'm surprised that Struts isn't a top level project already,
> but if it were to be, then that would be another top level project that
> depends on JC -- which doesn't quite fit with the charter.
>
> Although, as I just mentioned, the language issues still confuse me.

And it should. I'm essentially proposing we deal with it later on when we
have more data.

Hen


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to