This looks great Ly. On Monday we can transfer the main repo over and
then you can change the builds to point to the official repo. I'll
make a clone of the website next week so we can do a similar thing to
test building the website and then we can publish it to
mxnet.incubator.apache.org. Once
We just transferred the mxnet repo to the Apache Organization, that's
what's causing the increased mail to dev@mxnet. There needs to be a
log for all events on Github, and as such these are sent to the dev@
list. If there is consensus in moving the mail to another list
(creating another is
Hey there, we've got https://travis-ci.org/apache/incubator-mxnet
which was recently added in to our Org. In the move from org to org,
it seems something is off since the builds are kicking off on PRs.
I've disabled and reenabled the builds for this repo, but it doesn't
seem to be triggering
attention for work items
4). Discussion about your build system should be more transparent and
certainly include the Infra team.
Thanks for listening and good luck Incubating!
-Daniel Pono Takamori
Unfortunately we won't be able to enable all the Groovy methods for
security reasons. Fortunately the Beam team has found some work
arounds for this so I'm cc'ing them to connect you to figure out how
to get around this issue.
Jason, if you could point the MXNet folks to your builds repo so they
