We can keep an open discussion on this. There are pros and cons of having a separate nnvm repo vs merge it into mxnet.
Have a separate repo gives possibility of non-mxnet project to use it, e.g. https://github.com/tqchen/tinyflow NVidia is also considering use NNVM as their graph IR layer. Putting things into mxnet makes maintenance with MXNet easier. In terms of project design, the isolation is clear and there should be no problem of having a separate module. The most ideal case would to have an Apache deep learning stack that contains NNVM, and MXNet etc. That goes beyond what we might be able to tackle in this project and will requires concesus from more folks. Tianqi On Thu, Jun 29, 2017 at 12:48 PM, Markus Weimer <[email protected]> wrote: > On Thu, Jun 29, 2017 at 12:41 PM, Markus Weimer <[email protected]> wrote: > > Sounds good! What license is NNVM under? > > Now that was an unnecessary question :) Sorry about that. I see that > it is ASL 2.0 licensed. Would you consider putting it into Apache > MXNet? There are plenty of players in this space that might be more > comfortable picking it up that way. > > Markus >
