On 5/15/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
From a practical pov isn't java already associated with the word grouping
"commons apache"?
No, that's the point http://commons.apache.org/
Although this commons project was supposed to replace the commons
efforts in jakarta.apache and x
From a practical pov isn't java already associated with the word grouping
"commons apache"?
If you need a differentiator I would put it in the commons-net.apache.org or
whatever name instead of soiling the existing "branding" that has already
been cemented in everyones minds whether people like
Should it be commons4j.apache.org? (j = java or jakarta)? am not
worried about the java package name...
thanks,
dims
On 5/14/07, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Travelling ATM, limited internet
My preference is for a java-only commons.apache.org. I don't see that as scary
or
That's the most logical argument I've seen on this thread. :)
+1 (probably not binding and not mattering )
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.
Steph
Travelling ATM, limited internet
My preference is for a java-only commons.apache.org. I don't see that as scary
or unreasonable. My +1 is based on that assumption.
Also, from a practical matter, our projects already use org.apache.commons, so
this is already recognised in the ASF.
Stephen
On 5/14/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote:
If moving commons TLP is just a "twisted" (maybe a bad choice of a word) way to
come back to
jakarta.apache.org in the end, I am -1 on the TLP move..
IF, its a big if and one I think we need to devote some though, and a
*modest* ;-) am
If moving commons TLP is just a "twisted" (maybe a bad choice of a word) way to
come back to
jakarta.apache.org in the end, I am -1 on the TLP move..
We currently have 2 projects moving TLP (Turbine and POI) and after that we
need to start thinking
about every other project at Jakarta.
So if th
-1 to Commons being Jakarta. Commons should be commons, have its own
PMC/domain. It already has its own brand recognition. I had an
interesting conversation with a large financial customer about it just
before I left JBoss. They weren't clearly even aware that commons was
part of Jakarta.
-
On 5/8/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
[ ] +1 I support the proposal
[ ] +0 I don't care
[ ] -1 I'm opposed to the proposal because...
-1
I would like to see the issues raised regarding the name resolved.
I would also like to see the options regarding commons as a successor
to t
On 5/14/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
As my random suggestion that Ted quoted points out, you can have a PMC
without their having to be TLP. Least I was told that a couple of
years ago either on board@ or face to face, so we could do the
following:
* Create the Jakarta Commons PMC
10 matches
Mail list logo
