Change the name gluon will result in a significant problem of backward compatibility for many of the current users, and that would be a huge -1 for the current community. One possibility is to do that is to have a clear roadmap of 2.0(which gives the message of non-backward compatible) and we can discuss which features consolidate, but perhaps that will require a bit more thoughts and coordinated effort.
Tianqi On Fri, Mar 22, 2019 at 5:39 PM Junru Shao <[email protected]> wrote: > @Tianqi For sure GluonCV and GluonNLP should go with the current name. No > reason to change. > > @Lin If customers are interested, I guess we could say they are awesome > toolkits built on top of MXNet Gluon API, and perfect illustration to write > clever and powerful code on the top of it. >
