Re: Podling Mxnet Report Reminder - April 2020

Same. Post report, I'd like to see a more detailed "what is left for graduation" list from the 2 Ongoing items listed. Hen On Tue, Mar 31, 2020 at 4:50 AM Michael Wall wrote: > LGTM, thanks > > On Mon, Mar 30, 2020 at 12:10 AM Sheng Zha wrote: > > > I p

Re: ONNX Support

will do their best to respond. Or you can delete it. Amazon can always fork the code in a separate repo for their customers. Hen

Re: [DISCUSS] Apache MXNet: Path to graduation

Soup (yawn) of Heinz quality (yay!). "Ford Focus [quality] automobile", not "Ford Focus". If you think of it like a programming language's type system; science uses Gluon as a noun, which does not clash with it being used as an adjective elsewhere. If any of that makes sense :) Hen

Re: [DISCUSS] Apache MXNet: Path to graduation

for MXNet has been registered by other companies? Hen On Fri, Aug 30, 2019 at 1:27 AM Leonard Lausen wrote: > Carin recently noted that gluonhq.com already uses the Gluon brand for > end-to-end enterprise mobile solution and Marco found that they do so > apparently since at least 201

Re: [DISCUSS] Apache MXNet: Path to graduation

it was very recent, I don't believe there have been any trademark registrations. If Amazon would prefer Apache control the Gluon naming, I think the simplest 'act' to make that so would be to move the gluon-api repository over to ASF control. Hen On Thu, Aug 29, 2019 at 8:27 AM Chris Olivier wrote

Re: demise of dmlc.ml domain & new Julia docs hosting

Nice work :) What other links does the project have that are outside Apache Infra control and have this risk? Outside of 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 l

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

Noting that I am a belated +1 on the release. I had one item regarding dataset licensing that I’d like to see improved for the next release, but I don’t believe it would have been a blocker. Hen On Sat, May 4, 2019 at 00:00 Junru Shao wrote: > Dear MXNet community, > > I'm happy to

Re: [QUESTION] Release Apache MXNet (incubating) version 1.4.1.rc0

Thanks Sheng. I assume MNIST covers all 5 data files. Given that's a license with stronger conditions than the Apache license, I think the example should give a canonical URL for the data (i.e. a homepage of some kind) and mention the CC-BY-SA-3.0 licensing. Hen On Wed, May 8, 2019 at 1:03 PM

[QUESTION] Release Apache MXNet (incubating) version 1.4.1.rc0

luon/dataset/mnist/t10k-labels-idx1-ubyte.gz " "http://data.mxnet.io/data/mnist_train.csv.gz; Thanks, Hen On Mon, Apr 29, 2019 at 11:52 PM Junru Shao wrote: > Dear MXNet community, > > This is the 3-day vote to release Apache MXNet (incubating) version v1.4.1. > The votin

Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet.

(well, the Amazon ping. For the Apache ping, please share on @apache.org email;*multiple-hat-syndrome*) On Fri, Mar 29, 2019 at 11:44 AM Hen wrote: > Can you share that ping with me on our @amazon.com emails please Mu. I'd > like to understand the context better. > > On Thu,

Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet.

Can you share that ping with me on our @amazon.com emails please Mu. I'd like to understand the context better. On Thu, Mar 28, 2019 at 2:08 PM Mu Li wrote: > The name Gluon is originally used for a collaboration project between > Amazon and Microsoft [1]. > I pinged both Apache and Amazon

Re: Create a Jira board for C/C++ API project

Opened: https://issues.apache.org/jira/browse/INFRA-17128 On Fri, Oct 5, 2018 at 11:45 AM Naveen Swamy wrote: > Thanks for making the effort to bring tasks and feature improvements under > a managed boards in JIRA. This will help in users/contributors to quickly > look through the

Mentor changes

the last 2 years. Hen

Re: Request for feedback: proposal for MXNet SDK Office hours

Noting that, as far as I can tell, there is no such thing as 'MXNet SDK', 'AWS MXNet SDK' or 'Amazon MXNet SDK'. On Wed, Jul 18, 2018 at 2:30 PM, Mu Li wrote: > A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK. > > On Wed, Jul 18, 2018 at 2:22 PM, Davydenko, Denis < >

Re: Request for feedback: proposal for MXNet SDK Office hours

). Have you tried the more classic Open Source approach of a specific time on an IM channel to discuss? Apache often uses IRC (irc.freenode.net). Hen On Mon, Jul 23, 2018 at 7:36 PM, Naveen Swamy wrote: > Hey All, just created a INFRA ticket(https://issues.apache.o > rg/jira/browse/INFRA

Re: MXNet Berlin Office Hours

Noting that I find "MXNet Berlin team" a very confusing concept. Does that mean "Apache MXNet committers who happen to live in Berlin?" On Mon, Jul 16, 2018 at 2:27 AM, Anton Chernov wrote: > Dear MXNet community, > > As part of our customer support the MXNet Berlin team is offering office >

Re: [DISCUSSION] Initial draft for MXNet roadmap

items to the next release. ie: At the start of the roadmap there are a bunch of newbie items, and then as you get to release stage the existing committers take care of a large chunk of newbie items. My tuppence :) Hen On Wed, Jul 4, 2018 at 11:05 AM, Steffen Rochel wrote: > As a proj

Re: Abandoned MXNet readthedocs site

I’ve Twitter DM’d one of the core members of ReadTheDocs asking for help. On Thu, Jul 5, 2018 at 8:43 AM Chris Mattmann wrote: > Hi Hen happy 4th looks like a brand mgmt. topic to me… > > > > Cheers, > > Chris > > > > > > > > > > From: Hen >

Re: Abandoned MXNet readthedocs site

Makes sense (sorry - got my memory switched on the trademark/dmca aide of things). I’ll see on members to see if anyone has a connection to readthedocs. On Tue, Jul 3, 2018 at 1:00 PM Mark Thomas wrote: > On 03/07/18 18:44, Hen wrote: > > Chris/Mark - is this a Legal (Chris) topic o

Re: Abandoned MXNet readthedocs site

ain. Can we get a trademark C sent to the > readthedocs folks, so they'll go ahead and remove the derelict website? > It's still the #4 result in Google for "mxnet install". > > What's Apache's process? > > Thanks, > Aaron > > On 5/16/18, 8:20 AM, "Hen&quo

Re: About Becoming a Committer

. Becoming a committer is about the trust built up by the committers not having to modify the action (PR, proposed-answer, proposed-wiki-change etc). Hen On Fri, Jun 15, 2018 at 12:26 AM, Marco de Abreu < marco.g.ab...@googlemail.com.invalid> wrote: > Hen, > > As you stated, it's of

Re: About Becoming a Committer

individual has shown the commitment to be extended the trust to manage commits. So; -1 to quality being more important than quantity. It's not. Hen On Fri, Jun 8, 2018 at 1:15 PM, Sheng Zha wrote: > Hi, > > There have been a couple of offline inquiries from contributors about >

Re: About Becoming a Committer

so we can attract more users. > +1. The podling pmc needs to find consensus on the become-committer stage. Hen

Re: GitHub Label Bot Design

Thanks Cathy. As a high level concept, scripts the project depends on should be committed to the project (I say this more as a note for everyone rather than calling you out specifically :) ). Hen On Thu, Jun 14, 2018 at 9:31 PM, Yuelin Zhang wrote: > Hi Hen, > > I am not using probo

Re: GitHub Label Bot Design

Where will the bot code be committed? Are you using probot? On Tue, Jun 12, 2018 at 2:21 PM Marco de Abreu wrote: > Hello Cathy, > that's a great proposal. Thank you! > > A few comments from my side: > - Good idea with the alias. We should have a special email-list for > automated reports to

Re: [GitHub] szha closed pull request #11154: Revert "[MXNET-503] Website landing page for MMS (#11037)"

-andrilla' being asked if "a flexible, scalable, multi-framework serving solution" was okay. * I find it odd that github:lupesko is a reviewer. Hen On Tue, Jun 5, 2018 at 5:08 PM, GitBox wrote: > szha closed pull request #11154: Revert "[MXNET-503] Website landing page > fo

Re: Vote to stop using JIRA

Are you saying only committers can make JIRA accounts? On Fri, Jun 8, 2018 at 2:41 PM Qing Lan wrote: > + 0 > Can we keep this optional? Not totally abandon or support. > Pros: > I used JIRA to track most of my PRs and can place them together at one > place. It also being helpful if we find

Re: ICLA?

by memory) was to try and get folk to sign ICLAs or software (license) grant. It's one of those "you do a some diligence, and draw a line as to the right place to stop doing diligence because otherwise you would be diligencing forever" situations. Hen On Thu, Jun 7, 2018 at 3:15 PM, Jus

Re: ICLA?

-wise. Hen On Thu, Jun 7, 2018 at 11:02 AM, Tianqi Chen wrote: > Interesting, but how about the current process, as far as I understand > anybody can contributing to apache repo without signing CLA, only comitters > are required to do so > > Tianqi > > On Thu, Jun 7, 2018 at

Re: ICLA?

ICLA, just hadn't back in September 2017. Hen On Wed, Jun 6, 2018 at 10:14 PM, Tianqi Chen wrote: > Maybe I was wrong, The existing code in the DMLC repo is merged by original > committers(who are now Apache MXNet comitters and signed CLA). So I assume > there is no such problem

Re: ICLA?

This list was former contributors to DMLC who did not become Apache committers. Ideally some chunk of the larger contributors would sign ICLAs or software (license) grants. On Tue, Jun 5, 2018 at 9:23 PM Isabel Drost-Fromm wrote: > Hi, > > I'm not Hen, but: > > > https://

Re: MXNet Protobuf dependency

Have they opened a PR with the ps-lite project? On Wed, May 23, 2018 at 1:38 PM Singh, Rajan wrote: > Awesome > > Thanks Rahul for the info. Will align > > Thanks > Rajan > > On 5/23/18, 12:04 PM, "Rahul Huilgol" wrote: > > Hi Rajan, > >

Re: Using parts of code from library under PyTorch organization

It's 2-clause BSD: https://github.com/pytorch/cpuinfo/blob/master/LICENSE Which files are you looking to incorporate? I want to see what the source headers look like. Hen On Fri, May 18, 2018 at 5:47 PM, Marco de Abreu < marco.g.ab...@googlemail.com> wrote: > By the way. In general, I

Abandoned MXNet readthedocs site

with readthedocs before? Should we be sending them a Trademark takedown request? Thanks, Hen

Re: MXNet 1.2 release question ?

I don’t understand what “late with the release” means. Did the project publish a timeline of releases that it guaranteed or something? On Mon, May 14, 2018 at 10:11 AM Anirudh wrote: > Hi all, > > Our vote got blocked on general@ list. The main reason was the inclusion >

newdocs.readthedocs site

. If no one has the ability to contact the individual, it sounds like we'll have to reach out to Apache Legal and discuss a DMCA request (readthedocs' surprisingly heavy process for such): https://github.com/rtfd/readthedocs.org/issues/4042 Thanks, Hen

Re: Pre-release versions on website

nt in time. I'm happy to hear any suggestions or requests on this > area as we're in the middle of mocking up some solutions. > > Cheers, > Aaron > > > On Mon, May 7, 2018 at 8:03 AM, Hen <bay...@apache.org> wrote: > > > Agreed. > > > > RCs are for the

Re: Pre-release versions on website

Agreed. RCs are for the project contributors to review. They are not for users as they have not passed the release process. The website shouldn’t reflect RCs. Hen On Sat, May 5, 2018 at 10:42 PM Afrooze, Sina <sina@gmail.com> wrote: > I have mentioned this before and I st

Re: GitHub releases section used for non-releases

Wincing at a binary of 7z being there. Seems like something to delete. On Tue, May 1, 2018 at 3:32 PM Marco de Abreu wrote: > Hello, > > I have just had a look at > https://github.com/apache/incubator-mxnet/releases > and it seems like the releases section is being

Re: [VOTE] Release Apache MXNet(incubating) version 1.2.0.RC1

. Hen On Mon, Apr 30, 2018 at 1:23 PM Gautam <gautamn...@gmail.com> wrote: > +1 on merging this "https://github.com/dmlc/mshadow/pull/319 " > > I am curious how are we tracking the sub-modules's PRs which are really > important for MXNet? > This PR has been waiti

Re: Quick question about a submodule file’s license

There’s nothing special process-wise; subscribe to the list and email the question. The more detail and links the better to avoid any misunderstandings. Hen On Fri, Apr 6, 2018 at 11:43 AM Meghna Baijal <meghnabaijal2...@gmail.com> wrote: > Thank you Henri, Pedro. > Yes, we are on

Re: blog for MXNet

https://blogs.apache.org/mxnet/entry/1-1-0-release-makes On Wed, Apr 11, 2018 at 2:46 PM Aaron Markham wrote: > Having a blog for MXNet would be very useful for conveying news, > talking about features, demoing applications, and building awareness. > > Does anyone

Re: Podling Report Reminder - April 2018

in piling on in the debate, and that they recuse themselves from voting +1 on a vote as they already voted when brainstorming the idea. Hen [piling on => an email thread where multiple people all jump on to the thread to say, in essence, the same thing, and wear down an opposing argument through

Re: Podling Report Reminder - April 2018

[ ] Community building [ ] Nearing graduation [ ] Other:Date of last release: -XX-XXWhen were the last committers or PPMC members elected? Previous board report is in here: https://www.apache.org/foundation/records/minutes/2018/board_minutes_2018_01_17.txt Hen On Mon, Apr 2, 2018

Fwd: Abstracts on Apache MxNet - DataWorks Summit San Jose - Submission deadline extended thru Sunday

-- Forwarded message - From: Robert Hryniewicz Date: Fri, Feb 9, 2018 at 20:41 Subject: Re: Abstracts on Apache MxNet - DataWorks Summit San Jose - Submission deadline extended thru Sunday To: dev-ow...@mxnet.incubator.apache.org <

Re: JIRA notifications on dev@

The typical approach is to have them sent to a notifications list (along with CI etc). Normally that still redirects to dev iirc. On Wed, Feb 7, 2018 at 03:24 kellen sunderland wrote: > +1 > > On Feb 7, 2018 2:49 AM, "Marco de Abreu"

Re: Unit tests removed

on someone adding the tests back later, that’s just a good intention. Hen On Thu, Feb 1, 2018 at 11:11 Mu Li <muli@gmail.com> wrote: > I think simply reverting the MKL PR that Da has been working for a half > year and immediately enabling the cpp tests in the CI without reaching an

Re: Please Help Fix MXNet Licensing Issues for the next Release!

. Additionally each of MIT and BSD typically has a Copyright statement accompanying it. If the rules say to remove that from LICENSE, then we should be adding it to the NOTICE. Hen On Wed, Jan 24, 2018 at 5:07 PM, Meghna Baijal <meghnabaijal2...@gmail.com> wrote: > Marco, > Thanks a lot for loo

Re: Submitting changes to the MXNet website

Or maybe the README for https://github.com/apache/incubator-mxnet-site ? On Tue, Jan 23, 2018 at 1:15 PM, Haibin Lin wrote: > Hi Marco, > > Thanks for the clarification. I was wondering about the website build > process, too. I wonder if it will be beneficial to create

Re: dmlc packages into 3rdpary

Before the next release we need some kind of "this isn't Apache code" so the reviewers can treat it accordingly. Putting in third-party/ works for me. I suspect it will remain controversial; but at least the focus will be in the right way. Hen On Fri, Jan 19, 2018 at 11:43 AM, Chr

Re: Podling Report Reminder - January 2018

Thanks Bhavin. Let's definitely get that as an active conversation. In general I'm okay with the report. I'm having login pains with the wiki (yay for non-ldap service), but chatted with Suneel on IM and he said he'd update the wiki for me (much appreciated Suneel, thank you :) ). Hen On Tue

Re: Podling Report Reminder - January 2018

lan here? 2/ Noting that there needs to be more blogging on the Apache blog. I would assume that an Apache blog entry is Apache 2.0 licensed; thus it would be perfectly fine imo to post on the Apache site and then on the AWS site (with reference to it being previously posted on the Apache blog). Hen

Re: Perl module copyright/author notation

Thanks Sergey :) Cc'd to dev@ as an FYI. Hen On Thu, Nov 30, 2017 at 10:58 PM, Sergey Kolychev < sergeykolychev.git...@gmail.com> wrote: > Yes, sure please change it as needed. Thanks! > > On Thu, Nov 30, 2017 at 12:44 PM, Hen <bay...@apache.org> wrote: > >&g

FYI: [VOTE] Apache MXNet (incubating) 1.0.0 release RC0

Sorry, I should have cc'd dev@ on this. -- Forwarded message -- From: Hen <bay...@apache.org> Date: Wed, Nov 29, 2017 at 1:59 PM Subject: Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC0 To: gene...@incubator.apache.org Thanks Justin. Some comments inline on ones I

Re: CODEOWNERS file being removed

We should however, never enable the code-owner option of required reviews. As that's an Admin/Owner feature, and I don't think Apache Infra would do that, I think we're good there. So my suggestion would be to add a comment that this is an automatically-listed-on-reviews tool. Hen On Wed, Nov 29,

Re: AWS contributing ONNX-MXNet

It was contributed to 'ONNX'. Which is a joint Facebook/Microsoft project of some kind ( http://onnx.ai/ ). Hen On Fri, Nov 17, 2017 at 12:35 AM, Isabel Drost-Fromm <isa...@apache.org> wrote: > > > Am 16. November 2017 23:04:05 MEZ schrieb "Lupesko, Hagay" < > l

Re: [VOTE] A Separate CI System for Apache MXNet (incubating)

+1 on Jenkins; makes sense to me to keep it within the same tech as used on the Apache side. (Noting that as this is not a required vote, I don't believe this needs to go to general@incubator or need 3 mentor +1s). As long as 3 committers are +1 it's good in my opinion. Hen On Tue, Nov 14, 2017

Re: The process for a patch release

with security@ on the process. Hen On Tue, Nov 7, 2017 at 1:45 PM, Chris Olivier <cjolivie...@gmail.com> wrote: > Do we need a vote for a critical patch release? > > On Tue, Nov 7, 2017 at 12:08 PM, Meghna Baijal <meghnabaijal2...@gmail.com > > > wrote: > > >

Re: [Proposal] Stabilizing Apache MXNet CI build system

o why it's very important that the MXNet documentation explains how to get the source, how to build the source, and how to contribute. Security vulnerabilities are a little different. While good intentions remain, it's assumed that a healthy project can fulfill the good intentions, and repeated security issues without resolution will quickly raise the question of whether the project is not mature enough for its user base. Hen

Re: Draft of blog post for MXNet v0.12 release

It was noted that you've signed up. I've added you to the blog Sandeep :) On Tue, Oct 31, 2017 at 3:37 PM, Hen <bay...@apache.org> wrote: > Confirmed on the email. > > Can you sign in at blogs.apache.org using your Apache LDAP credentials > please? > > That will add

Re: Disable 'required status check' for master

This makes sense to me. CI isn't of value if it isn't continuous. +1. On Tue, Oct 31, 2017 at 12:07 PM, Indhu wrote: > Hi, > > We have been having issues getting CI to work fast enough. Currently the CI > is being the bottleneck to get commits in. This is severely

Re: Slack Subscribe

Looks like someone has sent you an invite. (Folk, please let the list know when you've invited, otherwise N other people will burn time; apologies if whomever invited was doing it at exactly the same time). On Mon, Oct 30, 2017 at 4:55 PM, Tyler Kvochick wrote: >

Re: MXNet blog for upcoming release

https://issues.apache.org/jira/browse/INFRA-15407 On Mon, Oct 30, 2017 at 12:12 PM, Hen <bay...@apache.org> wrote: > Having a blog for the project sounds like a good idea. > > I don't see one already existing, and I see other incubator podlings with > a blog, so I'll go ahe

Re: MXNet blog for upcoming release

Having a blog for the project sounds like a good idea. I don't see one already existing, and I see other incubator podlings with a blog, so I'll go ahead and open a JIRA. Hen On Mon, Oct 30, 2017 at 9:29 AM, Suk Won Kim <kim.suk...@gmail.com> wrote: > Hi all, > Meghna is goin

Re: [Proposal] Stabilizing Apache MXNet CI build system

How about we ask for a new mxnet repo to store all the config in? On Fri, Oct 27, 2017 at 05:30 Pedro Larroy wrote: > Just to provide a high level overview of the ideas and proposals > coming from different sources for the requirements for testing and > validation

ci mailing list?

Would it be useful to get an mxnet-ci mailing list setup so that it's easy to filter build failures and general conversation into different buckets? Hen

DMLC [Was: Request for suggestions- Supporting onnx in mxnet]

the last release was the large amount of DMLC code that Apache MXNet is wrapping/including as source code. This is unusual for an Apache project and one of the ways that unusual can impact is that the Apache project is handing a large amount of its design to a third party. Hen On Thu, Oct 19,

Re: proposal to shut down apache-mxnet.slack.com

the-asf? > > Steffen > > > > > > On Mon, Oct 16, 2017 at 10:34 PM Mu Li <muli@gmail.com> wrote: > > > > > there are several private channels on apache-mxnet.slack.com, how we > are > > > going to deal with it? > > > > > >

Re: proposal to shut down apache-mxnet.slack.com

+1. On Mon, Oct 16, 2017 at 10:01 PM, Chris Olivier wrote: > +1. Nuke it. > > > On Mon, Oct 16, 2017 at 8:23 AM Steffen Rochel > wrote: > > > As we have now migrated the majority of people from > apache-mxnet.slack.com > > to the-asf.slack.com I