Hi Lieven, The reason why we call it GluonCV instead of MXNetCV is because MXNet is a trademark owned by Apache, while Gluon doesn't have this issue.
Best Mu On Sat, Mar 23, 2019 at 1:52 AM Lieven Govaerts <[email protected]> wrote: > Hi, > > On Sat, 23 Mar 2019 at 00:02, Pedro Larroy <[email protected]> > wrote: > > > Hi dev@ > > > > We heard feedback from users that the Gluon name is confusing. Some of > > them don't even know it's MXNet and it's unclear the relationship with > > MXNet > > > > > From personal experience the confusing part is that the Gluon name is used > by both the MXNet community and the (overlapping but separate) GluonCV and > GluonNLP communities: > > - as a user ... As there is overlap between the two code bases (both have > their own model zoo, data loaders, augmentation functions etc.), tutorials > and documentation are not always as clear as they should be if two distinct > names would have been used. > Users and devs are also mot very careful in making the distinction between > the two. Heck, even the logo on the GluonCV homepage is just "GLUON". > > - as an Apache member I'd suggest it's a bad idea to let the Gluon > name/brand be used by projects that are not included in your incubation > here at the ASF. I don't know the history behind this so I'm not pushing in > a certain direction, but IMHO it's an issue that needs to be solved during > your incubation. > > > > > Would it make sense to rebrand Gluon to just MXNet or MXNet > > imperative? Diluting brands and names is never a good idea. > > > > There's also gluonhq which is related to JavaFX which adds to the > > confusion, search engine friendliness is not high as well. > > > > Pedro. > > > > regards, > > Lieven >
