On 5/13/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 5/13/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote:
> > I don't see why. As a member of the Jakarta PMC I'm willing to allow
> > jakarta-commons.apache.org to use our trademark :-)
>
> The problem is that you will be hijacking the Jakarta name and since the
future of Jakarta
> (and usage of the name) is by no way set, using the Jakarta name in a new
commons
> TLP is for me at this stage a premature call.
We can't "hijack" what is ours. This vote is not taking place on the
Jakarta Commons-Dev list. It is taking place on the Jakarta General
List, and, AFIAK, it represents a vote of the *Jakarta* PMC.
In the alternative, we "hijack" the Commons name, which, as others
have pointed out, is already being used by other ASF entities, not to
mention that it was also used by a top-level project, now closed.
* http://commons.apache.org/
I don't know if Henri has discussed the reuse of the Commons TLP name
with the Board, but it's possible not everyone will be thrilled with
creating a new Commons TLP with a different charter (e.g. "Java").
Nope, all I know of in terms of consensus is that the domain name is
available - there was an opinion that we shouldn't reuse old names,
but the consensus was in favour of commons.apache.org being reusable.
That was at least a year ago.
I think the Commons consensus that the word Java be in the resolution
makes it more likely that there will be debate.
Creating a "Jakarta Commons PMC" avoids overlap with the "closed"
Commons TLP, and avoids overlap with any future projects that might
want to create a TLP
Neither of those seem like things to avoid. The thing to avoid is
being commons.apache.org and then refusing to allow ws-commons to move
to commons.apache.org if they desired, or for .net commons to be
started there.
Maybe the drawing board is needed again.
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, without changing the website (or
even the svn maybe).
* Continue to encourage Jakarta subprojects to move to TLP, go into
maintenance or move over to other PMCs.
* Reach a point at which we can end the Jakarta PMC, or federate or whatever.
Basically we want to clean a room up, but we don't have a spare empty
room to use as a staging point.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
