Re: MXNet Name Change?

[Ly Nguyen]

I agree with comments on not breaking momentum by rebranding the name. It's
also my first time hearing about the pronunciation being "mixnet" and not
"m-x-net" so that clarification, along with the motivation behind the name,
feature parity, would strengthen the brand more.

To that point, Sean Comb's evolution of 5 different names was more
confusing than it was helpful. :)

On Wed, Apr 11, 2018 at 1:58 PM, Rahul Huilgol 
wrote:

> Even changing the pronunciation is not an easy thing to do IMHO. As someone
> who has been working on MXNet for the last 8 months, this thread is the
> first time I am reading that MXNet is supposed to be pronounced 'mix-net'.
> We risk losing the momentum even if we try to steer the pronunciation
> towards something which is not popular currently.
>
> I agree Gluon is a friendlier/cooler name. But since we are trying to
> present Gluon as an interface which multiple frameworks can implement, I'm
> not sure if we should try to shift the focus away from MXNet and towards
> Gluon.
>
> As far as adoption goes, I agree with Christopher that public benchmarks or
> blog posts about how MXNet is better or more usable than other frameworks
> would be worth spending effort on. Rebranding in a way to not lose the
> existing momentum honestly sounds more difficult than this :)
>
> By the way, we had some talk of a new friendlier logo sometime back. What
> happened to that?
>
> On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham 
> wrote:
>
> > Changing branding is hard as we already have some momentum under the
> > current name. It's not impossible, and if someone has a fantastic idea
> > and marketing plan for it, it's worth considering.
> >
> > Aside from that, updating the pronunciation could be useful if you
> > like having those gif vs jif debates, but at least people would be
> > talking about it. I personally like the sound of "mix-net" over
> > "em-ex-net". Since we're just starting Youtube videos, I think it's a
> > great idea to establish the pronunciation right away in those videos.
> >
> >
> >
> > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier 
> > wrote:
> > > Just curious why you think it’s a bad idea — you didn’t say?
> > >
> > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY 
> wrote:
> > >
> > >> At least people needs a way to speak it.
> > >> Just define its pronunciation as "mix-net" or "m-x-net" and use the
> > agreed
> > >> one everywhere helps a lot.
> > >> Changing name is a bad idea.
> > >>
> > >> 2018-04-11 20:29 GMT+01:00 Mu Li :
> > >>
> > >> > Agree that MXNet, the combination of Minerva and CXXNet, which can
> be
> > >> > interpreted as mixed-net, is hard to be pronounced. But rebranding a
> > name
> > >> > is a very big decision. We need a very carefully designed marketing
> > plan
> > >> > for it.
> > >> >
> > >> > A choice is that we can gradually refer MXNet as a backend, and talk
> > more
> > >> > about the frontend Gluon.
> > >> >
> > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > >> > thomas.delte...@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > FWIW Brainscript is actually a network definition language:
> > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > >> > > BrainScript-Network-Builder
> > >> > >
> > >> > >
> > >> > >
> > >> > > Thomas
> > >> > >
> > >> > >
> > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang :
> > >> > >
> > >> > > > IIRC CNTK renamed to something like brainscript which does not
> > seem
> > >> to
> > >> > be
> > >> > > > very successful publicity campaign?
> > >> > > >
> > >> > > > Chiyuan
> > >> > > >
> > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> > >> cjolivie...@gmail.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Should we consider renaming MXNet to something more
> "friendly"?
> > >> > > > >
> > >> > > > > IMHO, I think this may be related to adoption problems.
> > >> > > > >
> > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use,
> don't
> > >> they?
> > >> > > > >
> > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > >> > > > >
> > >> > > > --
> > >> > > > Semt ftom m ipohne
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Chen Hanyang 陈涵洋
> > >> Software School Fudan University
> > >> +86-138-1881-7745
> > >>
> >
>
>
>
> --
> Rahul Huilgol
>

Turned off PR builds

[Ly Nguyen]

I turned off PR builds to prioritize testing our v0.11.0 branch for cutting
RC1. The following PR builds that were in progress, and any new PR's or
updated PR's, will be affected and will pick back up once we cut the
release and re-enable PR builds tonight:

7433
7442
7458

Re: how CI system works in MxNet?

[Ly Nguyen]

As mentioned by Sheng this is an ongoing issue and a JIRA ticket has been
filed to Apache Infra team, will follow up tomorrow if status hasn't been
updated. https://issues.apache.org/jira/browse/INFRA-14840

On Sun, Aug 13, 2017 at 9:21 AM, Nan Zhu  wrote:

> no, I mean the CI system in our github repo..
>
> On Sun, Aug 13, 2017 at 8:06 AM, shiwen hu  wrote:
>
> > It may be that Sphinx cannot work incrementally
> >
> > 2017-08-13 23:05 GMT+08:00 shiwen hu :
> >
> > > I think it was the last build of a residual file. Try make clean. first
> > >
> > > 2017-08-13 22:35 GMT+08:00 Nan Zhu :
> > >
> > >> Hi, all
> > >>
> > >> I just noticed something which raises this question
> > >>
> > >> Yesterday afternoon, I checked
> > >> https://github.com/apache/incubator-mxnet/commits/master and the
> first
> > >> commit passed all tests
> > >>
> > >> However, when I checked again this morning, the test result was
> changed
> > to
> > >> fail...
> > >>
> > >> (one of my PRs also exposes this symptom)
> > >>
> > >> Would anyone please share the insights about which part of our CI
> system
> > >> can produce this?
> > >>
> > >> Best,
> > >>
> > >> Nan
> > >>
> > >
> > >
> >
>

[VOTE] Release MXNet version 0.11.0

[Ly Nguyen]

This is the vote to release Apache MXNet (incubating) version 0.11.0.
Voting will start now (Saturday, August 12, 2017 9:26 AM UTC) and
close Tuesday, August 15, 2017 9:26 AM UTC.

Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/v0.11.0+Release+Notes

Link to release candidate 0.11.0.rc0:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc0/



Please test and vote accordingly:

+1 = approve

+0 = no opinion

-1 = disapprove (provide reason)

Re: MXNet project web page

[Ly Nguyen]

The disclaimer message and downloads section is still pending but our
versioned website (thanks to Yao for the help) is on
http://mxnet.incubator.apache.org/. It defaults to our v0.10 docs as our
homepage and also has a master version that updates from the master branch
every night. Every time we make a new release, the homepage will default to
the new version's docs.

Let us know if you have any concerns.

On Fri, Aug 4, 2017 at 11:42 AM, Chris Mattmann <mattm...@apache.org> wrote:

> Check out this guide that shows how to conform to the Apache website
> policies:
>
> https://www.apache.org/foundation/marks/pmcs#introduction
>
> Cheers,
> Chris
>
>
> On 8/4/17, 11:20 AM, "Ly Nguyen" <nguyen...@gmail.com> wrote:
>
> Hi Isabelle,
>
> As Mu mentioned we are in the process of transferring our website to
> http://mxnet.incubator.apache.org so nothing there is official. Thank
> you
> for the note about the disclaimer about be an incubator though.
>
> Is this the writing that we need to add?:
>
> "Apache MXNet (incubating) is an effort undergoing incubation at The
> Apache Software Foundation (ASF), sponsored by the name of Apache
> Incubator PMC. Incubation is required of all newly accepted
> projects until a further review indicates that the
> infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF
> projects. While incubation status is not necessarily a reflection
> of the completeness or stability of the code, it does indicate
> that the project has yet to be fully endorsed by the ASF."
>
> On Fri, Aug 4, 2017 at 9:32 AM, Mu Li <muli@gmail.com> wrote:
>
> > I suggest using the current logo on http://mxnet.io
> >
> > We on the way to transfer the website to
> http://mxnet.incubator.apache.org
> >
> >
> > On Fri, Aug 4, 2017 at 2:35 AM, Isabel Drost-Fromm <
> isa...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > I'm currently in the process of creating a slide deck and wanted
> to use
> > the
> > > mxnet logo as part of that presentation.
> > >
> > > So I want ahead and opened
> > >
> > > http://mxnet.incubator.apache.org
> > >
> > > I found a directory listing including a test directory. Is that
> expected?
> > >
> > > Clicking on the "test" directory opened something that looked a
> whole lot
> > > like a
> > > lovely project page, except it didn't include the standard Apache
> > incubator
> > > branding disclaimer for podlings:
> > >
> > > http://incubator.apache.org/guides/branding.html#disclaimers
> > >
> > >
> > > I checked the Github Repo of the project, the Logo there still
> includes
> > > dmlc as
> > > org and outside of the news list doesn't include any reference to
> the
> > > project
> > > being Apache mxnet (incubating).
> > >
> > > Thinking that maybe ppl are working on a new site/logo already I
> checked
> > > the
> > > issue tracker. All I found was a discussion that seems to have
> subsided
> > 2.5
> > > months ago: https://github.com/apache/incubator-mxnet/issues/6103
> > >
> > > So here I am wondering which logo to include :)
> > >
> > > Isabel
> > >
> > >
> > >
> >
>
>
>
>

Halting code merges until CI is stable

[Ly Nguyen]

Hi, a pending item for our release is adding license headers to all source
files. We first need to stabilize the CI before we can merge the license
headers, which is a very big change. To avoid introducing any breaking
changes, we need to halt merges of new features. Until we have stability
and updated license headers, the only PRs that will be accepted will be bug
fixes.

Ly

Release plan - MXNET 0.11.0

[Ly Nguyen]

We are starting the process to prepare for MXNET v0.11.0 release. We
have drafted release notes
https://cwiki.apache.org/confluence/display/MXNET/v0.11.0+Release+Notes
to cover the tasks under this release.

A release candidate will be cut on Monday, August 7th, and voting will
commence from then until Sunday, August 13th. If you have any
additional features in progress and would like to include it in this
release, please assure they have been merged by Sunday, August 6th
11pm UTC and comment so we may update the release notes.

Feel free to add any other comments/suggestions.

Thanks,

Ly

Release Process

[Ly Nguyen]

A more detailed release process for release managers as the target audience
has been documented here:
https://cwiki.apache.org/confluence/display/MXNET/Release+Process

There are some details such as example commands that are still TODOs and
will be added as we go through the first official release. Please comment
if you have any concerns.

Re: Stop automated message from Apache Git Service

[Ly Nguyen]

JIRA ticket: https://issues.apache.org/jira/browse/INFRA-14732

On Fri, Jul 28, 2017 at 2:10 PM, Naveen Swamy  wrote:

> Can we move such emails to comm...@mxnet.incubator.apache.org or similar ?
>
> Whoever interested can subscribe on that.
>
> Thanks, Naveen
>
> On Fri, Jul 28, 2017 at 1:44 PM, Yuan Tang 
> wrote:
>
> > This is quite annoying. Could anyone please change this?
> >
> > On Fri, Jul 28, 2017 at 4:25 PM Dom Divakaruni <
> > dominic.divakar...@gmail.com>
> > wrote:
> >
> > > Can we please do this?
> > >
> > > @Lnx2
> > >
> > >
> > > > On Jul 28, 2017, at 12:53 PM, Daniel Pono Takamori 
> > > wrote:
> > > >
> > > > 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 possible by the PMC [0]) then please file an
> > > > Infra JIRA ticket [1].
> > > >
> > > > Cheers,
> > > > Pono from Infra
> > > >
> > > > [0] - https://whimsy.apache.org/officers/mlreq
> > > > [1] - https://issues.apache.org/jira/projects/INFRA/summary
> > > >
> > > >> On Fri, Jul 28, 2017 at 12:46 PM, Yutian Li 
> > > wrote:
> > > >> I noticed the emails are sent to a mailing list. So it can't be
> turned
> > > >> off for a single person unless I quit the mailing list?
> > > >>
> > > >>> On Fri, Jul 28, 2017 at 12:38 PM, Yutian Li 
> > > wrote:
> > > >>> Hi,
> > > >>>
> > > >>> Is it possible to stop automated message for every pull request or
> > > >>> issue to a repo that is linked on GitHub?
> > > >>>
> > > >>> I'm receiving these emails from g...@git.apache.org
> > > >>>
> > > >>> Thanks,
> > > >>> Yutian
> > >
> >
>

Re: Granting access to Jenkins

[Ly Nguyen]

Hi, can we also add Naveen Swamy and Mu Li to the jobsadmin group so they
have access to configure Jenkins?

On Tue, Jun 27, 2017 at 2:19 PM, Sebastian <s...@apache.org> wrote:

> I confirmed your subscription to the private@ list, so 3) shoudl already
> be done :)
>
> Best,
> Sebastian
>
>
> On 27.06.2017 23:02, Ly Nguyen wrote:
>
>> Now that I'm a committer and have an account (thanks all!) I still need
>> the
>> following to move migration forward:
>>
>> 1) Grant me access to Jenkins:
>> https://cwiki.apache.org/confluence/display/INFRA/Jenkins#
>> Jenkins-HowdoIgetanaccount
>> 2) Grant write access to mxnet test fork (need to make sure pushes,
>> merges,
>> night tests run against it)
>> https://git-wip-us.apache.org/repos/asf?p=incubator-mxnet-test.git
>> 3) Approve me on the private mailing list
>>
>> @Henri will you support with those?
>>
>> On Tue, Jun 20, 2017 at 4:56 PM, Henri Yandell <bay...@apache.org> wrote:
>>
>> I don't see it; and I don't see it in the moderate queue.
>>>
>>> On Tue, Jun 20, 2017 at 14:28 Naveen Swamy <mnnav...@gmail.com> wrote:
>>>
>>> Henri,
>>>>   I sent a separate email to the private email address(
>>>> priv...@mxnet.incubator.apache.org). I checked with a couple of
>>>>
>>> committers
>>>
>>>> here and they have not got my email, I am wondering who are all on the
>>>> private@ list or is it not setup?
>>>>
>>>> Thanks, Naveen
>>>>
>>>> On Tue, Jun 20, 2017 at 10:33 AM, Ly Nguyen <nguyen...@gmail.com>
>>>> wrote:
>>>>
>>>> I've confirmed with a few folks in the Apache Infra team that I indeed
>>>>>
>>>> have
>>>>
>>>>> to be a committer to be granted access to Jenkins. I would need an
>>>>>
>>>> Apache
>>>
>>>> LDAP account, and the PMC chair would add me to the jobsadmin group as
>>>>> detailed in the link above.
>>>>>
>>>>> On Sat, Jun 17, 2017 at 1:11 PM, Henri Yandell <bay...@apache.org>
>>>>>
>>>> wrote:
>>>>
>>>>>
>>>>> Please send this to private@; the primary use of the private@
>>>>>>
>>>>> channel
>>>
>>>> is
>>>>
>>>>> to
>>>>>> discuss the people side of things; most typically adding new
>>>>>>
>>>>> committers.
>>>>
>>>>>
>>>>>> Using the public side is unfair on Ly if there are negative votes,
>>>>>>
>>>>> and
>>>
>>>> unfair/pressurizing on any negative voter.
>>>>>>
>>>>>> Hen
>>>>>>
>>>>>>
>>>>>> On Sat, Jun 17, 2017 at 8:59 AM, Naveen Swamy <mnnav...@gmail.com>
>>>>>>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Ly,
>>>>>>> Continuous Integration is an integral part of MXNet's development
>>>>>>>
>>>>>> process,
>>>>>>
>>>>>>> you have been making great contributions in setting up Jenkins and
>>>>>>>
>>>>>> the
>>>>
>>>>> related tests for MXNet.
>>>>>>> I propose that we promote Ly Nguyen(github id:lxn2) to be a
>>>>>>>
>>>>>> committer
>>>
>>>> and
>>>>>
>>>>>> make it easy for her to help in migrating Jenkins job to Apache
>>>>>>>
>>>>>> Infra.
>>>>
>>>>>
>>>>>>> thoughts ?
>>>>>>>
>>>>>>> Henri,
>>>>>>> Can you or someone from the PMC board help with this if there are
>>>>>>>
>>>>>> no
>>>
>>>> objections from others?
>>>>>>>
>>>>>>> Thanks, Naveen
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 15, 2017 at 4:11 PM, Ly Nguyen <nguyen...@gmail.com>
>>>>>>>
>>>>>> wrote:
>>>>>
>>>>>>
>>>>>>> Hi, I'm helping with the code migration of MXNet to Apache and
>>>>>>>>
>>>>>>> need
>>>
>>>> to
>>>>>
>>>>>> set
>>>>>>>
>>>>>>>> up jobs on Jenkins. It seems I would need to be a committer
>>>>>>>>
>>>>>>> (detailed
>>>>
>>>>> below) which I'm currently not. What would the group suggest for
>>>>>>>>
>>>>>>> me
>>>
>>>> in
>>>>>
>>>>>> this
>>>>>>>
>>>>>>>> case?
>>>>>>>>
>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/
>>>>>>>>
>>>>>>> Jenkins#Jenkins-
>>>
>>>> HowdoIgetanaccount
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>

IMPORTANT: Link accounts to Apache today 7/12

[Ly Nguyen]

As mentioned in the migration FAQ, if you currently have any kind of write
access to MXNet repo, once migration happens, YOU WILL LOSE IT unless you
do the following.

If you haven't already, please link your Apache accounts (you need to
already be a committer) to Gitbox here: https://gitbox.apache.org/setup/
You will need to enable 2 Factor Auth and make sure all three boxes on the
page show check marks.

Please respond here with your Apache user id once complete.

@pono or @henri will have to make sure that committers and PMC members are
added to the `mxnet` group https://whimsy.apache.org/roster/ppmc/mxnet

Re: Rcpp licensing in Apache MXNet

[Ly Nguyen]

Hey KK,

I know we're planning a release end of this week/beginning of next week. It
may be critical to get this cleared if it is an issue. Eager to hear back.
:)

On Tue, Jul 11, 2017 at 3:35 PM, Qiang Kou <q...@umail.iu.edu> wrote:

> Hi, Ly,
>
> I will let you know when I have the answer.
>
> Best,
>
> KK
>
> On Tue, Jul 11, 2017 at 10:50 AM, Ly Nguyen <nguyen...@gmail.com> wrote:
>
> > Hi @KK, any updates from legal on whether excluding the R pkg is a
> solution
> > for our next release?
> >
> > On Mon, Jul 10, 2017 at 10:49 AM, Qiang Kou <q...@umail.iu.edu> wrote:
> >
> > > Thank you for the info.
> > >
> > > As I understand, if we skip the R pkg when releasing the a new version
> of
> > > MXNet, everything is OK. This is can be done by adding a .gitattribute.
> > >
> > > I will ask on legal-discuss@ for more info and confirmation.
> > >
> > > Really thank you for all the info! It is super helpful.
> > >
> > > Best,
> > >
> > > KK
> > >
> > >
> > > On Fri, Jul 7, 2017 at 8:47 AM, Felix Cheung <
> felixcheun...@hotmail.com>
> > > wrote:
> > >
> > > > I was only referring to string_hash_code.c - it's not being built and
> > > it's
> > > > not part of the binaries release.
> > > >
> > > > There are two parts to it.
> > > >
> > > > For Spark binaries release, R package is built and the output is
> > packaged
> > > > along with the rest of all jars  and python stuff.
> > > >
> > > > There is also a source-only R package that we want to publish to
> CRAN.
> > > > This contains only R source (no java stuff). CRAN will then build
> cross
> > > > platform from that source - but again the part with
> string_hash_code.c
> > is
> > > > disabled.
> > > >
> > > > I guess we should have removed string_hash_code.c from source but we
> > are
> > > > secretly hoping we could sort that out at some point in the future..
> > (ie.
> > > > building cross platform)
> > > >
> > > >
> > > > _
> > > > From: Qiang Kou <q...@umail.iu.edu<mailto:q...@umail.iu.edu>>
> > > > Sent: Friday, July 7, 2017 8:34 AM
> > > > Subject: Re: Rcpp licensing in Apache MXNet
> > > > To: <dev@mxnet.incubator.apache.org<mailto:dev@mxnet.
> > > incubator.apache.org
> > > > >>
> > > >
> > > >
> > > > Really thank you for the info.
> > > >
> > > > Can you tell us a little more on how Spark handles the R package?
> > > >
> > > > The building of R package is skipped when releasing, right?
> > > >
> > > > Best wishes,
> > > >
> > > > KK
> > > >
> > > > On Fri, Jul 7, 2017 at 7:41 AM, Felix Cheung <
> > felixcheun...@hotmail.com<
> > > > mailto:felixcheun...@hotmail.com>>
> > > > wrote:
> > > >
> > > > > Re this
> > > > >
> > > > > The Spark R package includes "R.h" and "Rinternals.h", which are
> both
> > > > LGPL
> > > > > (
> > > > > https://github.com/apache/spark/blob/master/R/pkg/src-
> > > > > native/string_hash_code.c#L24-L25
> > > > > ).
> > > > >
> > > > > This is actually disabled - it is not getting built and it is not
> in
> > > the
> > > > > release - because the way SparkR is packaged in Spark release we
> > > haven't
> > > > > figured out how to release cross multiple platforms.
> > > > >
> > > > > (I'm one of the main contributor to SparkR)
> > > > >
> > > > > 
> > > > > From: Henri Yandell <bay...@apache.org<mailto:bay...@apache.org>>
> > > > > Sent: Friday, July 7, 2017 12:02:16 AM
> > > > > To: dev@mxnet.incubator.apache.org<mailto:dev@mxnet.incubator.
> > > apache.org
> > > > >
> > > > > Subject: Re: Rcpp licensing in Apache MXNet
> > > > >
> > > > > We should bring this up on general@incubator or legal-discuss@.
> > > > >
> > > > > On Thu, Jul 6, 2017 at 10:59 PM, Qiang Kou <q...@umail.iu.edu
> >  > > > q...@umail.iu.ed

Re: Rcpp licensing in Apache MXNet

[Ly Nguyen]

Hi @KK, any updates from legal on whether excluding the R pkg is a solution
for our next release?

On Mon, Jul 10, 2017 at 10:49 AM, Qiang Kou  wrote:

> Thank you for the info.
>
> As I understand, if we skip the R pkg when releasing the a new version of
> MXNet, everything is OK. This is can be done by adding a .gitattribute.
>
> I will ask on legal-discuss@ for more info and confirmation.
>
> Really thank you for all the info! It is super helpful.
>
> Best,
>
> KK
>
>
> On Fri, Jul 7, 2017 at 8:47 AM, Felix Cheung 
> wrote:
>
> > I was only referring to string_hash_code.c - it's not being built and
> it's
> > not part of the binaries release.
> >
> > There are two parts to it.
> >
> > For Spark binaries release, R package is built and the output is packaged
> > along with the rest of all jars  and python stuff.
> >
> > There is also a source-only R package that we want to publish to CRAN.
> > This contains only R source (no java stuff). CRAN will then build cross
> > platform from that source - but again the part with string_hash_code.c is
> > disabled.
> >
> > I guess we should have removed string_hash_code.c from source but we are
> > secretly hoping we could sort that out at some point in the future.. (ie.
> > building cross platform)
> >
> >
> > _
> > From: Qiang Kou >
> > Sent: Friday, July 7, 2017 8:34 AM
> > Subject: Re: Rcpp licensing in Apache MXNet
> > To:  incubator.apache.org
> > >>
> >
> >
> > Really thank you for the info.
> >
> > Can you tell us a little more on how Spark handles the R package?
> >
> > The building of R package is skipped when releasing, right?
> >
> > Best wishes,
> >
> > KK
> >
> > On Fri, Jul 7, 2017 at 7:41 AM, Felix Cheung  > mailto:felixcheun...@hotmail.com>>
> > wrote:
> >
> > > Re this
> > >
> > > The Spark R package includes "R.h" and "Rinternals.h", which are both
> > LGPL
> > > (
> > > https://github.com/apache/spark/blob/master/R/pkg/src-
> > > native/string_hash_code.c#L24-L25
> > > ).
> > >
> > > This is actually disabled - it is not getting built and it is not in
> the
> > > release - because the way SparkR is packaged in Spark release we
> haven't
> > > figured out how to release cross multiple platforms.
> > >
> > > (I'm one of the main contributor to SparkR)
> > >
> > > 
> > > From: Henri Yandell >
> > > Sent: Friday, July 7, 2017 12:02:16 AM
> > > To: dev@mxnet.incubator.apache.org apache.org
> > >
> > > Subject: Re: Rcpp licensing in Apache MXNet
> > >
> > > We should bring this up on general@incubator or legal-discuss@.
> > >
> > > On Thu, Jul 6, 2017 at 10:59 PM, Qiang Kou  q...@umail.iu.edu>> wrote:
> > >
> > > > Really thank you for the clearance.
> > > >
> > > > From the link you provided,
> > > >
> > > > "However, if the component is only needed for optional features, a
> > > project
> > > > can provide the user with instructions on how to obtain and install
> the
> > > > non-included work."
> > > >
> > > > I think this is exactly our case. We provide instructions on how to
> > > install
> > > > GNU R and the Rcpp package.
> > > >
> > > > Besides, our case is very similar with Spark.
> > > >
> > > > The Spark R package includes "R.h" and "Rinternals.h", which are both
> > > LGPL
> > > > (
> > > > https://github.com/apache/spark/blob/master/R/pkg/src-
> > > > native/string_hash_code.c#L24-L25
> > > > ).
> > > >
> > > > Best wishes,
> > > >
> > > > Qiang Kou
> > > >
> > > > On Thu, Jul 6, 2017 at 6:09 PM, Felix Cheung <
> > felixcheun...@hotmail.com>
> > > > wrote:
> > > >
> > > > > I'm not the authority on this but a release from an ASF project is
> > > > > different from releasing with the Apache 2.0 license.
> > > > >
> > > > > You can find more out this here
> > > > > https://www.apache.org/legal/resolved.html#optional
> > > > >
> > > > > Specifically, quote:
> > > > > "Optional means that the component is not required for standard use
> > of
> > > > the
> > > > > product or for the product to achieve a desirable level of
> quality."
> > > > >
> > > > > Basically my interpretation is that if an ASF project cannot
> function
> > > > > without a component, then it is required and such required
> component
> > > > cannot
> > > > > be one of the prohibited licenses.
> > > > >
> > > > > https://www.apache.org/legal/resolved.html#category-x
> > > > >
> > > > > Probably a good idea to start a thread with legal@ if there are
> more
> > > > > questions.
> > > > >
> > > > > _
> > > > > From: Qiang Kou  > > q...@umail.iu.edu>>
> > > > > Sent: Thursday, July 6, 2017 3:41 PM
> > > > > Subject: Re: Rcpp licensing in Apache MXNet
> > > 

Re: MXNet -> Apache Migration proposal

[Ly Nguyen]

Also, DON'T mark the branch as "*Require status checks to pass before
merging*" since builds may be unstable at first. The existing configuration
should be preserved after the transfer but we just have to validate that.

https://help.github.com/articles/enabling-required-status-checks/

On Mon, Jul 10, 2017 at 12:36 PM, Ly Nguyen <nguyen...@gmail.com> wrote:

> From Mu:
> Please preserve the following hooks after transferring:
> -http://mxnet.io:8080/github-webhook/  (docs deployment)
> -https://ci.appveyor.com/api/github/webhook
> all other hooks can be removed
>
> On Mon, Jul 10, 2017 at 12:00 PM, Ly Nguyen <nguyen...@gmail.com> wrote:
>
>> @Suneel I don't think so. We'll just be transferring the organization of
>> the GitHub repo from DMLC -> Apache.
>>
>>
>> Pono has agreed to help with those steps from 2-3:30pm PDT today. Pending
>> Mu adding Pono as an owner.
>>
>> On Sat, Jul 8, 2017 at 11:33 AM, Suneel Marthi <smar...@apache.org>
>> wrote:
>>
>>> I suppose we'll be migrating to apache Gitbox, correct ??
>>>
>>> On Sat, Jul 8, 2017 at 1:48 PM, Li, Mu <m...@amazon.com> wrote:
>>>
>>> > Can we schedule a time on monday to finish the transfer together?
>>> > 
>>> > From: Daniel Pono Takamori <p...@apache.org>
>>> > Sent: Friday, July 7, 2017 5:22 PM
>>> > To: dev@mxnet.incubator.apache.org
>>> > Subject: Re: MXNet -> Apache Migration proposal
>>> >
>>> > 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 have that worked out we can move
>>> > forward with transferring the domain to our control.
>>> >
>>> > Have a great weekend everyone!
>>> >
>>> > On Fri, Jul 7, 2017 at 6:07 PM, Dominic Divakaruni
>>> > <dominic.divakar...@gmail.com> wrote:
>>> > > great stuff!! glad to see this getting close!
>>> > >
>>> > > On Fri, Jul 7, 2017 at 3:47 PM, Ly Nguyen <nguyen...@gmail.com>
>>> wrote:
>>> > >>
>>> > >> We have successfully validated that merges and pull requests
>>> against an
>>> > >> Apache fork of MXNet runs successfully on builds.apache.org:
>>> > >>
>>> > >> https://builds.apache.org/blue/organizations/jenkins/
>>> > incubator-mxnet-master2/detail/master/13/pipeline
>>> > >>
>>> > >> https://builds.apache.org/blue/organizations/jenkins/
>>> > incubator-mxnet-master2/detail/PR-3/1/pipeline
>>> > >>
>>> > >> We have also added a dummy nightly run to be populated with builds
>>> and
>>> > >> test
>>> > >> cases after migration, as discussed. We can now move forward with
>>> the
>>> > >> migration to Apache and I recommend the following steps:
>>> > >> - [ ] Add Pono as owner
>>> > >> - [ ] Pono adds Apache git hooks to MXNet repo
>>> > >> - [ ] Change source control of Apache Jenkins jobs to point to MXNet
>>> > repo,
>>> > >> verify a run is successful
>>> > >> - [ ] Change MXNet org to Apache, verify a run is successful,
>>> mxnet.io
>>> > >> still building
>>> > >> - [ ] Start docs build to mxnet.apache.org
>>> > >> Note that one kink to iron out is that PR build statuses aren’t
>>> being
>>> > >> updated. Here’s a ticket to follow:
>>> > >>
>>> > >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
>>> > rapidView=25=INFRA=detail=INFRA-14540
>>> > >>
>>> > >>
>>> > >> On Sat, Jul 1, 2017 at 9:15 PM, shiwen hu <yajiedes...@gmail.com>
>>> > wrote:
>>> > >>
>>> > >> > 1. The `mxnet directory` is a directory on the current CI server.
>>> He
>>> > >> > contains the necessary files, including library dependencies, data
>>> > files
>>> > >> > needed for testing, compiling scripts needed, and so on.You can
>>> find
>>> > Mu
>&

Re: Typo in the documentation

[Ly Nguyen]

I've posted an issue here: https://github.com/dmlc/mxnet/issues/6721

As soon as I get access to the original graphic I can make the change.

On Thu, Jun 15, 2017 at 9:09 AM, Ly Nguyen <nguyen...@gmail.com> wrote:

> Hi Sebastian. Thank you for spotting this. We will be looking into this
> and send an update later today.
>
> Ly
>
> On Thu, Jun 15, 2017 at 12:41 AM, Sebastian Schelter <s...@apache.org>
> wrote:
>
>> Hi,
>>
>> I think I found an typo in the documentation under
>> http://mxnet.io/architecture/note_engine.html, in the pseudo code for the
>> multiple GPU network:
>>
>>  # aggregate gradient and update
>> fc1_wgrad[cpu]  = fc1_wgrad[gpu0] + fc1_wgrad[gpu1]
>> fc2_wgrad[cpu]  = fc2_wgrad[gpu0] + fc2_wgrad[gpu1]
>> fc1_weight[cpu] -= lr *  fc1_wgrad[gpu0]
>> fc2_weight[cpu] -= lr *  fc2_wgrad[gpu0]
>>
>> I think the last two lines should refer to the weights on the 'cpu'
>> instead
>> of weights on 'gpu0', and these wrong lines have also been copied to the
>> picture below the code.
>>
>> Best,
>> Sebastian
>>
>
>

Granting access to Jenkins

[Ly Nguyen]

Hi, I'm helping with the code migration of MXNet to Apache and need to set
up jobs on Jenkins. It seems I would need to be a committer (detailed
below) which I'm currently not. What would the group suggest for me in this
case?

https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount