Les Hazlewood wrote:
I'd like to get a definitive answer here, just to ensure this is
absolutely mandatory:
Is it a _requirement_ by the ASF that we change the name?
it _is_ a requirement that the name we pick does not collide with an
existing name already used in a similar area. This has already been
discussed.
Because if
its not, and we can somehow skirt by it, my first choice would be to
keep the name the same...
trust me, if I were confident that we would not have _any_ problem with
JSecurity, I would rather keep this name because it's way better than
any of the other proposal. But It don't think this is the case.
How can we tell definitively?
Post to [EMAIL PROTECTED], ask them, but give them the names we have
googled too. We are not lawyers, we are just trying to avoid any legal
consequences, and if changing the name is the price to pay, well, it's a
cheap price !
Last, not least, people don't use a name, they use a product. The Apache
brand by itself will help more Jsecurity/whatever more than you can
imagine in bringing this product under the sunlights.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
