mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yuelin Zhang <zhangyuelinch...@gmail.com>
Subject Separate repo for MXNet infrastructure
Date Wed, 01 Aug 2018 07:36:24 GMT
Hello all,

I worked on a label bot which serves MXNet community. It is able to:
1. Send daily GitHub issue reports   (design
<https://cwiki.apache.org/confluence/display/MXNET/Machine+Learning+Based+GitHub+Label+Bot#MachineLearningBasedGitHubLabelBot-PartI-EmailBot>)
(PR 11861 <https://github.com/apache/incubator-mxnet/pull/11861>)
2. Predict labels of unlabeled issues (design
<https://cwiki.apache.org/confluence/display/MXNET/Machine+Learning+Based+GitHub+Label+Bot#MachineLearningBasedGitHubLabelBot-PartII-Predictlabelsautomaticallyforunlabeledissues>)
(PR 11935 <https://github.com/apache/incubator-mxnet/pull/11935> )
3. Help non-committers to add labels (design
<https://cwiki.apache.org/confluence/display/MXNET/Machine+Learning+Based+GitHub+Label+Bot#MachineLearningBasedGitHubLabelBot-PartIII-LabelBot>)
(PR 11957 <https://github.com/apache/incubator-mxnet/pull/11957>)

My concern is where should my code be finally merged. This bot is not a
part of MXNet framework but it serves MXNet community. For now, a good
option is to have a separate repo for infrastructure.

I will appreciate it if someone can share ideas.

Thanks,

Cathy

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message