Re: Can I please join the slack channel? Thank you

[Henri Yandell]

Looks like you've been added :)

On Fri, Oct 13, 2017 at 6:54 PM, paddy horan  wrote:

>
>
> Sent from Mail for
> Windows 10
>
>

Re: Apache MXNet build failures are mostly valid - verify before merge

[Henri Yandell]

A late followup on this.

Is the "How a committer develops on MXNet" documented anywhere?
Staging/master etc? The more complex the development process, the harder it
is for a newcomer to get involved on the project. I couldn't find it on the
website/github.

(I'd also note that the 'how to modify the website/documentation' also
needs to be documented)

I'd suggest that the how-to-dev doc also explain why it's bad for master to
not build. One could argue that, outside of when a release is being made,
master is not important to our users. Yes it should build, but an accident
should only affect those who have put themselves on the bleeding edge.

Hen

On Mon, Oct 2, 2017 at 1:19 PM, Gautam  wrote:

> Thanks All.
>
>  I've created the JIRA to mark the protected branch for master
> https://issues.apache.org/jira/browse/INCUBATOR-205.
> We also need to add all the committers to be code owner as discussed in the
> slack, I've opened a PR for it
> https://github.com/apache/incubator-mxnet/pull/8128.
>
> Good point Joern, I'll follow up on that.
>
> Regards,
> Gautam
>
> On Fri, Sep 29, 2017 at 2:20 AM, Joern Kottmann 
> wrote:
>
> > It also makes sense to block too old PRs from merging, because the
> > test results are outdated and the build might fail after it gets
> > merged.
> >
> > Jörn
> >
> > On Thu, Sep 28, 2017 at 9:14 PM, Zha, Sheng  wrote:
> > > +1 on protected branch.
> > >
> > > Best regards,
> > > -sz
> > >
> > > On 9/28/17, 11:48 AM, "Kumar, Gautam"  wrote:
> > >
> > > Hi Guys,
> > >
> > >  Let’s focus on specific issue here.
> > >
> > > Marking the master branch protected which involves “Only merge if
> > checks has passed, and yes it will run the complete build”.
> > >
> > > We can’t afford to degrade the quality and keep debugging the build
> > failure forever. If it’s slow down the development at the cost of
> quality I
> > will vote for the quality.
> > > We can work on improving the infrastructure to improve the overall
> > speed.  If you have any specific concerns on availability of Jenkins
> please
> > point out.
> > >
> > > -Gautam
> > >
> > >
> > > On 9/28/17, 11:38 AM, "Chris Olivier" 
> wrote:
> > >
> > > -1000 on that. :)
> > >
> > > On Thu, Sep 28, 2017 at 11:33 AM Naveen Swamy <
> > mnnav...@gmail.com> wrote:
> > >
> > > > PR->Sanity test/Linux build/test->reviewer/committer approves
> > the
> > > > change->Comment "Build Now" (Or trigger on at least one
> > approval from a
> > > > committer other than author)->*Full build-*>*passes
> > build*->Enable Merge
> > > >
> > > > Let us take this particular topic to a separate thread or
> > discuss offline
> > > > if further clarification is needed.
> > > >
> > > > On Thu, Sep 28, 2017 at 11:24 AM, Chris Olivier <
> > cjolivie...@gmail.com>
> > > > wrote:
> > > >
> > > > > I understand the proposal.  How to trigger a build in that
> > case?
> > > > >
> > > > >
> > > > > On Thu, Sep 28, 2017 at 10:54 AM Madan Jampani <
> > madan.jamp...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Chris,
> > > > > > I don't think Naveen is suggesting that a merge happen
> > without full
> > > > > > verification i.e. all tests across all platforms pass.
> > > > > > If a PR has some back and forth and results in multiple
> > revisions
> > > > (which
> > > > > is
> > > > > > arguably more common than a random unit test failing), we
> > simply delay
> > > > > full
> > > > > > verification until the owner/reviewer have settled on a
> > mutually
> > > > > acceptable
> > > > > > state.
> > > > > >
> > > > > > On Thu, Sep 28, 2017 at 10:25 AM, Chris Olivier <
> > cjolivie...@gmail.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > -1 for running only partial tests.  Most failing unit
> > tests that get
> > > > > > > through fail only for certain platforms/configurations.
> > I personally
> > > > > > > prefer to be assured the build and test is good before
> > merge.  Most
> > > > PR
> > > > > > > merges aren't in a huge hurry.
> > > > > > >
> > > > > > > On Thu, Sep 28, 2017 at 9:54 AM, Naveen Swamy <
> > mnnav...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > +1 to make it protected. Here is what I am thinking
> > for PR builds
> > > > > > > > on a PR run Sanity Tests + build/test one
> > platform->committer
> > > > reviews
> > > > > > the
> > > > > > > > code and issues "Build Now", a full build is
> > run->Github checks
> > > > that
> > > > > > the
> > > > > > > > full build checks succeed before it can be merged.
> > > > > > > >
> > > > > > > > I agree with Madan that PR should be approved by on

Re: Podling Report - Draft

[Henri Yandell]

I suspect that was me thinking the podling  status page was still the
canonical location rather than whimsy :(

Hen

On Sat, Oct 7, 2017 at 05:45 Jim Jagielski  wrote:

> AFAIK, I was never a Mentor. I volunteered, but was never
> added, which was confirmed by checking via Whimsy.
>
> > On Oct 6, 2017, at 7:40 PM, John D. Ament  wrote:
> >
> >
> >
> > On 2017-10-06 00:30, Henri Yandell  wrote:
> >> Done. Markus + Jim left :)
> >
> > How was this communicated?  Or maybe when?
> >
> >>
> >> On Tue, Oct 3, 2017 at 7:37 PM, Suneel Marthi 
> wrote:
> >>
> >>> The report's been posted to Wiki - mentors please comment and sign-off.
> >>>
> >>> On Tue, Oct 3, 2017 at 10:02 PM, Seb Kiureghian 
> >>> wrote:
> >>>
> >>>> Thanks Chris, fixed:
> >>>> https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> >>>> biPh4-aCm8-bWwFzexnOW_GMA/edit
> >>>>
> >>>> John, thanks for the suggestion. We will use Confluence for the next
> >>>> report.
> >>>>
> >>>> On Tue, Oct 3, 2017 at 6:11 PM, John D. Ament 
> >>>> wrote:
> >>>>
> >>>>> Its great to see community working on a report.  don't forget to post
> >>> it
> >>>>> to the wiki.  In addition, I would like to see you move the creation
> of
> >>>> it
> >>>>> into ASF infrastructure.  Many projects use Confluence to write it,
> >>>> others
> >>>>> use private SVN repos.
> >>>>>
> >>>>> On 2017-10-03 18:01, Chris Olivier  wrote:
> >>>>>> Are the line breaks added manually? Might be better if it wraps
> >>>>> naturally.
> >>>>>> For example, on my phone, the formatting is scattered at the line
> >>>> breaks:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Oct 3, 2017 at 2:45 PM Seb Kiureghian 
> >>>>> wrote:
> >>>>>>
> >>>>>>> Henri,
> >>>>>>>
> >>>>>>> I've updated the doc with your suggestions. Please check and sign
> >>>> off.
> >>>>>>>
> >>>>>>>
> >>>>>>> https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> >>>>> biPh4-aCm8-bWwFzexnOW_GMA/edit
> >>>>>>>
> >>>>>>> On Mon, Oct 2, 2017 at 11:01 AM, Henri Yandell 
> >>>>> wrote:
> >>>>>>>
> >>>>>>>> Can something be added on the website migration please. Also, not
> >>>>> sure if
> >>>>>>>> code migration should be listed as a "important thing for
> >>>>> graduation" if
> >>>>>>>> it's done.
> >>>>>>>>
> >>>>>>>> Perhaps one of:
> >>>>>>>>
> >>>>>>>> * migrate mxnet.io DNS
> >>>>>>>> * bring website up to Apache standard
> >>>>>>>> * identify if any more ICLAs or SGAs need signing
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Sun, Oct 1, 2017 at 08:58 Seb Kiureghian 
> >>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hi Dev@,
> >>>>>>>>>
> >>>>>>>>> As you may know, our Podling report is due this Wednesday.
> >>> Bhavin
> >>>>> Thaker
> >>>>>>>>> and I have prepared a draft:
> >>>>>>>>> https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> >>>>>>>>> biPh4-aCm8-bWwFzexnOW_GMA/edit
> >>>>>>>>>
> >>>>>>>>> Feel free to take a look and suggest edits. I'll submit this on
> >>>>>>> Wednesday.
> >>>>>>>>>
> >>>>>>>>> Best Regards,
> >>>>>>>>> Seb
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>

Re: Podling Report - Draft

[Henri Yandell]

Done. Markus and Jim left to comment + sign off :)

On Fri, Oct 6, 2017 at 4:40 PM, John D. Ament  wrote:

>
>
> On 2017-10-06 00:30, Henri Yandell  wrote:
> > Done. Markus + Jim left :)
>
> How was this communicated?  Or maybe when?
>
> >
> > On Tue, Oct 3, 2017 at 7:37 PM, Suneel Marthi 
> wrote:
> >
> > > The report's been posted to Wiki - mentors please comment and sign-off.
> > >
> > > On Tue, Oct 3, 2017 at 10:02 PM, Seb Kiureghian 
> > > wrote:
> > >
> > > > Thanks Chris, fixed:
> > > > https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > > > biPh4-aCm8-bWwFzexnOW_GMA/edit
> > > >
> > > > John, thanks for the suggestion. We will use Confluence for the next
> > > > report.
> > > >
> > > > On Tue, Oct 3, 2017 at 6:11 PM, John D. Ament  >
> > > > wrote:
> > > >
> > > > > Its great to see community working on a report.  don't forget to
> post
> > > it
> > > > > to the wiki.  In addition, I would like to see you move the
> creation of
> > > > it
> > > > > into ASF infrastructure.  Many projects use Confluence to write it,
> > > > others
> > > > > use private SVN repos.
> > > > >
> > > > > On 2017-10-03 18:01, Chris Olivier  wrote:
> > > > > > Are the line breaks added manually? Might be better if it wraps
> > > > > naturally.
> > > > > > For example, on my phone, the formatting is scattered at the line
> > > > breaks:
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Oct 3, 2017 at 2:45 PM Seb Kiureghian <
> sebou...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Henri,
> > > > > > >
> > > > > > > I've updated the doc with your suggestions. Please check and
> sign
> > > > off.
> > > > > > >
> > > > > > >
> > > > > > > https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > > > > biPh4-aCm8-bWwFzexnOW_GMA/edit
> > > > > > >
> > > > > > > On Mon, Oct 2, 2017 at 11:01 AM, Henri Yandell <
> he...@yandell.org>
> > > > > wrote:
> > > > > > >
> > > > > > > > Can something be added on the website migration please.
> Also, not
> > > > > sure if
> > > > > > > > code migration should be listed as a "important thing for
> > > > > graduation" if
> > > > > > > > it's done.
> > > > > > > >
> > > > > > > > Perhaps one of:
> > > > > > > >
> > > > > > > > * migrate mxnet.io DNS
> > > > > > > > * bring website up to Apache standard
> > > > > > > > * identify if any more ICLAs or SGAs need signing
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sun, Oct 1, 2017 at 08:58 Seb Kiureghian <
> sebou...@gmail.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > >> Hi Dev@,
> > > > > > > >>
> > > > > > > >> As you may know, our Podling report is due this Wednesday.
> > > Bhavin
> > > > > Thaker
> > > > > > > >> and I have prepared a draft:
> > > > > > > >> https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > > > > > > >> biPh4-aCm8-bWwFzexnOW_GMA/edit
> > > > > > > >>
> > > > > > > >> Feel free to take a look and suggest edits. I'll submit
> this on
> > > > > > > Wednesday.
> > > > > > > >>
> > > > > > > >> Best Regards,
> > > > > > > >> Seb
> > > > > > > >>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

PROCESS: Contacting the Apache Infra team

[Henri Yandell]

Hi Apache MXNet Committers and Contributors,

As a community we've been sending a lot of requests (JIRA, HipChat etc) in
the direction of the Apache Infra team without discussing them first here.
As a community we are causing them a lot of work corralling topics that
would be better sorted out on our dev@ list first.

We also have contributors who are contacting the Infra team without being
representatives of the project (i.e. committers). Contributors - your
energy is very much appreciated, but there is no way for Infra to know who
you are.

Going forward, please raise _all_ Infra topics on the dev@ list for initial
discussion. Once its been discussed as a community, one of the 5 mentors
for the project will make the request on the Infra JIRA. If a contributor
is subsequently looking to assist Infra (and because mentors aren't
infinitely scalable), my expectation is for a mentor to then introduce that
contributor to Infra on their Hipchat if deeper conversation is needed.

Thank you,

Hen

Re: Podling Report - Draft

[Henri Yandell]

Done. Markus + Jim left :)

On Tue, Oct 3, 2017 at 7:37 PM, Suneel Marthi  wrote:

> The report's been posted to Wiki - mentors please comment and sign-off.
>
> On Tue, Oct 3, 2017 at 10:02 PM, Seb Kiureghian 
> wrote:
>
> > Thanks Chris, fixed:
> > https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > biPh4-aCm8-bWwFzexnOW_GMA/edit
> >
> > John, thanks for the suggestion. We will use Confluence for the next
> > report.
> >
> > On Tue, Oct 3, 2017 at 6:11 PM, John D. Ament 
> > wrote:
> >
> > > Its great to see community working on a report.  don't forget to post
> it
> > > to the wiki.  In addition, I would like to see you move the creation of
> > it
> > > into ASF infrastructure.  Many projects use Confluence to write it,
> > others
> > > use private SVN repos.
> > >
> > > On 2017-10-03 18:01, Chris Olivier  wrote:
> > > > Are the line breaks added manually? Might be better if it wraps
> > > naturally.
> > > > For example, on my phone, the formatting is scattered at the line
> > breaks:
> > > >
> > > >
> > > >
> > > > On Tue, Oct 3, 2017 at 2:45 PM Seb Kiureghian 
> > > wrote:
> > > >
> > > > > Henri,
> > > > >
> > > > > I've updated the doc with your suggestions. Please check and sign
> > off.
> > > > >
> > > > >
> > > > > https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > > biPh4-aCm8-bWwFzexnOW_GMA/edit
> > > > >
> > > > > On Mon, Oct 2, 2017 at 11:01 AM, Henri Yandell 
> > > wrote:
> > > > >
> > > > > > Can something be added on the website migration please. Also, not
> > > sure if
> > > > > > code migration should be listed as a "important thing for
> > > graduation" if
> > > > > > it's done.
> > > > > >
> > > > > > Perhaps one of:
> > > > > >
> > > > > > * migrate mxnet.io DNS
> > > > > > * bring website up to Apache standard
> > > > > > * identify if any more ICLAs or SGAs need signing
> > > > > >
> > > > > >
> > > > > > On Sun, Oct 1, 2017 at 08:58 Seb Kiureghian 
> > > wrote:
> > > > > >
> > > > > >> Hi Dev@,
> > > > > >>
> > > > > >> As you may know, our Podling report is due this Wednesday.
> Bhavin
> > > Thaker
> > > > > >> and I have prepared a draft:
> > > > > >> https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > > > > >> biPh4-aCm8-bWwFzexnOW_GMA/edit
> > > > > >>
> > > > > >> Feel free to take a look and suggest edits. I'll submit this on
> > > > > Wednesday.
> > > > > >>
> > > > > >> Best Regards,
> > > > > >> Seb
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Migration of Apache MXNet from Private Slack area to ASF Slack

[Henri Yandell]

I'm signed up to the asf slack John. Could you give me admin access please?
(i'm not sure if being signed up to the asf slack is enough or if I should
have joined a particular channel.

Noting a typo in your email,  the-asf.slack.com rather than
the-ask.slack.com (unless we're planning to move into finance).

I don't know how to see how many have access to the current mxnet slack,
but I know that we give users and contributors access whenever any request.
Will that be an issue for the Apache one?

Hen


On Thu, Oct 5, 2017 at 7:40 PM, John D. Ament 
wrote:

> Dear Apache MXNet Podling,
>
> I would like to request that you migrate off of your external Slack
> instance and into the common one used, hosted as the-ask.slack.com.  By
> default sign up is restricted to @apache.org email addressed, but I would
> be happy to facilitate giving more people access to it.  I have given
> Suneel admin access, and assuming other mentors sign up I will give them
> access to invite non-apache.org email addresses.
>
> Please let me know your thoughts and if you think you can migrate over.
>
> John
>

Re: Web site questions

[Henri Yandell]

Looking at this link, that repo has been getting a nightly commit because
doxygen inserts the date:

https://github.com/apache/incubator-mxnet-site/commits/asf-site

Does the website live on the incubator-mxnet-site repo, or in the
incubator-mxnet/docs directory?

Hen

On Thu, Sep 28, 2017 at 1:17 AM, Seb Kiureghian  wrote:

> Hi Henry,
>
> 1. Not sure where you see the 'generated by' text. Could you provide a
> link?
>
> 2/3. The redesign is live at /master. I'm working with Santhosh Karuhatty
> to fix simple errors, and here
> <https://github.com/apache/incubator-mxnet/pulls?q=is%
> 3Apr+author%3Athinksanky>
> are
> some of the merged PR's. Your suggestions
> <https://github.com/apache/incubator-mxnet-site/issues> are good ones,
> although I was not aware of this separate repo for the website. Let's
> tackle these - I'll comment on the issues you've created.
>
> Seb
>
> On Wed, Sep 27, 2017 at 11:17 PM, Henri Yandell  wrote:
>
> > Looking at the website ( https://github.com/apache/incubator-mxnet-site
> ),
> > I've some questions:
> >
> > 1) Do we really need jenkins constantly committing date updates for
> > doxygen? Is there a way to stop that 'generated by' text including the
> > date?
> >
> > 2) Who is working on the website? There are some top level issues (
> > https://github.com/apache/incubator-mxnet-site/issues ) that need
> > addressing. I'm happy to dive in and work on them, but wanted to check
> > beforehand. It's useful dayjob wise for me to learn Sphinx :)
> >
> > 3) Seb - you mentioned you were working on contributing a redesign, could
> > you elaborate on where things are (post the Sep 12 initial email)?
> >
> > Hen
> >
>

Re: New Apache MXNet logo idea

[Henri Yandell]

Love :)

Lots of good connections here. Nice feather style/colour in the bunny's
silhouette, nice "magic" overlay for connection to Clarke's third law (any
sufficiently deep learning is indistinguishable from magic), great name
connection to 'mx' and the Chinese zodiac may, if appropriate, speak well
to MXNet's popularity in China (looking to those from/more versed in
China's culture for help there).

I do note that the zodiac rabbit's lucky colours are Apache's colours in
the feather.

Anyway - love it :)

Hen

On Thu, Sep 28, 2017 at 12:52 Seb Kiureghian  wrote:

>
> https://user-images.githubusercontent.com/591887/30987393-ba66e610-a44b-11e7-8226-da1711dcbdc5.jpg
>
>
>
> On Thu, Sep 28, 2017 at 12:38 PM, Madan Jampani 
> wrote:
>
> > Is there a picture of Max?
> >
> > On Thu, Sep 28, 2017 at 12:17 PM, Seb Kiureghian 
> > wrote:
> >
> >> Hi all,
> >>
> >> I have a new idea for a logo that I'd like to propose.
> >>
> >> The rabbit (I call him Max) is blazingly fast, like MXNet, but also
> >> friendly and approachable, like the Gluon interface.
> >>
> >> Do you all like it?
> >>
> >> Seb
> >>
> >
> >
>

Web site questions

[Henri Yandell]

Looking at the website ( https://github.com/apache/incubator-mxnet-site ),
I've some questions:

1) Do we really need jenkins constantly committing date updates for
doxygen? Is there a way to stop that 'generated by' text including the date?

2) Who is working on the website? There are some top level issues (
https://github.com/apache/incubator-mxnet-site/issues ) that need
addressing. I'm happy to dive in and work on them, but wanted to check
beforehand. It's useful dayjob wise for me to learn Sphinx :)

3) Seb - you mentioned you were working on contributing a redesign, could
you elaborate on where things are (post the Sep 12 initial email)?

Hen

Re: What's everyone working on?

[Henri Yandell]

Getting an instance of github.com/amzn/oss-dashboard setup for mxnet.

Hopefully useful to write custom metric analysis; like: "most pull requests
from non-committer" and "PRs without committer comment".

Hen

On Mon, Sep 25, 2017 at 11:24 Seb Kiureghian  wrote:

> Hey dev@,
>
> In the spirit of bringing more activity to the mailing lists and growing
> the community, can everyone who is working on MXNet please share what
> you're working on?
>
> I'm working on
> -Redesigning the website
> .
> -Setting up a forum for user support.
>
> Seb Kiureghian
>

Re: Integrating a forum with the mailing lists for better usability

[Henri Yandell]

I'd like to see the user@ list setup first; currently we don't have this
medium that you say we're losing engagement on.

Typically the Apache approach to forums has been to use Nabble ( for
example http://camel.465427.n5.nabble.com/Camel-Users-f465428.html ); which
iirc is a forum interface to the user list.

I think you can also sign in (via Google, or Apache if a committer) to
lists.apache.org for the same 'wrap the list' experience.

It looks like this came up historically:
https://github.com/apache/incubator-mxnet/issues/976 +
https://github.com/apache/incubator-mxnet/issues/1020

I also wonder how forums and stackoverflow compare. They seem to hit the
same topic, so is https://stackoverflow.com/questions/tagged/mxnet in
essence the forum?

I'll ask on general@incubator as to whether there has been discussion in
recent years on projects running forums, and whether the direction was to
self-host at Apache or use a third party (which means someday you will be
dealing with having to migrate off of that third party).

Hen


On Thu, Sep 14, 2017 at 11:17 PM, Seb Kiureghian  wrote:

> Hi dev@,
>
> I am glad to see more open discussion on the dev@ and user@ mailing
> lists. However, I also want to make sure that our website visitors can
> view, ask, or respond to questions from the community, in a user-friendly
> manner. I suspect that by relying only on mailing lists, we are losing
> engagement from users who don't like email and prefer other mediums, such
> as a Discourse forum . Other open source
> projects that have seen a recent sharp rise in popularity provide forums
> that see a ton of engagement, and provide user-friendly search and
> personalization tools that benefit users.
>
> Henri, John and community - what are your thoughts on setting up a forum
> on the Apache MXNet site and integrating it with the mailing lists, so that
> every forum post triggers an email and vice versa? Everything gets
> documented as usual, but we boost engagement and reach of our content.
>
> Seb
>
>
>
>
>

Discussion Forums?

[Henri Yandell]

The MXNet community have been discussing the possibilities of a discussion
forum. I suspect I'm out of date on the topic. Has there been Incubator
discussion on forums in the past few years? Are there projects running
forums? Discourse seems to be the current fashion.

My dated assumption is that Apache tends to be -1 to forums, but then we
had Nabble eking an existence on top of our lists as a semi-forum, then
StackExchange creating de facto Q&A forums; so perhaps user forums are a
thing now; or perhaps folk have their user@ mailing lists integrated with
discourse/stackoverflow etc?

Thanks,

Hen

Re: Testing and continuous integration of MXNet on devices / Android etc.

[Henri Yandell]

I've a feeling that you don't need write access but a token or oauth app
that is setup to edit the build status?  I know that's what TravisCI asks
for.

Similar issue of needing an account to access (and infra say no bot
accounts), but I think this can be done with lesser permissions to that
account than write.

On Thu, Sep 14, 2017 at 03:03 Larroy, Pedro  wrote:

> Hi there
>
> As a part of my daily job in Amazon which involves working with MXNet.
> Together with my team we have setup a dockerized multi-platform build for
> arm architectures including Android.
>
> It has anonymous read access so anyone can check the build status on the
> multiple platforms:
>
> ( http://ci.mxnet.amazon-ml.com/ )
>
> I think it would be useful to have this build feedback on PRs and commits
> on the Apache MXNet repository, and we are happy to contribute with this
> effort to the community.
>
> What I would like to do is to be able to set the build status on PRs and
> commits on Github so contributors sending PRs can see if their changes
> break the builds on devices, for that I need write access to the MXNet
> repository with a dedicated account that will be used exclusively for this
> and not by humans to prevent any potential errors.
> https://github.com/MXNetEdgeBot/
>
> You can see the build files in the following PR:
> https://github.com/apache/incubator-mxnet/pull/7792  we will extend this
> further with extensive testing on the different platforms, performance
> regressions and more.
>
> Because of the potential load of emulating and testing on this many
> architectures and flavors and for moving fast, for the moment I think it
> would be better to iterate on our own infrastructure and then if there’s
> the wish integrate with the testing infra in Apache do it.
>
> Any feedback or comments on this?  Do you like the idea?
> Constructive feedback is welcome.
>
> Thank you very much.
>
> Pedro.
>
> Amazon Development Center Germany GmbH
> Berlin - Dresden - Aachen
> main office: Krausenstr. 38
> , 10117
> Berlin
> Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
> Ust-ID: DE289237879
> Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
>

Re: MXNet: Run PR builds on Apache Jenkins only after the commit is reviewed

[Henri Yandell]

Side note:

There is no "we". The below should say something like "I would like to
propose...", or "As part of my work at , I would like to
propose..." if it's coming from a team at your day job and you don't want
to hog all the glory :)

If it truly is "we", then the email should end with the "we" that the email
is from. For example a release announcement from me would say "We are proud
to release" and would end with "Hen, on behalf of the Apache MXNet project".

Hen

On Mon, Sep 11, 2017 at 17:50 Meghna Baijal 
wrote:

> Hi All,
> We would like to initiate a change in the way the PR builds are being
> triggered. At the moment, every time a Pull Request is created, a build
> gets triggered on Jenkins. Additional builds also get triggered due to
> changes to the same PR.
> Too many PR builds leads to resource starvation and very long queues and
> long build times. Hence we would like to add some checks where a human
> reviewer manually marks it to something like “ok to build” before a PR
> build is triggered.
>
> Do you think this approach would be helpful and we should move forward
> with it?
>
> Thanks,
> Meghna Baijal
>
>
>
>

Re: Release missing on primary site

[Henri Yandell]

Thanks Naveen.

So the url in the website is wrong; install.html shouldn't have that
-incubating in the 0.11.0 directory name.



On Wed, Sep 13, 2017 at 11:33 AM, Naveen Swamy  wrote:

> It's under the release directory here:
>
> https://dist.apache.org/repos/dist/release/incubator/mxnet/0.11.0/
> https://dist.apache.org/repos/dist/release/incubator/mxnet/
> 0.11.0/apache-mxnet-src-0.11.0-incubating.tar.gz
>
>
> On Wed, Sep 13, 2017 at 11:13 AM, Henri Yandell  wrote:
>
> > The 0.11.0 release is missing from here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/
> >
> > Currently only the RCs are there.
> >
> > We do have the download link:
> >
> > * http://mxnet.apache.org takes you to:
> > * http://mxnet.apache.org/get_started/install.html takes you to:
> > *
> > https://www.apache.org/dyn/closer.cgi/incubator/mxnet/0.
> > 11.0-incubating/apache-mxnet-src-0.11.0-incubating.tar.gz
> > takes you to 404
> >
> > But that link is broken. Once we get the release on dist.apache, it will
> > mirror out to the various places and also be archived.
> >
> > Hen
> >
>

Release missing on primary site

[Henri Yandell]

The 0.11.0 release is missing from here:

https://dist.apache.org/repos/dist/dev/incubator/mxnet/

Currently only the RCs are there.

We do have the download link:

* http://mxnet.apache.org takes you to:
* http://mxnet.apache.org/get_started/install.html takes you to:
*
https://www.apache.org/dyn/closer.cgi/incubator/mxnet/0.11.0-incubating/apache-mxnet-src-0.11.0-incubating.tar.gz
takes you to 404

But that link is broken. Once we get the release on dist.apache, it will
mirror out to the various places and also be archived.

Hen

Re: MXNet website redesign

[Henri Yandell]

Clarifying as I think Isabel was too gentle :)

Before coming to Apache, there had been much talk of redoing the website,
perhaps via a dayjob contribution. I double checked at ApacheCon with Sally
that that was sane (corporate contribution of a website design).

The evolution of that conversation is that Seb & Dom (as part of their
dayjob at Amazon) have a proposal for a new look and feel. They would like
feedback. There is no pPMC activity here Dom/Seb, this is you personally
proposing a website redesign to the MXNet PPMC, of which you are not a part.

Currently the MXNet committers/PPMC are very strongly code-focused. As an
Amazon employee, I love that we (Amazon) have non-coders interested in
working on the project. I dream of a day where project managers, web
designers, tech editors, paper writing scientists and evangelists are able
to be committers too. We (Apache) want that - Apache committers should be a
diverse bunch, not just coders.

This kind of pain point is going to happen. Apache have a general
too-code-focused culture, which we (Apache) acknowledge. Until we (MXNet)
are more open to adding non-coding committers (in deed as well as word),
trying to contribute outside of coding is like trying to move a Snorlax[1].

Hen

1 - https://bulbapedia.bulbagarden.net/wiki/Snorlax_(Pok%C3%A9mon)


On Wed, Sep 13, 2017 at 8:35 AM, Dominic Divakaruni <
dominic.divakar...@gmail.com> wrote:

> I think this: >The pPMC would like to update the website.
>
> is just to say that, the project's mentors reached out to the folks who
> helped with the infra migration with a reminder about the website updates
> that are needed.
>
> I don't believe that a decision was made out of sight. Though I do fully
> agree that this reminder and the follow on website design should have been
> discussed on dev@ first.
>
>
> On Tue, Sep 12, 2017 at 11:48 PM, Isabel Drost-Fromm 
> wrote:
>
> > Hi,
> >
> > First of all, great to read there are people with interest and time to
> > update the website.
> >
> >
> > Am 12. September 2017 19:00:21 MESZ schrieb Seb Kiureghian <
> > sebou...@gmail.com>:
> > >The pPMC would like to update the website.
> >
> > This wording is worrying to me. It sounds like a decision was made out of
> > sight of the public project community, that is out of sight of dev@
> >
> > The only way to grow your community and make it possible for outsiders is
> > to have  conversations leading up to decisions like these here on dev@.
> > Maybe I missed those, happy for any pointers.
> >
> >
> > Isabel
> >
> >
> >
> >
> > --
> > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> >
>
>
>
> --
>
>
> Dominic Divakaruni
> 206.475.9200 Cell
>

Re: Jira and/or feature collision

[Henri Yandell]

Yes, Apache JIRA is free to use.

My observations of GitHub are that roadmaps/wishlist features need better
separation from bug reports. Ideally you want a nice big list of ideas for
future work, and a list of bug reports and smaller contributions that
you're always driving down to zero. One way to do that could be to put the
new features in JIRA, while keeping GitHub for bug reports, not sure if
that's what you were getting to Chris with the question.

Hen


On Sun, Sep 10, 2017 at 9:23 PM, sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:

> +1
> Thanks Chris for bringing up this important topic.
>
> I would really like to prioritize this topic and request users and mentors
> to come up a process or suggestions on how to:
> 1. Request for contributions from the community.
> 2. A community member raising feature requests.
> 3. A community member ready to contribute a feature or bug fix.
> 4. A community member actively proposing and driving a big new feature for
> the project.
>
> Projects in Github, Tagging Github issues with Call for Contributions may
> seem very straight forward approach. But, is there any other suggestions or
> standard practice to drive such efforts?
>
> This will go a long way in keeping community members informed about what
> next in the project, how can they be part and how they can set future
> directions in the project. Also, saving the time and effort in duplication
> of efforts.
>
> Regards,
> Sandeep
>
> On Sat, Sep 9, 2017 at 4:48 AM, Chris Olivier 
> wrote:
>
> > Is Apache JIRA free to use? What do most projects use? While it's natural
> > that some companies have internal priorities which drive their
> development
> > plans, how do other Apache projects avoid having the same feature
> developed
> > independently by more than one party, because they isn't know the other
> was
> > working on it already?  Or coordinate forces (so to speak) on a large
> > feature or initiative?
> >
> > -Chris
> >
>
>
>
> --
> Sandeep Krishnamurthy
>

Slack requests

[Henri Yandell]

I'm not sure who handles the Slack requests we get (or if they get
handled). When someone adds someone to Slack, could they reply to them,
cc'ing dev@, and that way we'll know that users are being connected. Right
now I couldn't say if we're leaving lots of people outside of the
conversation.

Note that they may not be subscribed, so you will need to both email them
and dev@, rather than just dev@.

Thanks,

Hen

Re: [ANNOUNCE] Apache MXNet (incubating) 0.11.0 Release

[Henri Yandell]

A link to either the wiki page or the change diff would help here (so your
fellow community members can dive deeper).

On Thu, Sep 7, 2017 at 17:15 Meghna Baijal 
wrote:

> Thank you for your suggestion! I have updated our release process wiki to
> reflect your point and we will make sure to incorporate next time.
>
> - Meghna
>
> > On Sep 7, 2017, at 4:16 AM, sebb  wrote:
> >
> > What is the project about? Why should I be interested in it?
> > [rhetorical questions]
> >
> > The Announce emails are sent to people not on the developer or user
> lists.
> > Most will have no idea what the project is about.
> >
> > So the e-mails should contain at least brief details of what the
> > product does, and some info on why the new release might be of
> > interest to them.
> >
> > Readers should not have to click the link to find out the basic
> information
> > (although of course it is useful to have such links for further detail).
> >
> > Please can you add that information to future announce mails?
> >
> > Thanks.
> >
> >
> > On 7 September 2017 at 03:06, Naveen Swamy  wrote:
> >> The Apache MXNet community is happy to announce Apache MXNet version
> 0.11.0!
> >> We hit some major milestones with this release!
> >> This is our first official release as an incubating Apache project. The
> >> project has now fully migrated its code base and website to Apache.
> >> This release includes code contributions from developers from Apple,
> >> Samsung, Microsoft and many other.
> >> We have also crossed over 400 contributors on the project so far. The
> 0.11.0
> >> release features Apple Core ML model converter, Support for Keras
> v1.2.2.
> >>
> >> A blog that explains an end to end use case of building an ios app using
> >> MXNet and Core ML:
> >>
> https://aws.amazon.com/blogs/ai/bring-machine-learning-to-ios-apps-using-apache-mxnet-and-apple-core-ml/
> <
> https://aws.amazon.com/blogs/ai/bring-machine-learning-to-ios-apps-using-apache-mxnet-and-apple-core-ml/
> >
> >>
> >> The AWS blog that highlights the key features of the release:
> >>
> https://aws.amazon.com/blogs/ai/apple-core-ml-and-keras-support-now-available-for-apache-mxnet/
> <
> https://aws.amazon.com/blogs/ai/apple-core-ml-and-keras-support-now-available-for-apache-mxnet/
> >
> >>
> >> A full list of the changes in this release can be found in the release
> >> notes:
> >>
> https://cwiki.apache.org/confluence/display/MXNET/MXNet+0.11.0+Release+Notes
> >> <
> https://cwiki.apache.org/confluence/display/MXNET/MXNet+0.11.0+Release+Notes
> >
> >>
> >> Link to Download: http://www.apache.org/dist/incubator/mxnet/
> >> 
> >>
> >> To build this project, view this page and select “Build from Source”:
> >> http://mxnet.incubator.apache.org/get_started/install.html
> >> 
> >>
> >> The Docker Images can be found here:
> >> https://hub.docker.com/u/mxnet/ 
> >>
> >> The Pip package can be found here:
> >> https://pypi.python.org/pypi/mxnet 
> >>
> >> The Release Tag is here:
> >> https://github.com/apache/incubator-mxnet/tree/0.11.0
> >> 
> >>
> >> MXNet Resources
> >>   - Issues: https://github.com/apache/incubator-mxnet/issues
> >> 
> >>   - Wiki: https://cwiki.apache.org/confluence/display/MXNET
> >> 
> >>   - Mailing list(s): dev@mxnet.incubator.apache.org
> >> 
> >>
> >> For more information on Apache MXNet, please see:
> >> https://mxnet.incubator.apache.org/ <
> https://mxnet.incubator.apache.org/>
> >>
> >> Thanks!
> >> Apache MXNet(incubating) Team
> >> ___
> >>
> >> DISCLAIMER:
> >> 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.
>
>

Re: ICLAs vs Contributors

[Henri Yandell]

Hi Przemyslaw,

We need each of you to sign an ICLA (
https://www.apache.org/licenses/icla.pdf ). That will cover your
contributions, including future contributions.

If you'd like to only sign something for only past contributions (ie: not
looking to make future contributions), then having you sign an SGA would be
an alternative to an ICLA (
https://www.apache.org/licenses/software-grant.txt ).

Whether or not you should sign a CCLA is up to NVIDIA. Apache does not
require that corporations sign the CCLA, but some corporations choose to
sign a CCLA (for example if they feel that their employees are unable to
sign an ICLA without the corporation also signing something).

You can keep contributing (sending pull requests) before signing. Signing
this helps to strengthen MXNet's provenance (aka proof that the code is
legally authentic). There's already proof that the code is legally
authentic (some examples: you opening pull requests, the Apache license
requiring you to identify if the contribution is not under Apache license,
GitHub terms of service), this strengthens it :)

Many thanks for doing this,

Hen



On Wed, Sep 6, 2017 at 10:25 AM, Chris Olivier 
wrote:

> I think individual (personal email addresses), which is how everyone else
> is doing it, as far as I know
>
> On Wed, Sep 6, 2017 at 3:20 AM, ptre...@gmail.com 
> wrote:
>
> > Hi,
> >
> > Me (ptrendx on GitHub), Dick (DickJC123) and Marek (mkolod) are NVIDIA
> > employees working on MXNet. Should we sign individual CLAs or should
> NVIDIA
> > sign corporate CLA with ASF? If so, could you point us to the document
> that
> > needs to be signed? Can we contribute in the meantime?
> >
> > Thank you
> > Przemyslaw Tredak
> >
> > On 2017-09-01 12:28, Henri Yandell  wrote:
> > > I've listed the top 100 contributors (as of the other day) on GitHub
> > here:
> > >
> > > https://cwiki.apache.org/confluence/display/MXNET/ICLA+Progress
> > >
> > > With a check if they have signed an ICLA.
> > >
> > > John/Justin - can you confirm that we don't have to get an ICLA signed
> > from
> > > someone whose significant contributions have only been since MXNet came
> > to
> > > Apache? (Assuming it's not such a large piece of work that would flag
> for
> > > software-grant/ICLA - a new component etc).
> > >
> > > --
> > >
> > > I'd like us (MXNet) to work our way down the list getting (up to
> > > yanqingmen) ICLAs signed. After that we will review the nature of the
> > next
> > > batch of contributors commits and determine how much more ICLA signing
> we
> > > need.
> > >
> > > Thanks,
> > >
> > > Hen
> > >
> > >
> > > On Tue, Aug 29, 2017 at 10:06 PM, Henri Yandell 
> > wrote:
> > >
> > > > (cc to John and Justin as they'd asked about this)
> > > >
> > > > Looking at the current MXNet GitHub contributors list (411
> > contributors):
> > > >
> > > > We have 36 signed CLAs at this point.
> > > >
> > > > Of the top 36 contributors, the following 15 top contributors aren't
> > > > covered by a CLA:
> > > >
> > > > 8:sneakerkg
> > > > 9:kevinthesun  (post Incubation)
> > > > 17:hjk41
> > > > 18:mavenlin
> > > > 19:tornadomeet
> > > > 20:winstywang
> > > > 21:jermainewang
> > > > 22:qiaohaijun
> > > > 23:vchuravy
> > > > 25:Roshrini  (post Incubation)
> > > > 26:howard0su
> > > > 28:sbodenstein
> > > > 31:ptrendx  (post Incubation)
> > > > 35:zackchase   (post Incubation)
> > > > 36:yanqingmen
> > > >
> > > > Note that some of these are post entering the Incubator.
> > > >
> > > > Some of the 411 contributors we should ask for CLA/SGs from. Those
> > above
> > > > are most likely the first to get agreements signed from, and we need
> to
> > > > determine how far down the list to go.
> > > >
> > > > The git logs are trickier to use as they don't use the github login;
> so
> > > > doing an analysis of the diffs themselves is trickier.
> > > >
> > > > Hen
> > > >
> > >
> >
>

Re: open issues

[Henri Yandell]

I'd suggest writing up a triage process on the wiki.

Using labels makes a lot of sense. One label that I've found useful with
Issues in the past is "Patch Needed" (ie: contributors, please work on
these). Another would be "easyfix"; ie) new contributors, this is a good
place to start.

One of the 'problems' imo with GitHub's approach is that there's no real
place for 'backlog' or 'wishlist'. Requests for new things that you're
unlikely to work on soon get in the way of bugs. :(

Hen


On Thu, Aug 31, 2017 at 6:33 AM, Dom Divakaruni <
dominic.divakar...@gmail.com> wrote:

> Agree! The first step need to be to comb thru these and assign a tag. A
> hurdle with this is that, non committers, like myself don't have the
> ability to assign tags.
>
> Does anyone have a solution to get around that? Temporary roles, or task
> based credentials perhaps?
>
> As we solve that, we can propose a definition for tags - "outdated",
> "bug-needs investigation" and "FAQ" make sense as tags - and specific
> instructions for the cleanup crew.
>
> We can add a comment to each one of the "outdated" ones to say "is this
> still an issue? If there is no response, the issue will be closed after 2
> weeks"... or something like that
>
> After the tags comes the hard work :)
> That said, over 900 of these issues are older than Jan 1, and may by and
> large, be outdated.
>
>
> Regards,
> Dom
>
>
> > On Aug 31, 2017, at 2:10 AM, Chiyuan Zhang  wrote:
> >
> > I could also help with this from time to time. I think maybe at least
> half
> > of the issues are outdated, in the sense that the original reporter was
> no
> > longer working on it or able to provide enough details to reproduce it.
> > While some still correspond to important feature request or potential
> > serious bugs, many of them could probably be safely closed. I am not
> > advocating we should always close issues that are too old, clearly the
> best
> > way is really to resolve it if we have enough man power.
> >
> > I would suggest creating some tags for this, things could be 'out-dated',
> > 'FAQ', etc. And periodically sweep through the issues, if you see an
> issues
> > that should be closed due to inactivity, you label it as 'out-dated' and
> > leave a message saying that it will be closed after XXX days if remains
> > inactive. Or if it corresponds to some frequently asked questions, mark
> it
> > as 'FAQ'. And another sweep that also happens periodically could try to
> > close the issues marked for 'out-dated' for a while and assemble entries
> > into documentation for the 'FAQ' issues.
> >
> > - chiyuan
> >
> > On Thu, Aug 31, 2017 at 4:32 AM, Dominic Divakaruni <
> > dominic.divakar...@gmail.com> wrote:
> >
> >> fellow mxnet'ers, we have >1900 open issues on git. The most out of any
> >> deep learning framework. I am eager to carve out some time to work on
> >> reducing this backlog (to the extent of my technical ability). I'd like
> to
> >> make this a team effort to make a meaningful impact. Any ideas? Would
> you
> >> be open to an issue-clean-up-athon?
> >>
>

Re: Dependency directories?

[Henri Yandell]

I'm not sure for C/C++.

For the languages that have artifact repositories (Java, Python, Perl etc),
the norm is to use those systems.

It does feel weird to have an Apache source project with a large lump of
its code appearing to be the same product but not part of the project.

The approaches that naively jump out to me are:

1) As it currently is, linking MXNet to the other git repositories.
2) User installs them themselves and MXNet uses configure/make to build.
3) Copy the source over into the MXNet project.
4) Create new repositories at Apache for each of them (and then possibly
still just link them in).

Jim (or anyone else) - any advice you could offer on how C/C++ dependencies
are handled at Apache projects?


Hen

On Tue, Aug 29, 2017 at 10:55 PM, Chris Olivier 
wrote:

> I've been curious about the same thing. How do other Apache projects handle
> this sort of thing?
>
> What's are the pros and cons?
>
>
> On Tue, Aug 29, 2017 at 9:57 PM Henri Yandell  wrote:
>
> > What's the plan for the source that isn't included in the mxnet repo?
> >
> >  cub/
> >  dlpack/
> >  dmlc-core/
> >  mshadow/
> >  nnvm/
> >  ps-lite/
> >
> > Is the plan to keep those as separate DMLC packages, or to consider them
> > MXNet specific?
> >
> > Thanks,
> >
> > Hen
> >
>

Re: ICLAs vs Contributors

[Henri Yandell]

I've listed the top 100 contributors (as of the other day) on GitHub here:

https://cwiki.apache.org/confluence/display/MXNET/ICLA+Progress

With a check if they have signed an ICLA.

John/Justin - can you confirm that we don't have to get an ICLA signed from
someone whose significant contributions have only been since MXNet came to
Apache? (Assuming it's not such a large piece of work that would flag for
software-grant/ICLA - a new component etc).

--

I'd like us (MXNet) to work our way down the list getting (up to
yanqingmen) ICLAs signed. After that we will review the nature of the next
batch of contributors commits and determine how much more ICLA signing we
need.

Thanks,

Hen


On Tue, Aug 29, 2017 at 10:06 PM, Henri Yandell  wrote:

> (cc to John and Justin as they'd asked about this)
>
> Looking at the current MXNet GitHub contributors list (411 contributors):
>
> We have 36 signed CLAs at this point.
>
> Of the top 36 contributors, the following 15 top contributors aren't
> covered by a CLA:
>
> 8:sneakerkg
> 9:kevinthesun  (post Incubation)
> 17:hjk41
> 18:mavenlin
> 19:tornadomeet
> 20:winstywang
> 21:jermainewang
> 22:qiaohaijun
> 23:vchuravy
> 25:Roshrini  (post Incubation)
> 26:howard0su
> 28:sbodenstein
> 31:ptrendx  (post Incubation)
> 35:zackchase   (post Incubation)
> 36:yanqingmen
>
> Note that some of these are post entering the Incubator.
>
> Some of the 411 contributors we should ask for CLA/SGs from. Those above
> are most likely the first to get agreements signed from, and we need to
> determine how far down the list to go.
>
> The git logs are trickier to use as they don't use the github login; so
> doing an analysis of the diffs themselves is trickier.
>
> Hen
>

Re: ICLAs vs Contributors

[Henri Yandell]

*facepalm*

Link: https://www.apache.org/licenses/icla.pdf

On Fri, Sep 1, 2017 at 12:04 PM, Henri Yandell  wrote:

> Hi tornadomeet :)
>
> If you could sign this (ink, not typed) and email it to
> secret...@apache.org that would be brilliant.
>
> Thanks,
>
> Hen
>
>
> On Thu, Aug 31, 2017 at 9:19 AM, tornadomeet <1530735...@qq.com> wrote:
>
>> hello, i'm tornadomeet, how to sign CLAs?
>>
>>
>> thanks
>>
>>
>> -- 原始邮件 --
>> 发件人: "Henri Yandell";;
>> 发送时间: 2017年8月30日(星期三) 中午1:06
>> 收件人: "dev"; "John D. Ament"<
>> johndam...@apache.org>; "Justin Mclean";
>>
>> 主题: ICLAs vs Contributors
>>
>>
>>
>> (cc to John and Justin as they'd asked about this)
>>
>> Looking at the current MXNet GitHub contributors list (411 contributors):
>>
>> We have 36 signed CLAs at this point.
>>
>> Of the top 36 contributors, the following 15 top contributors aren't
>> covered by a CLA:
>>
>> 8:sneakerkg
>> 9:kevinthesun  (post Incubation)
>> 17:hjk41
>> 18:mavenlin
>> 19:tornadomeet
>> 20:winstywang
>> 21:jermainewang
>> 22:qiaohaijun
>> 23:vchuravy
>> 25:Roshrini  (post Incubation)
>> 26:howard0su
>> 28:sbodenstein
>> 31:ptrendx  (post Incubation)
>> 35:zackchase   (post Incubation)
>> 36:yanqingmen
>>
>> Note that some of these are post entering the Incubator.
>>
>> Some of the 411 contributors we should ask for CLA/SGs from. Those above
>> are most likely the first to get agreements signed from, and we need to
>> determine how far down the list to go.
>>
>> The git logs are trickier to use as they don't use the github login; so
>> doing an analysis of the diffs themselves is trickier.
>>
>> Hen
>>
>
>

Re: ICLAs vs Contributors

[Henri Yandell]

Hi tornadomeet :)

If you could sign this (ink, not typed) and email it to secret...@apache.org
that would be brilliant.

Thanks,

Hen


On Thu, Aug 31, 2017 at 9:19 AM, tornadomeet <1530735...@qq.com> wrote:

> hello, i'm tornadomeet, how to sign CLAs?
>
>
> thanks
>
>
> -- 原始邮件 ------
> 发件人: "Henri Yandell";;
> 发送时间: 2017年8月30日(星期三) 中午1:06
> 收件人: "dev"; "John D. Ament"<
> johndam...@apache.org>; "Justin Mclean";
>
> 主题: ICLAs vs Contributors
>
>
>
> (cc to John and Justin as they'd asked about this)
>
> Looking at the current MXNet GitHub contributors list (411 contributors):
>
> We have 36 signed CLAs at this point.
>
> Of the top 36 contributors, the following 15 top contributors aren't
> covered by a CLA:
>
> 8:sneakerkg
> 9:kevinthesun  (post Incubation)
> 17:hjk41
> 18:mavenlin
> 19:tornadomeet
> 20:winstywang
> 21:jermainewang
> 22:qiaohaijun
> 23:vchuravy
> 25:Roshrini  (post Incubation)
> 26:howard0su
> 28:sbodenstein
> 31:ptrendx  (post Incubation)
> 35:zackchase   (post Incubation)
> 36:yanqingmen
>
> Note that some of these are post entering the Incubator.
>
> Some of the 411 contributors we should ask for CLA/SGs from. Those above
> are most likely the first to get agreements signed from, and we need to
> determine how far down the list to go.
>
> The git logs are trickier to use as they don't use the github login; so
> doing an analysis of the diffs themselves is trickier.
>
> Hen
>

Re: ICLAs vs Contributors

[Henri Yandell]

Thanks Minjie, I'll add you to my list.

The minpy source isn't currently at Apache, so I wasn't including that in
the review.

If anyone knows of significant code in MXNet that has authors who are not
represented in the GitHub log, please raise that on the list.

Hen

On Wed, Aug 30, 2017 at 5:56 AM, Minjie Wang  wrote:

> Hi Henri,
>
> It will be great to ask them again. For example, I recently just found that
> my ICLA is bounced back since my signature is typed rather than
> hand-written. However, I found that I am still on the list
> (21:jermainewang).
> I guess many of them do not know about this situation, so it will be great
> to ping them again.
>
> Also, by looking at the github history may not be that accurate. For
> example, sneakerkg has been working on the project since beginning and then
> put most of his efforts in minpy project (the core function of which has
> been merged to mxnet). Unfortunately, MXNet's github history cannot reflect
> that.
>
> Best,
> Minjie
>
> On Wed, Aug 30, 2017 at 2:55 AM, shiwen hu  wrote:
>
> > open some issue and @them
> >
> > 2017-08-30 14:54 GMT+08:00 shiwen hu :
> >
> > > yes.nobody tell them.
> > >
> > > 2017-08-30 14:43 GMT+08:00 Henri Yandell :
> > >
> > >> They're not committers, so I doubt anyone has requested they sign a
> > ICLA.
> > >> Looking at the GitHub history, some haven't been active in a while.
> > >>
> > >> Hen
> > >>
> > >> On Tue, Aug 29, 2017 at 11:07 PM, shiwen hu 
> > >> wrote:
> > >>
> > >> > Maybe they don't know how to start the ICLA process.Consider
> creating
> > a
> > >> > boot page.
> > >> >
> > >> > 2017-08-30 13:06 GMT+08:00 Henri Yandell :
> > >> >
> > >> > > (cc to John and Justin as they'd asked about this)
> > >> > >
> > >> > > Looking at the current MXNet GitHub contributors list (411
> > >> contributors):
> > >> > >
> > >> > > We have 36 signed CLAs at this point.
> > >> > >
> > >> > > Of the top 36 contributors, the following 15 top contributors
> aren't
> > >> > > covered by a CLA:
> > >> > >
> > >> > > 8:sneakerkg
> > >> > > 9:kevinthesun  (post Incubation)
> > >> > > 17:hjk41
> > >> > > 18:mavenlin
> > >> > > 19:tornadomeet
> > >> > > 20:winstywang
> > >> > > 21:jermainewang
> > >> > > 22:qiaohaijun
> > >> > > 23:vchuravy
> > >> > > 25:Roshrini  (post Incubation)
> > >> > > 26:howard0su
> > >> > > 28:sbodenstein
> > >> > > 31:ptrendx  (post Incubation)
> > >> > > 35:zackchase   (post Incubation)
> > >> > > 36:yanqingmen
> > >> > >
> > >> > > Note that some of these are post entering the Incubator.
> > >> > >
> > >> > > Some of the 411 contributors we should ask for CLA/SGs from. Those
> > >> above
> > >> > > are most likely the first to get agreements signed from, and we
> need
> > >> to
> > >> > > determine how far down the list to go.
> > >> > >
> > >> > > The git logs are trickier to use as they don't use the github
> login;
> > >> so
> > >> > > doing an analysis of the diffs themselves is trickier.
> > >> > >
> > >> > > Hen
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
>
>
> --
> Minjie Wang
> *New York University | Computer Science*
> 715 Broadway, New York, NY, 10009
>

Re: release launch

[Henri Yandell]

Sounds good to me. Start of week releasing gets more user awareness than
end of week.

On Wed, Aug 30, 2017 at 17:51 Dominic Divakaruni <
dominic.divakar...@gmail.com> wrote:

> We have an opportunity to use AWS and Apple (for the Core ML converter
> part) to market this release via blogs and social media on Tuesday 9/6.
> This will be a good way to promote the work of the Apache MXNet community.
>
> The Apache release policy states "Please ensure that you wait at least 24
> hours after uploading a new release before updating the project download
> page and sending the announcement email(s)."
>
> How do you all feel about waiting until Monday to upload the new release so
> we can have a big splash on Tuesday 9/6?
>
> Announcements could go out of:
> announce@apache
> dev@
> AWS blogs and social media
> Apple developer news feed
>
> To use the release in the mean time we can just use RC3 as there are no
> changes.
>

Re: ICLAs vs Contributors

[Henri Yandell]

They're not committers, so I doubt anyone has requested they sign a ICLA.
Looking at the GitHub history, some haven't been active in a while.

Hen

On Tue, Aug 29, 2017 at 11:07 PM, shiwen hu  wrote:

> Maybe they don't know how to start the ICLA process.Consider creating a
> boot page.
>
> 2017-08-30 13:06 GMT+08:00 Henri Yandell :
>
> > (cc to John and Justin as they'd asked about this)
> >
> > Looking at the current MXNet GitHub contributors list (411 contributors):
> >
> > We have 36 signed CLAs at this point.
> >
> > Of the top 36 contributors, the following 15 top contributors aren't
> > covered by a CLA:
> >
> > 8:sneakerkg
> > 9:kevinthesun  (post Incubation)
> > 17:hjk41
> > 18:mavenlin
> > 19:tornadomeet
> > 20:winstywang
> > 21:jermainewang
> > 22:qiaohaijun
> > 23:vchuravy
> > 25:Roshrini  (post Incubation)
> > 26:howard0su
> > 28:sbodenstein
> > 31:ptrendx  (post Incubation)
> > 35:zackchase   (post Incubation)
> > 36:yanqingmen
> >
> > Note that some of these are post entering the Incubator.
> >
> > Some of the 411 contributors we should ask for CLA/SGs from. Those above
> > are most likely the first to get agreements signed from, and we need to
> > determine how far down the list to go.
> >
> > The git logs are trickier to use as they don't use the github login; so
> > doing an analysis of the diffs themselves is trickier.
> >
> > Hen
> >
>

Re: MXNet site questions

[Henri Yandell]

Thanks Yao :)

Note on source that the links should be to mirrors rather than directly to
Apache.  PGP/SHA/MD5 links to dist.apache.org make sense.

I'll open some issues in the site GitHub project.

Hen

On Tue, Aug 29, 2017 at 12:39 PM, Yao Wang  wrote:

> I just talked with apache guy to enable github issue. For apache
> information on the website, currently we have apache incubator disclaimer
> on as home page footer. Also we’ll have source package, PGP, SHA and MD5
> links to apache pages. Would you like to add anything here?
>
> 
>
> > We need to ask Apache infrastructure team about GitHub issue and website
> > permission.
> > Currently most images on website are stored under dmlc/web-data repo and
> a
> > few on data.mxnet.io. Also need to ask apache if we want to move them to
> > somewhere apache controls. Maybe another repo similar to web-data to
> store
> > all website related static resources.
> >
> > 2017-08-25 19:26 GMT-07:00 Henri Yandell  > >:
> >
> >> * Could Issues be turned on for the site so we can report site issues?
> >> * How does one go about getting permission to the site?
> >> * Apache footer needed (Copyright/trademarks statement)
> >> * Need to add some links to Apache pages (Foundation page, Sponsors,
> >> ApacheCon jump to mind)
> >> * The logo is being pulled from mxnet.io
> >>
> >
> >
>

ICLAs vs Contributors

[Henri Yandell]

(cc to John and Justin as they'd asked about this)

Looking at the current MXNet GitHub contributors list (411 contributors):

We have 36 signed CLAs at this point.

Of the top 36 contributors, the following 15 top contributors aren't
covered by a CLA:

8:sneakerkg
9:kevinthesun  (post Incubation)
17:hjk41
18:mavenlin
19:tornadomeet
20:winstywang
21:jermainewang
22:qiaohaijun
23:vchuravy
25:Roshrini  (post Incubation)
26:howard0su
28:sbodenstein
31:ptrendx  (post Incubation)
35:zackchase   (post Incubation)
36:yanqingmen

Note that some of these are post entering the Incubator.

Some of the 411 contributors we should ask for CLA/SGs from. Those above
are most likely the first to get agreements signed from, and we need to
determine how far down the list to go.

The git logs are trickier to use as they don't use the github login; so
doing an analysis of the diffs themselves is trickier.

Hen

Dependency directories?

[Henri Yandell]

What's the plan for the source that isn't included in the mxnet repo?

 cub/
 dlpack/
 dmlc-core/
 mshadow/
 nnvm/
 ps-lite/

Is the plan to keep those as separate DMLC packages, or to consider them
MXNet specific?

Thanks,

Hen

Source Headers [Was: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3]

[Henri Yandell]

On Tue, Aug 29, 2017 at 6:38 PM, John D. Ament 
wrote:

> On Tue, Aug 29, 2017 at 9:30 PM John D. Ament 
> wrote:
>
> > On Tue, Aug 29, 2017 at 9:27 PM Henri Yandell  wrote:
> >
> >> Reverted to "Copyright Contributors"?
> >>
> >>
> > Yes, for any file that we don't have full agreement (ICLA on file) we
> > can't remove the copyright claim that already exists.  Us receiving an
> ICLA
> > is what allows us to say "Licensed to the ASF" (it's in the ICLA).
> >
> > It's not a big deal, since its Apache licensed, we just have to be
> careful
> > we're removing someone's pre-existing claim.
> >
>
> I'll give a more concrete example.
>
> Let's say I imported this file into an ASF repo
> https://github.com/spring-projects/spring-framework/
> blob/v5.0.0.RC3/spring-core/src/main/java/org/springframework/util/
> StringUtils.java
>
> I wouldn't change the header to say licensed to the ASF.  None of the
> contributors have signed ICLAs.  The file header would remain in tact.  I
> would also have to carry their notice file around
> https://github.com/spring-projects/spring-framework/
> blob/v5.0.0.RC3/src/docs/dist/notice.txt
> (at
> least I'm assuming this is their NOTICE file, I can't find any others
> around)
>
>
For a concrete example with copyright Pivotal; sure - nice and easy.

In this case we have 'Copyright Contributors'. It's an empty phrase that
would just cause confusion. Because Contributor isn't defined, it looks
like a repeat of our source header:

"Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with this
work for additional information regarding copyright ownership. ... "

Perhaps the solution is to, in the NOTICE, state:

Copyright 2015-2016 by Contributors
Copyright 2017 The Apache Software Foundation

Where we could change 'by Contributors' to be more descriptive, but I seem
to recall lots of pushback at changing 3rd party source headers to make
them more understandable.

---

Note also that clause 5 of Apache 2.0 means that many of those 'contributor
license agreements' are Apache 2.0 Licenses and not SGA/ICLA/CCLA. Its
language should also cover something else published under Apache 2.0; ie)
no need for a different Apache source header.

Hen

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

Reverted to "Copyright Contributors"?

On Tue, Aug 29, 2017 at 18:15 John D. Ament  wrote:

> Ok, so here's my +1 to release, with the following notes:
>
> - The NOTICE file is wrong.  Unless the dependencies listed have explicit
> notice requirements (they don't seem to) nothing needs to be added to the
> NOTICE file.
> - The source headers should be reverted in any areas where not all
> contributors to that file have signed ICLAs, otherwise we need some kind of
> agreement they are OK with moving to NOTICE file (which is how this has
> been handled in the past).
>
> Please create JIRAs to track these.
>
> John
>
> On Tue, Aug 29, 2017 at 9:09 PM Henri Yandell  wrote:
>
> > I believe all the major contributors were ICLA'd, and I disagree that all
> > contributors need to SGA/ICLA; we don't do that for an existing project.
> >
> > We need to do the check to see how the footprint of contributions for the
> > largest contributor without an ICLA is (apologies for the horrible
> wording
> > there). There are over 400 contributors, but (quickly eyeballing) most
> are
> > covered by ICLA or small contributions. Note that we also have clause 5
> of
> > Apache 2.0 at play for historical contributions here.
> >
> > To John's point on source headers; the previous source headers said
> > "Copyright  by Contributors".
> >
> > Hen
> >
> > On Tue, Aug 29, 2017 at 11:01 Craig Russell 
> wrote:
> >
> > > Hi Henri,
> > >
> > > If a project was developed outside Apache then everyone who contributed
> > to
> > > the project has to have an ICLA on file or file a Software Grant as
> part
> > of
> > > IP Clearance.
> > >
> > > It's not sufficient that the code has always been under the ASL 2.0.
> > >
> > > Are there any contributors to the project before it came to the
> incubator
> > > who are not now committers?
> > >
> > > Regards,
> > >
> > > Craig
> > >
> > > > On Aug 29, 2017, at 9:43 AM, Henri Yandell 
> wrote:
> > > >
> > > > Apologies - I missed that mentors hadn't voted on the podling
> release.
> > > Will
> > > > review tonight; hopefully their mentors can do similar.
> > > >
> > > > There's no reason for an SGA here (and who would even sign it?). Code
> > has
> > > > been apache 2.0 since the initial commit on GitHub.
> > > >
> > > > On Tue, Aug 29, 2017 at 06:45 John D. Ament 
> > > wrote:
> > > >
> > > >> Dominic,
> > > >>
> > > >> One question, from looking a second time.  Was MXNet always Apache
> > > Licensed
> > > >> (prior to coming to the ASF)?
> > > >>
> > > >> John
> > > >>
> > > >> On Tue, Aug 29, 2017 at 8:39 AM Dominic Divakaruni <
> > > >> dominic.divakar...@gmail.com> wrote:
> > > >>
> > > >>> Thanks for the reply, John. None of the mentors have voted so far.
> > > >>> Henri, Suneel, Marcus, Sebastian, can you gents please review and
> > vote?
> > > >>>
> > > >>> Also, Henri, didn't you mention that there was an SGA for this
> > project?
> > > >>> Sorry if I don't recollect the exact details on the SGA bit.
> > > >>>
> > > >>> Dom
> > > >>>
> > > >>>
> > > >>> On Tue, Aug 29, 2017 at 5:27 AM, John D. Ament <
> > johndam...@apache.org>
> > > >>> wrote:
> > > >>>
> > > >>>> Non pmc members can vote non-binding.  Usually mentors review
> > > releases.
> > > >>>> Have any of your mentors reviewed and voted on it?  Due to there
> > being
> > > >> no
> > > >>>> SGA its a harder release to review.  I also need to cross check
> > ICLAs
> > > >> and
> > > >>>> files that have changed license.
> > > >>>>
> > > >>>> On Aug 29, 2017 8:13 AM, "Dominic Divakaruni" <
> > > >>>> dominic.divakar...@gmail.com>
> > > >>>> wrote:
> > > >>>>
> > > >>>>> Can this vote pass without the three +1's from the PMC? Can the
> > > >>>> committers
> > > >>>>> for this project provide binding

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

I believe all the major contributors were ICLA'd, and I disagree that all
contributors need to SGA/ICLA; we don't do that for an existing project.

We need to do the check to see how the footprint of contributions for the
largest contributor without an ICLA is (apologies for the horrible wording
there). There are over 400 contributors, but (quickly eyeballing) most are
covered by ICLA or small contributions. Note that we also have clause 5 of
Apache 2.0 at play for historical contributions here.

To John's point on source headers; the previous source headers said
"Copyright  by Contributors".

Hen

On Tue, Aug 29, 2017 at 11:01 Craig Russell  wrote:

> Hi Henri,
>
> If a project was developed outside Apache then everyone who contributed to
> the project has to have an ICLA on file or file a Software Grant as part of
> IP Clearance.
>
> It's not sufficient that the code has always been under the ASL 2.0.
>
> Are there any contributors to the project before it came to the incubator
> who are not now committers?
>
> Regards,
>
> Craig
>
> > On Aug 29, 2017, at 9:43 AM, Henri Yandell  wrote:
> >
> > Apologies - I missed that mentors hadn't voted on the podling release.
> Will
> > review tonight; hopefully their mentors can do similar.
> >
> > There's no reason for an SGA here (and who would even sign it?). Code has
> > been apache 2.0 since the initial commit on GitHub.
> >
> > On Tue, Aug 29, 2017 at 06:45 John D. Ament 
> wrote:
> >
> >> Dominic,
> >>
> >> One question, from looking a second time.  Was MXNet always Apache
> Licensed
> >> (prior to coming to the ASF)?
> >>
> >> John
> >>
> >> On Tue, Aug 29, 2017 at 8:39 AM Dominic Divakaruni <
> >> dominic.divakar...@gmail.com> wrote:
> >>
> >>> Thanks for the reply, John. None of the mentors have voted so far.
> >>> Henri, Suneel, Marcus, Sebastian, can you gents please review and vote?
> >>>
> >>> Also, Henri, didn't you mention that there was an SGA for this project?
> >>> Sorry if I don't recollect the exact details on the SGA bit.
> >>>
> >>> Dom
> >>>
> >>>
> >>> On Tue, Aug 29, 2017 at 5:27 AM, John D. Ament 
> >>> wrote:
> >>>
> >>>> Non pmc members can vote non-binding.  Usually mentors review
> releases.
> >>>> Have any of your mentors reviewed and voted on it?  Due to there being
> >> no
> >>>> SGA its a harder release to review.  I also need to cross check ICLAs
> >> and
> >>>> files that have changed license.
> >>>>
> >>>> On Aug 29, 2017 8:13 AM, "Dominic Divakaruni" <
> >>>> dominic.divakar...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Can this vote pass without the three +1's from the PMC? Can the
> >>>> committers
> >>>>> for this project provide binding votes on general@ to weigh in on
> >> this
> >>>>> release?
> >>>>>
> >>>>> On Mon, Aug 28, 2017 at 5:47 PM, Meghna Baijal <
> >>>> meghnabaijal2...@gmail.com
> >>>>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi All,
> >>>>>> This is a reminder that the vote to release MXNet (incubating)
> >> 0.11.0
> >>>> is
> >>>>>> still open.
> >>>>>> The vote will close on Tuesday, August 29, 2017 8.04 PM UTC.
> >>>>>>
> >>>>>> [ ] +1 Release this package as 0.1.0
> >>>>>> [ ] +0 no opinion
> >>>>>> [ ] -1 Do not release this package because…
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Meghna
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Aug 25, 2017, at 1:04 PM, Meghna Baijal <
> >>>> meghnabaijal2...@gmail.com
> >>>>>>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi all
> >>>>>>>
> >>>>>>> This is a call for a releasing Apache MXNet (incubating) 0.11.0,
> >>>>> release
> >>>>>>> candidate 3.
> >>>>>>>
> >>>>>>> Apache MXNet community has voted and approved the releas

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

Apologies - I missed that mentors hadn't voted on the podling release. Will
review tonight; hopefully their mentors can do similar.

There's no reason for an SGA here (and who would even sign it?). Code has
been apache 2.0 since the initial commit on GitHub.

On Tue, Aug 29, 2017 at 06:45 John D. Ament  wrote:

> Dominic,
>
> One question, from looking a second time.  Was MXNet always Apache Licensed
> (prior to coming to the ASF)?
>
> John
>
> On Tue, Aug 29, 2017 at 8:39 AM Dominic Divakaruni <
> dominic.divakar...@gmail.com> wrote:
>
> > Thanks for the reply, John. None of the mentors have voted so far.
> > Henri, Suneel, Marcus, Sebastian, can you gents please review and vote?
> >
> > Also, Henri, didn't you mention that there was an SGA for this project?
> > Sorry if I don't recollect the exact details on the SGA bit.
> >
> > Dom
> >
> >
> > On Tue, Aug 29, 2017 at 5:27 AM, John D. Ament 
> > wrote:
> >
> > > Non pmc members can vote non-binding.  Usually mentors review releases.
> > > Have any of your mentors reviewed and voted on it?  Due to there being
> no
> > > SGA its a harder release to review.  I also need to cross check ICLAs
> and
> > > files that have changed license.
> > >
> > > On Aug 29, 2017 8:13 AM, "Dominic Divakaruni" <
> > > dominic.divakar...@gmail.com>
> > > wrote:
> > >
> > > > Can this vote pass without the three +1's from the PMC? Can the
> > > committers
> > > > for this project provide binding votes on general@ to weigh in on
> this
> > > > release?
> > > >
> > > > On Mon, Aug 28, 2017 at 5:47 PM, Meghna Baijal <
> > > meghnabaijal2...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > > This is a reminder that the vote to release MXNet (incubating)
> 0.11.0
> > > is
> > > > > still open.
> > > > > The vote will close on Tuesday, August 29, 2017 8.04 PM UTC.
> > > > >
> > > > > [ ] +1 Release this package as 0.1.0
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because…
> > > > >
> > > > > Thanks,
> > > > > Meghna
> > > > >
> > > > >
> > > > >
> > > > > > On Aug 25, 2017, at 1:04 PM, Meghna Baijal <
> > > meghnabaijal2...@gmail.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > Hi all
> > > > > >
> > > > > > This is a call for a releasing Apache MXNet (incubating) 0.11.0,
> > > > release
> > > > > > candidate 3.
> > > > > >
> > > > > > Apache MXNet community has voted and approved the release.
> > > > > >
> > > > > > Vote thread:
> > > > > >
> > https://lists.apache.org/thread.html/2695a598ae0622484d4c886dc5b2ea
> > > > > 823c306ca4ebef66accec6ee76@%3Cdev.mxnet.apache.org%3E <
> > > > >
> https://lists.apache.org/thread.html/2695a598ae0622484d4c886dc5b2ea
> > > > > 823c306ca4ebef66accec6ee76@%3Cdev.mxnet.apache.org%3E>
> > > > > >
> > > > > >
> > > > > > Result thread:
> > > > > >
> > https://lists.apache.org/thread.html/d860c49194ec71c5c83ac0fa68df13
> > > > > 050dbfada4ff7052be3401fc1b@%3Cdev.mxnet.apache.org%3E <
> > > > >
> https://lists.apache.org/thread.html/d860c49194ec71c5c83ac0fa68df13
> > > > > 050dbfada4ff7052be3401fc1b@%3Cdev.mxnet.apache.org%3E>
> > > > > >
> > > > > >
> > > > > > The source tarball, including signatures, digests, etc. can be
> > found
> > > > at:
> > > > > >
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> > <
> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> >
> > > > > >
> > > > > >
> > > > > > The release tag can be found here:
> > > > > > https://github.com/apache/incubator-mxnet/tree/0.11.0.rc3 <
> > > > > https://github.com/apache/incubator-mxnet/tree/0.11.0.rc3>
> > > > > >
> > > > > >
> > > > > > The release hash is ba6413d29769075dd883ec5fe6eb24afc98fb3fd and
> > can
> > > > be
> > > > > found here:
> > > > > > https://github.com/apache/incubator-mxnet/commit/
> > > > > ba6413d29769075dd883ec5fe6eb24afc98fb3fd <
> https://github.com/apache/
> > > > > incubator-mxnet/commit/ba6413d29769075dd883ec5fe6eb24afc98fb3fd>
> > > > > >
> > > > > >
> > > > > > Release artifacts are signed with the following key:
> > > > > > AA3EBCC3E65A768AE3D2A64B8EF47B8720E8C549
> > > > > >
> > > > > >
> > > > > > KEY files are available here:
> > > > > >
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> > <
> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> >
> > > > > >
> > > > > >
> > > > > > For information about the contents of this release, see:
> > > > > > https://cwiki.apache.org/confluence/display/MXNET/v0.
> > > > > 11.0+Release+Notes+-+MXNet+v0.11+Release+Candidate <
> > > > > https://cwiki.apache.org/confluence/display/MXNET/v0.
> > > > > 11.0+Release+Notes+-+MXNet+v0.11+Release+Candidate>
> > > > > >
> > > > > >
> > > > > > The vote will be open for at least 72 hours.
> > > > > >
> > > > > > [ ] +1 Release this package as 0.1.0
> > > > > > [ ] +0 no opinion
> > > > > > [ ] -1 Do not release this package because...
> > > > > >
> > > > > > Thanks.
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > >

MXNet site questions

[Henri Yandell]

* Could Issues be turned on for the site so we can report site issues?
* How does one go about getting permission to the site?
* Apache footer needed (Copyright/trademarks statement)
* Need to add some links to Apache pages (Foundation page, Sponsors,
ApacheCon jump to mind)
* The logo is being pulled from mxnet.io

Two more additions to Jenkins

[Henri Yandell]

Hi Incubator folk with Chair permissions,

Could someone add cjolivier01 (Chris) and skm (Sandeep) to Jenkins for
MXNet please?

Thanks,

Hen

Re: Formalize Committer Proposal and Application Procedure

[Henri Yandell]

I worry that it creates a high barrier to entry.

It's a far more common pattern for a project to do poorly at recruiting new
committers, than it is for one to recruit too many.

Could you provide an example that provides a likely (imaginary if you'd
like) candidate? Mu's a pretty bad example for a new committer :) From the
attached doc I walk away thinking that I need to contribute for 2 years
before I can become a committer.

Hen

On Thu, Aug 3, 2017 at 9:49 AM, Ziheng Jiang  wrote:

> Forward my comment in private mail list:
>
> I agree that it would be nice to have some quantitative standards to
> evaluate the candidates. Let's encourage the future candidates do this.
>
> - Ziheng
>
> On Thu, Aug 3, 2017 at 09:44 Mu Li  wrote:
>
> > It seems that this thread didn't show in the dev list.
> >
> > Totally agree that we should make the committer nomination more formal.
> >
> > -- Forwarded message --
> > From: Tianqi Chen 
> > Date: Wed, Aug 2, 2017 at 4:20 PM
> > Subject: Formalize Committer Proposal and Application Procedure
> > To: priv...@mxnet.incubator.apache.org
> >
> >
> > Hi Guys:
> >  As I mentioned in another thread, I personally think the current
> > committer proposal and application process is too informal.
> >  As MXNet grows larger and the community involves, I think it would
> be
> > very helpful to formalize the process and provide a clear standard for
> what
> > are we looking for in the comitter proposal process, and allow us to
> > evaluate based on the concrete evidence listed in the application to
> > promote the comitters.
> >  This will setup a good standard for the contributors, as well as
> > provide solid material to back our decisions. After did some search, I
> > created this application template based on the committer application from
> > Apache Mesos. I wrote it from the perspective of myself.
> >  https://docs.google.com/document/d/1vKTgX1_EkAT7NSmaiBKBmbq
> > DuhF9kQd53BB4iUxGn4M/edit?usp=sharing
> >
> >  I would recommend this to become the mandatory thing for the future
> > committer nomination and voting, as well as the re-evaluation standard of
> > current comitters when we graduate from the incubator project.
> >
> > Tianqi
> >
> --
> Ziheng Jiang
> Fudan University | Computer Science
>

Re: Draft MXNet Podling report for Aug-2017

[Henri Yandell]

Following up on this - the first 3 reports in a new podling, or a new TLP
PMC, are made monthly. Then it moves to quarterly.

So MXNet doesn't have to report monthly again until it graduates.

The quarterly cycle for MXNet is:

   - January, April, July, October


On Tue, Aug 1, 2017 at 8:17 AM, Suneel Marthi  wrote:

> MxNet is not due to report for Aug 17, so we can disregard this.
>
>
>
> On Mon, Jul 31, 2017 at 4:40 PM, Bhavin Thaker 
> wrote:
>
> > Hi All,
> >
> >
> >
> > Please review the Podling Report for August 2017 so that we can file on
> > time. Feel free to make updates to this shared Google doc directly.
> >
> >
> >
> > https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_
> > biPh4-aCm8-bWwFzexnOW_GMA/edit
> >
> >
> >
> > Given below is the current snapshot of the report – it may change as
> > updates are made directly to the above shared Google doc.
> >
> >
> >
> > --snip—
> >
> > *MXNet*
> >
> >
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> >
> > train, and deploy deep neural networks on a wide array of devices, from
> >
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> >
> > fast model training, and supports a flexible programming model and
> multiple
> >
> > languages. MXNet allows you to mix symbolic and imperative programming
> >
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> >
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> >
> > and imperative operations on the fly. A graph optimization layer on top
> of
> >
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> >
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> >
> > machines.
> >
> >
> >
> > MXNet has been incubating since 2017-01-23.
> >
> >
> >
> > *Three most important issues to address in the move towards graduation:*
> >
> >
> >
> >  1. Migrate code (GitHub) and website to Apache Infra.
> >
> >  2. Establish a predictable release process consistent with Apache Way.
> >
> >  3. Grow the community.
> >
> >
> >
> > *Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be*
> >
> > *aware of?*
> >
> >
> >
> >   None
> >
> >
> >
> > *How has the community developed since the last report?*
> >
> >
> >
> >1. Various Slack channels and dev@ mailing lists are being used
> > actively.
> >2. A new blog published on OReilly web-site on 27-July having
> >step-by-step instructions to implement a convolutional neural network
> to
> >classify traffic signs with Apache MXNet:
> >
> > https://www.oreilly.com/ideas/classifying-traffic-signs-
> > with-mxnet-an-introduction-to-computer-vision-with-neural-networks
> >
> >1. A new blog post published on 28-July showing users how to exploit
> the
> >unique features of Apache MXNet with a cheat sheet:
> >
> > https://aws.amazon.com/blogs/ai/exploiting-the-unique-
> > features-of-the-apache-mxnet-deep-learning-framework-with-a-cheat-sheet/
> >
> >
> >
> > *How has the project developed since the last report?*
> >
> >
> >
> >1. The code base was migrated from http://github.com/dmlc/mxnet to
> >https://github.com/apache/incubator-mxnet on 28-July, 2017.
> >2. From a statistics perspective, 54 authors have pushed 140 commits
> to
> >master, with updates to 358 files including 22K additions and 3K
> > deletions.
> >3. Documentation- Architecture guides, How To’s, Tutorials, and APIs
> >continue to be improved.
> >4. More features (e.g. operators, algorithms) and bug-fixes requested
> by
> >the user community continue to be added.
> >
> >
> >
> > *How would you assess the podling's maturity?*
> >
> >
> >
> >   Podling's still getting established in Apache - so maturity == Low.
> >
> >
> >
> > Please feel free to add your own commentary.
> >
> >  [X] Initial setup
> >
> >  [  ] Working towards first release
> >
> >  [  ] Community building
> >
> >  [  ] Nearing graduation
> >
> >  [X] Other: A maintenance release is being planned for August 2017
> >
> >
> >
> > *Date of last release:*
> >
> >
> >
> >  A maintenance release MXNet 0.10.0 Post 2 with few bug-fixes was
> released
> > on 17-July, 2017.
> >
> >  https://github.com/apache/incubator-mxnet/releases/tag/0.10.0.post2
> >
> >
> >
> > *When were the last committers or PPMC members elected?*
> >
> >
> >
> >  Ly Nguyen added as a committer and PPMC member in June 2017.
> >
> >
> >
> > *Signed-off-by:*
> >
> >  [ ](mxnet) Sebastian Schelter
> >
> > Comments:
> >
> >  [ ](mxnet) Suneel Marthi
> >
> > Comments:
> >
> >  [ ](mxnet) Markus Weimer
> >
> > Comments:
> >
> >  [ ](mxnet) Henri Yandell
> >
> > Comments:
> >
> >
> >
> > --snip—
> >
> >
> >
> > Thanks,
> >
> > Bhavin Thaker.
> >
>

Re: Migration to Apache has completed

[Henri Yandell]

Brilliant :)

Thank you for all your work Ly.

On Fri, Jul 28, 2017 at 12:18 PM, Ly Nguyen  wrote:

> Hi folks,
>
> We've migrated our code base to Apache/incubator-mxnet:
> https://github.com/apache/incubator-mxnet
>
> Please help us test whether:
>
>- your existing forks can continue to pull
>- clone/fork from the old URL http://github.com/dmlc/mxnet as well as
>the new URL
>- make a pull request against the new URL
>- etc.
>
> Thanks and let us know if you run into any problems. Much appreciated.
>
> Thanks to Pono for the help!
>
> Ly
>

Two additions to Jenkins

[Henri Yandell]

Hi PMC-Chair type folk on general@incubator.

Could someone add Naveen Swamy (nswamy@) and Mu Li (muli@) to the Jenkins
ldap group please.

Thank you,

Hen

Re: Granting access to Jenkins

[Henri Yandell]

Looking at this, the path to access is to ask for someone to do it on
general@incubator. I'll send an email.

The docs say you have to be a PMC chair, which I'm not.

Hen

On Mon, Jul 17, 2017 at 3:00 PM, Ly Nguyen  wrote:

> Hi Henri, checking in about this. Can Naveen and Mu gain access?
>
> On Fri, Jul 14, 2017 at 3:11 PM, Ly Nguyen  wrote:
>
>> 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  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#Je
>>>> nkins-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 
>>>> 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  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 
>>>>>> 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 
>>>>>>>
>>>>>> 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 
>>>>>>>>
>>>>>>> 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 
>>>>>>>>>
>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>

Re: Why its a good idea to move to your own infrastructure

[Henri Yandell]

That's a bit over-simplified in my (not lawyer) understanding.

If Apache received a DMCA takedown, it would have to do the same things
that GitHub did. There seem to potentially be similar laws in Europe. My
vague understanding of US DMCA is that you have to take it down when
reported, and then review whether it should have been taken down; but I
could have misunderstood that (was on some mailing list conversation years
ago :) ).

The advantage of hosting things yourself is that you would still have
access to the thing you took down (as it wouldn't be a distribution).
GitHub's not permitted to distribute the content to the account owners. I'm
not sure whether Apache would provide it to the committers or not; I
suspect it would be locked down while Apache figured things out.

A disadvantage of hosting things (personal project) is that you will
potentially be slow and fail to take the content down quickly enough.

New t-shirt slogan:"Don't hate the hub :)"

Hen



On Thu, Jul 13, 2017 at 12:30 AM, Sebastian Schelter  wrote:

> Hi,
>
> This mail is a little bit off-topic, but I would like to share a story that
> shows how important it is for open source projects to move to their own
> infrastructure (like the one provided by the ASF) and not rely on the
> goodwill of hosters like github:
>
> https://blog.freeyourgadget.org/our-dmca-takedown-a-post-mortem.html
>
> Best,
> Sebastian
>

Re: July 2017 Release

[Henri Yandell]

The release manager should upload their PGP key to public servers; however
it doesn't need to be in the web of trust.

+1 on SHAs being created; that shouldn't be difficult.

(The SHAs give confidence that the mirrors are providing the right content;
the PGP gives confidence that Apaches content hasn't been sneakily changed;
the web of trust gives confidence that the release manager is trustworthy).

The vote/review can start when an RC has been produced.


On Thu, Jul 13, 2017 at 9:47 AM, Markus Weimer  wrote:

> Hi,
>
> thanks for sharing the plans! Is there a specific reason to skip the
> SHA hashes? Much of the integrity of Apache releases stems from having
> those SHAs in as many inboxes as possible, after all.
>
> Thanks,
>
> Markus
>
> On Tue, Jul 11, 2017 at 4:07 PM, Ly Nguyen  wrote:
> > @mentors, we would like to hold a RC vote and release on Monday July
> 17th.
> >
> >- Are there any blockers (i.e., licenses)?
> >- Can you validate the proposal below?
> >
> >
> > *PROPOSAL FOR JULY RELASE (version?):*
> > *Start voting THIS week. Release on Monday July 17th.*
> >
> >1. Create signing keys
> >   1. SKIP web of trust linking and upload to public keyserver this
> time
> >2. Create RC in
> >https://dist.apache.org/repos/dist/dev/incubator/podlingName
> >   1. Currently missing a DISCLAIMER file - do we need that?
> >   2. SKIP creating SHA checksum this time
> >3. Start a vote on dev@ list
> >4. svn mv RC to the release location
> >
> >
> >
> >
> > *NOTES FROM DOCS FOR REFERENCE:*
> > http://incubator.apache.org/guides/releasemanagement.html
> >
> >- 3 +1 votes from IPMC members (these are the votes that count but we
> >should open up to the whole podling community)
> >- For podlings, 2 additional constraints:
> >   - Release artifacts must include “incubating” in final file name
> (ex:
> >   apache-mxnet-src-0.10.1-incubating.tar.gz)
> >   - Release artifacts must include disclaimer in the release
> artifacts
> >
> >
> >- The Incubator PMC expects the source releases to be staged on
> >https://dist.apache.org/repos/dist/dev/incubator/podlingName so that
> >they can easily be moved to the release location via svn mv   (
> >http://www.apache.org/dist/incubator/)
> >- After graduating, RC’s go into https://dist.apache.org/repos/
> dist/dev/
> >and official releases go into https://dist.apache.org/repos/
> dist/release/
> >
> >
> > http://incubator.apache.org/guides/branding.html#disclaimers
> >
> >- Apache Press Team [http://www.apache.org/press/index.html#whoweare]
> >must review and coordinate releases for branding
> >- On website and in release DISCLAIMER file:
> >- Apache Podling-Name is an effort undergoing incubation at The Apache
> >   Software Foundation (ASF), sponsored by the name of Apache TLP
> sponsor.
> >   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.
> >   - Website should include Apache Incubator logo:
> >   http://incubator.apache.org/guides/press-kit.html
> >
> >
> >- Release should include:
> >   - DISCLAIMER
> >   - LICENSE
> >   - NOTICE - attribution notices
> >
> >
> > http://www.apache.org/legal/release-policy.html
> >
> >- A release must contain source package which is cryptographically
> >signed by Release Manager with detached signature. It must be tested
> prior
> >to voting for release.
> >- Release must only contain appropriately licensed code
> >- Please ensure you wait >=24 hours after uploading a release before
> >making announcements so mirrors catch up
> >- Releases of more than 1GB of artifacts require a heads-up to
> >Infrastructure in advance.
> >- Which directory for what build?
> >http://www.apache.org/legal/release-policy.html#build-directories
> >
> >
> > http://www.apache.org/dev/release-distribution.html
> >
> >- Artifacts MUST be accompanied by:
> >   - apache-mxnet-src-0.10.1-incubating.asc - contains OpenPGP
> >   compatible ASCII armored detached signature
> >   - apache-mxnet-src-0.10.1-incubating.md5 - MD5 checksum
> >   - apache-mxnet-src-0.10.1-incubating.sha - SHA checksum (SHOULD)
> >- Publish KEYS file in distribution directory root
> >   - Signing keys MUST be published in KEYS file, SHOULD be available
> in
> >   global public keyserver
> >   http://www.apache.org/dev/release-signing#keyserver, SHOULD be
> linked
> >   into web of trust
> >   - Keys MUST be RSA & 4096 bits
> >
> >
> > http://www.apache.org/dev/re

Re: Rcpp licensing in Apache MXNet

[Henri Yandell]

We should bring this up on general@incubator or legal-discuss@.

On Thu, Jul 6, 2017 at 10:59 PM, Qiang Kou  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 
> 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 mailto:q...@umail.iu.edu>>
> > Sent: Thursday, July 6, 2017 3:41 PM
> > Subject: Re: Rcpp licensing in Apache MXNet
> > To: mailto:dev@mxnet.
> incubator.apache.org
> > >>
> >
> >
> > Hi, Felix,
> >
> > I just want to make sure there is no misunderstanding between us.
> >
> > (1) The MXNet R package heavily used the Rcpp package, but we only
> include
> > the
> > header file, Rcpp.h, like https://github.com/dmlc/mxnet/
> > blob/master/R-package/src/base.h#L11
> >
> > The MXNet R package doesn't contain any source code from Rcpp and there
> is
> > no linking against Rcpp.
> >
> > (2) There is "LinkingTo: Rcpp" in the R package description (
> > https://github.com/dmlc/mxnet/blob/master/R-package/DESCRIPTION#L32).
> > However, this only means we want to use the header files from Rcpp.
> >
> > "A package that wishes to make use of header files in other
> > packages needs to declare them as a
> > comma-separated list in the field ‘LinkingTo’ in the DESCRIPTION file. "
> >
> > More details can be found from R's official manual (
> > https://cran.r-project.org/doc/manuals/r-release/R-exts.
> > html#Package-Dependencies).
> >
> > (3) Many R packages who use Rcpp to communicate with C++ have been
> released
> > under Apache License, like feather (https://github.com/wesm/
> > feather/blob/master/R/DESCRIPTION).
> >
> > Best,
> >
> > Qiang Kou
> >
> > On Thu, Jul 6, 2017 at 1:20 AM, Felix Cheung  > mailto:felixcheun...@hotmail.com>>
> > wrote:
> >
> > > On a related note, Rcpp, used extensively in the R package, is
> > GPLv2/GPLv3
> > > licensed.
> > >
> > > I'm not aware of any other R package available that supports R<->C++.
> > >
> > > https://www.apache.org/legal/resolved.html#category-x
> > > https://cran.r-project.org/web/packages/Rcpp/index.html
> > >
> > >
> >
> >
> >
>
>
> --
> Qiang Kou
> q...@umail.iu.edu
> School of Informatics and Computing, Indiana University
>

Licensing update per code move

[Henri Yandell]

Thought I'd describe one of the first sets of changes we should make when
the code moves to an Apache git repo.

We should update the licensing.

1) We should update the NOTICE file, once on Apache's source control, to
say:

 Apache MXNet
Copyright 2017 The Apache Software Foundation
This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).

2) Every source file (basically all files bar images, binaries and test
data) should have a commented source header:

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.


Described on this page: https://www.apache.org/legal/src-headers.html

---

Hope that's useful :)

Hen

ZeroMQ licensing in Apache MXNet

[Henri Yandell]

One of the items that is on the list to do before releasing Apache MXNet is
removing ZeroMQ from the codebase/dependencies.

ZeroMQ is licensed under the LGPL 3.0 with an exception for static
compiling.

They have long been interested in relicensing to MPL 2.0, but haven't made
much progress, though they did relicense JeroMQ (Java
wrapper/implementaiton) last year.

In the last few months they've made a lot of progress towards relicensing:
https://github.com/zeromq/libzmq/tree/master/RELICENSE

I'd like to ask on legal-discuss@ for an exception (one year?) to continue
using ZeroMQ, with prominent documentation, in MXNet given the trend
towards MPL 2.0.

Any concerns before I do so?

Thanks,

Hen

Re: Podling Report Reminder - July 2017

[Henri Yandell]

Thanks Dominic :)

I signed off with a couple of minor word changes (contributor->committer),
(next->afterwards).

On Wed, Jul 5, 2017 at 9:47 PM, Sebastian  wrote:

> Also signed off!
>
>
>
> On 06.07.2017 00:34, Markus Weimer wrote:
>
>> On Wed, Jul 5, 2017 at 3:30 PM, Suneel Marthi  wrote:
>>
>>> Thanks Dom, the report has been filed.
>>>
>>> Mentors, please sign-off on the report.
>>>
>>
>> Thanks and done!
>>
>> Markus
>>
>>

Board report due

[Henri Yandell]

In case the relentless automated pinging hasn't given it away, we've a
board report due.

Hen

Re: Granting access to Jenkins

[Henri Yandell]

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  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  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 
> 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 
> > 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 
> > 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
> > > > >
> > > >
> > >
> >
>

Re: Granting access to Jenkins

[Henri Yandell]

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  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  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
> >
>

Re: Typo in the documentation

[Henri Yandell]

Hopefully the original graphics can be committed.

On Fri, Jun 16, 2017 at 11:24 AM, Ly Nguyen  wrote:

> 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  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 
> > 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
> >>
> >
> >
>

Re: ask for slack invitation

[Henri Yandell]

The archiving is a paid feature, or having a public Slack channel that
users of the software can join without having to come cap in hand to the
dev@ list?

On Thu, Jun 15, 2017 at 1:06 AM, Suneel Marthi 
wrote:

> Right, now that Amazon is gonna buy Slack for 9B - maybe we can do that -
> otherwise that kind'a stuff would only work for paid Slack subscriptions.
>
> :-)
>
> On Thu, Jun 15, 2017 at 10:00 AM, Sebastian Schelter <
> ssc.o...@googlemail.com> wrote:
>
> > Ideally, the slack channel should also be archived somewhere, so that
> > people can search through past conversations and search engines can index
> > them.
> >
> > Best,
> > Sebastian
> >
> > 2017-06-15 9:58 GMT+02:00 Isabel Drost-Fromm :
> >
> > > On Thu, Jun 15, 2017 at 06:49:21AM +0200, Suneel Marthi wrote:
> > > > anyone with apache.org shuld be able to register on slack -
> Sebastian
> > > was
> > > > asking me the same question in Berlin last week.
> > > >
> > > > Suggest leave the channel open to anyone registering with apache.org
> > > email.
> > >
> > > Is there a way to make it entirely public? @apache.org mail addresses
> > > only go to
> > > ppl who are already committers. The goal of any such channel should be
> to
> > > attract new blood to the project...
> > >
> > > Isabel
> > >
> > > --
> > > Sorry for any typos: Mail was typed in vim, written in mutt, via ssh
> > (most
> > > likely involving some kind of mobile connection only.)
> > >
> >
>

Re: ask for slack invitation

[Henri Yandell]

Hopefully someone sent Xiang an invite.

Is there a way Slack can be setup so that we don't have to send invites?

Where are the instructions to the community on how to join the Slack
channel?

Hen


On Sat, Jun 10, 2017 at 12:29 AM, Xiang Ruan  wrote:

> Hi, Dear Sir/Madam
>
> My name is Xiang Ruan.
>
> I am pretty interested in using mxnet for deep learning and would like to
> use mxnet for many of our projects.
> Could you please be kind to send me a slack invitation to mxnet channel?
>
> Thank you in advance.
>
> Best regards,
>
>
> --
> Xiang Ruan, Ph.D (阮 翔 - ゲン ショウ)
> Co-founder & CEO
> tiwaki Co., Ltd. Japan
>
> Email:  ruanxi...@tiwaki.com
> Homepage:   http://www.tiwaki.com
> Phone:  +81-77-567-8018
> Mobile: +81-90-9860-7528
>

Fwd: [NOTICE] Upcoming changes to our GitHub Org

[Henri Yandell]

FYI/reminder (you should all have got this email).

When we move the GitHub repo over, you'll need to have registered your
GitHub login.


-- Forwarded message --
From: Daniel Gruno 
Date: Sun, May 28, 2017 at 7:31 AM
Subject: [NOTICE] Upcoming changes to our GitHub Org
To: committ...@apache.org


Hi folks,
this is a notice that we have changed some parts of the way we handle
invites to our GitHub organisation. The following rules are now in place:

- To be a part of our GitHub Org, you MUST have your GitHub ID in LDAP
(see https://id.apache.org to change it)
- Anyone not with their name in LDAP will be removed automatically.
- Changes now take place every 10 minutes instead of every hour.

If you are not interested in being a part of our GitHUb org, you can
safely ignore this email for now.

With regards,
Daniel on behalf of ASF Infra.

Re: [Launch Announcement] MXNet v0.10.0

[Henri Yandell]

Noting that this is the last release before bringing the code to Apache.
ie) This is the pre-Apache community's action, rather than any form of
Apache release. Now the line has been drawn in the sand on the previous
work, the community can start focusing on migrating the code/site over and
preparing a first Apache MXNet release.

On Sat, May 27, 2017 at 7:25 AM, Naveen Swamy  wrote:

> Hi All,
>
> We are happy to announce the release of MXNet v0.10.0 that brings:
>
>
>
>-
>
>Overhauled documentation for commonly used Python APIs, Installation
>Instructions, Tutorials, HowTos and MXNet Architecture.
>-
>
>Updated mxnet.io for improved readability.
>-
>
>Pad operator now support reflection padding.
>-
>
>Fixed a memory corruption error in threadedengine.
>-
>
>Added CTC loss layer to contrib package. See mx.contrib.sym.ctc_loss.
>-
>
>Added new sampling operators for several distributions
>(normal,uniform,gamma,exponential,negative binomial).
>-
>
>Added documentation for experimental RNN APIs.
>
> The RC tag in git is: v0.10.0 
> and the latest commit id is 8713d257cde97a660a459aa8a50a780944cf823c
>  0944cf823c>.
> We have also made this release available for Python binding via pip.
>
>
> Please update to this latest version and provide your feedback.
>
>
> Thanks, Naveen
>

Re: Release of v0.10.0-rc0 release candidate

[Henri Yandell]

When: ASAP.
Who: Mu (or another DMLC owner) needs to give Pono (Github login: pono)
Owner permissions on the DMLC organization. Then Pono can do the migration.
The first part is a matter of clicking a button on the GitHub UI. After
that it's a question of seeing what changes there are to the developer
workflow, and figuring out how to deal with those.

Hen


On Fri, May 26, 2017 at 10:40 PM, Thaker, Bhavin  wrote:

> Thanks for the confirmation, Henri.
>
> Curious:
> When do we plan to make this change?
> Who will make this change?
>
> Bhavin Thaker.
>
> > On May 26, 2017, at 6:51 PM, Henri Yandell  wrote:
> >
> > Yes.
> >
> >  https://github.com/dmlc/mxnet -> https://github.com/apache/incu
> bator-mxnet
> > .
> >
> > Then when it graduates, the 'incubator-' means another move.
> >
> > Hen
> >
> >> On Fri, May 26, 2017 at 9:45 AM, Thaker, Bhavin 
> wrote:
> >>
> >> Hi Henri,
> >>
> >> Henri>ie) We should plan GitHub migration for June 3->10?
> >>
> >> What does GitHub migration exactly mean?
> >>
> >> Does it mean moving mxnet from dmlc to apache,
> >> i.e. from https://github.com/dmlc/mxnet to
> https://github.com/apache/mxnet
> >> ?
> >>
> >> Bhavin Thaker.
> >>
> >> On 5/21/17, 6:31 PM, "hyand...@gmail.com on behalf of Henri Yandell" <
> >> hyand...@gmail.com on behalf of he...@yandell.org> wrote:
> >>
> >>This would be a line-in-the-sand old-community release before we then
> >> move
> >>the code over to Apache?
> >>
> >>ie) We should plan GitHub migration for June 3->10?
> >>
> >>On Sun, May 21, 2017 at 8:42 AM, Naveen Swamy 
> >> wrote:
> >>
> >>> Hi All ,
> >>>
> >>> We are happy to announce the release of v0.10.0-rc0 release
> >> candidate that
> >>> brings
> >>>
> >>>   -
> >>>
> >>>   Overhauled documentation for commonly used Python APIs,
> >> Installation
> >>>   instructions, Tutorials, HowTos and MXNet Architecture.
> >>>   -
> >>>
> >>>   Updated mxnet.io for improved readability.
> >>>   -
> >>>
> >>>   Added support for reflection padding.
> >>>   -
> >>>
> >>>   Fixed memory corruption in threadedengine.
> >>>   -
> >>>
> >>>   Added support for CTC loss layer. See mx.contrib.sym.ctc_loss.
> >>>
> >>>
> >>>
> >>> The RC tag in git is:v0.10.0-rc0
> >>> <https://github.com/dmlc/mxnet/tree/v0.10.0-rc0>, and the latest
> >> commit id
> >>> is: 13fc92f52cc55157a4764227109d7c37c0c988cd
> >>> <https://github.com/dmlc/mxnet/commit/13fc92f52cc55157a4764227109d7c
> >>> 37c0c988cd>
> >>>
> >>> We invite you to try it out and provide feedback. we will pick the
> >>> requested changes after 05-31-2017 and release v0.10.0 on 06-02-2017.
> >>>
> >>> Thanks, Naveen
> >>>
> >>
> >>
> >>
>

Re: Release of v0.10.0-rc0 release candidate

[Henri Yandell]

Yes.

  https://github.com/dmlc/mxnet -> https://github.com/apache/incubator-mxnet
.

Then when it graduates, the 'incubator-' means another move.

Hen

On Fri, May 26, 2017 at 9:45 AM, Thaker, Bhavin  wrote:

> Hi Henri,
>
> Henri>ie) We should plan GitHub migration for June 3->10?
>
> What does GitHub migration exactly mean?
>
> Does it mean moving mxnet from dmlc to apache,
> i.e. from https://github.com/dmlc/mxnet to https://github.com/apache/mxnet
> ?
>
> Bhavin Thaker.
>
> On 5/21/17, 6:31 PM, "hyand...@gmail.com on behalf of Henri Yandell" <
> hyand...@gmail.com on behalf of he...@yandell.org> wrote:
>
> This would be a line-in-the-sand old-community release before we then
> move
> the code over to Apache?
>
> ie) We should plan GitHub migration for June 3->10?
>
> On Sun, May 21, 2017 at 8:42 AM, Naveen Swamy 
> wrote:
>
> > Hi All ,
> >
> > We are happy to announce the release of v0.10.0-rc0 release
> candidate that
> > brings
> >
> >-
> >
> >Overhauled documentation for commonly used Python APIs,
> Installation
> >instructions, Tutorials, HowTos and MXNet Architecture.
> >-
> >
> >Updated mxnet.io for improved readability.
> >-
> >
> >Added support for reflection padding.
> >-
> >
> >Fixed memory corruption in threadedengine.
> >-
> >
> >Added support for CTC loss layer. See mx.contrib.sym.ctc_loss.
> >
> >
> >
> > The RC tag in git is:v0.10.0-rc0
> > <https://github.com/dmlc/mxnet/tree/v0.10.0-rc0>, and the latest
> commit id
> > is: 13fc92f52cc55157a4764227109d7c37c0c988cd
> > <https://github.com/dmlc/mxnet/commit/13fc92f52cc55157a4764227109d7c
> > 37c0c988cd>
> >
> > We invite you to try it out and provide feedback. we will pick the
> > requested changes after 05-31-2017 and release v0.10.0 on 06-02-2017.
> >
> > Thanks, Naveen
> >
>
>
>

Website?

[Henri Yandell]

Is this where the source currently is for mxnet.io?

https://github.com/dmlc/web-data/tree/master/mxnet

I was thinking that those of us on the mentor side could help out with
migrating that over to Apache-land.

Hen

Re: Release of v0.10.0-rc0 release candidate

[Henri Yandell]

This would be a line-in-the-sand old-community release before we then move
the code over to Apache?

ie) We should plan GitHub migration for June 3->10?

On Sun, May 21, 2017 at 8:42 AM, Naveen Swamy  wrote:

> Hi All ,
>
> We are happy to announce the release of v0.10.0-rc0 release candidate that
> brings
>
>-
>
>Overhauled documentation for commonly used Python APIs, Installation
>instructions, Tutorials, HowTos and MXNet Architecture.
>-
>
>Updated mxnet.io for improved readability.
>-
>
>Added support for reflection padding.
>-
>
>Fixed memory corruption in threadedengine.
>-
>
>Added support for CTC loss layer. See mx.contrib.sym.ctc_loss.
>
>
>
> The RC tag in git is:v0.10.0-rc0
> , and the latest commit id
> is: 13fc92f52cc55157a4764227109d7c37c0c988cd
>  37c0c988cd>
>
> We invite you to try it out and provide feedback. we will pick the
> requested changes after 05-31-2017 and release v0.10.0 on 06-02-2017.
>
> Thanks, Naveen
>

Re: Blog

[Henri Yandell]

Makes sense (start new mxnet specific one; keep dmlc old one).

It'd also be cool to come up with some kind of method by which drafts are
written, mailing list informed, and folk on the list can offer editorial
feedback.

If you ever need someone to test blogs for newbies, I can definitely help
there :)

Hen


On Sun, May 21, 2017 at 9:54 AM, Tianqi Chen 
wrote:

> We might want to still keep dmlc blog, as it also contains announcement for
> other dmlc projects, but move the mxnet related announcements to new blog
> location.
>
> Tianqi
>
> On Sat, May 20, 2017 at 10:38 PM, Mu Li  wrote:
>
> > Currently, we have one at http://dmlc.ml/. We can transfer it to a new
> > place if necessary
> >
> >
> > On Sat, May 20, 2017 at 3:03 PM, Henri Yandell 
> wrote:
> >
> > > It was recommended that we set up a blog:
> > >
> > >   * Request a blog: https://www.apache.org/dev/project-blogs
> > >
> > > That will give us a place to start communicating about new features
> etc.
> > >
> > > Personally in the quality of a heartbeat. I don't much care how great
> > each
> > > individual blog is, but if it has a steady pace and doesn't repeat
> > itself,
> > > then it's a good thing.
> > >
> > > With things like adding new operators, a short blog entry on Apache
> > > mentioning that it's been added is an awesomeness.
> > >
> > > Anyone interested in volunteering to request/setup the blog?
> > >
> > > Hen
> > >
> >
>

Blog

[Henri Yandell]

It was recommended that we set up a blog:

  * Request a blog: https://www.apache.org/dev/project-blogs

That will give us a place to start communicating about new features etc.

Personally in the quality of a heartbeat. I don't much care how great each
individual blog is, but if it has a steady pace and doesn't repeat itself,
then it's a good thing.

With things like adding new operators, a short blog entry on Apache
mentioning that it's been added is an awesomeness.

Anyone interested in volunteering to request/setup the blog?

Hen

Code Migration

[Henri Yandell]

Dominic and I chatted with Pono and the Infra team at ApacheCon last week.

I admin GitHub organizations in my dayjob, so was asking some questions
about things were setup to understand what impact there would be after the
move. Here are my notes:

* The migration, as previously stated, will involve giving Pono Owner
permissions on github.com/dmlc, and letting him know which repositories we
want to migrate. He will click a few buttons, double-check things, and then
the DMLC Owners can remove his Owner permissions. Afaik, we're only looking
to migrate github.com/dmlc/mxnet at this time, but might come back with
more to migrate as things are ironed out. Pono will then sync the code with
git.apache.org|gitbox.

* We will use GitBox (https://gitbox.apache.org/) to connect our GitHub
accounts with our Apache accounts, thus giving us permission to do things
on GitHub.

* It was noted that we wouldn't be able to resolve a pull request that
isn't being merged (other than by doing an empty commit). Thinking back on
that, I'm not sure why that would be the case (not aware GitHub has
different permissions for issues/pull-requests), so I've just linked my
account on GitBox and am going to play in the test account.

* For releases, we would need to use the GitHub draft release notion. ie)
We would tag a release candidate in git, but mark it as a draft on GitHub
so it doesn't show there. Then we would prepare-release/review/vote/repeat
until happy, and switch the 'winning' release to being public (rather than
draft).

* Jenkins. Apache has a Jenkins cluster(? - not sure if that's the right
way to refer to it) and we can either use Jenkins there or, for example if
we want GPU testing, get one of our employers to provide GPU instances and
run a node there that is connected to the central ASF Jenkins.

Various Jenkins links:

  Jenkins nodes: https://reference.apache.org/committer/node-hosting (for
GPU/CI etc)

  More Jenkins: https://cwiki.apache.org/confluence/display/INFRA/Jenkins

  https://cwiki.apache.org/confluence/display/INFRA/Create+new+Jenkins+node

---

* For the website, post code-migration, the recommendation is that we
should get a separate repository setup and use something like Pelican to
build .md files. A Jenkins instance would build said .md into html, and
push to git (I think). Some work to do, but should be easy to find another
project to copy.

Info on Pelican: http://docs.getpelican.com/en/3.6.3/publish.html​
 (recommended website .md support)​

* We would also work with Infra to transfer over the current domain name so
redirects are swift and no trademark issues.

Hen

Re: Podling Report - May 2017

[Henri Yandell]

I agree that doing a release & documenting a process is an important item
to address. Not sure there's a requirement for a formal release schedule in
the Apache way.

Growing more community - yes. Lots of diverse interest, but majority of
commits are from 2 people. My one complaint is that it's not actionable.

I've updated that section to:

1.  Migrate code(GitHub) and website to Apache.
2.  Grow the community:
2.1 Improving documentation including APIs & Tutorials.
2.2 Improving user-experience, for example improved error messages.
3   Establish a dependable, Apache-way consistent release process.
3.1 Features: New operators requested by user community.
  Accelerate performance on CPUs and GPUs.

How does that look? Idea is to make it clearer what we're doing on that
front. We'll also need a 3.2 of 'Fix licensing policy issues' and others
before #3.

Hen

On Thu, May 4, 2017 at 1:43 AM, Suneel Marthi  wrote:

> IMO, the top 3 items to be addressed for graduation are:-
>
> 1.  Migrate code(GitHub) and website to Apache. 2.  Establish a
> formal release schedule and process, allowing for dependable release
> cycles in a manner consistent with the Apache way.3.  Grow the
> community to establish diversity of background.
>
>
> On Thu, May 4, 2017 at 3:29 AM, Henri Yandell  wrote:
>
> > Thank you Mu.
> >
> > I added it to https://wiki.apache.org/incubator/May2017 (with some
> > additions) and signed off as Mentor. Everyone let me know if any of the
> > additions I made were objectionable. The main change was to insert
> > Migrating code+website as the top priority.
> >
> > Other Mentors - your review is much appreciated :)
> >
> > On Wed, May 3, 2017 at 1:22 PM, Mu Li  wrote:
> >
> > > *   Your project name:
> > >
> > > Apache MXNet
> > >
> > > *   A brief description of your project, which assumes no knowledge of
> > the
> > > project or necessarily of its field
> > >
> > > MXNet is an open-source deep learning framework that allows you to
> > define,
> > > train, and deploy deep neural networks on a wide array of devices, from
> > > cloud infrastructure to mobile devices. It is highly scalable, allowing
> > for
> > > fast model training, and supports a flexible programming model and
> > multiple
> > > languages. MXNet allows you to mix symbolic and imperative programming
> > > flavors to maximize both efficiency and productivity. MXNet is built
> on a
> > > dynamic dependency scheduler that automatically parallelizes both
> > symbolic
> > > and imperative operations on the fly. A graph optimization layer on top
> > of
> > > that makes symbolic execution fast and memory efficient. The MXNet
> > library
> > > is portable and lightweight, and it scales to multiple GPUs and
> multiple
> > > machines.
> > >
> > > *   A list of the three most important issues to address in the move
> > > towards graduation.
> > >
> > > 1.   Improved documentation including APIs, Tutorials, etc. and
> > > user-experience like improved error messages, etc.
> > > 2.   Support additional features (new operators) requested by user
> > > community.
> > > 3.   Accelerate performance on CPUs and GPUs.
> > >
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> > > aware of:
> > >
> > > None.
> > >
> > > *   How has the community developed since the last report.
> > >
> > > 1. The community was engaged for contributions to API documentation and
> > > tutorials.
> > > 2. Slack channels have been created for the community to contribute
> > > discussions to.
> > > 3. In the last month, excluding merges, 51 authors have pushed 165
> > commits
> > > to master and 180 commits to all branches. On master, 502 files have
> > > changed and there have been 26,246 additions and 12,188 deletions.
> Count
> > of
> > > Closed Issues = 62, Count of New Issues = 146, Count of Merged Pull
> > > Requests = 161, Count of Proposed Pull Requests = 27.
> > >
> > > *   How has the project developed since the last report.
> > >
> > > 1. The API Documentation has improved.
> > > 2. More features (e.g. operators) requested by the user community has
> > been
> > > added.
> > > 3. Hardware acceleration like cuDDN6 integration and MKL ML package
> > > integration was completed.
> > > 4. A new Perl language binding for MXNet was added.
> > >
> > > *   How does the podling rate their own maturity.
> > >
> > > Maturity = Low
> > >
> > > Thanks,
> > > Mu
> > >
> >
>

Re: Podling Report - May 2017

[Henri Yandell]

Thank you Mu.

I added it to https://wiki.apache.org/incubator/May2017 (with some
additions) and signed off as Mentor. Everyone let me know if any of the
additions I made were objectionable. The main change was to insert
Migrating code+website as the top priority.

Other Mentors - your review is much appreciated :)

On Wed, May 3, 2017 at 1:22 PM, Mu Li  wrote:

> *   Your project name:
>
> Apache MXNet
>
> *   A brief description of your project, which assumes no knowledge of the
> project or necessarily of its field
>
> MXNet is an open-source deep learning framework that allows you to define,
> train, and deploy deep neural networks on a wide array of devices, from
> cloud infrastructure to mobile devices. It is highly scalable, allowing for
> fast model training, and supports a flexible programming model and multiple
> languages. MXNet allows you to mix symbolic and imperative programming
> flavors to maximize both efficiency and productivity. MXNet is built on a
> dynamic dependency scheduler that automatically parallelizes both symbolic
> and imperative operations on the fly. A graph optimization layer on top of
> that makes symbolic execution fast and memory efficient. The MXNet library
> is portable and lightweight, and it scales to multiple GPUs and multiple
> machines.
>
> *   A list of the three most important issues to address in the move
> towards graduation.
>
> 1.   Improved documentation including APIs, Tutorials, etc. and
> user-experience like improved error messages, etc.
> 2.   Support additional features (new operators) requested by user
> community.
> 3.   Accelerate performance on CPUs and GPUs.
>
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of:
>
> None.
>
> *   How has the community developed since the last report.
>
> 1. The community was engaged for contributions to API documentation and
> tutorials.
> 2. Slack channels have been created for the community to contribute
> discussions to.
> 3. In the last month, excluding merges, 51 authors have pushed 165 commits
> to master and 180 commits to all branches. On master, 502 files have
> changed and there have been 26,246 additions and 12,188 deletions. Count of
> Closed Issues = 62, Count of New Issues = 146, Count of Merged Pull
> Requests = 161, Count of Proposed Pull Requests = 27.
>
> *   How has the project developed since the last report.
>
> 1. The API Documentation has improved.
> 2. More features (e.g. operators) requested by the user community has been
> added.
> 3. Hardware acceleration like cuDDN6 integration and MKL ML package
> integration was completed.
> 4. A new Perl language binding for MXNet was added.
>
> *   How does the podling rate their own maturity.
>
> Maturity = Low
>
> Thanks,
> Mu
>

Re: PyPI for MXNet 0.9.5

[Henri Yandell]

Is that something that would take care of the sub-modules linking?

We could either keep them at DMLC and send to PyPI for MXNet's needs, or we
could have separate repos at Apache and push separately.

In terms of which is the above seems best, I'm not sure how related the
submodules are to the MXNet focus. Would need to understand more about the
modules and what their scope is to grokk better :)

Hen

On Wed, May 3, 2017 at 10:31 PM, Spisak, Joseph  wrote:

> Awesome work Sheng!
>
> Cheers,
> -Joe
>
>
> On 5/3/17, 10:29 PM, "Dominic Divakaruni" 
> wrote:
>
> Much thanks to szha@ for this!
>
> Python pip install packages for OSX, Linux for MKL and Cuda 7.5 and 8
> are
> now available! As an added bonus, the CU75 and CU80 packages have
> cuDNN v6
> bundled!
>
> https://pypi.python.org/pypi/mxnet
>
>
>

Re: Need for MXNet API documentation Standards/Guidelines

[Henri Yandell]

Sounds like good stuff.

We could get a wiki setup at Apache and document it there.

Something that mxnet.io doesn't currently do is talk about the project
development; it's focused on the product. If you look at most Apache
websites, they are a mix of product and project development (which
personally I think is confusing, so I'd suggest we still keep the two
distinct). Having a subsite called contributing/developers would be useful,
and a documentation section could be in there.

Your 1-4 sound good to me. Do you have an example/template?

Hen


On Wed, May 3, 2017 at 10:51 AM, Naveen Swamy  wrote:

> Currently a group of us within Amazon are documenting and improving the
> MXNet APIs to make it easier for users to build products/models.
>
> From my experience of this exercise, I see that as MXNet grows with more
> contributors joining in and develop new APIs, It is essential that we
> enforce and set guidelines that APIs come with some amount of documentation
> which will help the user to build models/products quickly instead of having
> to experiment with the APIs to understand their behavior.
>
> Since we have contributors around the world whose native language is not
> English, we do not have to go to the extent of getting the perfectly
> correct documentation(we can fix grammar and alike as a part of the PR
> ourselves before merging or educate the contributors), we have to be
> careful not to discourage the contributors just to have perfect
> documentation.
>
> Also I think documenting the APIs cannot be an after-thought or a one-time
> exercise.
>
> I think we need the following at a minimum documentation when an API is
> developed.
>
> 1. Follow documentation standard.
> 2. A clear description of what the API is.
> 3. A clear description of the parameters.
> 4. Examples in(Python?) to show the usage and clarify the parameters/API.
>
> open to comments/suggestions ?
>
> Thanks, Naveen
>

Re: infra migration

[Henri Yandell]

On Mon, May 1, 2017 at 4:13 PM, Dominic Divakaruni <
dominic.divakar...@gmail.com> wrote:

> (trying this from my personal email, since the previous one didnt go out)
>
> Nudging this to the top of your inbox. Relocating infrastructure to its
> Apache home is one of the first steps in the incubator and is long overdue.
> Contributors and mentors please voice your opinion and move this migration
> forward.  I am restating the relocation work list below with two additional
> items that have been suggested. Please add more that may be missing..
>
>
>
> 1.   Code relocation from GitHub to Apache.
>
> a.   What are the steps involved to enable the transfer? Any associated
> timelines that the community needs to be aware of? – *Apache Mentors *we
> need your input
>

At this point it's as soon as possible.

The steps are very simple - give an ASF Infra person temporary Owner
permissions on DMLC and they can move the code in minutes.

I know that both you and I will be at Apache in a week and a bit. I suggest
we meet with ASF Infra to talk through what might go wrong and then get it
done the week after ApacheCon (or possibly while we're at ApacheCon, though
I seem to recall that there are other machine learning conferences at that
time?).


> b.   MXNet has cross-dependencies on several DMLC foundational
> sub-modules like core and ps-lite. How does a migration impact such cross
> links to non-apache projects? Should we merge all the MXNet dependent
> modules into a single repository or keep them as separate source
> repositories at Apache? How do projects handle code dependencies/ links
> with other non-apache projects? –*Apache Mentors *we need your input
>
>
Excellent question. Typically I see the dependencies done via things like
Maven, RubyGems, PyPI etc.

I'm not aware of Incubator projects having more than one Git repo, but I
don't see that it's not something we can ask for. Another good to discuss
item with Infra.


> c.   What are the project’s build server requirements?*Committers *can
> you please comment?* Apache Mentors, *can one off infrastructure needs be
> addressed?
>
>
Weird build requirements have been handled in the past by
contributors/their employers. We'll have to gauge Infra's thoughts on this
once we know what CIs we have running.


> d.   *Contributors*, please raise any additional questions or concerns
> you may have.
>
> 2.   Moving from mxnet.io to mxnet.apache.org
>
> a.   AWS may be willing to sponsor the development of a new website
> with Apache branding and guidelines with collective requirements of the
> community!*Contributors/Mentors* what do you think? Are there any other
> potential sponsors for a new website?
>
>
I read this as AWS being prepared to bring in a designer if that'll help
(from chatting with you, it'd be a contract rather than in-house); so it's
a weird contribution where AWS will pay someone to contribute. Sally
Khudairi has done similar for the Apache Foundation website, so I suggest
we talk with her about how best to do such things.

Note that Apache Infra will need to run the website, so the implementation
options are tied to what Infra support (HTML or the Apache CMS iiuc).


> b.  What happens to search links and bookmarks when the website moves
> to an Apache URL? *Mentors*, do you have some guidance on this?
>
>
My expectation is that the mxnet.io domain name would be transferred to
Apache, and Infra would host that as an alias for incubator.apache.org/mxnet,
and change it to mxnet.apache.org when graduated.


> 3.   Moving project communication away the current Slack team
> (apache-mxnet) to the official Apache Slack team per Henri’s
> recommendation.
>
> a.   There are some active discussions on slack. One of them has to do
> with the docs improvement effort. Suggestion: should the move occur at the
> conclusion of the current docs project? Maybe doing this along with the
> code base relocation makes sense? *Contributors, Mentors,*thoughts?
>
>
>
IIUC that's fairly soon, so that makes sense.

I'm an idiot about Slack though, barely used it.

Hen

Re: Podling Report Reminder - May 2017

[Henri Yandell]

Thoughts for a board report:

* ApacheCon - anyone going to be there? I'm planning to be there, and I
know from conversation that Dominic is too.
* Code migration - we should be planning next steps. I suspect ApacheCon
can be used to discuss out items f2f with Infra. Doing a final
old-community release on old GitHub might make sense.
* Slack channel is good, but we should move it to the Apache org that was
setup last month.
* Still a dearth of folk on private@.


On Wed, Apr 26, 2017 at 5:41 PM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 17 May 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, May 03).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/May2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: communication

[Henri Yandell]

Digging around - looks like https://the-asf.slack.com/ has been setup as an
organization on Slack, so would be good to move our new Slack channels over
to that.

Hen

On Thu, Apr 20, 2017 at 1:40 PM, Divakaruni, Dominic 
wrote:

> Hi all,
> Our friend @muli was nice enough to setup a Slack team for us and many of
> us at work have jumped on. Apache-mxnet.slack.com is our team name on
> Slack and we hope to use it for real-time messaging on projects. It should
> be an open channel but please shoot me a note if you’d like access and
> can’t get in for some reason.
>
> I’ve started a #docs channel to discuss updates we are making to the API
> docstrings and mxnet.io tutorials etc., as they could use an upgrade ☺.
>
> While the Slack channels are useful, I recommend we also use the
> dev@mxnet.incubator.apache.org
> email list for anything you believe needs to be messaged out to the group
> (so as to include folks that are not keeping a close eye on Slack), any key
> decisions that need to be made, or simply to keep folks that are across the
> globe in various time zones in the loop.
>
> Please chime in if you have other suggestions.
>
> Best,
> Dom
>
>

Slack vs email

[Henri Yandell]

I thought this article was a nice summary on keeping Slack discussions to
the low priority items:
https://dave.cheney.net/2017/04/11/why-slack-is-inappropriate-for-open-source-communications

Re: Podling Report Reminder - April 2017

[Henri Yandell]

On Mon, Apr 10, 2017 at 11:08 PM, Divakaruni, Dominic 
wrote:

> Hello MXNet members,
>
> Here is a draft report proposal for the April report. Please do weigh in
> with any comments, clarifications and additional context that you may want
> to add:
>
>
>
> 
>
> MXNet
>
>
>
> A Flexible and Efficient Library for Deep Learning
>
>
>
> MXNet has been incubating since 2017-01-23.
>
>
>
> Three most important issues to address in the move towards graduation:
>
>
>
>   1. Move the code and website to Apache Infrastructure.
>
>   2. Establish a formal release process and schedule, allowing for
> dependable release cycles in line with Apache development process.
>
>   3.
>

Get the PMC members to subscribe to the private mailing list, and grow the
contributor/committer community.


>
>
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>
>
> Contributors of the project are kicking off a focused effort towards
> completing the initial setup, including code and website migration to
> Apache infrastructure and moving past that quickly towards the first
> release. The project’s contributors look to the ASF for best practices
> related to moving the infrastructure of a large active project while
> maintaining user experience.
>
>
>
> How has the community developed since the last report?
>
>
>
> While the infrastructure of the project is still under DMLC, the
> contributors are making headway on documentation quality and bug fixes
> towards a stability release. Target for this release is May 15. The
> committers will look to make this the first release under ASF guidelines.
>
>
Where was the May 15th decision made? List has been quiet :)

Is this a Slack thing? (acknowledging that I don't have access/accounts on
Slack).


>
>
> How has the project developed since the last report?
>
>   Development is active under the original project (DMLC/MXNet).
>
>
>
> How would you assess the podling's maturity?
>
>
>
>   [X] Initial setup
>
>   [ ] Working towards first release
>
>   [ ] Community building
>
>   [ ] Nearing graduation
>
>   [ ] Other:
>
>
>
> Date of last release:
>
>
>
> No Apache Release yet
>
>
>
> When were the last committers or PPMC members elected?
>
>
>
>   Project is being set up with the initial set of committers.
>
>
>
> Thanks!
>
> Dom
>
>
>
Thanks for putting together the report :)

Re: Podling Report Reminder - April 2017

[Henri Yandell]

On Mon, Apr 10, 2017 at 9:55 PM, Divakaruni, Dominic 
wrote:

> Hi All,
> It appears there are some issues/concerns regarding moving MXNet’s code
> from DMLC to Apache. A big one is user experience since this is an active
> framework.
>

I've not heard of any concerns (but not heard much of anything on list).


>
> Looking at the JIRA issue https://issues.apache.org/
> jira/browse/INFRA-13800 I couldn’t identify a clear list of issues or
> path to resolution. Can someone please help us with some guidance on next
> steps?
>
>
The next step is giving Daniel (pono@) temporary Owner rights on
github.com/dmlc so he can initiate the transfer.

The primary items I've been able to think of as worries are:

* Making sure to get the new repo name right the first time. I believe,
from looking at others, it should be "github.com/apache/incubator-mxnet".
* MXNet doesn't use the GitHub wiki, so no issue to worry about there.
* IMO; When we do the first Apache release, we should release both at
Apache and then put a copy in the GitHub releases so users used to looking
on GitHub aren't wondering why the code has gotten stale, nor are they
wondering why we deleted every release.
* I worry a little that the process for pull-request/issue management is
going to be convoluted.


> Will it help if we had a conference call with the committers and mentors
> to discuss?
>

Given that those involved are doing so in a mixture of their personal and
work time, and from multiple timezones, conference calls are typically the
last resort. Too much use of conference calls can create a project that is
tied to a single timezone, and it robs the project of the diversity of
individuals who can't call during work hours, or can't do a phone
conversation in their personal time (it's hard to do a phone call with a
crying baby for example).

Good to have started on the list, let's keep going here if we can :)

Thanks,

Hen

Re: Podling Report Reminder - April 2017

[Henri Yandell]

I doubt we'll get it in btw - I think this month it'll flag as "Did not
report", however if we can put together a late report I can at least
include that in the board notes as a comment.

On Sun, Apr 9, 2017 at 7:23 PM, Henri Yandell  wrote:

> Can't hurt :)
>
> On Sun, Apr 9, 2017 at 19:23 Divakaruni, Dominic 
> wrote:
>
>> My apologies, I didn’t catch the 4/5 date. I was shooting for 4/19. Is
>> there still time to send this in tomorrow?
>>
>>
>>
>> On 4/3/17, 8:13 PM, "Henri Yandell"  wrote:
>>
>> Thank you Dom, that would be very much appreciated :)
>>
>> https://wiki.apache.org/incubator/April2017 shows the template
>> (search for
>> MXNet).
>>
>> If you look at the last couple of Incubator reports,
>> https://wiki.apache.org/incubator/February2017 +
>> https://wiki.apache.org/incubator/March2017 - you can find the 2
>> previous
>> reports.
>>
>> If you'd like to propose something to the mailing list, that would be
>> great. One of the mentors can add to the wiki once we have some text.
>>
>> Thanks - personal-life items have been filling my weekend/week so this
>> wasn't flagging for me,
>>
>> Hen
>>
>> On Sat, Apr 1, 2017 at 11:51 PM, Divakaruni, Dominic <
>> ddiva...@amazon.com>
>> wrote:
>>
>> > Hello,
>> > Is anyone taking this?
>> >
>> > If not sent me a template for one that's been done in the past and
>> I can
>> > help.
>> >
>> > Regards,
>> > Dom
>> >
>> >
>> > > On Apr 1, 2017, at 6:42 PM, "johndam...@apache.org" <
>> > johndam...@apache.org> wrote:
>> > >
>> > > Dear podling,
>> > >
>> > > This email was sent by an automated system on behalf of the Apache
>> > > Incubator PMC. It is an initial reminder to give you plenty of
>> time to
>> > > prepare your quarterly board report.
>> > >
>> > > The board meeting is scheduled for Wed, 19 April 2017, 10:30 am
>> PDT.
>> > > The report for your podling will form a part of the Incubator PMC
>> > > report. The Incubator PMC requires your report to be submitted 2
>> weeks
>> > > before the board meeting, to allow sufficient time for review and
>> > > submission (Wed, April 05).
>> > >
>> > > Please submit your report with sufficient time to allow the
>> Incubator
>> > > PMC, and subsequently board members to review and digest. Again,
>> the
>> > > very latest you should submit your report is 2 weeks prior to the
>> board
>> > > meeting.
>> > >
>> > > Thanks,
>> > >
>> > > The Apache Incubator PMC
>> > >
>> > > Submitting your Report
>> > >
>> > > --
>> > >
>> > > Your report should contain the following:
>> > >
>> > > *   Your project name
>> > > *   A brief description of your project, which assumes no
>> knowledge of
>> > >the project or necessarily of its field
>> > > *   A list of the three most important issues to address in the
>> move
>> > >towards graduation.
>> > > *   Any issues that the Incubator PMC or ASF Board might
>> wish/need to be
>> > >aware of
>> > > *   How has the community developed since the last report
>> > > *   How has the project developed since the last report.
>> > > *   How does the podling rate their own maturity.
>> > >
>> > > This should be appended to the Incubator Wiki page at:
>> > >
>> > > https://wiki.apache.org/incubator/April2017
>> > >
>> > > Note: This is manually populated. You may need to wait a little
>> before
>> > > this page is created from a template.
>> > >
>> > > Mentors
>> > > ---
>> > >
>> > > Mentors should review reports for their project(s) and sign them
>> off on
>> > > the Incubator wiki page. Signing off reports shows that you are
>> > > following the project - projects that are not signed may raise
>> alarms
>> > > for the Incubator PMC.
>> > >
>> > > Incubator PMC
>> >
>>
>>
>>

Re: Podling Report Reminder - April 2017

[Henri Yandell]

Some bits to include:

JIRA issue for transferring the source code:   https://issues.apache.org/
jira/browse/INFRA-13800

This is our biggest blocker to community growth at Apache; the code isn't
at Apache so we haven't really gotten started.

I'm not sure where to list it report-wise, but we also need to vote on
whether to make-committer the interested volunteers who indicated their
interest during the public Incubator vote.

I only see about a third of the committers on the private@ list, so only a
third will get to vote on who gets added etc.

Hen


On Sun, Apr 9, 2017 at 7:23 PM, Henri Yandell  wrote:

> Can't hurt :)
>
> On Sun, Apr 9, 2017 at 19:23 Divakaruni, Dominic 
> wrote:
>
>> My apologies, I didn’t catch the 4/5 date. I was shooting for 4/19. Is
>> there still time to send this in tomorrow?
>>
>>
>>
>> On 4/3/17, 8:13 PM, "Henri Yandell"  wrote:
>>
>> Thank you Dom, that would be very much appreciated :)
>>
>> https://wiki.apache.org/incubator/April2017 shows the template
>> (search for
>> MXNet).
>>
>> If you look at the last couple of Incubator reports,
>> https://wiki.apache.org/incubator/February2017 +
>> https://wiki.apache.org/incubator/March2017 - you can find the 2
>> previous
>> reports.
>>
>> If you'd like to propose something to the mailing list, that would be
>> great. One of the mentors can add to the wiki once we have some text.
>>
>> Thanks - personal-life items have been filling my weekend/week so this
>> wasn't flagging for me,
>>
>> Hen
>>
>> On Sat, Apr 1, 2017 at 11:51 PM, Divakaruni, Dominic <
>> ddiva...@amazon.com>
>> wrote:
>>
>> > Hello,
>> > Is anyone taking this?
>> >
>> > If not sent me a template for one that's been done in the past and
>> I can
>> > help.
>> >
>> > Regards,
>> > Dom
>> >
>> >
>> > > On Apr 1, 2017, at 6:42 PM, "johndam...@apache.org" <
>> > johndam...@apache.org> wrote:
>> > >
>> > > Dear podling,
>> > >
>> > > This email was sent by an automated system on behalf of the Apache
>> > > Incubator PMC. It is an initial reminder to give you plenty of
>> time to
>> > > prepare your quarterly board report.
>> > >
>> > > The board meeting is scheduled for Wed, 19 April 2017, 10:30 am
>> PDT.
>> > > The report for your podling will form a part of the Incubator PMC
>> > > report. The Incubator PMC requires your report to be submitted 2
>> weeks
>> > > before the board meeting, to allow sufficient time for review and
>> > > submission (Wed, April 05).
>> > >
>> > > Please submit your report with sufficient time to allow the
>> Incubator
>> > > PMC, and subsequently board members to review and digest. Again,
>> the
>> > > very latest you should submit your report is 2 weeks prior to the
>> board
>> > > meeting.
>> > >
>> > > Thanks,
>> > >
>> > > The Apache Incubator PMC
>> > >
>> > > Submitting your Report
>> > >
>> > > --
>> > >
>> > > Your report should contain the following:
>> > >
>> > > *   Your project name
>> > > *   A brief description of your project, which assumes no
>> knowledge of
>> > >the project or necessarily of its field
>> > > *   A list of the three most important issues to address in the
>> move
>> > >towards graduation.
>> > > *   Any issues that the Incubator PMC or ASF Board might
>> wish/need to be
>> > >aware of
>> > > *   How has the community developed since the last report
>> > > *   How has the project developed since the last report.
>> > > *   How does the podling rate their own maturity.
>> > >
>> > > This should be appended to the Incubator Wiki page at:
>> > >
>> > > https://wiki.apache.org/incubator/April2017
>> > >
>> > > Note: This is manually populated. You may need to wait a little
>> before
>> > > this page is created from a template.
>> > >
>> > > Mentors
>> > > ---
>> > >
>> > > Mentors should review reports for their project(s) and sign them
>> off on
>> > > the Incubator wiki page. Signing off reports shows that you are
>> > > following the project - projects that are not signed may raise
>> alarms
>> > > for the Incubator PMC.
>> > >
>> > > Incubator PMC
>> >
>>
>>
>>

Re: Podling Report Reminder - April 2017

[Henri Yandell]

Can't hurt :)

On Sun, Apr 9, 2017 at 19:23 Divakaruni, Dominic 
wrote:

> My apologies, I didn’t catch the 4/5 date. I was shooting for 4/19. Is
> there still time to send this in tomorrow?
>
>
>
> On 4/3/17, 8:13 PM, "Henri Yandell"  wrote:
>
> Thank you Dom, that would be very much appreciated :)
>
> https://wiki.apache.org/incubator/April2017 shows the template
> (search for
> MXNet).
>
> If you look at the last couple of Incubator reports,
> https://wiki.apache.org/incubator/February2017 +
> https://wiki.apache.org/incubator/March2017 - you can find the 2
> previous
> reports.
>
> If you'd like to propose something to the mailing list, that would be
> great. One of the mentors can add to the wiki once we have some text.
>
> Thanks - personal-life items have been filling my weekend/week so this
> wasn't flagging for me,
>
> Hen
>
> On Sat, Apr 1, 2017 at 11:51 PM, Divakaruni, Dominic <
> ddiva...@amazon.com>
> wrote:
>
> > Hello,
> > Is anyone taking this?
> >
> > If not sent me a template for one that's been done in the past and I
> can
> > help.
> >
> > Regards,
> > Dom
> >
> >
> > > On Apr 1, 2017, at 6:42 PM, "johndam...@apache.org" <
> > johndam...@apache.org> wrote:
> > >
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of
> time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 19 April 2017, 10:30 am
> PDT.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, April 05).
> > >
> > > Please submit your report with sufficient time to allow the
> Incubator
> > > PMC, and subsequently board members to review and digest. Again,
> the
> > > very latest you should submit your report is 2 weeks prior to the
> board
> > > meeting.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > --
> > >
> > > Your report should contain the following:
> > >
> > > *   Your project name
> > > *   A brief description of your project, which assumes no
> knowledge of
> > >the project or necessarily of its field
> > > *   A list of the three most important issues to address in the
> move
> > >towards graduation.
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need
> to be
> > >aware of
> > > *   How has the community developed since the last report
> > > *   How has the project developed since the last report.
> > > *   How does the podling rate their own maturity.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > https://wiki.apache.org/incubator/April2017
> > >
> > > Note: This is manually populated. You may need to wait a little
> before
> > > this page is created from a template.
> > >
> > > Mentors
> > > ---
> > >
> > > Mentors should review reports for their project(s) and sign them
> off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise
> alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> >
>
>
>

ApacheCon US 2017 Miami

[Henri Yandell]

Highly recommended that folk attend ApacheCon in May (if feasible).

May 16-18 in Miami: http://apachecon.com/

A great time to connect with the greater Apache community, to understand
better what it means to be an Apache project and to get others at Apache
aware of what MXNet is. It's also a good time for committers to meet face
to face.

Until April 16th, there is a great rate for both committers and students of
$275 (compared to the standard rate for attendees of $800).

Hope to see many of you there,

Hen

Re: Podling Report Reminder - April 2017

[Henri Yandell]

Thank you Dom, that would be very much appreciated :)

https://wiki.apache.org/incubator/April2017 shows the template (search for
MXNet).

If you look at the last couple of Incubator reports,
https://wiki.apache.org/incubator/February2017 +
https://wiki.apache.org/incubator/March2017 - you can find the 2 previous
reports.

If you'd like to propose something to the mailing list, that would be
great. One of the mentors can add to the wiki once we have some text.

Thanks - personal-life items have been filling my weekend/week so this
wasn't flagging for me,

Hen

On Sat, Apr 1, 2017 at 11:51 PM, Divakaruni, Dominic 
wrote:

> Hello,
> Is anyone taking this?
>
> If not sent me a template for one that's been done in the past and I can
> help.
>
> Regards,
> Dom
>
>
> > On Apr 1, 2017, at 6:42 PM, "johndam...@apache.org" <
> johndam...@apache.org> wrote:
> >
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 19 April 2017, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, April 05).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> >the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> >towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> >aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/April2017
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
>

Re: [Vote] New MXNet Logo

[Henri Yandell]

Nudge to close the vote.

https://www.apache.org/foundation/voting.html describes Apache votes.
Typically at this point the vote caller would:

a) Create a "[RESULT] New MXNet Logo" thread as a reply to the original
vote email.
b) Summarise the votes (+1, ±0 and -1);
c) Break them down by binding (PPMC) and non-binding votes. Currently all
committers to the project are considered PPMC members so
http://incubator.apache.org/projects/mxnet.html can be used for the list.
d) Review the -1s, if any. Treat differently based on code vote (veto) or
procedural vote (majority).
e) Call the vote a pass or fail.

Tbh - I don't know how the process junkies would view a logo vote :)
Whenever I'm reviewing a vote thread's -1s, I consider the reasons given.
If a -1 is given without a reason in a thread, I would ask the voter to
provide one.

In this case our one -1 is a preference rather than a problem. As no one
else joined in on the preference, and as the +1s were preferences in the
opposite direction, I would consider this vote passed.

End of the day - Apache projects are more about consensus than Robert's
Rules of Order (parliamentary procedure document for running meetings :) ).
The vote caller is using their skill to measure the community, and if in
doubt you can always ask the community for their thoughts.

Hen


On Sun, Mar 5, 2017 at 8:21 PM, sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:

> +1; Yep, love it!
>
>
> On Sun, Mar 5, 2017 at 12:36 PM, Sebastian  wrote:
>
> >
> >
> > On 05.03.2017 16:23, Spisak, Joseph wrote:
> >
> >> Talking to me? Name is Joe.. :). Let's run for 3days and then close.
> >>
> >
> > Oops, yes Joe not John, sorry for that :)
> >
> > Sent from Joe's iPhone
> >>
> >> On Mar 5, 2017, at 12:11 AM, Sebastian  wrote:
> >>>
> >>> Dear John,
> >>>
> >>> I would kindly ask you to specify how long this vote will be running,
> to
> >>> adhere with best practices at Apache.
> >>>
> >>> Best,
> >>> Sebastian
> >>>
> >>> On 05.03.2017 06:07, Joseph Spisak wrote:
> 
>  Let's vote on a new MXNet logo.  Thoughts on this one?
> 
>  [ ] +1; Yep, love it!
> 
>  [ ] -1; Hate it, because 
> 
> 
> 
> >>>
>
>
> --
> Sandeep Krishnamurthy
>

Re: Ready to move the source code over to Apache?

[Henri Yandell]

Thanks Chiyuan.

I've sent an email connecting one of the Apache Infra members with them,
asking them to coordinate the GitHub repository move.

Hen

On Tue, Feb 21, 2017 at 10:21 AM, Chiyuan Zhang  wrote:

> I believe at least Mu, Tianqi and Eric all have owner permission on the
> dmlc org on github.
>
>
> On Tue, Feb 21, 2017 at 2:43 AM, Henri Yandell  wrote:
>
> > Apologies for slowness on my part (busy home/work time of year).
> >
> > We have 23 committers with ICLAs/accounts.
> >
> > Currently we only have 4 people on the PPMC (per
> > https://whimsy.apache.org/roster/ppmc/mxnet). 14 are subscribed to the
> > private list, so that suggests there is something else that needs
> changing.
> > Will get that fixed (I've mailed general@incubator asking for assistance
> > in
> > how to fix).
> >
> > The next step is to move the source code to Apache. The change involves
> > giving an Apache Infra member Owner permissions on github.com/dmlc, they
> > will then do the transfer to github.com/apache, and then a name change
> of
> > mxnet to apache-mxnet. Everything else should 'just work'. We'll then
> need
> > to do some cleanup on licensing.
> >
> > The main change I then see happening is that releases need to follow the
> > Apache  rules. Releasing the Apache way is one of the primary items for a
> > community to learn about while in Incubation. This document talks more
> > about it: http://incubator.apache.org/guides/releasemanagement.html
> >
> > I would high-level summarize it as:
> >
> > 1) Must make a decision to release on the lists (i.e. a vote); and
> > subsequently have the Incubator PMC approve on general@incubator
> (another
> > vote).
> > 2) Must be in source form, and obey Apache policies (for example third
> > party library licensing).
> > 3) Additional Incubator items around flagging to users that mxnet is in
> the
> > Incubator.
> >
> > The biggest blocker, I believe, will be the zeromq licensing. There is
> > acceptance to do releases with issues while in the Incubator, so that's
> > something to raise on general@incubator.
> >
> > Who on the DMLC side should I put in contact with Apache Infrastructure
> to
> > plan the source migration (i.e. who has Owner permissions on DMLC and can
> > work with them)?
> >
> > Hen
> >
>

Re: Draft of March 2016 Podling Report

[Henri Yandell]

Thanks Suneel :) Couple of bits inline.

On Wed, Mar 1, 2017 at 2:57 PM, Suneel Marthi  wrote:

> Here's an initial draft of podling report for March 2016, please feel free
> to add/edit as you deem fit.
>
> --
>
> MXNet
>
> A Flexible and Efficient Library for Deep Learning
>
> MXNet has been incubating since 2017-01-23.
>
> Three most important issues to address in the move towards graduation:
>
>   1.Establish a formal release process and schedule, allowing for
> dependable release cycles in line with Apache development process.
>
>   2. Move the code and website to Apache Infra.
>
>   3.


Perhaps:

PPMC to discuss adding in some community members who asked to join
while the Incubator vote was ongoing (learning how to vote new committers
in).  ?


> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   Project is still being established in Incubator
>
> How has the project developed since the last report?
>
>   This would be the first podling report
>

Second report :)


>
> How would you assess the podling's maturity?
>
> Please feel free to add your own commentary.
>
>   [X] Initial setup
>
>   [ ] Working towards first release
>
>   [ ] Community building
>
>   [ ] Nearing graduation
>
>   [ ] Other:
>
> Date of last release:
>
>   No release yet
>
> When were the last committers or PPMC members elected?
>
> Project is being established with initial set of committers.
>
> Signed-off-by:
>
>   [ ](mxnet) Sebastian Schelter
>
>  Comments:
>
>   [ ](mxnet) Suneel Marthi
>
>  Comments:
>
>   [ ](mxnet) Markus Weimer
>
>  Comments:
>
>   [ ](mxnet) Henri Yandell
>
>  Comments:
>

Re: ZeroMQ dependency

[Henri Yandell]

It's sounding like nanomsg is the direction to go. Any other thoughts?

On Tue, Feb 21, 2017 at 2:06 PM, Minjie Wang  wrote:

> My colleagues and I are working on adding more support for data
> transmission. For example, send/recv operators in dataflow graph to support
> some fancier parallelism. I feel like this could be part of mxnet in the
> future (need more discussions for sure). Currently, we are using zeromq
> since we already depend on it. Does that mean we should actually consider
> using other libraries?
>
> For 3), it should not be hard since we are only transmitting arrays. We
> don't need to support rich types and complex data structures like normal
> RPC.
>
> - Minjie
>
> On Tue, Feb 21, 2017 at 11:53 AM, Will, Martin 
> wrote:
>
> > Re 3.) Nanomsg is licensed under BSD. [http://nanomsg.org/]. It’s
> written
> > by one of the original authors of zeromq, and can be considered as an
> > evolution it. The API mostly maps 1-to-1.
> >
> > - Martin
> >
> >
> > On 2/20/17, 11:54 PM, "Henri Yandell"  wrote:
> >
> > How tied is MXNet to ZeroMQ?
> >
> > My notes are that ps-lite depends on it.
> >
> > Options I can see here are:
> >
> > 1) Discuss on general@incubator and determine if the exception is
> > acceptable. I suspect this is unlikely given that Apache Toree had a
> > problem with jeromq which led to jeromq very kindly relicensing to
> MPL
> > (
> > https://github.com/zeromq/jeromq/issues/326).
> > 2) Request libzmq relicense to MPL. This is something the project has
> > begun, but seems to be in frozen currently (unless I'm missing recent
> > activity).
> > 3) Rewrite MXNet to not rely on zeromq. How difficult would that be?
> > 4) Switching MXNet to use something other than ps-lite? (Not sure if
> > that's
> > easier than #3).
> >
> > Any thoughts on #3 + #4?
> >
> > Thanks,
> >
> > Hen
> >
> >
> >
>
>
> --
> Minjie Wang
> *New York University | Computer Science*
> 715 Broadway, New York, NY, 10009
>

Re: New Logo?

[Henri Yandell]

I almost said "Happy to review a draft if anyone wants as sometimes votes
can kick off prematurely".

The thingy vote text was an example :)

Hen

On Mon, Feb 20, 2017 at 11:57 PM, Henri Yandell  wrote:

> We should do a vote on this, now that we have everyone here.
>
> Voting is described here:  http://apache.org/foundation/voting.html
>
> (though basically it comes down to an email saying:
>
> 
> Let's vote on a thingy
> [ ] +1; Yay, thingy
> [ ] -1; Hate it, because 
>
> Making sure that enough time elapses (minimum 3 days), and that the project
> has voted (minimum 3 PMC members); and then getting the Incubator PMC to
> sign off as we operate as a child of theirs.
> 
>
> If anyone wants to include details and propose a vote, that would be
> brilliant :) I'm happy to review an email if anyone is unsure and wants to
> send a draft my way.
>
> Hen
>
>
> On Thu, Jan 26, 2017 at 2:55 PM, Spisak, Joseph 
> wrote:
>
> > Thanks Henri, we’ve done some votes in the past on GitHub but haven’t
> > really concluded. It would be great if the community came up with some
> > proposals that we could vote on.  The past vote can be found here:
> > https://github.com/dmlc/mxnet/issues/4392
> >
> >
> >
> >
> >
> > Cheers,
> >
> > -Joe
> >
> >
> >
> >
> >
> > *From: *Henri Yandell 
> > *Date: *Thursday, January 26, 2017 at 2:47 PM
> > *To: *"dev@mxnet.incubator.apache.org" 
> > *Cc: *"Spisak, Joseph" 
> > *Subject: *New Logo?
> >
> >
> >
> > Joe - from a private conversation I believe you wanted to propose/offer a
> > new logo for the project?
> >
> > Aka *nudge* to bring the topic up here as a first item of business :)
> >
> > Hen
> >
>

Re: New Logo?

[Henri Yandell]

We should do a vote on this, now that we have everyone here.

Voting is described here:  http://apache.org/foundation/voting.html

(though basically it comes down to an email saying:


Let's vote on a thingy
[ ] +1; Yay, thingy
[ ] -1; Hate it, because 

Making sure that enough time elapses (minimum 3 days), and that the project
has voted (minimum 3 PMC members); and then getting the Incubator PMC to
sign off as we operate as a child of theirs.


If anyone wants to include details and propose a vote, that would be
brilliant :) I'm happy to review an email if anyone is unsure and wants to
send a draft my way.

Hen


On Thu, Jan 26, 2017 at 2:55 PM, Spisak, Joseph  wrote:

> Thanks Henri, we’ve done some votes in the past on GitHub but haven’t
> really concluded. It would be great if the community came up with some
> proposals that we could vote on.  The past vote can be found here:
> https://github.com/dmlc/mxnet/issues/4392
>
>
>
>
>
> Cheers,
>
> -Joe
>
>
>
>
>
> *From: *Henri Yandell 
> *Date: *Thursday, January 26, 2017 at 2:47 PM
> *To: *"dev@mxnet.incubator.apache.org" 
> *Cc: *"Spisak, Joseph" 
> *Subject: *New Logo?
>
>
>
> Joe - from a private conversation I believe you wanted to propose/offer a
> new logo for the project?
>
> Aka *nudge* to bring the topic up here as a first item of business :)
>
> Hen
>

ZeroMQ dependency

[Henri Yandell]

How tied is MXNet to ZeroMQ?

My notes are that ps-lite depends on it.

Options I can see here are:

1) Discuss on general@incubator and determine if the exception is
acceptable. I suspect this is unlikely given that Apache Toree had a
problem with jeromq which led to jeromq very kindly relicensing to MPL (
https://github.com/zeromq/jeromq/issues/326).
2) Request libzmq relicense to MPL. This is something the project has
begun, but seems to be in frozen currently (unless I'm missing recent
activity).
3) Rewrite MXNet to not rely on zeromq. How difficult would that be?
4) Switching MXNet to use something other than ps-lite? (Not sure if that's
easier than #3).

Any thoughts on #3 + #4?

Thanks,

Hen

Ready to move the source code over to Apache?

[Henri Yandell]

Apologies for slowness on my part (busy home/work time of year).

We have 23 committers with ICLAs/accounts.

Currently we only have 4 people on the PPMC (per
https://whimsy.apache.org/roster/ppmc/mxnet). 14 are subscribed to the
private list, so that suggests there is something else that needs changing.
Will get that fixed (I've mailed general@incubator asking for assistance in
how to fix).

The next step is to move the source code to Apache. The change involves
giving an Apache Infra member Owner permissions on github.com/dmlc, they
will then do the transfer to github.com/apache, and then a name change of
mxnet to apache-mxnet. Everything else should 'just work'. We'll then need
to do some cleanup on licensing.

The main change I then see happening is that releases need to follow the
Apache  rules. Releasing the Apache way is one of the primary items for a
community to learn about while in Incubation. This document talks more
about it: http://incubator.apache.org/guides/releasemanagement.html

I would high-level summarize it as:

1) Must make a decision to release on the lists (i.e. a vote); and
subsequently have the Incubator PMC approve on general@incubator (another
vote).
2) Must be in source form, and obey Apache policies (for example third
party library licensing).
3) Additional Incubator items around flagging to users that mxnet is in the
Incubator.

The biggest blocker, I believe, will be the zeromq licensing. There is
acceptance to do releases with issues while in the Incubator, so that's
something to raise on general@incubator.

Who on the DMLC side should I put in contact with Apache Infrastructure to
plan the source migration (i.e. who has Owner permissions on DMLC and can
work with them)?

Hen

Re: ICLA status

[Henri Yandell]

On Wed, Feb 8, 2017 at 9:08 PM, Henri Yandell  wrote:

>
> Updating:
>
> Junyuan has an account now. I found the page that lists who will have git
> access, it looks like someone (the Incubator PMC chair perhaps) is updating
> these in batches. The current unadded batch is:
>
> liuyizhi
> muli
> bingxu
> gengyifeng
> yzhang87
> ozawa
> jxie
>

All were added, except ozawa who already had an Apache account. I'll mail
general@incubator to ask he be added.


>
> The other item everyone who has an account (i.e. is an Apache MXNet
> committer) should be doing is subscribing to priv...@mxnet.apache.org (by
> mailing private-subscr...@mxnet.apache.org).
>

Reminder :)

Hen

Re: ICLA status

[Henri Yandell]

Fixed on the MXNetProposal :)

Updating:

Junyuan has an account now. I found the page that lists who will have git
access, it looks like someone (the Incubator PMC chair perhaps) is updating
these in batches. The current unadded batch is:

liuyizhi
muli
bingxu
gengyifeng
yzhang87
ozawa
jxie

Which maps to the most recent accounts. So I assume these will be added
soon.

The other item everyone who has an account (i.e. is an Apache MXNet
committer) should be doing is subscribing to priv...@mxnet.apache.org (by
mailing private-subscr...@mxnet.apache.org).

Hen


On Wed, Feb 8, 2017 at 7:18 AM, Minjie Wang  wrote:

> Hi Henri,
>
> Thank you for the reminder. I will do this ASAP. BTW, I'm from "NYU" not
> "UYU". Thanks.
>
> Best,
> Minjie
>
> On Wed, Feb 8, 2017 at 12:48 AM, Henri Yandell  wrote:
>
> > Updated again. Of the 31 committers listed, 22 have ICLAs signed/accounts
> > created and 9 still to sign.
> >
> > To sign:
> >
> > *Junyuan Xie (AWS)
> > *Minjie Wang (UYU)
> > *Naiyan Wang (Tusimple)
> > Indhu Bharathi (AWS)
> > Chris Olivier (AWS)
> > Liang Xiang (Toutiao Lab)
> > Tsuyoshi Ozawa (NTT)
> > Terry Chen (Novumind)
> > Jian Zhang (Horizon Robotics)
> >
> > Asterisks marks those who had write commit afaik to the current code.
> > Junyuan is the only one of those active at the moment, so I'm going to
> > follow up with him. Once he's got an account, we can move along to moving
> > the code over. The expectation there is that we're going to 1) check
> > everyone has incubator commit writes, then 2) give one of the ASF Infra
> > admins permissions on dmlc, then they will transfer the repository over
> to
> > Apache (with a rename). A redirect will be put in place, issues, pull
> > requests, source, and history of all will remain; no expected data loss.
> >
> > Hen
> >
> >
> > On Thu, Feb 2, 2017 at 9:29 PM, Henri Yandell  wrote:
> >
> > > I updated http://incubator.apache.org/projects/mxnet.html with the
> > latest
> > > status.
> > >
> > > Of the 31 committers listed on the proposal, we have 15 with ICLAs
> > > signed/accounts created and 16 still to sign.
> > >
> > > As a reminder, those still to get accounts are:
> > >
> > > Mu Li
> > > Junyuan Xie
> > > Bing Xu
> > > Minjie Wang
> > > Naiyan Wang
> > > Yizhi Liu
> > > Tong He
> > > Indhu Bharathi
> > > Chris Olivier
> > > Yu Zhang
> > > Shiwen Hu
> > > Liang Xiang
> > > Tsuyoshi Ozawa
> > > Terry Chen
> > > Yifeng Geng
> > > Jian Zhang
> > >
> >
>
>
>
> --
> Minjie Wang
> *New York University | Computer Science*
> 715 Broadway, New York, NY, 10009
>

Re: ICLA status

[Henri Yandell]

Updated again. Of the 31 committers listed, 22 have ICLAs signed/accounts
created and 9 still to sign.

To sign:

*Junyuan Xie (AWS)
*Minjie Wang (UYU)
*Naiyan Wang (Tusimple)
Indhu Bharathi (AWS)
Chris Olivier (AWS)
Liang Xiang (Toutiao Lab)
Tsuyoshi Ozawa (NTT)
Terry Chen (Novumind)
Jian Zhang (Horizon Robotics)

Asterisks marks those who had write commit afaik to the current code.
Junyuan is the only one of those active at the moment, so I'm going to
follow up with him. Once he's got an account, we can move along to moving
the code over. The expectation there is that we're going to 1) check
everyone has incubator commit writes, then 2) give one of the ASF Infra
admins permissions on dmlc, then they will transfer the repository over to
Apache (with a rename). A redirect will be put in place, issues, pull
requests, source, and history of all will remain; no expected data loss.

Hen


On Thu, Feb 2, 2017 at 9:29 PM, Henri Yandell  wrote:

> I updated http://incubator.apache.org/projects/mxnet.html with the latest
> status.
>
> Of the 31 committers listed on the proposal, we have 15 with ICLAs
> signed/accounts created and 16 still to sign.
>
> As a reminder, those still to get accounts are:
>
> Mu Li
> Junyuan Xie
> Bing Xu
> Minjie Wang
> Naiyan Wang
> Yizhi Liu
> Tong He
> Indhu Bharathi
> Chris Olivier
> Yu Zhang
> Shiwen Hu
> Liang Xiang
> Tsuyoshi Ozawa
> Terry Chen
> Yifeng Geng
> Jian Zhang
>

Podling Name Search

[Henri Yandell]

While we're waiting to get the majority of the committers setup with
accounts (which is blocking moving the code over to github.com/apache), one
of the items on the path to graduation is 'a suitable name search' (see:
http://incubator.apache.org/guides/index.html).

I kicked that off a bit earlier than usual and there were no objections
raised with the MXNet name. So we can already cross that off the todo list
:)

Hen

ICLA status

[Henri Yandell]

I updated http://incubator.apache.org/projects/mxnet.html with the latest
status.

Of the 31 committers listed on the proposal, we have 15 with ICLAs
signed/accounts created and 16 still to sign.

As a reminder, those still to get accounts are:

Mu Li
Junyuan Xie
Bing Xu
Minjie Wang
Naiyan Wang
Yizhi Liu
Tong He
Indhu Bharathi
Chris Olivier
Yu Zhang
Shiwen Hu
Liang Xiang
Tsuyoshi Ozawa
Terry Chen
Yifeng Geng
Jian Zhang

Re: Proposed Board report

[Henri Yandell]

Report posted at https://wiki.apache.org/incubator/February2017 and ready
for mentor sign offs.

On Wed, Feb 1, 2017 at 8:32 AM, Markus Weimer  wrote:

> On 2017-02-01 05:27, Chiyuan Zhang wrote:
>
>> One minor comment: "date of last release -- no release yet", does the
>> "release" here only include mature release, i.e. things that are beyond
>> version 1.0? Or it means something under the name Apache MXNet? Otherwise,
>> there seem to be quite a few past releases?
>>
>
> "release" here refers to releases made as a podling adhering to the Apache
> standards for a release (legal and technical). Hence, past releases are not
> reported here.
>
> That said, there is no reason to reset the version number or anything. I
> believe REEF was at 0.1x when we entered incubation and we just kept
> incrementing the version number.
>
> Markus
>

Blog posting

[Henri Yandell]

Writing the report reminded me that my dayjob worked with Sally (VP
Marketing & Publicity for Apache) on a blog posting:

  https://aws.amazon.com/blogs/aws/excited-about-mxnet-joining-apache/

Once we're up and running with private@, we would also see that list cc'd
on such things.

Need lots more ICLAs signed :)

Hen

Proposed Board report

[Henri Yandell]

Thoughts?

-

MXNet

MXNet is an open-source deep learning framework that allows you to define,
train, and deploy deep neural networks on a wide array of devices, from
cloud infrastructure to mobile devices. It is highly scalable, allowing
for fast model training, and supports a flexible programming model and
multiple languages.

MXNet has been incubating since 2017-01-23.

Three most important issues to address in the move towards graduation:

  1. Getting ICLAs signed/private@ populated.
  2. Sharing documentation/mentor thoughts on being an Apache committer.
  3. Migrating the code/issues over to Apache.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  1. This is our first report.
  2. The mailing lists are created; with the dev@ list being well populated.
  3. ICLAs are being signed.

How has the project developed since the last report?

  1. Trademark review seems complete.
  2. A vendor, AWS, worked with Sally on a blog posting[1].

Date of last release:

  No release yet.

When were the last committers or PPMC members elected?

  At Proposal time. We have a few folk who asked to join the incubation
  proposal after the vote started and will be discussed once private@
  is populated.

[1] - https://aws.amazon.com/blogs/aws/excited-about-mxnet-joining-apache/

Re: Welcome to the MXNet Dev list

[Henri Yandell]

I'm fine to draft a short report - sometimes best just to get started with
these things :)

Thanks for the reminder John - I'm used to the normal cadence of board
reporting for a TLP and hadn't realized how early a podling has to get a
report in.

Hen


On Mon, Jan 30, 2017 at 7:50 PM, Suneel Marthi  wrote:

> I would target the first report for March.
>
> On Mon, Jan 30, 2017 at 10:42 PM, John D. Ament 
> wrote:
>
> > All,
> >
> > I'm wondering, does MXNet plan to report this month? Or should we expect
> > the first report with March's timeline?
> >
> > John
> >
> > On 2017-01-26 17:46 (-0500), Henri Yandell  wrote:
> > > Hi MXNet Community :)
> > >
> > > There are 40-odd emails subscribed now, so looks like the list is ready
> > to
> > > be used in anger.
> > >
> > > Committer-wise, the main task is to get your ICLAs signed. Thus far
> I've
> > > only seen half a dozen or so signed, so more signing needed to be
> doing.
> > >
> > > As commiters get Apache accounts (or if they already have them), send
> an
> > > email to private-subscr...@mxnet.incubator.apache.org. But only after
> > you
> > > have those accounts please :)
> > >
> > > Hen
> > >
> >
>

Twitter accounts?

[Henri Yandell]

Do we have a process for Twitter accounts such that we can share a login
amongst a project's committers and don't end up losing the account if the
person who opened it becomes unavailable?

Looking to figure out how to manage the apachemxnet twitter account.

Thanks,

Hen

New Logo?

[Henri Yandell]

Joe - from a private conversation I believe you wanted to propose/offer a
new logo for the project?

Aka *nudge* to bring the topic up here as a first item of business :)

Hen

Welcome to the MXNet Dev list

[Henri Yandell]

Hi MXNet Community :)

There are 40-odd emails subscribed now, so looks like the list is ready to
be used in anger.

Committer-wise, the main task is to get your ICLAs signed. Thus far I've
only seen half a dozen or so signed, so more signing needed to be doing.

As commiters get Apache accounts (or if they already have them), send an
email to private-subscr...@mxnet.incubator.apache.org. But only after you
have those accounts please :)

Hen