Alright Sam! Congratulations!
On Wed, Jul 29, 2020, 8:41 PM Kshitij Kalambarkar <
kshitijkalambar...@gmail.com> wrote:
> Congrats Sam! Keep up the great work.
>
> On Thu, 30 Jul, 2020, 8:49 AM Zhang Zhi, wrote:
>
> > Congrats Sam!!
> >
> > -Zhi
> >
> > On Wed, Jul 29, 2020 at 7:30 PM Chen,
>
> Thank you all for this amazing tool that you've built and maintain.
>
> Kind regards,
> Foivos
>
> On Sat, Apr 25, 2020 at 12:05 AM Aaron Markham
> wrote:
>
> > Hi MXNet community!
> >
> > I recently looked through stats for Q1 and compared them to previous
>
Hi MXNet community!
I recently looked through stats for Q1 and compared them to previous
quarters. I also checked out some of the insights. Here's what I found:
MXNet traffic was relatively flat with a 0.24% gain in users QoQ, but a
slight decline of users of -2.36% month over month. However,
out dependency pinning?
>
> The cache should not be our method to do dependency pinning and
> synchronization.
>
> -Marco
>
> Aaron Markham schrieb am Fr., 27. März 2020,
> 03:45:
>
> > I'm dealing with a Ruby dep breaking the site build right now.
> > I wish this wo
gt;
> > wrote:
> >
> > > WRT Docker Cache: We need to add a mechanism to invalidate the cache
> and
> > > rebuild
> > > the containers on a set schedule. The builds break too often and the
> > > breakage is
> > > only detected when a con
@gmail.com>
> > > > wrote:
> > > >
> > > > > Back then I have created a system which exports all Jenkins results
> > to
> > > > > cloud watch. It does not include individual test results but rather
> > > > stages
> > > > > and jobs
+1 for sanity check - that's fast.
-1 for unix-cpu - that's slow and can just hang.
So my suggestion would be to see the data apart - what's the failure
rate on the sanity check and the unix-cpu? Actually, can we get a
table of all of the tests with this data?!
If the sanity check fails... let's
I noticed at point the iops limit was getting hit.
Upgrading the storage specs could be a great idea too.
On Wed, Mar 18, 2020, 11:59 Patrick Mu wrote:
> Dear Community,
>
> Our developers have identified frequently occurrence of "Cannot contact
> " issue
> in our CI system. Sheng and Leonard
> Thanks @zachgk - I took a couple of screenshots so I could share here
>
> Here is the Scala package
> 
>
> and here is the Clojure package
>
@leezu @szha - We need a clear direction on what to do for the current site's
docs generation. It isn't really website versioning. It's generating
documentation from different branches. The core website jekyll should stay the
same and be generated from master. However, the default docs for each
Docs are currently generated from master. What's the proposal for what should
be the default version of the docs on the website?
Do we need to escalate the production of docs variations for different versions
- like at a minimum, master(2.0) and 1.x?
--
You are receiving this because you
Félicitations!
On Thu, Feb 13, 2020 at 10:09 AM Chaitanya Bapat wrote:
>
> Congrats Thomas! Well deserved. Keep it up!
>
> On Thu, 13 Feb 2020 at 10:04, Naveen Swamy wrote:
>
> > Hi all,
> >
> > Please join me in welcoming Thomas Delteil as a new member of Apache MXNet
> > (incubating) PPMC!
>
+1 These are good action items that should help alleviate part of the
CI issues.
The following comments are not to take away from your proposal. Move
forward, assuming the community agrees.
I'd really like to see particular tests run only when the PR is
touching a related part. While this is more
Hi Ciyong, thanks for the proposal.
I like your suggestions. Will you be submitting a PR?
Some feedback:
* Regarding changing the URLs, let's avoid that. We just had a lot of
work trying to fix broken links.
* As far as changing the headings, sure, Tutorials and FAQs makes sense.
* Adding
This note is about two things:
1. I added a CI pipeline for contributors to test their website & docs
changes on the staging site [1]. To speed it up, it only generates the
Jekyll and Python API parts of the site. Usage info is in the PR's [2]
description. I was going to add a guide for this on
r properly, for example - forward function,
> > backward function and shape inference.
> >
> >
> > Thanks
> > Anirudh
> >
> >
> >
> >
> > On Wed, Sep 25, 2019 at 7:53 AM Aaron Markham
> > wrote:
> >
> >> I'm seeing GA
; > > >>> > > >
> > > >>> > > >
> > > >>> > > > I suggest you do a scan of the new website to find these
> > dangling
> > > >>> links.
> > > >>> > > >
> > > >>>
Alrighty! The new site is launched. You might need to clear your cache.
Cheers,
Aaron
On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham wrote:
>
> Thanks everyone. The PRs passed CI, but please continue holding off on
> docs and CI edits. Unless there are any objections, I'd like
Thanks everyone. The PRs passed CI, but please continue holding off on
docs and CI edits. Unless there are any objections, I'd like to launch
the new website today.
On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham wrote:
>
> Hi everyone,
> The last two PRs [1][2] for the new website and
Hi everyone,
The last two PRs [1][2] for the new website and docs have passed CI
(finally). Please do not make changes to /docs or /ci until we get
these approved and merged. Every time there's a merge conflict it has
set us back a day or two while shepherding the PRs through CI again.
Unless
I went down the path for this and was disuaded by the errors I had and the
open issues about the same errors. It's one thing to leave something around
that works, but another to leave something around that wastes a lot of time
and causes abandonment.
The project needs a mobile solution. What's
gt; Nowadays Github pages + pkgdown combination is getting more and more
> > popular so we would see a trend soon towards web hosted docs for R
> > packages.
> >
> > On Thu, Aug 29, 2019 at 8:58 PM Aaron Markham
> > wrote:
> >
> > > pkgdown makes some nice
cally generated the
> documentation pages (tutorials, API reference, etc.). I've seen huge
> adoption of this package being used for documentations in the R community.
>
>
> On Thu, Aug 29, 2019 at 8:26 PM Aaron Markham
> wrote:
>
> > Hi everyone,
> >
> > I'm very exci
Hi everyone,
I'm very excited to share a preview and the pull requests for a new
website and new documentation pipelines.
The following link is using Apache's new staging site setup. It is
built from the new docs publishing pipelines in CI where a Jekyll
website is built, and documentation
I have an open issue about gathering data per platform install so there can
be an informed discussion on prioritization or even cutting platforms.
Until then... I wouldn't cut one.
I would like to hear the pros and cons for dropping some native platform
support in favor of containers. But... For
frontend can help to cherry pick the commits to the v1.5.x branch.
>
> thanks,
> -tao
>
> On Wed, Aug 28, 2019 at 11:43 PM Aaron Markham
> wrote:
>
> > I don't see any request for action on the Julia PRs: 5 or 6.
> > We didn't put the change in right away bec
I don't see any request for action on the Julia PRs: 5 or 6.
We didn't put the change in right away because we wanted it to not break
anything. But the changes are needed to make Julia setup more seamless.
What "update" is needed?
On Wed, Aug 28, 2019, 08:36 Tao Lv wrote:
> @Pedro, seems the
dentified issue with the docker cache:
> > https://github.com/docker/docker.github.io/issues/8886
> >
> > We can get a short term workaround for #1 by explicitly pulling bases from
> > the script, but I think docker should do it when using --cache-from so
> > maybe contribu
One use case I'm thinking of here would cover the generation of docs
for different versions. The problem I'm running up against right now,
is that in the pending PR to update the docs workflows, I have all of
this new logic and processes, but I can't run it against an old
branch, because once I
u are saying that the Docker cache
> doesn't work properly and regularly reinstalls dependencies? Or do you mean
> that you only have cache misses when you modify the dependencies - which
> would be expected?
>
> -Marco
>
> On Fri, Aug 16, 2019 at 12:48 AM Aaron Markham
> wrote:
&
a storage solution to make that happen. We can't
archive every intermediate artifact for each PR.
On Thu, Aug 15, 2019, 13:47 Pedro Larroy
wrote:
> Hi Aaron. Why speeds things up? What's the difference?
>
> Pedro.
>
> On Wed, Aug 14, 2019 at 8:39 PM Aaron Markham
> wrote:
&g
pload the entire folder that is
> being created. Is there anything specifically you're looking for?
>
> * That's awesome!
>
> Best regards,
> Marco
>
> On Thu, Aug 15, 2019 at 8:52 PM Aaron Markham
> wrote:
>
> > I'll start a different thread about the website. S
Ouch. Someone either didn't file a trademark, or do a trademark
search. Or they don't care because there's no trademark. I'd forward
this to Apache legal.
+ Hen for advice.
On Thu, Aug 15, 2019 at 11:54 AM Carin Meier wrote:
>
> Gluon came up in one of my feeds in the context
gt; --Patric
>
>
> > -Original Message-
> > From: Aaron Markham
> > Sent: Thursday, August 15, 2019 11:40 AM
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: CI and PRs
> >
> > The PRs Thomas and I are working on for the new docs and
The PRs Thomas and I are working on for the new docs and website share the
mxnet binary in the new CI pipelines we made. Speeds things up a lot.
On Wed, Aug 14, 2019, 18:16 Chris Olivier wrote:
> I see it done daily now, and while I can’t share all the details, it’s not
> an incredibly complex
ing the thread/doc where we discussed the
> requirements for the new website?
>
> -Marco
>
> On Thu, Jul 18, 2019 at 9:49 PM Aaron Markham
> wrote:
>
> > I agree with you. I'd like the website to be fairly standard Jekyll and
> > normal front end stuff, rather than a
version for every single build - that's not necessary.
>
> Considering how many people are unable to use the latest version of MXNet,
> I'd prefer if we provide the docs as long as the release binaries are
> available.
>
> -Marco
>
> Aaron Markham schrieb am Do., 18. Juli 2019,
>
will be too difficult and disruptive.
On Tue, Jul 16, 2019, 16:41 Marco de Abreu wrote:
> While we are at it, we should maybe also take about SSL to avoid these
> kinds of downloads in future.
>
> -Marco
>
> Aaron Markham schrieb am Mi., 17. Juli 2019,
> 01:20:
>
> >
github.com/dmlc which is well known and iiuc in process for
> resolving.
>
> Hen
>
>
> On Tue, Jul 9, 2019 at 4:46 PM Aaron Markham
> wrote:
>
> > The PR has passed CI. Please take a look.
> > https://github.com/apache/incubator-mxnet/pull/15454
> >
th
> the MD plugin of Sphinx.
>
> Iblis Lin
> 林峻頤
>
> On 7/4/19 12:12 PM, Aaron Markham wrote:
> > Hi dev@,
> > In case you missed the issues with the dmlc.ml domain, it was let go
> > or sniped and now goes to a malware site. [1] Several assets like
> > models a
Hi dev@,
In case you missed the issues with the dmlc.ml domain, it was let go
or sniped and now goes to a malware site. [1] Several assets like
models and the Julia documentation were hosted there.
I made some progress getting the Julia docs generated as part of the
regular website build flow.
l find the
> first commit in which the navbar is broken.
>
> On Wed, Jun 12, 2019 at 6:26 PM Pedro Larroy
> wrote:
> >
> > I would suggest bisecting to find when the navbar was gone. I have a
> > python script that I use for bisecting that I can offer.
> >
Hi everyone, there's an issue with the navigation for master. When
you browse any of the API docs, the left nav is gone.
Here's the issue: https://github.com/apache/incubator-mxnet/issues/15200
If anyone has ideas, I'd love to hear them.
In the meantime, people browsing the docs are going to
-1
There's an autogenerated file that doesn't get cleaned up in the
scala-package folder when you run make clean. This causes the scaladoc
step to fail. I'm putting in workaround messaging in the error message
and that'll go into master, but if anyone wants to specifically run
the scaladocs for
Hi everyone, I was fixing some broken links on the contribute page[1]
today and noticed that one was for the Slack channel archive[2]. It
doesn't appear to be there anymore, so I'm removing the link for now.
Should the archive situation be investigated?
[1]
and
> > > some pip wheels are available, but there are known performance issues. And
> > > we are quickly moving to CUDA 10.1. So things are still in flux now. I
> > > think the best approach would be to wait a couple more weeks before
> > > updating this part of th
I sent you all invites. Join #mxnet once you're in!
On Fri, May 24, 2019 at 1:37 PM Bossi, Marcelo
wrote:
> Hi Marc,
>
>
>
> I believe you need to send a Slack request to:
> dev@mxnet.incubator.apache.org.
>
>
>
> Please let me know if you don’t get access by mid next week. I will track
> it
What version of CUDA is currently recommended?
Now that there are packages for CUDA 10, shouldn't the build from
source (and other) documentation reflect the latest greatest
combinations?
Specifically the Ubuntu guide [1] states: "CUDA 9.2 is recommended."
[1]
Congrats Darren!
On Thu, May 23, 2019, 18:48 Zhao, Patric wrote:
> Congratulations, Darren :) Thanks for your great works in Horovod.
>
> > -Original Message-
> > From: Chaitanya Bapat [mailto:chai.ba...@gmail.com]
> > Sent: Friday, May 24, 2019 9:46 AM
> > To:
Congrats Aston.
On Thu, May 23, 2019, 18:45 Chaitanya Bapat wrote:
> Congratulations Aston! Your book is fantastic!
>
> On Fri, 24 May, 2019, 12:50 AM Sheng Zha, wrote:
>
> > Hi all,
> >
> > Please join me in welcoming Aston Zhang as a new committer of Apache
> MXNet
> > (incubating)!
> >
> >
Thanks for doing a thorough look at the version ranges. I have this PR
[1] waiting for review that tries to pin graphviz and opencv, and it
updates CI as well as the docs that go on the website.
I think your updates would be beneficial in the docs that go on the
website and should also update CI.
+1 for the pledge and to start moving things to Python 3.
I think our installation instructions and tutorials can be updated to
default to Python3 and we should update Python2-only tutorials. I know
we have a handful of those, and when I spot them, I'll create an
issue.
I can also look at
A new feature: https://help.github.com/en/articles/locking-conversations
So someone must have locked it. I can see the option on the right hand
side column, all the way at the bottom. You will probably have the
ability to unlock it from there too.
On Thu, May 9, 2019 at 3:42 PM Chaitanya Bapat
One option is Amazon Educate. https://aws.amazon.com/education/awseducate/
Last I checked, you can get $75/month AWS credit as a student or
educator. If you belong to an educational organization, your org can
apply on your behalf and get anyone with that org's domain easier
access to the credits.
Make that +1 (non-binding)
On Wed, May 1, 2019 at 3:42 PM Aaron Markham wrote:
>
> +1 (binding)
>
> * Built with GPU and tested the first part of the ssd example.
> * Built with GPU / cross-compiled to arm8 for Jetson.
> * Built Scala/Java on top of the cross-compiled arm8
+1 (binding)
* Built with GPU and tested the first part of the ssd example.
* Built with GPU / cross-compiled to arm8 for Jetson.
* Built Scala/Java on top of the cross-compiled arm8 (ran into trouble
here, but I think this is not popular enough yet to derail things,
plus there are workarounds)
*
Hello everyone!
I've been pecking away at adding content to the beta site. Take a look
and let me know what you think. Right now, I'm focused 100% on the
content and the organization thereof.
One feature I thought would be great for the API docs would be to
cross-reference usage of a particular
Just curious about when this kind of change will land. Would it wait for
2.0 or would it be in 1.5 or another minor release?
On Thu, Apr 11, 2019, 00:15 Junru Shao wrote:
> Really nice improvement over MXNet's usability! I suggest that we could
> make numpy-compatible behavior default in 2.0.
>
+1
Reduced complexity. Choice of math library... Hopefully you can just
install MKL and not be forced into mshadow's dependency on OpenBLAS. This
could make Windows setup easier.
Maybe this issue will get fixed: #11769.
On Sun, Apr 7, 2019, 00:51 Junru Shao wrote:
> Does merging mshadow into
I am disappointed when I see articles that use Gluon, but don't mention
MXNet [1]. If MSFT or anyone had actually run with it and made Gluon an
interface for another framework, this would be a different matter. There
are more references to Gluon without MXNet [2] than there are to Gluon with
MXNet
Anton, can you share the design and specs and code for the robot arm demo?
I wish that was being shown at GTC now. It would be great to let people
borrow it for West coast events. Maybe I can get one built here in Palo
Alto.
On Tue, Mar 19, 2019, 05:54 Anton Chernov wrote:
> I don't know
I sent you an invite. Welcome!
On Thu, Mar 14, 2019 at 7:24 AM Ge wrote:
> thanks.
>
---
>
> Page Not Found
> We can't find that page. This could be because:
>
> The page doesn't exist.
> The page exists, but you don't have view permission for that space.
>
>
>
> I have checked that I'm logged in.
>
> Best
> Anton
>
> чт, 7
This is great. It will help drive traffic to the site, create content for
the site, and increase engagement. MailChimp is pretty good too. I can help
set that up. I have one tiny nagging question though... I don't recall
doing any GDPR compliance stuff on the site, so I'm wondering what kind of
Thanks Aston.
For contributors interested in helping improve the website's UX and design:
I spent some time learning the Material Design ecosystem as the beta site
uses this as its template. From there I refactored the wireframes using
Sketch + Material Design plugin and added them to
--force flag [1] to override
> > > the needed parts. That would allow to provide a 'default' version of the
> > > documentation, that could be adjusted where needed.
> > >
> > > Best
> > > Anton
> > >
> > > [1]
> > &
I'd like to see if we can get designers involved. I noted that there are
some boot camps for UX and design. They pick up projects for class to
design a brand or a new site or service. Why not get them involved with
open source? Apache has a lot of projects with sites that could use help,
and ours,
I sent you an invite.
On Thu, Feb 28, 2019 at 7:11 AM Bazan, Ivy wrote:
>
> I’d like to request an invitation to the #mxnet Slack channel.
Hi everyone,
A recent issue and pending PR has brought a thorny docs situation to
my attention again and I'd like to hear from the community on how to
proceed.
We currently get some of the docs for the Python API pulled out of .cc
files. Other APIs also get docs from there, or pull the Python docs
Sheng, thanks for being so proactive, but adding license headers to
the markdown files in #14142 breaks the website as I warned. I caught
it before it went live.
I've disabled website publishing until this situation is resolved.
On Wed, Feb 13, 2019 at 10:59 AM Sheng Zha wrote:
>
> Update: All
rty files from the RAT check is fine, but not files
> > originating from the MXNet repo.
> >
> > It would be good to know exactly how Luciano ran the RAT check, cc'd.
> > Here
> > is a link to the thread
> >
> > https://lists.apache.org/thr
This is really great research. I've often wondered what the difference
really is, and why it has to be so complicated. It seems the answer is
there isn't much difference and it shouldn't be as complex.
As for your next steps, would you propose that cmake be brought up to
parity? It seems strange
build process as part of these efforts, right?
>
> Best regards
> Marco
>
> Am Di., 5. Feb. 2019, 01:22 hat Aaron Markham
> geschrieben:
>
> > Hello MXNet folks!
> >
> > As I mentioned last week, I'm soliciting feedback on a website
> > redesign. Some of you
Hello MXNet folks!
As I mentioned last week, I'm soliciting feedback on a website
redesign. Some of you may have seen the beta site that Mu has been
working on, which is a big step in the right direction for the
automatically generated API docs. I've posted a wiki article [1] that
proposes how to
+1 I built the full website including the branch and it was fine.
On Wed, Jan 30, 2019, 22:39 kellen sunderland +0
>
> Overall release looks good. Probably something I'm doing wrong, but so far
> not able to validate the .asc. I'm getting "Can't check signature: No
> public key". I've added
Congrats on the Horovod integration everyone. That's really great to hear.
On Wed, Jan 30, 2019 at 10:08 AM Lin Yuan wrote:
>
> Hi Yuan,
>
> Thanks for your interest. We have just supported MXNet in Horovod and are
> working on performance tuning and adding more examples. We are definitely
>
Hello dev folks! I thought I'd let you all know some of the recent
updates related to the website, docs & related features.
MXNet CI and website build pipeline
We had few blips last week from where GitHub was unreachable. The red
block in the trend graph [1] is from the previous week’s
now
> moved to https://xxx.html; to redirect users, when this kind of reorg
> happens.
>
> Best,
> Haibin
>
> On Fri, Jan 18, 2019 at 4:50 PM Aaron Markham
> wrote:
>
> > +1 but note that this is probably going to create a bunch of broken links
> > on the M
+1 but note that this is probably going to create a bunch of broken links
on the MXNet website and maybe elsewhere. Should make time to deal with
that in this process.
On Fri, Jan 18, 2019, 12:43 Carin Meier +1 Great idea
>
> On Fri, Jan 18, 2019 at 2:38 PM Sheng Zha wrote:
>
> > Hi MXNet,
> >
I've been trying to diagnose issues with some of the CI pipelines and one
blind spot in the reporting is in the stages - we'll have timing info on
the first couple of parts and maybe the last part, but the lion's share is
in one big part in the middle. It'll say 45 minutes, or jump to an hour,
and
w do I join the
> #mxnet channel?
>
> Thanks a lot!
> Istvan
>
> On 1/4/19, 5:44 AM, "Aaron Markham" wrote:
>
> I sent you an invite.
> Cheers,
> Aaron
>
> On Fri, Jan 4, 2019 at 1:12 PM István Fehérvári
> wrote:
>
> &g
I sent you an invite.
Cheers,
Aaron
On Fri, Jan 4, 2019 at 1:12 PM István Fehérvári wrote:
> Please add me to the slack channel.
>
> Thank you,
> Istvan
>
Hi Istvan,
You can make a page here:
https://cwiki.apache.org/confluence/display/MXNET/Website+Update+Proposals
If you don't have an account yet you can sign up, and then we can check on
edit access.
Also if you're not on slack yet, please join and we can also chat there.
With regard to the
Marco, thanks for your hard work on this. I'm super excited about the new
Jenkins jobs. This is going to be very helpful and improve sanity for our
PRs and ourselves!
Cheers,
Aaron
On Wed, Nov 21, 2018, 05:37 Marco de Abreu
Hello,
>
> the CI is now back up and running. Auto scaling is working
to get around the issue. For the next
release, we could upgrade scala in the dependencies and provide a
little better cross-platform support, but either way it shouldn't
happen in v1.4 since it's already patched in master.
Cheers,
Aaron
On Sat, Nov 17, 2018 at 1:05 PM Aaron Markham wrote:
>
> W
Website and docs for 1.3.x branch is working fine. However...
Two things to note that could be blockers:
1) The Scala API going out with the JavaAPI bundled inside it:
/api/scala/docs/index.html#org.apache.mxnet.javaapi.package - this is
fixed in master with #13071.
2) `make docs` doesn't work
e testing to the example when you touch the example - at the
> least to check the functionality. These can be run once a week.
>
>
> On Tue, Nov 13, 2018 at 6:52 AM Aaron Markham
> mailto:aaron.s.mark...@gmail.com>>
> wrote:
>
> I've been actively promoting moving ex
I've been actively promoting moving examples to tutorials during reviews.
That way they fall under the testing umbrella and get added to the website.
Many times there's not really a great distinction as to why something is in
the examples folder, other than it's like a graveyard of untested
Hi Anirudh,
Once the existing errors in docs building are cleaned up, I'm all for
having CI bubble up a build break when docs are broken by a PR. That
way we're keeping things up to date and not letting a minor bug turn
into a serious issue for the entire API documentation. One break
causes a
+1 non-binding
One minor thing first: can you define PPMC in the doc? It's brought in
without saying what it stands for. Even the link it goes to just talks
about PMC and there's no mention of PMCC... so I'm not sure what the
definition is.
On Tue, Oct 30, 2018 at 8:07 AM Carin Meier wrote:
>
Hello everyone!
I'm writing this note to raise awareness about some issues I'm seeing with
the Python API docs. While some of the issues can be traced back prior to
v1.3.0, the biggest issue of docs not rendering is fairly recent.
At a high level, Sphinx (our Python API docs generator) is getting
Thanks Marco, this is a great feature. I didn't see git listed under "when
to use this guide". Can we use this to access git credentials like for when
we publish the website?
Cheers,
Aaron
On Wed, Oct 17, 2018, 06:19 Marco de Abreu
wrote:
> Hello,
>
> I have just published a new guide how to
+1 to rebase and merge to retain the efforts of all of the contributors. If
there's some git maintenance that can trim it down from 700+ commits then
maybe that's a compromise.
On Wed, Sep 26, 2018, 21:23 Naveen Swamy wrote:
> this PR comes from more than 1 individual, if we squash merge we'll
>> >
> >> >
> >> > On Tue, Aug 21, 2018 at 11:57 AM Lin Yuan
> wrote:
> >> >
> >> > > Hi Aaron,
> >> > >
> >> > > Thanks for your answer. I think it's a very worthwhile effort to
> move
> >> all
> &
I'm looking at, even if it's been renamed or
> moved around). I feel like it can be a great internship project. - Sina
>
> On 9/18/18, 5:08 PM, "Aaron Markham" wrote:
>
> Hello dev list!
>
> I've been doing a bit with .htaccess redirects on the site to get us
&g
I find it unintuitive that mxnet-mkl doesn't actually ship with MKL. Why
isn't it called mxnet-mkldnn instead?
Side note, if mkldnn fulfills BLAS requirements, then why can't we strip
out OpenBLAS for the "mxnet-mkl" package? Is there no way to make the
submodules conform to using mkldnn? All in
cket so that our mentors just have to create it?
>
> I think we could ask Infra for an investigation about *why* this happened,
> considering the fact that it should be an exact mirror, and tools to
> self-service these kind of things.
>
> -Marco
>
> On Wed, Sep 19, 2018 at 4:
Thanks for this translation and feedback Qing!
I've addressed point 3 of the documentation feedback with this PR:
https://github.com/apache/incubator-mxnet/pull/12604
I'm not sure how to take the first two points without some explicit URLs
and examples, so if anyone has those I'd be happy to take
It's not on the site repo. Seems like it is only on the Apache infra. Can
someone request it's removal?
On Tue, Sep 18, 2018, 20:34 Hagay Lupesko wrote:
> The /test site seems to be something old that should have been removed a
> long time ago, it lists versions 0.10 and 0.10.14 :)
> Maybe
Hello dev list!
I've been doing a bit with .htaccess redirects on the site to get us things
like custom 404s and redirecting google searches that come in on outdated
material. That's working pretty well because the redirects are simple.
I need help though. I've written a short proposal on how I
1 - 100 of 143 matches
Mail list logo
