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
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
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
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+se
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 t
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
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
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.
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
>
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
>
>
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 b
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 stuf
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
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 w
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 coup
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 wit
16 matches
Mail list logo
