new website, docs code freeze

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 there

Re: new website, docs code freeze

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

Re: new website, docs code freeze

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 t

Re: new website, docs code freeze

; > >>> > > > https://mxnet.incubator.apache.org/ubuntu_setup.html > > > >>> > > > > > > >>> > > > > > > >>> > > > I suggest you do a scan of the new website to find these > > dangling > &g

Re: new website, docs code freeze

render 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

Re: new website, docs code freeze

; - There is no version selector for the docs > > > >> > >>> > > > > - There is bug in search box of the python docs, but > > this > > > is > > > >> > just > > > >> > >>> > > > > a > > > >

move DNS for beta.mxnet.io

Now that google analytics is back on the site I'm seeing that about half of "mxnet" traffic is still going to beta.mxnet.io. This should point that back to mxnet.apache.org instead to consolidate the audience. Page load time has decreased by 32% and download time down 93% which is great. But for s

CI/website tests & user guidance

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 Dev

Re: Proposal for MXNet website improving

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 perform

Re: Update on upcoming changes to the MXNet CI: Jenkins

+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

Re: [ANOUNCEMENT] New PPMC Member Thomas DELTEIL

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

Re: [apache/incubator-mxnet] [RFC] New Branches for MXNet 1.x, 1.7.x, and 2.x (#17701)

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 author

Re: [apache/incubator-mxnet] [RFC] New Branches for MXNet 1.x, 1.7.x, and 2.x (#17701)

@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

Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 API Deprecation (#17676)

> Thanks @zachgk - I took a couple of screenshots so I could share here > > Here is the Scala package >  > > and here is the Clojure package > ![clojure-mxnet-downloads](https://user-

Re: [NOTIFICATION] CI Restart

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 ha

Re: CI Pipeline Change Proposal

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

Re: CI Pipeline Change Proposal

; > marco.g.ab...@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 > > >

Re: CI Pipeline Change Proposal

at 1:12 PM Lausen, Leonard > > > > > 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

Re: CI Pipeline Change Proposal

0, 00:55 Marco de Abreu wrote: > What about 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

site speed and content translation

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

Re: site speed and content translation

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

Re: [Announcement] New Committer - Sam Skalicky

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

Re: Display the master branch website in default for a period

Do you have specific public benchmarks in mind? On Mar 1, 2018 10:13, "Barber, Christopher" wrote: > I think one thing that could draw more users would be published benchmarks > that show that networks implemented using MXNet perform better than > comparable ones using other platforms using the

404 issues

I've been notified by several parties about 404s for files that are now longer available on the site. https://github.com/apache/incubator-mxnet/issues/9917 This page returns 404: https://mxnet.incubator.apache.org/api/python/module.html It was moved here: https://mxnet.incubator.apache.org/api/py

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

I'm not quite sure if I have enough background on reasons for or against this to vote in the next round, but my two cents: I didn't see much debate on why we need yet another tool for issues that we have to manually maintain...the vote kind of slid in there without many stakeholders realizing what

Re: Display the master branch website in default for a period

build > and publish process, so input like this is definitely helpful. This > could > basically be summarized as a requirement to make the website contain > static > parts (e.g. APIs and documentation) as well as dynamic parts (e.g. > news, > statistics, recent p

Re: Display the master branch website in default for a period

Embedding images doesn't work, I guess. Here's a link to the chart. https://drive.google.com/file/d/1GzxDEhF6tx9_bsFc4LuUzgoIaMSiEV5s/view?usp=sharing On Tue, Mar 20, 2018 at 9:24 AM, Aaron Markham wrote: > I would like to get a sense of people's feelings with regard to ac

Re: MXNet Name Change?

Changing branding is hard as we already have some momentum under the current name. It's not impossible, and if someone has a fantastic idea and marketing plan for it, it's worth considering. Aside from that, updating the pronunciation could be useful if you like having those gif vs jif debates, bu

blog for MXNet

Having a blog for MXNet would be very useful for conveying news, talking about features, demoing applications, and building awareness. Does anyone have particular preferences or recommendations on blog hosting or platform? I currently have editor access for an MXNet branded account on Medium. htt

Re: blog for MXNet

ld be happy to contribute to the blogs, if you want to add me >> > > to the writer/editor list. >> > > >> > > >> > > >> > > Also, there is a mxnet subreddit r/mxnet which was created by >> > > Sebastian >> > > (thanks

mxnet.data.io is gone!?

So anyone know what happened? It's a critical resource for datasets and examples and more... and all the files seem gone. http://data.mxnet.io/ That's show forbidden... which is unusual. Then any resource like http://data.mxnet.io/models/imagenet/squeezenet/ is missing.

data.mxnet.io is gone (correction)

So anyone know what happened? It's a critical resource for datasets and examples and more... and all the files seem gone. http://data.mxnet.io/ That's show forbidden... which is unusual. Then any resource like http://data.mxnet.io/models/imagenet/squeezenet/ is missing.

mxnet.io website publishing

I've updated Jenkins CI and the docs build scripts with #10485 . The CI run to build the website with the latest docs has completed successfully , and it deploy

Re: mxnet.io website publishing

ocess. (Thanks for the idea, Marco). Cheers, Aaron On Wed, Apr 25, 2018 at 2:16 PM, Aaron Markham wrote: > I've updated Jenkins CI and the docs build scripts with #10485 > <https://github.com/apache/incubator-mxnet/pull/10485>. The CI run to > build the website with the

Re: Pre-release versions on website

Hi Marco, Putting 1.2.0 was meant to allow a preview and for testing, but I see how this can cause confusion. Change the names and/or hiding the RC is possible with some refactoring of the site build scripts. I'd be happy to take a look at this. I think another solution could be: 1. create pip in

Re: Pre-release versions on website

. #3 in combination with #1 > sounds > > like > > a good idea. > > > > In the meantime, we could just patch the install page for 1.2.0 and a > > big > > red warning message that states that this a release candidate and > that > > the > &

installation page UX

Hi, I've written some notes on the wiki about issues with the installation page along with some suggestions. I'd appreciate your feedback here or on the wiki. https://cwiki.apache.org/confluence/display/MXNET/Installation+page+UX Cheers, Aaron

Re: MXNet issues labeling

AI obviously. On Mon, May 21, 2018 at 5:01 PM, Anirudh wrote: > Hi Roshani, > > Good suggestion! How will the bot decide what labels to add ? > > Anirudh > > On Mon, May 21, 2018 at 4:39 PM, Naveen Swamy wrote: > > > +1 for the proposal to triage issues, I think committers should also do > > th

Re: Introduction of restricted slaves and jobs

Thanks Marco, this is a welcome improvement. On Fri, May 25, 2018, 05:56 Marco de Abreu wrote: > Hello MXNet community, > > I'd like to announce the launch of restricted slaves and jobs for our CI > system. > > The purpose of this feature is to allow separating slaves that execute > arbitrary c

Good First Issue label

Just wanted to bring everyone's attention to the label: Good First Issue. When you're going through new issues and labelling, keep this one in mind, so there are opportunities for new members to the project. I think a lot of people would like to contribute, but often the issues are so complex they

installation page UX update

Hi everyone, @kpmurali (Krishnan) has worked on some of the initial feedback for the install UX. He has this preview link: http://54.210.6.225/install/index.html?version=v1.2.0&device=Windows&language=Python&processor=GPU It has a couple nice features: * When you choose different install paths, it

home page highlights section updates

Hi everyone, happy Friday, I've mocked up a couple of modifications for the highlights on the home page. The goal is to expose more news, more tutorials, and other interesting things people have been working on. If you've contributed something interesting and want to highlight it, you should be ab

Re: home page highlights section updates

; various events. > > > On Sat, Jun 2, 2018 at 12:57 AM, Aaron Markham > wrote: > > > Hi everyone, happy Friday, > > > > I've mocked up a couple of modifications for the highlights on the home > > page. > > The goal is to expose more news, more t

Re: PR validation and runtime of CI

I'd like to disable flaky tests until they're fixed. What would the process be for fixing a failure if the tests are done nightly? Would the commit be reverted? Won't we end up in the same situation with so many flaky tests? I'd like to see if we can separate the test pipelines based on the conten

Re: Github link on MXNet Homepage

What about a GitHub icon instead the word? Could also use a per page GitHub link to take you to the current page's code on GitHub instead of just a link to the project home. I like how docker does a similar thing to solicit feedback and contributions. On Thu, Jun 7, 2018, 10:18 Marco de Abreu wr

Re: Regarding 1.2.1 patch release

Hi Anirudh, Marco brought my attention to CI failures on the 1.2.1 builds with regard to docs. The failures are because the build scripts that are in the 1.2.0 branch are out of date and have problems due to package updates that are incompatible with each other. To fix this you'll need to bring al

landing pages for the website

Hi dev@, We've had a lot of great expansions to MXNet's functionality and family of tools in recent months. I would like to gauge the temp on what would be good to highlight, and what would be good as navigation items with actual landing pages. For example, when ONNX was added, being in a contrib

Re: test/versions in the website

It's not on the repo. https://github.com/apache/incubator-mxnet-site/tree/asf-site/test Must be sitting on the server. Maybe infra can take a look. On Wed, Jun 13, 2018 at 2:38 PM, Naveen Swamy wrote: > I think this was some testing during migration to Apache infra, I think it > probs is sittin

Re: Update on 1.2.1 release

I'd keep an eye on this one... Flaky test: test_gru_bidirectional #11219 https://github.com/apache/incubator-mxnet/issues/11219 Just reran several PR's CI runs that all had the same error! On Wed, Jun 13, 2018 at 5:42 PM, Anirudh wrote: > Hi, > > PRs still in progress : #11127, #11236, #11210

Re: Request for Sign up

Hi, Have you checked out this page? https://mxnet.incubator.apache.org/community/contribute.html The dev comm section has info on how to subscribe to the mail list. I think Steffen already added you to slack. On Fri, Jun 15, 2018, 16:33 Kalyanee Chendke wrote: > Hello, > > Bumping this up. I w

Re: landing pages for the website

into MXNet, otherwise, it may > make > > > the MXnet docs have too many dependencies and hard to maintain. We may > > just > > > create an "ecosystem" page to add links to all high-quality 3rd party > > > libraries. > > > > > > On Mon,

Re: Abandoned MXNet readthedocs site

If they could redirect to the official website that would be ideal. Otherwise, we'd be supporting yet another doc outlet and possibly run into the same problem of it getting out of sync and being incorrect. On Jul 5, 2018 10:32, "Craig Russell" wrote: Peanut gallery please ignore if off topic.

Re: Squash/Merge PRs

This is a great discussion, and close to my heart, because I want to include more writers and editors in our community, and I'm struggling to see how to best manage this. It seems like being the sole contributor on a feature is like an engineer's Lone Ranger badge of pride! I feel like it should b

Re: Squash/Merge PRs

ful, which was exactly what I was saying in my previous > email. Thanks! > Hao > > On Thu, Jul 12, 2018 at 8:16 AM, Aaron Markham > wrote: > > > This is a great discussion, and close to my heart, because I want to > > include more writers and editors in our community

Re: Squash/Merge PRs

or not) and add other contributors as > > > > > > co-authors. > > > > > > > > > > > > > > > > @Marco, co-author might not be suitable always suitable and > agree > > > > > with > > > > > > > Hao > > > > > > > >

Re: [VOTE] Subscribe dev@ to Github Activities

+1, I don't read your emails anyways. Just kidding. I think it would be good to see the action, even if I eventually have to setup filters if it gets overwhelming. On Tue, Jul 17, 2018 at 9:15 AM, Tianqi Chen wrote: > +1, most of issue and PR activities are about development, and they belong > t

Re: ApacheCon is just 60 days away. Are you ready?

Floating a couple ideas about this... 1) could add it to the home page in the space to the right of "learn more". 2) could add it to a news page or events page (after creating said page) 3) should definitely add it to the meetups and events page in the wiki On Jul 26, 2018 10:16, "Naveen Swamy"

custom 404 and other error landing pages and server logs

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

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

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

Re: Significant windows build improvements from source

I followed the directions and got stuck on OpenBLAS. Then I tried to just use MKL, but then mshadow build threw an error saying it required OpenBLAS. #11769 That whole part can really use some clarification. On Sat, Aug 4, 2018, 05:21 Pedro Larroy wrote: > Hi Qing > > The problem you are facing

social media promotion / menu

Hi dev, I've been asked a variety of times how we can improve social media awareness on the site. We kind of had a social section, but it was really only evident on the contribute page. Sharing any page now results in a decent preview image. To help raise awareness of our different media channels

Re: Consolidating developer guide in one place (cwiki preferred)

Hi Lin, I agree with this organization. If you feel like somethings should be transitioned from the website to the wiki, I can help with that, but for the moment I've been suggesting that new developer-focused content be placed on the wiki. On Tue, Aug 14, 2018 at 10:40 AM, Lin Yuan wrote: > Dea

build from source instructions

Hello, I was looking into the C++ instructions and came across this seemingly pretty old page: https://mxnet.incubator.apache.org/install/build_from_source I think it has several inaccuracies as different/updated installation info has been added to different pages. Should it be deleted? Or shoul

Re: build from source instructions

t; > instruction. Why was it vastly different from building from source > on > > > Linux > > > given these two OS have similar shell commands. I feel the > automatic > > > scripts on MacOS platform is rather confusing than simplifying. > &g

Re: [LAZY VOTE] Consolidating developer guide in one place (cwiki preferred)

t; Thanks for your answer. I think it's a very worthwhile effort to move all > > the developer related content from mxet.io website to a dedicated > > developer > > site. Would you like to initiate this effort? > > > > Best, > > > > Lin > > &

Re: [VOTE] Release MXNet version 1.3.0.RC0

0 (non-binding) If we have a problem that blocks users, and a solution in hand... then we should fix it, but not at the expense of starting the release cycle again just for one fix. Users can cherry pick or build from master if they want the fix right away, right? I'd change my mind to -1 if this w

Re: [DISCUSS] Build OSX builds in CI (possibly with TravisCI).

Is there any way to make it not show a red X failure in the GitHub UI when TravisCI fails? I keep going back to check what flakey test failed this time and realizing that Jenkins is still running and it was the "not required" Travis fail. The green checkmark makes me happy and it's easier to keep a

improving API docs and tutorials user experience

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 t

Re: multiple installation guides?

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 Aaron

Re: Some feedback from MXNet Zhihu topic

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 a

Re: multiple installation guides?

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:

Re: Remove MKLML as dependency

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 t

Re: improving API docs and tutorials user experience

tches the content 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

Re: [LAZY VOTE] Consolidating developer guide in one place (cwiki preferred)

revisit on Delete permissions. > >> > > >> > > >> > 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

Re: Which merge option to use on the Import Julia binding PR?

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

Re: New MXNet CI guide: Managing and accessing credentials

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 man

Python API docs issues

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

Re: [VOTE] - Adopt "Become a Committer and PPMC Member" Document

+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: > F

Re: [Announce] Upcoming Apache MXNet (incubating) 1.3.1 patch release

Hi Anton, I have the following suggestions for fixes to include in 1.3.1. These each have updates to files that will impact docs generation for the 1.3.x version of the website's Python API docs: https://github.com/apache/incubator-mxnet/pull/12879 https://github.com/apache/incubator-mxnet/pull/12

Re: Run Sphinx checks on MXNet CI

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 ripp

Re: Nightly/Weekly tests for examples

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 sample

Re: Nightly/Weekly tests for examples

s to add some 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 pro

Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0

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 whe

Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0

pdate in mxdoc.py 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 Aar

Re: CI impaired

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 as

Re: Running CI for doc changes

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

Re: joining slack channel

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 >

Re: joining slack channel

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

CI reporting & diagnostics improvements

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

Re: Taxonomy on our cwiki

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

Re: Taxonomy on our cwiki

> 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

website, docs & related features updates

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 subprocess

Re: Horovod-MXNet Integration

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

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

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

website updates & redesign

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

Re: website updates & redesign

vamp the website 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 > >

Re: Benchmarking MXNet with different compilers and different OpenMP implementations (results)

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 th

Re: [RESTARTING][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

+1 I disagree about 3rd party considerations. This is an ecosystem after all. The distributed training story is quite nice with Horovod. Given my interaction with tensorflow with Horovod and dynamic training with MXNet and the kvstore, this new route is, IMO, easier to setup and manage. I see the

Re: [RESTARTING][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

tent.com/apache/incubator-mxnet/master/README.md. > > Excluding 3rd party 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 &

Re: [RESTARTING][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

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 l

  1   2   >