+1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m
On Sun, Jan 6, 2019 at 1:19 AM iblis <ib...@hs.ntnu.edu.tw> wrote: > Before PR #10149 got merged (Oct 5, 2018) into main repo, > julia code is developed and maintained in the separate repo -- > dmlc/MXNet.jl. > > After that PR, there are no further development happened in dmlc/MXNet.jl. > We work with the main repo now. > But the original MXNet.jl repo is still there, it just isn't deleted or > archived yet. > I receive some issue ticks from this repo occasionally, > maybe we should just disable the issue tracker of it. > > > Does it work with other frameworks other than mxnet? > hmm, I'm not sure what you mean. > > On 1/6/19 1:18 PM, Chris Olivier wrote: > > Curious: Why is the julia code maintained in a separate repo? I was > under > > the impression that it was donated/permanently merged into the mxnet > source > > tree. Does it work with other frameworks other than mxnet? > > > > On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin <ib...@hs.ntnu.edu.tw> wrote: > > > >> If there is trademark issue, how about this option: > >> 3) transferring the MXNet.jl repo ownership from DMLC to Apache. > >> > >> On 1/6/19 6:45 AM, Justin Mclean wrote: > >>> Hi, > >>> > >>>> 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > >>>> It's under DMLC. I have the committer bit of this repo. > >>> > >>> I'm not 100% sure that would be allowed from a branding/trademark > >> perspective, any distribution owned by a 3rd party can't be called > "Apache > >> MXNet". > >>> > >>>> 2) A new repo under ASF's organization? > >>> > >>> That seems preferable I think. > >>> > >>> Thanks, > >>> Justin > >>> > >> > >> -- > >> Iblis Lin > >> 林峻頤 > >> > > > > -- > Iblis Lin > 林峻頤 >