I think the concerns with Metastore are twofold.  One, it’s a common term
in software, and thus would be hard to defend as a trademark.  Hence
Gopal’s link to the Debian package already named metastore.  IANAL but as I
understand trademark law the test is whether a name could cause a
reasonable person to be confused as to who is offering a good or service.
So a McDonalds tire store is ok, a reasonable person knows McDonalds sells
food, not tires, but a restaurant named McDonnies that serves hamburgers
isn’t.  Whether IceWeasal (or any of the suggested names besides metastore)
passes that test I don’t know.  The board will require us to go through a
namesearch as part of the TLP process.

If I understand Gopal’s second point it is that it will cause confusion for
users as to whether this is still part of Hive or something separate.  I
think stressing the continuity is exactly what Vihang and Carl like about
keeping the name.

My suggestion would be that the project needs a name other than metastore,
but we can call the module metastore.  Having a more unique name is good
for trademarks and helping users find your stuff via google, etc.  (Go to
Google and search on “Hive" to see what I mean here.)  If we pick X as the
project name, we can then refer to it as the X metastore, the maven modules
can be x-metastore, etc.  I think this strikes the balance between the
benefits of a unique-ish name and telling users what it does and where it
came from.

Plus, IceWeasal is a _way_ cooler name for a project that metastore. :)

Alan.

On Tue, Jul 25, 2017 at 4:45 PM, Carl Steinbach <c...@apache.org> wrote:

> "IceWeasel" and "MetaStore" are both examples of English compound words.
> What exactly makes the former any safer than the latter?
>
> On Mon, Jul 24, 2017 at 4:17 PM, Gopal Vijayaraghavan <gop...@apache.org>
> wrote:
>
> > Hi,
> >
> >
> > Changing the name isn't really optional or "being google-able" [2].
> >
> > The naming is a crucial part of trademark protection [1], which is the
> > only protection ASF has against hostile Embrace & Extends.
> >
> > Fragmented forks with the same name is particularly bad, especially if
> the
> > feature in question can be only used by a proprietary tool (like Dain's
> > suggestion about Presto view metadata, except it only works with a
> per-cpu
> > license).
> >
> > The safe path isn't pretty, it still ends up with IcedTea and IceWeasel …
> > but at least, those are clearly weird.
> >
> > Cheers,
> > Gopal
> >
> > [1] - https://en.wikipedia.org/wiki/A_moron_in_a_hurry#United_States
> > [2] - https://packages.debian.org/jessie/misc/metastore
> >
> > On 7/24/17, 3:04 PM, "Carl Steinbach" <cwsteinb...@gmail.com> wrote:
> >
> >     +1 to Vihang's suggestion. Changing the name will only cause
> confusion.
> >
> >     On Mon, Jul 24, 2017 at 2:28 PM, Johndee Cloudera <
> > john...@cloudera.com>
> >     wrote:
> >
> >     > +1 Vihang, I do not really like Catalog as it could create
> confusion
> > with
> >     > the Catalog daemon from impala.
> >     >
> >     > On Mon, Jul 24, 2017 at 5:20 PM, Vihang Karajgaonkar <
> > vih...@cloudera.com>
> >     > wrote:
> >     >
> >     > > Before we see a flood of name suggestions :) Why not just keep it
> >     > > Metastore? Its already well-known in the community and easy to
> > relate to.
> >     > >
> >     > > On Mon, Jul 24, 2017 at 2:13 PM, Alan Gates <
> alanfga...@gmail.com>
> >     > wrote:
> >     > >
> >     > > > In the same vein Carter and Gunther suggested Omegastore.  Pick
> > your
> >     > > > alphabet and whether it’s a catalog or a store I guess.
> >     > > >
> >     > > > Alan.
> >     > > >
> >     > > > On Mon, Jul 24, 2017 at 1:35 PM, Sergey Shelukhin <
> >     > > ser...@hortonworks.com>
> >     > > > wrote:
> >     > > >
> >     > > > > I’d like to suggest ZCatalog.
> >     > > > >
> >     > > > > On 17/7/11, 15:41, "Lefty Leverenz" <leftylever...@gmail.com
> >
> > wrote:
> >     > > > >
> >     > > > > >>> I'd like to suggest Riven.  (Owen O'Malley)
> >     > > > > >
> >     > > > > >> How about "Flora"?  (Andrew Sherman)
> >     > > > > >
> >     > > > > >Nice idea and thanks for introducing me to that book,
> Andrew.
> >     > > > > >
> >     > > > > >Along the same lines, how about "Honeycomb"?
> >     > > > > >
> >     > > > > >But since the idea is to make the metastore useful for many
> >     > projects,
> >     > > a
> >     > > > > >generic name that starts with "Meta" would be less confusing
> > ...
> >     > even
> >     > > > > >though it breaks the tradition of Apache projects having
> > quirky
> >     > names.
> >     > > > > >Unfortunately "Metalog" is already in use.  "Metamorph" has
> > other
> >     > > > > >connotations, but it's cool.
> >     > > > > >
> >     > > > > >Naming enthusiasm notwithstanding, I'm +/-0 on the idea of
> > splitting
> >     > > off
> >     > > > > >the metastore into a new project:  -0.5 for the sake of Hive
> > and
> >     > +0.5
> >     > > > for
> >     > > > > >the greater good.  Wishy-washy, that's me.
> >     > > > > >
> >     > > > > >-- Lefty
> >     > > > > >
> >     > > > > >
> >     > > > > >On Tue, Jul 11, 2017 at 1:04 PM, Andrew Sherman <
> >     > > asher...@cloudera.com>
> >     > > > > >wrote:
> >     > > > > >
> >     > > > > >> On Fri, Jun 30, 2017 at 5:05 PM, Owen O'Malley <
> >     > > > owen.omal...@gmail.com>
> >     > > > > >> wrote:
> >     > > > > >>
> >     > > > > >> > On Fri, Jun 30, 2017 at 3:26 PM, Chao Sun <
> > sunc...@apache.org>
> >     > > > wrote:
> >     > > > > >> >
> >     > > > > >> > > and maybe a different project name?
> >     > > > > >> > >
> >     > > > > >> >
> >     > > > > >> > Yes, it certainly needs a new name. I'd like to suggest
> > Riven.
> >     > > > > >> >
> >     > > > > >> > .. Owen
> >     > > > > >> >
> >     > > > > >>
> >     > > > > >> How about "Flora"?
> >     > > > > >>
> >     > > > > >> (Flora is the protagonist of The Bees by Laline Paull)
> >     > > > > >>
> >     > > > > >> -Andrew
> >     > > > > >>
> >     > > > >
> >     > > > >
> >     > > >
> >     > >
> >     >
> >     >
> >     >
> >     > --
> >     > - JRB
> >     >
> >
> >
> >
> >
>

Reply via email to