On Thu, Jun 29, 2017 at 1:00 PM, Tianqi Chen <[email protected]> wrote: > 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.
+1 on keeping it a separate artifact. However, that is not in conflict to moving it into the MXNet project. There doesn't have to be a 1:1 relationship between Apache projects and the artifacts they produce. The Apache MXNet community could develop and maintain both mxnet and nnvm. > The most ideal case would to have an Apache deep learning stack that > contains NNVM, and MXNet etc. +1! There is no need for that to be a coordinated effort in one project, though. As long as all the projects involved are somewhat apprised of one another and there is community overlap, this can work well. The example of that is the Apache Big Data stack, which consists of many top- and sublevel projects that all, kinda sorta, work together. Markus
