I put the note.
I'm fine with leaving the issue tracker at that.
On 1/8/19 1:28 AM, Chiyuan Zhang wrote:
I just checked that I have ability to disable the issue tracker on
dmlc/MXNet.jl. Iblis: let me know if you would like me to disable the issue
(after you transferred active ones to mxnet
I just checked that I have ability to disable the issue tracker on
dmlc/MXNet.jl. Iblis: let me know if you would like me to disable the issue
(after you transferred active ones to mxnet main repo). Disabling issues
makes the whole 'issues' tab disappear. I think we can also adopt clojure
repo's
Yes, I have them on main repo.
But for MXNet.jl, I'm repo collaborator.
Anyway, I'm browsing the issues and migrating some of them.
On 1/8/19 12:46 AM, Chris Olivier wrote:
Do you not have write permissions on mxnet repo?
On Mon, Jan 7, 2019 at 6:13 AM iblis wrote:
just found that I don't
Do you not have write permissions on mxnet repo?
On Mon, Jan 7, 2019 at 6:13 AM iblis wrote:
> just found that I don't have the permission to transfer issues of
> dmlc/MXNet.jl.
> Could anyone help me on this?
>
> On 1/7/19 12:16 PM, iblis wrote:
> > okay.
> > Before disabling the issue
I think you need admin permissions on both repos to do that which might be
problematic. Since it looks like there is just one recent open issue, can
you replicate it on the main MXNet repo and have a link to the original
issue?
FWIW - When the Clojure package joined the main repo. I just put
just found that I don't have the permission to transfer issues of dmlc/MXNet.jl.
Could anyone help me on this?
On 1/7/19 12:16 PM, iblis wrote:
okay.
Before disabling the issue tracker, I'm going to transfer the issue
from MXNet.jl to main repo.
(via
okay.
Before disabling the issue tracker, I'm going to transfer the issue
from MXNet.jl to main repo.
(via
https://help.github.com/articles/transferring-an-issue-to-another-repository/)
On 1/7/19 12:17 AM, Chris Olivier wrote:
+1 for disabling issue tracker and putting a note on original repo
+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 wrote:
> Before PR #10149 got merged (Oct 5, 2018) into main repo,
> julia
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
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 wrote:
> If there is trademark issue, how
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.
On 1/6/19 5:48 AM, Carin Meier wrote:
Do you know of any other Julia Apache projects? Maybe we could look and see
how they are doing it.
well, seems no.
--
Iblis Lin
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
Hi,
> I know there are some conditions under which Apache can distribute releases
> downstream.
Short version it's fine to distribute packages that consist of voted on ASF
releases, but you are not allowed to create and distribute packages that
contain un-released code.
See also [1]
Thanks,
Iblis,
Thank you for your work in developing a release process for the Julia
package. Thanks especially for explaining it in way that is approachable
for others not familiar with the Julia dependency management system.
I know there are some conditions under which Apache can distribute releases
Hello MXNet community,
After the Julia package has been imported into the main repo,
the next unresolved issue is establishing the releasing process for Julia.
The PR #12845, which is for upgrading Julia package to work with Julia v0.7+,
is ready for review at this moment.
I want to release the
16 matches
Mail list logo
