RE: new website, docs code freeze

[Zhao, Patric]

For the install page [1], I suggest to add the selection of backend DeepNumpy 
[2] which will be more clean.

[1] http://mxnet.incubator.apache.org/index.html
[2] https://numpy.mxnet.io/#installation



> -Original Message-
> From: kellen sunderland 
> Sent: Monday, September 23, 2019 12:47 PM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: new website, docs code freeze
> 
> New site looks good.  I do notice that a few tutorials from the old site are
> missing (for example the TensorRT tutorial).  Any plans to bring them back?
> 
> On Sun, Sep 22, 2019 at 10:04 AM Haibin Lin 
> wrote:
> 
> > Another issue I found with the current website: the Sphinx object
> > inventory
> >  doc.org/en/master/usage/extensions/intersphinx.htm
> > l> file https://mxnet.apache.org/objects.inv is missing. GluonNLP
> > relies on this file to link document across projects. Shall we add it
> > back?
> >
> > Best,
> > Haibin
> >
> > On Sun, Sep 22, 2019 at 2:04 AM Lieven Govaerts  wrote:
> >
> > > Hi,
> > >
> > >
> > > On Sat, 21 Sep 2019 at 06:28, Thomas DELTEIL
> > > 
> > > wrote:
> > >
> > > > Thanks all for the feedback,
> > > >
> > > > We'll send an email next week with the list of missing features,
> > content
> > > > and bugs that we plan to fix.
> > > > We took the option of releasing early, with some features missing,
> > rather
> > > > than trying to be at feature parity with the old website before
> > launching
> > > > the website.
> > > > The reason why we decided to do that is two-fold:
> > > > - playing catch-up with docs in master introduce daily conflicts
> > > > that
> > > need
> > > > to be resolved and introduce opportunity for errors
> > > > - by releasing early, we can take advantage of the community
> > > contributions
> > > > in modifying whatever the community feels like a better way of
> > > > doing things.
> > > >
> > > > One of the goals of the new website was to disentangle the main
> > website,
> > > > now called "static_site" to the auto-generated docs. Now the
> > > > overall
> > site
> > > > is made of a main static site, with easy to modify content and
> > > > easy to understand architecture for anybody familiar with basic
> > > > html, and a collection of mini-websites for each language bindings
> > > > that can be
> > built
> > > in
> > > > isolation and that are self-contained. Actually the new CI jobs
> > > > builds
> > > all
> > > > of them in parallel independently.
> > > >
> > > > There is PLENTY of room for improvement, it would be great if the
> > > community
> > > > can help contribute to bring the new website at the same level of
> > content
> > > > richness as the old one, and then even further.
> > > >
> > > > Missing features:
> > > > - As pointed by Haibin, the API docs do not have the full list of
> > > operators
> > > > and classes. There is a mix of auto-generated docs based on
> > > > packages,
> > and
> > > > some docs that are spelled out manually to improve the logical
> > > organization
> > > > of the package where there is a need. The drawback with manually
> > > > listed classes in a package is that it's very easy to miss some.
> > > > If someone
> > > wanted
> > > > to build a sanity check that would automatically detect which
> > > > classes
> > are
> > > > not in the documentation, or if someone knew how to enable that
> > > > with sphinx, that would be a great addition to the python docs
> > > > - There is missing content in the python tutorials, and the
> > > discoverability
> > > > could be improved. Some old tutorials have not been migrated just yet.
> > > > - The nightly tests on tutorials have been disabled for now
> > > > - There is no "Download jupyter notebook" for tutorials just yet.
> > > > - Non-python tutorials might benefit from a blurb description and
> > > > a
> > > better
> > > > content organization.
> > > > - Python tutorials could be better organized, have a picture
> > accompanying
> > > > their description
> > > > - There is no site-wide search, this is not an easy problem to
> > > > solve to
> > > be
> > > > fair given the static nature of the website, but maybe an external
> > plugin
> > > > might be able to give a half-way solution
> > > > - There is no version selector for the docs
> > > > - There is bug in search box of the python docs, but this is just
> > > > a
> > small
> > > > JS bug that can be fixed easily (on my list for next week)
> > > > - Most old links have not had a redirect put in place.
> > > >
> > > >
> > > I noticed on the Ubuntu home page in the Developer dropdown that the
> > > link MXNet on Ubuntu
> > >  > > >with
> > > Nvidia
> > > <
> > >
> > https://www.nvidia.com/en-us/data-center/gpu-accelerated-applications/
> > mxnet/
> > > >
> > > doesn't work anymore, it points to:
> > > https://mxnet.incubator.apache.org/install/index.html
> > >
> > > Also, on the MXNet 'getting started' page
> > > 

Re: new website, docs code freeze

[kellen sunderland]

New site looks good.  I do notice that a few tutorials from the old site
are missing (for example the TensorRT tutorial).  Any plans to bring them
back?

On Sun, Sep 22, 2019 at 10:04 AM Haibin Lin 
wrote:

> Another issue I found with the current website: the Sphinx object inventory
> 
> file https://mxnet.apache.org/objects.inv is missing. GluonNLP relies on
> this file to link document across projects. Shall we add it back?
>
> Best,
> Haibin
>
> On Sun, Sep 22, 2019 at 2:04 AM Lieven Govaerts  wrote:
>
> > Hi,
> >
> >
> > On Sat, 21 Sep 2019 at 06:28, Thomas DELTEIL 
> > wrote:
> >
> > > Thanks all for the feedback,
> > >
> > > We'll send an email next week with the list of missing features,
> content
> > > and bugs that we plan to fix.
> > > We took the option of releasing early, with some features missing,
> rather
> > > than trying to be at feature parity with the old website before
> launching
> > > the website.
> > > The reason why we decided to do that is two-fold:
> > > - playing catch-up with docs in master introduce daily conflicts that
> > need
> > > to be resolved and introduce opportunity for errors
> > > - by releasing early, we can take advantage of the community
> > contributions
> > > in modifying whatever the community feels like a better way of doing
> > > things.
> > >
> > > One of the goals of the new website was to disentangle the main
> website,
> > > now called "static_site" to the auto-generated docs. Now the overall
> site
> > > is made of a main static site, with easy to modify content and easy to
> > > understand architecture for anybody familiar with basic html, and a
> > > collection of mini-websites for each language bindings that can be
> built
> > in
> > > isolation and that are self-contained. Actually the new CI jobs builds
> > all
> > > of them in parallel independently.
> > >
> > > There is PLENTY of room for improvement, it would be great if the
> > community
> > > can help contribute to bring the new website at the same level of
> content
> > > richness as the old one, and then even further.
> > >
> > > Missing features:
> > > - As pointed by Haibin, the API docs do not have the full list of
> > operators
> > > and classes. There is a mix of auto-generated docs based on packages,
> and
> > > some docs that are spelled out manually to improve the logical
> > organization
> > > of the package where there is a need. The drawback with manually listed
> > > classes in a package is that it's very easy to miss some. If someone
> > wanted
> > > to build a sanity check that would automatically detect which classes
> are
> > > not in the documentation, or if someone knew how to enable that with
> > > sphinx, that would be a great addition to the python docs
> > > - There is missing content in the python tutorials, and the
> > discoverability
> > > could be improved. Some old tutorials have not been migrated just yet.
> > > - The nightly tests on tutorials have been disabled for now
> > > - There is no "Download jupyter notebook" for tutorials just yet.
> > > - Non-python tutorials might benefit from a blurb description and a
> > better
> > > content organization.
> > > - Python tutorials could be better organized, have a picture
> accompanying
> > > their description
> > > - There is no site-wide search, this is not an easy problem to solve to
> > be
> > > fair given the static nature of the website, but maybe an external
> plugin
> > > might be able to give a half-way solution
> > > - There is no version selector for the docs
> > > - There is bug in search box of the python docs, but this is just a
> small
> > > JS bug that can be fixed easily (on my list for next week)
> > > - Most old links have not had a redirect put in place.
> > >
> > >
> > I noticed on the Ubuntu home page in the Developer dropdown that the link
> > MXNet on Ubuntu  > >with
> > Nvidia
> > <
> >
> https://www.nvidia.com/en-us/data-center/gpu-accelerated-applications/mxnet/
> > >
> > doesn't work anymore, it points to:
> > https://mxnet.incubator.apache.org/install/index.html
> >
> > Also, on the MXNet 'getting started' page
> > https://mxnet.incubator.apache.org/get_started , the link "Ubuntu
> > Installation Guide" at the bottom doesn't work either, it points to:
> > https://mxnet.incubator.apache.org/ubuntu_setup.html
> >
> >
> > I suggest you do a scan of the new website to find these dangling links.
> >
> > regards,
> >
> > Lieven
> >
> >
> >
> > > We'll formalize this in github issues next week, but they are all
> fairly
> > > small and helping out on these would be a great way of familiarizing
> > > yourself with the new website build system and website architecture.
> > >
> > >  Thanks all for the feedback, please keep it coming!
> > >
> > > Thomas Delteil
> > >
> > > Le sam. 21 sept. 2019 à 09:53, Haibin Lin  a
> > > écrit :
> > >
> > > > It looks like my previous 

RE: [Announcement] New PPMC Member - Tao Lv

[Zhao, Patric]

Congratulations, Tao!


> -Original Message-
> From: Sheng Zha 
> Sent: Monday, September 23, 2019 12:07 PM
> To: d...@mxnet.apache.org
> Subject: [Announcement] New PPMC Member - Tao Lv
> 
> Hi all,
> 
> Please join me in welcoming Tao Lv as a new PPMC member of Apache
> MXNet (incubating)!
> 
> Tao has been a committer of our project since Nov. 2018, and has remained
> very active in not only maintaining MKLDNN backend, but many other areas.
> Over time he and the Intel team has greatly helped the project on CPU
> performance.
> 
> Welcome, Tao!
> 
> -sz

[Announcement] New PPMC Member - Tao Lv

[Sheng Zha]

Hi all,

Please join me in welcoming Tao Lv as a new PPMC member of Apache MXNet 
(incubating)!

Tao has been a committer of our project since Nov. 2018, and has remained very 
active
in not only maintaining MKLDNN backend, but many other areas. Over time he and 
the Intel team has greatly helped the project on CPU performance.

Welcome, Tao!

-sz

mxnet ctrl-c

[Chris Olivier]

question: how does gluon handle ctrl-c during a “long” imperative operation
where the GLI hasn’t been released yet? is it supposed to be caught in c++
or python or no special handling for it at the moment?

Re: new website, docs code freeze

[Haibin Lin]

Another issue I found with the current website: the Sphinx object inventory

file https://mxnet.apache.org/objects.inv is missing. GluonNLP relies on
this file to link document across projects. Shall we add it back?

Best,
Haibin

On Sun, Sep 22, 2019 at 2:04 AM Lieven Govaerts  wrote:

> Hi,
>
>
> On Sat, 21 Sep 2019 at 06:28, Thomas DELTEIL 
> wrote:
>
> > Thanks all for the feedback,
> >
> > We'll send an email next week with the list of missing features, content
> > and bugs that we plan to fix.
> > We took the option of releasing early, with some features missing, rather
> > than trying to be at feature parity with the old website before launching
> > the website.
> > The reason why we decided to do that is two-fold:
> > - playing catch-up with docs in master introduce daily conflicts that
> need
> > to be resolved and introduce opportunity for errors
> > - by releasing early, we can take advantage of the community
> contributions
> > in modifying whatever the community feels like a better way of doing
> > things.
> >
> > One of the goals of the new website was to disentangle the main website,
> > now called "static_site" to the auto-generated docs. Now the overall site
> > is made of a main static site, with easy to modify content and easy to
> > understand architecture for anybody familiar with basic html, and a
> > collection of mini-websites for each language bindings that can be built
> in
> > isolation and that are self-contained. Actually the new CI jobs builds
> all
> > of them in parallel independently.
> >
> > There is PLENTY of room for improvement, it would be great if the
> community
> > can help contribute to bring the new website at the same level of content
> > richness as the old one, and then even further.
> >
> > Missing features:
> > - As pointed by Haibin, the API docs do not have the full list of
> operators
> > and classes. There is a mix of auto-generated docs based on packages, and
> > some docs that are spelled out manually to improve the logical
> organization
> > of the package where there is a need. The drawback with manually listed
> > classes in a package is that it's very easy to miss some. If someone
> wanted
> > to build a sanity check that would automatically detect which classes are
> > not in the documentation, or if someone knew how to enable that with
> > sphinx, that would be a great addition to the python docs
> > - There is missing content in the python tutorials, and the
> discoverability
> > could be improved. Some old tutorials have not been migrated just yet.
> > - The nightly tests on tutorials have been disabled for now
> > - There is no "Download jupyter notebook" for tutorials just yet.
> > - Non-python tutorials might benefit from a blurb description and a
> better
> > content organization.
> > - Python tutorials could be better organized, have a picture accompanying
> > their description
> > - There is no site-wide search, this is not an easy problem to solve to
> be
> > fair given the static nature of the website, but maybe an external plugin
> > might be able to give a half-way solution
> > - There is no version selector for the docs
> > - There is bug in search box of the python docs, but this is just a small
> > JS bug that can be fixed easily (on my list for next week)
> > - Most old links have not had a redirect put in place.
> >
> >
> I noticed on the Ubuntu home page in the Developer dropdown that the link
> MXNet on Ubuntu  >with
> Nvidia
> <
> https://www.nvidia.com/en-us/data-center/gpu-accelerated-applications/mxnet/
> >
> doesn't work anymore, it points to:
> https://mxnet.incubator.apache.org/install/index.html
>
> Also, on the MXNet 'getting started' page
> https://mxnet.incubator.apache.org/get_started , the link "Ubuntu
> Installation Guide" at the bottom doesn't work either, it points to:
> https://mxnet.incubator.apache.org/ubuntu_setup.html
>
>
> I suggest you do a scan of the new website to find these dangling links.
>
> regards,
>
> Lieven
>
>
>
> > We'll formalize this in github issues next week, but they are all fairly
> > small and helping out on these would be a great way of familiarizing
> > yourself with the new website build system and website architecture.
> >
> >  Thanks all for the feedback, please keep it coming!
> >
> > Thomas Delteil
> >
> > Le sam. 21 sept. 2019 à 09:53, Haibin Lin  a
> > écrit :
> >
> > > It looks like my previous email did not go through. Re-sending:
> > >
> > > Hi Aaron,
> > >
> > > The website looks cool. Thanks for pushing this to production. A few
> > > questions:
> > >
> > > - I was looking for the API doc for mx.sym.dot, but I find that most
> > > operators under mx.sym.* are missing. Is this expected?
> > > - I was also checking the search functionality, searching the keyword
> > > "ndarray" only returns one result "mxnet.ndarray.NDArray", which
> doesn't
> > > 

Podling Report Reminder - October 2019

[jmclean]

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, 16 October 2019, 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, October 02).

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.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

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://cwiki.apache.org/confluence/display/INCUBATOR/October2019

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

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: new website, docs code freeze

[Lieven Govaerts]

Hi,


On Sat, 21 Sep 2019 at 06:28, Thomas DELTEIL 
wrote:

> Thanks all for the feedback,
>
> We'll send an email next week with the list of missing features, content
> and bugs that we plan to fix.
> We took the option of releasing early, with some features missing, rather
> than trying to be at feature parity with the old website before launching
> the website.
> The reason why we decided to do that is two-fold:
> - playing catch-up with docs in master introduce daily conflicts that need
> to be resolved and introduce opportunity for errors
> - by releasing early, we can take advantage of the community contributions
> in modifying whatever the community feels like a better way of doing
> things.
>
> One of the goals of the new website was to disentangle the main website,
> now called "static_site" to the auto-generated docs. Now the overall site
> is made of a main static site, with easy to modify content and easy to
> understand architecture for anybody familiar with basic html, and a
> collection of mini-websites for each language bindings that can be built in
> isolation and that are self-contained. Actually the new CI jobs builds all
> of them in parallel independently.
>
> There is PLENTY of room for improvement, it would be great if the community
> can help contribute to bring the new website at the same level of content
> richness as the old one, and then even further.
>
> Missing features:
> - As pointed by Haibin, the API docs do not have the full list of operators
> and classes. There is a mix of auto-generated docs based on packages, and
> some docs that are spelled out manually to improve the logical organization
> of the package where there is a need. The drawback with manually listed
> classes in a package is that it's very easy to miss some. If someone wanted
> to build a sanity check that would automatically detect which classes are
> not in the documentation, or if someone knew how to enable that with
> sphinx, that would be a great addition to the python docs
> - There is missing content in the python tutorials, and the discoverability
> could be improved. Some old tutorials have not been migrated just yet.
> - The nightly tests on tutorials have been disabled for now
> - There is no "Download jupyter notebook" for tutorials just yet.
> - Non-python tutorials might benefit from a blurb description and a better
> content organization.
> - Python tutorials could be better organized, have a picture accompanying
> their description
> - There is no site-wide search, this is not an easy problem to solve to be
> fair given the static nature of the website, but maybe an external plugin
> might be able to give a half-way solution
> - There is no version selector for the docs
> - There is bug in search box of the python docs, but this is just a small
> JS bug that can be fixed easily (on my list for next week)
> - Most old links have not had a redirect put in place.
>
>
I noticed on the Ubuntu home page in the Developer dropdown that the link
MXNet on Ubuntu with
Nvidia

doesn't work anymore, it points to:
https://mxnet.incubator.apache.org/install/index.html

Also, on the MXNet 'getting started' page
https://mxnet.incubator.apache.org/get_started , the link "Ubuntu
Installation Guide" at the bottom doesn't work either, it points to:
https://mxnet.incubator.apache.org/ubuntu_setup.html


I suggest you do a scan of the new website to find these dangling links.

regards,

Lieven



> We'll formalize this in github issues next week, but they are all fairly
> small and helping out on these would be a great way of familiarizing
> yourself with the new website build system and website architecture.
>
>  Thanks all for the feedback, please keep it coming!
>
> Thomas Delteil
>
> Le sam. 21 sept. 2019 à 09:53, Haibin Lin  a
> écrit :
>
> > It looks like my previous email did not go through. Re-sending:
> >
> > Hi Aaron,
> >
> > The website looks cool. Thanks for pushing this to production. A few
> > questions:
> >
> > - I was looking for the API doc for mx.sym.dot, but I find that most
> > operators under mx.sym.* are missing. Is this expected?
> > - I was also checking the search functionality, searching the keyword
> > "ndarray" only returns one result "mxnet.ndarray.NDArray", which doesn't
> > seem right. There animation keeps going (Searching. -> Searching.. ->
> > Searching ...) and gives me an impression that the search is never
> > completely done(?).
> >
> > Best,
> > Haibin
> >
> >
> > On Fri, Sep 20, 2019 at 4:50 PM Chaitanya Bapat 
> > wrote:
> >
> > > Thanks Aaron and the team for launching new website!
> > >
> > > 1. There's no search button anywhere on the landing page.
> > > 2. I wasn't able to find FAQ (and without search button I dont have
> > option
> > > but to go manually on each menu). Only when I go to Docs ->
> FAQ
> > > -> Extend and Cotribute (that