On 5/14/07, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Also, from a practical matter, our projects already use org.apache.commons, so
this is
already recognised in the ASF.
Verbose package names are a Java notion, and they are only relevant
within a Java application. Regardless of whether there are other
{$Language} Commons projects, we could still use the o.a.c package
name.
On 5/15/07, Danny Angus <[EMAIL PROTECTED]> wrote:
No, that's the point.... http://commons.apache.org/
I think what's important is that the Java-language Commons PMC not
hijack the top-level hostname space or the top-level projectname space
all to ourselves. If we plan to share the hostname space with other
TLPs, then we all we need to do is make the base URI
* http://commons.apache.org/jakarta
or
* http://jakarta.commons.apache.org
instead. But, we should do that from the beginning, rather than try
and retrofit it later.
The key point would be what modifier to use along with the "Commons"
moniker. We can't use "Java", because Sun will likely complain again.
We could use some other modifier, but we already adopted the term
"Jakarta" for this very reason.
We can create a "Jakarta Commons PMC" without affecting the future of
the "Jakata PMC". We should stop thinking of "Jakarta" only as an
entity, and go back to thinking of it as to the ASF synonym for
"Java", as originally intended.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
