Proposed Board report

Thoughts? - MXNet MXNet is an open-source deep learning framework that allows you to define, train, and deploy deep neural networks on a wide array of devices, from cloud infrastructure to mobile devices. It is highly scalable, allowing for fast model training, and supports a flexible

Blog posting

Writing the report reminded me that my dayjob worked with Sally (VP Marketing & Publicity for Apache) on a blog posting: https://aws.amazon.com/blogs/aws/excited-about-mxnet-joining-apache/ Once we're up and running with private@, we would also see that list cc'd on such things. Need lots

Re: New Logo?

I almost said "Happy to review a draft if anyone wants as sometimes votes can kick off prematurely". The thingy vote text was an example :) Hen On Mon, Feb 20, 2017 at 11:57 PM, Henri Yandell <bay...@apache.org> wrote: > We should do a vote on this, now that we have everyo

Re: Ready to move the source code over to Apache?

ermission on the > dmlc org on github. > > > On Tue, Feb 21, 2017 at 2:43 AM, Henri Yandell <bay...@apache.org> wrote: > > > Apologies for slowness on my part (busy home/work time of year). > > > > We have 23 committers with ICLAs/accounts. > > > >

Re: Draft of March 2016 Podling Report

on > > [ ] Other: > > Date of last release: > > No release yet > > When were the last committers or PPMC members elected? > > Project is being established with initial set of committers. > > Signed-off-by: > > [ ](mxnet) Sebastian Schelter > > Comments: > > [ ](mxnet) Suneel Marthi > > Comments: > > [ ](mxnet) Markus Weimer > > Comments: > > [ ](mxnet) Henri Yandell > > Comments: >

Slack vs email

I thought this article was a nice summary on keeping Slack discussions to the low priority items: https://dave.cheney.net/2017/04/11/why-slack-is-inappropriate-for-open-source-communications

Re: Podling Report Reminder - April 2017

Yandell <bay...@apache.org> wrote: > Can't hurt :) > > On Sun, Apr 9, 2017 at 19:23 Divakaruni, Dominic <ddiva...@amazon.com> > wrote: > >> My apologies, I didn’t catch the 4/5 date. I was shooting for 4/19. Is >> there still time to send this in tomorrow?

Re: Podling Report Reminder - April 2017

I doubt we'll get it in btw - I think this month it'll flag as "Did not report", however if we can put together a late report I can at least include that in the board notes as a comment. On Sun, Apr 9, 2017 at 7:23 PM, Henri Yandell <bay...@apache.org> wrote: > Can't hurt :

Re: Podling Report Reminder - April 2017

On Mon, Apr 10, 2017 at 9:55 PM, Divakaruni, Dominic wrote: > Hi All, > It appears there are some issues/concerns regarding moving MXNet’s code > from DMLC to Apache. A big one is user experience since this is an active > framework. > I've not heard of any concerns (but not

Re: Podling Report Reminder - April 2017

On Mon, Apr 10, 2017 at 11:08 PM, Divakaruni, Dominic wrote: > Hello MXNet members, > > Here is a draft report proposal for the April report. Please do weigh in > with any comments, clarifications and additional context that you may want > to add: > > > >

ApacheCon US 2017 Miami

Highly recommended that folk attend ApacheCon in May (if feasible). May 16-18 in Miami: http://apachecon.com/ A great time to connect with the greater Apache community, to understand better what it means to be an Apache project and to get others at Apache aware of what MXNet is. It's also a good

Re: Draft MXNet Podling report for Aug-2017

's maturity?* > > > > > > > > Podling's still getting established in Apache - so maturity == Low. > > > > > > > > Please feel free to add your own commentary. > > > > [X] Initial setup > > > > [ ] Work

Re: Formalize Committer Proposal and Application Procedure

I worry that it creates a high barrier to entry. It's a far more common pattern for a project to do poorly at recruiting new committers, than it is for one to recruit too many. Could you provide an example that provides a likely (imaginary if you'd like) candidate? Mu's a pretty bad example for

Re: July 2017 Release

The release manager should upload their PGP key to public servers; however it doesn't need to be in the web of trust. +1 on SHAs being created; that shouldn't be difficult. (The SHAs give confidence that the mirrors are providing the right content; the PGP gives confidence that Apaches content

Two additions to Jenkins

Hi PMC-Chair type folk on general@incubator. Could someone add Naveen Swamy (nswamy@) and Mu Li (muli@) to the Jenkins ldap group please. Thank you, Hen

Licensing update per code move

Thought I'd describe one of the first sets of changes we should make when the code moves to an Apache git repo. We should update the licensing. 1) We should update the NOTICE file, once on Apache's source control, to say: Apache MXNet Copyright 2017 The Apache Software Foundation This product

Re: Podling Report Reminder - July 2017

Thanks Dominic :) I signed off with a couple of minor word changes (contributor->committer), (next->afterwards). On Wed, Jul 5, 2017 at 9:47 PM, Sebastian wrote: > Also signed off! > > > > On 06.07.2017 00:34, Markus Weimer wrote: > >> On Wed, Jul 5, 2017 at 3:30 PM, Suneel

ZeroMQ licensing in Apache MXNet

One of the items that is on the list to do before releasing Apache MXNet is removing ZeroMQ from the codebase/dependencies. ZeroMQ is licensed under the LGPL 3.0 with an exception for static compiling. They have long been interested in relicensing to MPL 2.0, but haven't made much progress,

Re: Rcpp licensing in Apache MXNet

We should bring this up on general@incubator or legal-discuss@. On Thu, Jul 6, 2017 at 10:59 PM, Qiang Kou wrote: > Really thank you for the clearance. > > From the link you provided, > > "However, if the component is only needed for optional features, a project > can provide

Re: Migration to Apache has completed

Brilliant :) Thank you for all your work Ly. On Fri, Jul 28, 2017 at 12:18 PM, Ly Nguyen wrote: > Hi folks, > > We've migrated our code base to Apache/incubator-mxnet: > https://github.com/apache/incubator-mxnet > > Please help us test whether: > >- your existing forks

Re: Granting access to Jenkins

team that I indeed > have > > to be a committer to be granted access to Jenkins. I would need an Apache > > LDAP account, and the PMC chair would add me to the jobsadmin group as > > detailed in the link above. > > > > On Sat, Jun 17, 2017 at 1:11 PM, Henri Yandell <

Re: [Launch Announcement] MXNet v0.10.0

Noting that this is the last release before bringing the code to Apache. ie) This is the pre-Apache community's action, rather than any form of Apache release. Now the line has been drawn in the sand on the previous work, the community can start focusing on migrating the code/site over and

Fwd: [NOTICE] Upcoming changes to our GitHub Org

FYI/reminder (you should all have got this email). When we move the GitHub repo over, you'll need to have registered your GitHub login. -- Forwarded message -- From: Daniel Gruno Date: Sun, May 28, 2017 at 7:31 AM Subject: [NOTICE] Upcoming changes to our

Re: ask for slack invitation

Hopefully someone sent Xiang an invite. Is there a way Slack can be setup so that we don't have to send invites? Where are the instructions to the community on how to join the Slack channel? Hen On Sat, Jun 10, 2017 at 12:29 AM, Xiang Ruan wrote: > Hi, Dear Sir/Madam >

Re: ask for slack invitation

The archiving is a paid feature, or having a public Slack channel that users of the software can join without having to come cap in hand to the dev@ list? On Thu, Jun 15, 2017 at 1:06 AM, Suneel Marthi wrote: > Right, now that Amazon is gonna buy Slack for 9B - maybe we

Re: infra migration

On Mon, May 1, 2017 at 4:13 PM, Dominic Divakaruni < dominic.divakar...@gmail.com> wrote: > (trying this from my personal email, since the previous one didnt go out) > > Nudging this to the top of your inbox. Relocating infrastructure to its > Apache home is one of the first steps in the

Re: Podling Report - May 2017

Thank you Mu. I added it to https://wiki.apache.org/incubator/May2017 (with some additions) and signed off as Mentor. Everyone let me know if any of the additions I made were objectionable. The main change was to insert Migrating code+website as the top priority. Other Mentors - your review is

Re: PyPI for MXNet 0.9.5

Is that something that would take care of the sub-modules linking? We could either keep them at DMLC and send to PyPI for MXNet's needs, or we could have separate repos at Apache and push separately. In terms of which is the above seems best, I'm not sure how related the submodules are to the

Re: Need for MXNet API documentation Standards/Guidelines

Sounds like good stuff. We could get a wiki setup at Apache and document it there. Something that mxnet.io doesn't currently do is talk about the project development; it's focused on the product. If you look at most Apache websites, they are a mix of product and project development (which

Release missing on primary site

The 0.11.0 release is missing from here: https://dist.apache.org/repos/dist/dev/incubator/mxnet/ Currently only the RCs are there. We do have the download link: * http://mxnet.apache.org takes you to: * http://mxnet.apache.org/get_started/install.html takes you to: *

Re: MXNet website redesign

Clarifying as I think Isabel was too gentle :) Before coming to Apache, there had been much talk of redoing the website, perhaps via a dayjob contribution. I double checked at ApacheCon with Sally that that was sane (corporate contribution of a website design). The evolution of that conversation

Re: Release missing on primary site

os/dist/release/incubator/mxnet/0.11.0/ > https://dist.apache.org/repos/dist/release/incubator/mxnet/ > 0.11.0/apache-mxnet-src-0.11.0-incubating.tar.gz > > > On Wed, Sep 13, 2017 at 11:13 AM, Henri Yandell <bay...@apache.org> wrote: > > > The 0.11.0 release is missing fro

Re: Testing and continuous integration of MXNet on devices / Android etc.

I've a feeling that you don't need write access but a token or oauth app that is setup to edit the build status? I know that's what TravisCI asks for. Similar issue of needing an account to access (and infra say no bot accounts), but I think this can be done with lesser permissions to that

Discussion Forums?

The MXNet community have been discussing the possibilities of a discussion forum. I suspect I'm out of date on the topic. Has there been Incubator discussion on forums in the past few years? Are there projects running forums? Discourse seems to be the current fashion. My dated assumption is that

Re: MXNet: Run PR builds on Apache Jenkins only after the commit is reviewed

Side note: There is no "we". The below should say something like "I would like to propose...", or "As part of my work at , I would like to propose..." if it's coming from a team at your day job and you don't want to hog all the glory :) If it truly is "we", then the email should end with the

Re: Podling Report - Draft

g via Whimsy. > > > On Oct 6, 2017, at 7:40 PM, John D. Ament <johndam...@apache.org> wrote: > > > > > > > > On 2017-10-06 00:30, Henri Yandell <bay...@apache.org> wrote: > >> Done. Markus + Jim left :) > > > > How was this comm

Re: Podling Report - Draft

Done. Markus and Jim left to comment + sign off :) On Fri, Oct 6, 2017 at 4:40 PM, John D. Ament <johndam...@apache.org> wrote: > > > On 2017-10-06 00:30, Henri Yandell <bay...@apache.org> wrote: > > Done. Markus + Jim left :) > > How was this communicated? Or

Re: Podling Report - Draft

> > > > > Henri, > > > > > > > > > > I've updated the doc with your suggestions. Please check and sign > > off. > > > > > > > > > > > > > > > https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_ > &

PROCESS: Contacting the Apache Infra team

Hi Apache MXNet Committers and Contributors, As a community we've been sending a lot of requests (JIRA, HipChat etc) in the direction of the Apache Infra team without discussing them first here. As a community we are causing them a lot of work corralling topics that would be better sorted out on

Re: Migration of Apache MXNet from Private Slack area to ASF Slack

I'm signed up to the asf slack John. Could you give me admin access please? (i'm not sure if being signed up to the asf slack is enough or if I should have joined a particular channel. Noting a typo in your email, the-asf.slack.com rather than the-ask.slack.com (unless we're planning to move

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

Apologies - I missed that mentors hadn't voted on the podling release. Will review tonight; hopefully their mentors can do similar. There's no reason for an SGA here (and who would even sign it?). Code has been apache 2.0 since the initial commit on GitHub. On Tue, Aug 29, 2017 at 06:45 John D.

Dependency directories?

What's the plan for the source that isn't included in the mxnet repo? cub/ dlpack/ dmlc-core/ mshadow/ nnvm/ ps-lite/ Is the plan to keep those as separate DMLC packages, or to consider them MXNet specific? Thanks, Hen

ICLAs vs Contributors

(cc to John and Justin as they'd asked about this) Looking at the current MXNet GitHub contributors list (411 contributors): We have 36 signed CLAs at this point. Of the top 36 contributors, the following 15 top contributors aren't covered by a CLA: 8:sneakerkg 9:kevinthesun (post Incubation)

Re: ICLAs vs Contributors

creating a > boot page. > > 2017-08-30 13:06 GMT+08:00 Henri Yandell <bay...@apache.org>: > > > (cc to John and Justin as they'd asked about this) > > > > Looking at the current MXNet GitHub contributors list (411 contributors): > > > > We have 36 sign

Re: MXNet site questions

ve them to > > somewhere apache controls. Maybe another repo similar to web-data to > store > > all website related static resources. > > > > 2017-08-25 19:26 GMT-07:00 Henri Yandell <bay...@apache.org > > <javascript:_e(%7B%7D,'cvml','bay...@apache.org');>>

Re: Jira and/or feature collision

Yes, Apache JIRA is free to use. My observations of GitHub are that roadmaps/wishlist features need better separation from bug reports. Ideally you want a nice big list of ideas for future work, and a list of bug reports and smaller contributions that you're always driving down to zero. One way

Re: ICLAs vs Contributors

123) and Marek (mkolod) are NVIDIA > > employees working on MXNet. Should we sign individual CLAs or should > NVIDIA > > sign corporate CLA with ASF? If so, could you point us to the document > that > > needs to be signed? Can we contribute in the meantime? > > >

Re: [ANNOUNCE] Apache MXNet (incubating) 0.11.0 Release

A link to either the wiki page or the change diff would help here (so your fellow community members can dive deeper). On Thu, Sep 7, 2017 at 17:15 Meghna Baijal wrote: > Thank you for your suggestion! I have updated our release process wiki to > reflect your point

Re: What's everyone working on?

Getting an instance of github.com/amzn/oss-dashboard setup for mxnet. Hopefully useful to write custom metric analysis; like: "most pull requests from non-committer" and "PRs without committer comment". Hen On Mon, Sep 25, 2017 at 11:24 Seb Kiureghian wrote: > Hey dev@, >

Re: New Apache MXNet logo idea

Love :) Lots of good connections here. Nice feather style/colour in the bunny's silhouette, nice "magic" overlay for connection to Clarke's third law (any sufficiently deep learning is indistinguishable from magic), great name connection to 'mx' and the Chinese zodiac may, if appropriate, speak

Web site questions

Looking at the website ( https://github.com/apache/incubator-mxnet-site ), I've some questions: 1) Do we really need jenkins constantly committing date updates for doxygen? Is there a way to stop that 'generated by' text including the date? 2) Who is working on the website? There are some top

Re: Web site questions

gt; tackle these - I'll comment on the issues you've created. > > Seb > > On Wed, Sep 27, 2017 at 11:17 PM, Henri Yandell <bay...@apache.org> wrote: > > > Looking at the website ( https://github.com/apache/incubator-mxnet-site > ), > > I've some questions: > &g

MXNet site questions

* Could Issues be turned on for the site so we can report site issues? * How does one go about getting permission to the site? * Apache footer needed (Copyright/trademarks statement) * Need to add some links to Apache pages (Foundation page, Sponsors, ApacheCon jump to mind) * The logo is being

Re: Dependency directories?

ts handle > this sort of thing? > > What's are the pros and cons? > > > On Tue, Aug 29, 2017 at 9:57 PM Henri Yandell <bay...@apache.org> wrote: > > > What's the plan for the source that isn't included in the mxnet repo? > > > > cub/ > > d

Re: ICLAs vs Contributors

gt; -- 原始邮件 ------ > 发件人: "Henri Yandell";<bay...@apache.org>; > 发送时间: 2017年8月30日(星期三) 中午1:06 > 收件人: "dev"<dev@mxnet.incubator.apache.org>; "John D. Ament"< > johndam...@apache.org>; "Justin Mclean"&l

Re: open issues

I'd suggest writing up a triage process on the wiki. Using labels makes a lot of sense. One label that I've found useful with Issues in the past is "Patch Needed" (ie: contributors, please work on these). Another would be "easyfix"; ie) new contributors, this is a good place to start. One of the

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

arance. > > It's not sufficient that the code has always been under the ASL 2.0. > > Are there any contributors to the project before it came to the incubator > who are not now committers? > > Regards, > > Craig > > > On Aug 29, 2017, at 9:43 AM, Henri Yandell <bay.

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

how this has > been handled in the past). > > Please create JIRAs to track these. > > John > > On Tue, Aug 29, 2017 at 9:09 PM Henri Yandell <bay...@apache.org> wrote: > > > I believe all the major contributors were ICLA'd, and I disagree that all > > contributors

Source Headers [Was: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3]

On Tue, Aug 29, 2017 at 6:38 PM, John D. Ament <johndam...@apache.org> wrote: > On Tue, Aug 29, 2017 at 9:30 PM John D. Ament <johndam...@apache.org> > wrote: > > > On Tue, Aug 29, 2017 at 9:27 PM Henri Yandell <bay...@apache.org> wrote: > > &