On Jan 11, 2009, at 4:02 PM, Tim Veil wrote:


On Jan 11, 2009, at 5:53 PM, Alan D. Cabrera wrote:


On Jan 11, 2009, at 10:52 AM, Tim Veil wrote:

I guess my take is that
JSecurity has been in the name of this project for nearly 4 years without compliant

Sorry, I'm not following. Unless Juniper has held the name for three years or less, how is that relevant?

I guess I'm suggesting that JSecurity has been out in the wild for 4 years. At no time during this period has Juniper been concerned about name collision enough to contact anyone on the project. That suggests to me they will be unlikely to do so in the future. I have no idea how long they have been using their name.

Let's say that 4 years ago a bunch of buddies and I in North Dakota started a project called Google. It's pretty popular and people in South Dakota even start using it. We have been out in the wild for 4 years. At no time during this period has Google Inc. in Mountain View, CA, been concerned about name collision enough to contact anyone on the project. Does this suggest that they are unlikely to do so in the future when developers in CA start using it? Not likely.

JSecurity has name recognition and a following

Sorry, I don't understand if this is pertinent other than it being motivation for keeping the name. I also am motivated to keep the name but I don't see how we can get past the issues below.

The project of concern, "J-Security" is not a product at all but rather a " resource for security information and analysis." J-Security's parent company Juniper is in the network hardware business not the Java application business JSecurity is an open-source software project not a "product" we are looking to sell (not a competitor in any way to Juniper)

It doesn't matter if we sell a product or not. It's a name collision, albeit a potential collision. If they chose to push out a product under that name we would be in trouble; if I am wrong here someone please tell me.

I don't think you are wrong it just seems like such a remote possibility. In order for them to do this they would have to stray pretty far from their existing business. Even if they were to enter the fray and offer a similar product it seems unlikely they would choose to do so under the J-Security banner. I would imagine they would they would create a new brand for this service since they already have an unrelated presence under the name J-Security. Repackaging their J-Security center into something unrelated wouldn't make much sense.

One of my jobs as a mentor is to protect the ASF as new projects are incubated. Let's hope that discussions with Juniper work out.

Now, if you told me that we held our name longer than Juniper held theirs then it would be a different story.

So to put it more succinctly, here are the criteria where I am happy to change my vote. Any single one would work for me.


Would you change your vote if I use the magic word?  Please?


Heh heh. I wish it were that easy. (I'm sure others are mumbling that they wish it were as well ;) )


Regards,
Alan

Reply via email to