As a physicist I would like to point out that "Gluon" means: An elementary
particle that acts as the exchange particle for the strong force between
quarks [1].
As a general scientific term it can barely be seen as a candidate for
trademark registration.

[1] https://en.wikipedia.org/wiki/Gluon

On Fri, 30 Aug 2019 at 10:27, Leonard Lausen <l-softw...@lausen.nl> wrote:

> Carin recently noted that gluonhq.com already uses the Gluon brand for
> end-to-end enterprise mobile solution and Marco found that they do so
> apparently since at least 2015. Do you see any impact on the Gluon brand
> for deep learning models?
>
> The MXNet brand is currently also unregistered by Apache (but registered
> by various other companies), whereas for example Tensorflow is
> registered by Google LLC in a variety of jurisdictions. Trademarks
> registered under the Madrid System can be found at
> https://www3.wipo.int/branddb/en/
>
> Best regards
> Leonard
>
> Hen <bay...@apache.org> writes:
>
> > Amazon. Amazon created the brand. They own the first repository to use
> the
> > term in this conext ( https://github.com/gluon-api ). There was some
> > involvement from Microsoft, so Microsoft's opinion may also be relevant.
> > Gluon is not an Apache Software Foundation nor Apache MXNet brand.
> >
> > Unless it was very recent, I don't believe there have been any trademark
> > registrations. If Amazon would prefer Apache control the Gluon naming, I
> > think the simplest 'act' to make that so would be to move the gluon-api
> > repository over to ASF control.
> >
> > Hen
> >
> > On Thu, Aug 29, 2019 at 8:27 AM Chris Olivier <cjolivie...@gmail.com>
> wrote:
> >
> >> Who is the gluon “Brand Owner”?
> >>
> >> On Tue, Aug 27, 2019 at 10:43 AM Chris Olivier <cjolivie...@gmail.com>
> >> wrote:
> >>
> >> > Who is the gluon "brand owner"?
> >> >
> >> > On Tue, Aug 27, 2019 at 10:13 AM Qing Lan <lanking...@live.com>
> wrote:
> >> >
> >> >> Hi Lieven,
> >> >>
> >> >> Thanks for your comments. After the discussion with several
> committers
> >> >> and contributors offline, we agreed that there are space for
> >> improvement.
> >> >>
> >> >>
> >> >>   1.  About the Gluon naming
> >> >>
> >> >> As we know, Gluon is born with the unique API design pattern. It
> >> >> gradually became the dominant Python front end for MXNet. I would
> >> suggest
> >> >> to discuss more with the Brand owner and see if there could be a
> further
> >> >> integration with MXNet. To MXNet itself, it becomes more popular with
> >> this
> >> >> frontend. We lean on the strong community and improve our product
> >> better by
> >> >> consuming the feedback from it.
> >> >>
> >> >>      2. Diversity of the PMC
> >> >> Currently, we have 40 PMC numbers from different companies, like
> Amazon,
> >> >> Uber, NVIDIA, ByteDance and a lot more. We are trying to grow the
> number
> >> >> and invite indivials from different companies as well as research
> >> institute.
> >> >>
> >> >>     3. Release rotation
> >> >> In the history, most of the releases were done by the Amazon side.
> >> >> Currently, we are moving on to rotate this responsibility with
> >> >> contributors/committers not from Amazon to start working on them.
> >> >>
> >> >>     4. Committers from different firm/institution should have real
> work
> >> >> on MXNet
> >> >> I can tell from the issues/PRs/rfcs they submitted and indeed and
> indeed
> >> >> we should encourage the committers who is less active to be involved
> >> into
> >> >> MXNet contribution.
> >> >>
> >> >> Thanks,
> >> >> Qing
> >> >>
> >> >> ________________________________
> >> >> From: Lieven Govaerts <l...@mobsol.be>
> >> >> Sent: Saturday, August 10, 2019 5:59
> >> >> To: dev@mxnet.incubator.apache.org <dev@mxnet.incubator.apache.org>
> >> >> Cc: d...@mxnet.apache.org <d...@mxnet.apache.org>
> >> >> Subject: Re: [DISCUSS] Apache MXNet: Path to graduation
> >> >>
> >> >> Hi Qing,
> >> >>
> >> >> as a user and ASF member observing this project:
> >> >>
> >> >> On Sat, 10 Aug 2019 at 01:44, Qing Lan <lanking...@live.com> wrote:
> >> >>
> >> >> > Hi All,
> >> >> >
> >> >> > I would like to start a thread to discuss about the graduation for
> >> >> Apache
> >> >> > MXNet. From my time working in the community, I saw a great
> >> improvement
> >> >> in
> >> >> > most of the area that we do to make MXNet a better place. We keep
> >> >> tracking
> >> >> > on all of the issues user raised and reviewing PRs. We follow the
> >> Apache
> >> >> > Way to release the package in official repository.
> >> >> >
> >> >> >
> >> >> in terms of code, documentation, visibility this project is certainly
> >> in a
> >> >> healthy state, I see a lot of interest of companies and people, the
> >> >> community is growing... As a user that gives me confidence my time
> >> >> invested
> >> >> in this product is well spent.
> >> >>
> >> >>
> >> >> > In 2017, Apache MXNet joined the Apache incubation project. I think
> >> now
> >> >> is
> >> >> > a good time to review the path to graduate MXNet and move forward
> to
> >> it.
> >> >> > Please feel free to share your thoughts on graduation and space for
> >> >> > improvement.
> >> >> >
> >> >> >
> >> >> If I may share one observation: I don't see the community working a
> lot
> >> on
> >> >> non-code topics. One example that I personally find important is the
> >> >> discussion of the Gluon brand. People have expressed confusion about
> how
> >> >> the name is used by multiple non-ASF projects, the MXNet team finds
> the
> >> >> Gluon name very valuable yet the discussion on how to protect the
> name
> >> and
> >> >> decide on acceptable use by other projects has stalled [1]. I suggest
> >> you
> >> >> make a decision on this topic before you go for graduation.
> >> >>
> >> >> regards,
> >> >>
> >> >> Lieven
> >> >>
> >> >> [1]
> >> >>
> >> >>
> >>
> https://mail-archives.apache.org/mod_mbox/mxnet-dev/201903.mbox/%3ccac_cu1gi+3s6ob48kt0x5wta4oxdum8uq9tmnyku2ujyaya...@mail.gmail.com%3e
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> > You can find more about graduation policy in here:
> >> >> > https://incubator.apache.org/guides/graduation.html
> >> >> >
> >> >> > Thanks,
> >> >> > Qing
> >> >> >
> >> >>
> >> >
> >>
>

Reply via email to