Re: custom 404 and other error landing pages and server logs

[Aaron Markham]

Pedro, that would be cool.

On a related note, I've reviewed the results from the broken link checker
job and submitted a PR for 3 links out of >50 reports.
35 of these are in a "regression" category. The others are mostly
redirects, and the tool will get updated to deal with those (not report
temp moves, warn about perm moves).

Regarding the regression category, I propose that we remove this check in
favor of getting the server logs and analyzing issues from that end.

The 35 "broken links" are pages that existed at one time, but do not now.
There's no data if any site visitor even tried to hit these old pages. Yet,
this regression info comes in a report mixed with actual broken links and
make it seem like there's a problem when, well, maybe there's not. If we
had data to say, 500 users a week go to this link and we give them a 404.
Ok, that's a problem. But this regression check doesn't do that. It just
says "a link existed one day, and it isn't there now, and I (the link
checker) might be the only one in the world that cares." Also, this
regression check has no idea if users are going to a page that doesn't
exist due to a bad link in a blog or other outside resource. If we get the
server logs, we'll know what pages users are going to that aren't there. We
can make an informed decision for fixing it by redirecting it or by putting
something there and how to prioritize. Also, these 35 links just say
they're missing. Someone would have to investigate or just guess where to
redirect them, and maybe all that work doesn't even yield any benefit.

To summarize (remove the regression check, and...):
* check server logs on what pages users are getting errors on, and make
plans to fix those
* show users better error pages
* report broken links only when there's a live link on the site that yields
a true 404 (not a 301 or 303 or anything else)

Cheers,
Aaron


On Thu, Aug 2, 2018 at 3:17 PM, Pedro Larroy 
wrote:

> Yes, we can do something fun for these errors, something maybe with a cat
> an a DL theme, or some funny style transfer stuff.
>
> Pedro
>
> On Thu, Aug 2, 2018 at 11:54 PM Aaron Markham 
> wrote:
>
> > Hi everyone,
> > I would like to suggest that we adopt a custom landing page for missing
> > pages, rather than the dead-end error the website has now. Typically you
> > set this up by modifying the server config and pointing it to a custom
> > page.
> >
> > I'd like to know how we go about requesting that kind of change on the
> > Apache infra.
> >
> > Also, so that we know if people are getting 404s on certain pages, or if
> > pages are breaking and throwing 500 errors, we could look at the server
> > logs for the domain. A cron job that pushes them to s3 would work if we
> > can't get direct access.
> >
> > How do we get regular access to or a feed of these logs that are residing
> > on the web server?
> >
> > Cheers,
> > Aaron
> >
>

Invitation: Apache MXNet Hangout 5pm PDT @ Wed Sep 5, 2018 5pm - 6pm (PDT) (dev@mxnet.incubator.apache.org)

[Steffen Rochel]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180906T00Z
DTEND:20180906T01Z
DTSTAMP:20180802T223928Z
ORGANIZER;CN=Steffen Rochel:mailto:steffenroc...@gmail.com
UID:2co9qpt209vhp3n9rppsciq...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Steffen Rochel;X-NUM-GUESTS=0:mailto:steffenroc...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
CREATED:20180802T223928Z
DESCRIPTION:See details https://cwiki.apache.org/confluence/di
 splay/MXNET/Hangout+September+5th+2018+8am+and+5pm+PDT">hereCal
 l in information:1. Click to join the meeting: https://chime.aws/443297
 2704   Meeting ID: 4432 97 27042. You can use your computer’s micro
 phone and speakers\, however\, a headset is recommended. Or\, call in using
  your phone:United States Toll-Free: +1 855-552-4463Meeting PIN
 : 4432 97 2704One-click Mobile Dial-in (United States (1)): +1 206-
 462-5569\,\,4432972704#United States (1): +1 206-462-5569Intern
 ational: https://chime.aws/dialinnumbers/\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not ed
 it this section of the description.\n\nView your event at https://www.googl
 e.com/calendar/event?action=VIEW=MmNvOXFwdDIwOXZocDNuOXJwcHNjaXFic3MgZG
 V2QG14bmV0LmluY3ViYXRvci5hcGFjaGUub3Jn=MjMjc3RlZmZlbnJvY2hlbEBnbWFpbC5j
 b21jNjA1NDFmODc3NjFjZGJhODljZTlkNTg3OTkyYjM5ZDU3N2E2YWE3=America%2FLos_
 Angeles=en=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180802T223928Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Apache MXNet Hangout 5pm PDT
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

Invitation: Apache MXNet Hangout 8am PDT @ Wed Sep 5, 2018 8am - 9am (PDT) (dev@mxnet.incubator.apache.org)

[Steffen Rochel]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180905T15Z
DTEND:20180905T16Z
DTSTAMP:20180802T223807Z
ORGANIZER;CN=Steffen Rochel:mailto:steffenroc...@gmail.com
UID:4sb67q8679arcajd3n8recb...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Steffen Rochel;X-NUM-GUESTS=0:mailto:steffenroc...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
CREATED:20180802T223807Z
DESCRIPTION:Apache MXNet Hangout \n\nCall information:\n1. Click to join th
 e meeting: https://chime.aws/4432972704   Meeting ID: 4432 97 2704\n\n2. Yo
 u can use your computer’s microphone and speakers\, however\, a headset is 
 recommended. Or\, call in using your phone:\n\nUnited States Toll-Free: +1 
 855-552-4463\nMeeting PIN: 4432 97 2704\n\nOne-click Mobile Dial-in (United
  States (1)): +1 206-462-5569\,\,4432972704#\n\nUnited States (1): +1 206-4
 62-5569\nInternational: https://chime.aws/dialinnumbers/\n\n-::~:~::~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nP
 lease do not edit this section of the description.\n\nView your event at ht
 tps://www.google.com/calendar/event?action=VIEW=NHNiNjdxODY3OWFyY2FqZDN
 uOHJlY2JicnEgZGV2QG14bmV0LmluY3ViYXRvci5hcGFjaGUub3Jn=MjMjc3RlZmZlbnJvY
 2hlbEBnbWFpbC5jb20wNjRmMTNhZmExNjQ3YmE0NDQxZWUyNTIyYjNiZWRhMTU5NmMxM2E5
 =America%2FLos_Angeles=en=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180802T223807Z
LOCATION:Palo Alto\, CA\, USA
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Apache MXNet Hangout 8am PDT
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

Re: MXNet virtual hangout 2018-August-1 8am and 5pm PDT

[Steffen Rochel]

Apology first - we had few audio problems and as result no recording of the
meeting.

I would like to thank all attendees, especially Ming Zhang for the deep
dive in the challenges he is facing.
Please see hangout notes at
https://cwiki.apache.org/confluence/display/MXNET/Aug+1st.+2018+-+5pm+PDT+session


Please mark your calendar for next hangout on September 5th 2018 8am and
5pm PDT. Call in information is here

and
below.
Please feel free to add agenda items you wish to discuss.

Regards,
Steffen

*Meeting information:*

1. Click to join the meeting: https://chime.aws/4432972704   Meeting ID:
4432 97 2704

2. You can use your computer’s microphone and speakers, however, a headset
is recommended. Or, call in using your phone:

United States Toll-Free: +1 855-552-4463
Meeting PIN: 4432 97 2704

One-click Mobile Dial-in (United States (1)): +1 206-462-5569,,4432972704#

United States (1): +1 206-462-5569
International: https://chime.aws/dialinnumbers/
On Wed, Aug 1, 2018 at 8:47 AM Steffen Rochel 
wrote:

> Hi - it looks there has been confusion about the hangout scheduled for
> today. I was on the 8am PDT call and chatted with Marco.
> I will be on the call today Aug 1st 5pm PDT as well.
> Please drop me a note if you missed the hangout notice or got confused due
> to changes in the hangout invite and would like to get an a call next week.
>
> Regards,
> Steffen
>
> On Sun, Jul 29, 2018 at 9:50 PM Steffen Rochel 
> wrote:
>
>> I would like to remind everybody about the hangout on August 1st 8am PDT
>> and 5pm PDT. Please see also the hangout invitations from Pedro.
>>
>>
>>
>>-
>>
>>Dial in instructions:
>>-
>>
>>   https://chime.aws/8536075882
>>
>>   Meeting ID: 8536 07 5882
>>
>>   United States Toll-Free: +1 855-552-4463 <(855)%20552-4463>
>>   Meeting PIN: 8536 07 5882
>>
>>   One-click Mobile Dial-in (United States (1)): +1 206-462-5569
>>   <(206)%20462-5569>,,8536075882#
>>
>>   International: https://chime.aws/dialinnumbers/
>>
>>
>>-
>>
>>Agenda - see hangout wiki page
>>
>> .
>>Feel free to add topics you consider important for the community.
>>
>>
>> Regards,
>> Steffen
>>
>> On Wed, Jul 18, 2018 at 10:32 AM Steffen Rochel 
>> wrote:
>>
>>> I would like to invite for virtual hangout on 2018-August-1 8am and 5pm
>>> PDT.
>>>
>>>-
>>>
>>>Dial in instructions:
>>>-
>>>
>>>   https://chime.aws/8536075882
>>>
>>>   Meeting ID: 8536 07 5882
>>>
>>>   United States Toll-Free: +1 855-552-4463 <(855)%20552-4463>
>>>   Meeting PIN: 8536 07 5882
>>>
>>>   One-click Mobile Dial-in (United States (1)): +1 206-462-5569
>>>   <(206)%20462-5569>,,8536075882#
>>>
>>>   International: https://chime.aws/dialinnumbers/
>>>   -
>>>
>>>Agenda:
>>>- TBD
>>>
>>>
>>> Please feel free to add agenda items to hangout wiki page
>>> 
>>> .
>>> Hope to (virtually) see you on August 1st.
>>>
>>> Steffen
>>>
>>

Re: custom 404 and other error landing pages and server logs

[Pedro Larroy]

Yes, we can do something fun for these errors, something maybe with a cat
an a DL theme, or some funny style transfer stuff.

Pedro

On Thu, Aug 2, 2018 at 11:54 PM Aaron Markham 
wrote:

> Hi everyone,
> I would like to suggest that we adopt a custom landing page for missing
> pages, rather than the dead-end error the website has now. Typically you
> set this up by modifying the server config and pointing it to a custom
> page.
>
> I'd like to know how we go about requesting that kind of change on the
> Apache infra.
>
> Also, so that we know if people are getting 404s on certain pages, or if
> pages are breaking and throwing 500 errors, we could look at the server
> logs for the domain. A cron job that pushes them to s3 would work if we
> can't get direct access.
>
> How do we get regular access to or a feed of these logs that are residing
> on the web server?
>
> Cheers,
> Aaron
>

custom 404 and other error landing pages and server logs

[Aaron Markham]

Hi everyone,
I would like to suggest that we adopt a custom landing page for missing
pages, rather than the dead-end error the website has now. Typically you
set this up by modifying the server config and pointing it to a custom page.

I'd like to know how we go about requesting that kind of change on the
Apache infra.

Also, so that we know if people are getting 404s on certain pages, or if
pages are breaking and throwing 500 errors, we could look at the server
logs for the domain. A cron job that pushes them to s3 would work if we
can't get direct access.

How do we get regular access to or a feed of these logs that are residing
on the web server?

Cheers,
Aaron

Re: MXNet Berlin Office Hours

[Ivan Serdyuk]

I have a single global question: I am looking for a global plan for
covering MXNet, for developer meetups. There are various APIs, for various
languages. So I guess i might come up with diff. backend communities (in my
home country - Ukraine).

Ivan

On Wed, Aug 1, 2018 at 7:31 PM, Steffen Rochel 
wrote:

> Ivan - you don't have to wait until next week, please feel free to post
> your question on https://discuss.mxnet.io/ or here or
> u...@mxnet.apache.org.
>
> Regards,
> Steffen
>
> On Wed, Aug 1, 2018 at 8:52 AM Marco de Abreu
>  wrote:
>
> > Hello Ivan,
> >
> > Sorry, the office hours were yesterday. It would be great if you could
> > attend next week!
> >
> > Best regards,
> > Marco
> >
> > Ivan Serdyuk  schrieb am Mi., 1. Aug.
> 2018,
> > 17:28:
> >
> > > Nock-nock. Anybody in a meeting room?
> > >
> > > On Mon, Jul 16, 2018 at 12:27 PM, Anton Chernov 
> > > wrote:
> > >
> > > > Dear MXNet community,
> > > >
> > > > As part of our customer support the MXNet Berlin team is offering
> > office
> > > > hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
> > > >
> > > > They happen onsite in the Amazon Berlin office:
> > > > Krausenstraße 38, 10117 Berlin in BER12 01.501
> > > >
> > > > Conference Bridge Information
> > > >
> > > > Chime meeting ID: 5461650798
> > > > Join via browser screen share: https://chime.aws/5461650798
> > > > Join via phone (US): +1-929-432-4463 <(929)%20432-4463>,,5461650798#
> > > > Join via phone (US toll-free): +1-855-552-4463 <(855)%20552-4463>
> > ,,5461650798#
> > > > International dial-in: https://chime.aws/dialinnumbers/
> > > > In-room video system: Ext: 62000, Meeting PIN: 5461650798#
> > > >
> > > > How can we help you?
> > > >
> > > > The following are a few examples of the types of consultations we
> > > provide:
> > > >
> > > > * CI and infrastructure questions
> > > > * Build system
> > > > * Benchmarking
> > > > * Edge devices (for example Raspberry Pi, Jetson)
> > > > * C++
> > > > * General questions
> > > >
> > > > Before attending
> > > >
> > > > Try finding answers on:
> > > >
> > > > * Our discussion forum (https://discuss.mxnet.io)
> > > > * StackOverflow mxnet tag (https://stackoverflow.com/
> > > > questions/tagged/mxnet)
> > > > * MXNet website (https://mxnet.incubator.apache.org/faq/)
> > > > * Github issues (https://github.com/apache/incubator-mxnet/issues)
> > > >
> > > > If this does not help:
> > > >
> > > > In advance fill out a github issue (
> > > > https://github.com/apache/incubator-mxnet/issues/new) at least a few
> > > days
> > > > before so that the team member who will help with the issue gets a
> > chance
> > > > to prepare.
> > > >
> > > > Main point of contact through email: mxnet-edge-oncall-primary[at]a
> > > > mazon.com
> > > >
> > > > Best regards
> > > > Anton Chernov
> > > >
> > > > [1]
> > > > https://cwiki.apache.org/confluence/display/MXNET/
> > > > MXNet+Berlin+Office+Hours
> > > >
> > >
> >
>

Re: Significant windows build improvements from source

[Qing Lan]

Hi Pedro,

Great works! Thanks for supporting Windows build in here.

Thanks,
Qing

On 8/2/18, 10:08 AM, "Marco de Abreu"  
wrote:

Hello Pedro,

These are great efforts! It's great to see that we are improving our
situation around Windows.

Looking forward to using it.

Best regards,
Marco

Pedro Larroy  schrieb am Do., 2. Aug. 2018,
19:04:

> Hi
>
> I have taken some effort to cleanup the Windows build process and condense
> it in a single python script, provided that the required dependencies are
> installed (opencv, openblas and cuda/cudnn in gpu).
>
> Now there's a single command necessary to get a build:
>
> python ci\build_windows.py
>
> The build flavour can be given with the '-f' argument.
>
> This produces a windows_package.7z file with MXNet libraries, python
> bindings and includes.
>
> For testing, just running a powershell script like:
>
>ci/windows/test_py3_cpu.ps1
>
> Will execute the unit tests.
>
> Let me know what you think.  I pretty much would like to see these changes
> in the release branch which will help with any windows issues that we 
might
> find.
>
> https://github.com/apache/incubator-mxnet/pull/11947
>
> Simple installation of dependencies and update to the documentation about
> windows builds from source will come in the future.
>
> Pedro.
>

Re: Significant windows build improvements from source

[Marco de Abreu]

Hello Pedro,

These are great efforts! It's great to see that we are improving our
situation around Windows.

Looking forward to using it.

Best regards,
Marco

Pedro Larroy  schrieb am Do., 2. Aug. 2018,
19:04:

> Hi
>
> I have taken some effort to cleanup the Windows build process and condense
> it in a single python script, provided that the required dependencies are
> installed (opencv, openblas and cuda/cudnn in gpu).
>
> Now there's a single command necessary to get a build:
>
> python ci\build_windows.py
>
> The build flavour can be given with the '-f' argument.
>
> This produces a windows_package.7z file with MXNet libraries, python
> bindings and includes.
>
> For testing, just running a powershell script like:
>
>ci/windows/test_py3_cpu.ps1
>
> Will execute the unit tests.
>
> Let me know what you think.  I pretty much would like to see these changes
> in the release branch which will help with any windows issues that we might
> find.
>
> https://github.com/apache/incubator-mxnet/pull/11947
>
> Simple installation of dependencies and update to the documentation about
> windows builds from source will come in the future.
>
> Pedro.
>

Re: Separate repo for MXNet infrastructure

[Pedro Larroy]

Was there any confusion?

On Thu, Aug 2, 2018 at 7:02 PM Marco de Abreu
 wrote:

> Just to clarify and avoid confusion: The dockerized pipeline and other
> things that are tightly integrated would stay in the mxnet repository.
>
> We would only add new projects to the new repository.
>
> -Marco
>
> Pedro Larroy  schrieb am Do., 2. Aug. 2018,
> 18:42:
>
> > Agree with Marco, there's a lot of stuff unrelated to MXNet. And right
> now
> > we have good separation of concerns via the dockerized builds and
> > ci/build.py infrastructure.
> > I'm also in favor of a separate repo.
> >
> > On Thu, Aug 2, 2018 at 6:08 PM Marco de Abreu
> >  wrote:
> >
> > > Very good questions! My proposal would be that projects stored in that
> > > separate repository would be entirely independent of the mxnet code. If
> > > there is something that would need an update on both repositories,
> it's a
> > > strong indicator that it should be put into the mxnet repository. There
> > is
> > > no coupling between the two repositories.
> > >
> > > From my perspective, we would not do any releases in that repository.
> > > Contributions would happen in the same way as it happens right now:
> > People
> > > make pull requests and they can then be merged by committers.
> > >
> > > I personally think that storing things like these under the mxnet
> > > repository might make it unnecessarily big and also create a conflict
> of
> > > concerns. Code in the mxnet repository repository should be in direct
> > > relation to the source of mxnet.
> > > Another problem there would be our ci process. We would have to run the
> > > entire CI pipeline although a patch might only touch the tools. This is
> > not
> > > necessary.
> > >
> > > Avoiding the coupling allows us to ensure that solutions are entirely
> > > standalone and that they build on top of the user APIs. If we tightl
> > > integrate it, we might run into cases where people make changes in the
> > > mxnet code out of convenience on a fly-by.
> > >
> > > One example for a project would be the email not from Cathy. Her
> project
> > is
> > > entirely independent from the mxnet source and it should be made clear
> > that
> > > this is actually the case.
> > >
> > > Best regards,
> > > Marco
> > >
> > > sandeep krishnamurthy  schrieb am Do., 2.
> > > Aug.
> > > 2018, 17:50:
> > >
> > > > apache/incubator-mxnet-tools is a good idea.
> > > > I have few queries on - how do we manage separate repository,
> releases,
> > > > changes by contributors may have to go to 2 repositories (when CI
> > updates
> > > > are required), is it going to be inside 3rd party module, versions of
> > > > dependencies in tools should match with other resources in repo ex:
> > > > setup.py etc.
> > > >
> > > > Why not under mxnet repo a CI / tools / infra folder and all this
> tools
> > > go
> > > > under it?
> > > >
> > > > Best,
> > > > Sandeep
> > > >
> > > > On Wed, Aug 1, 2018 at 4:12 AM Pedro Larroy <
> > > pedro.larroy.li...@gmail.com>
> > > > wrote:
> > > >
> > > > > I like tools more.
> > > > >
> > > > > On Wed, Aug 1, 2018 at 11:05 AM Marco de Abreu
> > > > >  wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > definitely a good point, Isabel. During our office hour we
> thought
> > > > about
> > > > > > creating a repository under the Apache account with a name like
> > > > > > incubator-mxnet-tools or incubator-mxnet-infrastructure. Does
> > anybody
> > > > > have
> > > > > > other ideas for naming or maybe a better solution?
> > > > > >
> > > > > > Best regards,
> > > > > > Marco
> > > > > >
> > > > > > On Wed, Aug 1, 2018 at 10:35 AM Isabel Drost-Fromm <
> > > isa...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang <
> > > > > > > zhangyuelinch...@gmail.com>:
> > > > > > > >My concern is where should my code be finally merged. This bot
> > is
> > > > not
> > > > > a
> > > > > > > >part of MXNet framework but it serves MXNet community. For
> now,
> > a
> > > > good
> > > > > > > >option is to have a separate repo for infrastructure.
> > > > > > >
> > > > > > > As this would be something that serves the mxnet project, my
> > advise
> > > > > would
> > > > > > > be to make sure it ends up in a location that is controlled by
> > the
> > > > > Apache
> > > > > > > mxnet PMC, in a location that is mirrored back to ASF
> resources.
> > > > > > >
> > > > > > > Isabel
> > > > > > >
> > > > > > > --
> > > > > > > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail
> > > gesendet.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Sandeep Krishnamurthy
> > > >
> > >
> >
>

Significant windows build improvements from source

[Pedro Larroy]

Hi

I have taken some effort to cleanup the Windows build process and condense
it in a single python script, provided that the required dependencies are
installed (opencv, openblas and cuda/cudnn in gpu).

Now there's a single command necessary to get a build:

python ci\build_windows.py

The build flavour can be given with the '-f' argument.

This produces a windows_package.7z file with MXNet libraries, python
bindings and includes.

For testing, just running a powershell script like:

   ci/windows/test_py3_cpu.ps1

Will execute the unit tests.

Let me know what you think.  I pretty much would like to see these changes
in the release branch which will help with any windows issues that we might
find.

https://github.com/apache/incubator-mxnet/pull/11947

Simple installation of dependencies and update to the documentation about
windows builds from source will come in the future.

Pedro.

Re: MXNet virtual hangout 2018-August-1 8am and 5pm PDT

[Pedro Larroy]

How was it? I actually missed it while trying to get code in for the
release.

On Wed, Aug 1, 2018 at 5:47 PM Steffen Rochel 
wrote:

> Hi - it looks there has been confusion about the hangout scheduled for
> today. I was on the 8am PDT call and chatted with Marco.
> I will be on the call today Aug 1st 5pm PDT as well.
> Please drop me a note if you missed the hangout notice or got confused due
> to changes in the hangout invite and would like to get an a call next week.
>
> Regards,
> Steffen
>
> On Sun, Jul 29, 2018 at 9:50 PM Steffen Rochel 
> wrote:
>
> > I would like to remind everybody about the hangout on August 1st 8am PDT
> > and 5pm PDT. Please see also the hangout invitations from Pedro.
> >
> >
> >
> >-
> >
> >Dial in instructions:
> >-
> >
> >   https://chime.aws/8536075882
> >
> >   Meeting ID: 8536 07 5882
> >
> >   United States Toll-Free: +1 855-552-4463 <(855)%20552-4463>
> >   Meeting PIN: 8536 07 5882
> >
> >   One-click Mobile Dial-in (United States (1)): +1 206-462-5569
> >   <(206)%20462-5569>,,8536075882#
> >
> >   International: https://chime.aws/dialinnumbers/
> >
> >
> >-
> >
> >Agenda - see hangout wiki page
> ><
> https://cwiki.apache.org/confluence/display/MXNET/Meetups+and+Hangouts#Meetups+and+Hangouts-2018Aug
> >.
> >Feel free to add topics you consider important for the community.
> >
> >
> > Regards,
> > Steffen
> >
> > On Wed, Jul 18, 2018 at 10:32 AM Steffen Rochel  >
> > wrote:
> >
> >> I would like to invite for virtual hangout on 2018-August-1 8am and 5pm
> >> PDT.
> >>
> >>-
> >>
> >>Dial in instructions:
> >>-
> >>
> >>   https://chime.aws/8536075882
> >>
> >>   Meeting ID: 8536 07 5882
> >>
> >>   United States Toll-Free: +1 855-552-4463 <(855)%20552-4463>
> >>   Meeting PIN: 8536 07 5882
> >>
> >>   One-click Mobile Dial-in (United States (1)): +1 206-462-5569
> >>   <(206)%20462-5569>,,8536075882#
> >>
> >>   International: https://chime.aws/dialinnumbers/
> >>   -
> >>
> >>Agenda:
> >>- TBD
> >>
> >>
> >> Please feel free to add agenda items to hangout wiki page
> >> <
> https://cwiki.apache.org/confluence/display/MXNET/Meetups+and+Hangouts#Meetups+and+Hangouts-2018Aug
> >
> >> .
> >> Hope to (virtually) see you on August 1st.
> >>
> >> Steffen
> >>
> >
>

Re: Separate repo for MXNet infrastructure

[Pedro Larroy]

Agree with Marco, there's a lot of stuff unrelated to MXNet. And right now
we have good separation of concerns via the dockerized builds and
ci/build.py infrastructure.
I'm also in favor of a separate repo.

On Thu, Aug 2, 2018 at 6:08 PM Marco de Abreu
 wrote:

> Very good questions! My proposal would be that projects stored in that
> separate repository would be entirely independent of the mxnet code. If
> there is something that would need an update on both repositories, it's a
> strong indicator that it should be put into the mxnet repository. There is
> no coupling between the two repositories.
>
> From my perspective, we would not do any releases in that repository.
> Contributions would happen in the same way as it happens right now: People
> make pull requests and they can then be merged by committers.
>
> I personally think that storing things like these under the mxnet
> repository might make it unnecessarily big and also create a conflict of
> concerns. Code in the mxnet repository repository should be in direct
> relation to the source of mxnet.
> Another problem there would be our ci process. We would have to run the
> entire CI pipeline although a patch might only touch the tools. This is not
> necessary.
>
> Avoiding the coupling allows us to ensure that solutions are entirely
> standalone and that they build on top of the user APIs. If we tightl
> integrate it, we might run into cases where people make changes in the
> mxnet code out of convenience on a fly-by.
>
> One example for a project would be the email not from Cathy. Her project is
> entirely independent from the mxnet source and it should be made clear that
> this is actually the case.
>
> Best regards,
> Marco
>
> sandeep krishnamurthy  schrieb am Do., 2.
> Aug.
> 2018, 17:50:
>
> > apache/incubator-mxnet-tools is a good idea.
> > I have few queries on - how do we manage separate repository, releases,
> > changes by contributors may have to go to 2 repositories (when CI updates
> > are required), is it going to be inside 3rd party module, versions of
> > dependencies in tools should match with other resources in repo ex:
> > setup.py etc.
> >
> > Why not under mxnet repo a CI / tools / infra folder and all this tools
> go
> > under it?
> >
> > Best,
> > Sandeep
> >
> > On Wed, Aug 1, 2018 at 4:12 AM Pedro Larroy <
> pedro.larroy.li...@gmail.com>
> > wrote:
> >
> > > I like tools more.
> > >
> > > On Wed, Aug 1, 2018 at 11:05 AM Marco de Abreu
> > >  wrote:
> > >
> > > > Hi,
> > > >
> > > > definitely a good point, Isabel. During our office hour we thought
> > about
> > > > creating a repository under the Apache account with a name like
> > > > incubator-mxnet-tools or incubator-mxnet-infrastructure. Does anybody
> > > have
> > > > other ideas for naming or maybe a better solution?
> > > >
> > > > Best regards,
> > > > Marco
> > > >
> > > > On Wed, Aug 1, 2018 at 10:35 AM Isabel Drost-Fromm <
> isa...@apache.org>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > > Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang <
> > > > > zhangyuelinch...@gmail.com>:
> > > > > >My concern is where should my code be finally merged. This bot is
> > not
> > > a
> > > > > >part of MXNet framework but it serves MXNet community. For now, a
> > good
> > > > > >option is to have a separate repo for infrastructure.
> > > > >
> > > > > As this would be something that serves the mxnet project, my advise
> > > would
> > > > > be to make sure it ends up in a location that is controlled by the
> > > Apache
> > > > > mxnet PMC, in a location that is mirrored back to ASF resources.
> > > > >
> > > > > Isabel
> > > > >
> > > > > --
> > > > > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail
> gesendet.
> > > > >
> > > >
> > >
> >
> >
> > --
> > Sandeep Krishnamurthy
> >
>

Re: Separate repo for MXNet infrastructure

[Marco de Abreu]

Very good questions! My proposal would be that projects stored in that
separate repository would be entirely independent of the mxnet code. If
there is something that would need an update on both repositories, it's a
strong indicator that it should be put into the mxnet repository. There is
no coupling between the two repositories.

>From my perspective, we would not do any releases in that repository.
Contributions would happen in the same way as it happens right now: People
make pull requests and they can then be merged by committers.

I personally think that storing things like these under the mxnet
repository might make it unnecessarily big and also create a conflict of
concerns. Code in the mxnet repository repository should be in direct
relation to the source of mxnet.
Another problem there would be our ci process. We would have to run the
entire CI pipeline although a patch might only touch the tools. This is not
necessary.

Avoiding the coupling allows us to ensure that solutions are entirely
standalone and that they build on top of the user APIs. If we tightl
integrate it, we might run into cases where people make changes in the
mxnet code out of convenience on a fly-by.

One example for a project would be the email not from Cathy. Her project is
entirely independent from the mxnet source and it should be made clear that
this is actually the case.

Best regards,
Marco

sandeep krishnamurthy  schrieb am Do., 2. Aug.
2018, 17:50:

> apache/incubator-mxnet-tools is a good idea.
> I have few queries on - how do we manage separate repository, releases,
> changes by contributors may have to go to 2 repositories (when CI updates
> are required), is it going to be inside 3rd party module, versions of
> dependencies in tools should match with other resources in repo ex:
> setup.py etc.
>
> Why not under mxnet repo a CI / tools / infra folder and all this tools go
> under it?
>
> Best,
> Sandeep
>
> On Wed, Aug 1, 2018 at 4:12 AM Pedro Larroy 
> wrote:
>
> > I like tools more.
> >
> > On Wed, Aug 1, 2018 at 11:05 AM Marco de Abreu
> >  wrote:
> >
> > > Hi,
> > >
> > > definitely a good point, Isabel. During our office hour we thought
> about
> > > creating a repository under the Apache account with a name like
> > > incubator-mxnet-tools or incubator-mxnet-infrastructure. Does anybody
> > have
> > > other ideas for naming or maybe a better solution?
> > >
> > > Best regards,
> > > Marco
> > >
> > > On Wed, Aug 1, 2018 at 10:35 AM Isabel Drost-Fromm 
> > > wrote:
> > >
> > > >
> > > >
> > > > Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang <
> > > > zhangyuelinch...@gmail.com>:
> > > > >My concern is where should my code be finally merged. This bot is
> not
> > a
> > > > >part of MXNet framework but it serves MXNet community. For now, a
> good
> > > > >option is to have a separate repo for infrastructure.
> > > >
> > > > As this would be something that serves the mxnet project, my advise
> > would
> > > > be to make sure it ends up in a location that is controlled by the
> > Apache
> > > > mxnet PMC, in a location that is mirrored back to ASF resources.
> > > >
> > > > Isabel
> > > >
> > > > --
> > > > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> > > >
> > >
> >
>
>
> --
> Sandeep Krishnamurthy
>

Re: Separate repo for MXNet infrastructure

[sandeep krishnamurthy]

apache/incubator-mxnet-tools is a good idea.
I have few queries on - how do we manage separate repository, releases,
changes by contributors may have to go to 2 repositories (when CI updates
are required), is it going to be inside 3rd party module, versions of
dependencies in tools should match with other resources in repo ex:
setup.py etc.

Why not under mxnet repo a CI / tools / infra folder and all this tools go
under it?

Best,
Sandeep

On Wed, Aug 1, 2018 at 4:12 AM Pedro Larroy 
wrote:

> I like tools more.
>
> On Wed, Aug 1, 2018 at 11:05 AM Marco de Abreu
>  wrote:
>
> > Hi,
> >
> > definitely a good point, Isabel. During our office hour we thought about
> > creating a repository under the Apache account with a name like
> > incubator-mxnet-tools or incubator-mxnet-infrastructure. Does anybody
> have
> > other ideas for naming or maybe a better solution?
> >
> > Best regards,
> > Marco
> >
> > On Wed, Aug 1, 2018 at 10:35 AM Isabel Drost-Fromm 
> > wrote:
> >
> > >
> > >
> > > Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang <
> > > zhangyuelinch...@gmail.com>:
> > > >My concern is where should my code be finally merged. This bot is not
> a
> > > >part of MXNet framework but it serves MXNet community. For now, a good
> > > >option is to have a separate repo for infrastructure.
> > >
> > > As this would be something that serves the mxnet project, my advise
> would
> > > be to make sure it ends up in a location that is controlled by the
> Apache
> > > mxnet PMC, in a location that is mirrored back to ASF resources.
> > >
> > > Isabel
> > >
> > > --
> > > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> > >
> >
>


-- 
Sandeep Krishnamurthy