Lyken17 commented on issue #7376: MXbox -- a simple and flexible vision toolbox 
for mxnet framework.
   @szha  Gluon's documentation seems to be under construction.  Could u show 
some examples of `mx.symbol`?  In fact `mxbox` provides 
  which allows user to easily create extensions . Thus supports for `mx.symbol` 
should not be a trouble issue.
   @zhreshold Gluon and mxbox are both inspired by torchvision, so they have 
many same functions. What I think is to keep the relation of `mxbox` and 
`mxnet`  like `pytorch` and `torchvision` -- standalone but strongly connected. 
The advantage of doing this is people can develop `mxbox` without affecting 
`mxnet` (push to `mxbox` only), and user can always enjoy the latest update of 
mxbox from PyPi.
   Maintaining a standalone toolbox will not be a nightmare, instead, it brings 
faster update -- for example, a new network comes out, once I get the 
definition scripts and the pretrained weight, I can upload to `mxnet` and give 
a release immediately, where in mxnet, it requires a reviewer to merge in and 
extra time to release a new version on PyPi.
   We all aim for a good toolbox, and I think a standalone repo is a better 
choice. But as I mentioned, my free time on next semester is very limited, so 
to merge in or not, actually depends on later maintainers' idea. If he thinks 
merging to be a better choice, I will create a pull request after construction 
for `model` is finished.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to