Re: [Announcement] New Committer - Sam Skalicky

Welcome! -Marco On Wed, Jul 29, 2020, 4:58 PM sandeep krishnamurthy < sandeep.krishn...@gmail.com> wrote: > Hello all, > > Please join me in welcoming Sam Skalicky(@samskalicky) as a new committer > of Apache MXNet (incubating)! > > Sam has made a number of contributions to this project such as

Re: [RESULTS] [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

Thanks! Please don't forget the release vote on incubator. -Marco On Thu, Jul 23, 2020, 9:37 AM Chen, Ciyong wrote: > Dear MXNet community, > > I'm happy to announce the results of the vote. > This vote passes with 10 +1 votes (3 binding) and no 0 or -1 votes. > > +1 votes > * Sheng Zha /

Re: [DISCUSS] Examples Repo for 2.0

+1 good idea! On Thu, Jul 16, 2020, 5:39 AM Skalicky, Sam wrote: > +1 For regular testing, enhanced doc/tutorial > > > On Jul 15, 2020, at 7:40 PM, Sheng Zha wrote: > > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can

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

Okay, thanks for the clarification! -Marco On Sun, Jul 12, 2020, 5:58 PM Sheng Zha wrote: > Hi Marco, > > Since the license issues apply to binary distribution, we should still be > able to make official source releases. > > Regards, > Sheng > > > On Jul 12, 20

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

Are we in the position to make a release given that we have open license issues with the ipmc and Apache board? I want to avoid giving the impression that we are ignoring their requests - my current understanding is that we are non compliant. -Marco On Sat, Jul 11, 2020, 9:46 AM Tong He wrote:

Re: Ownership of discuss.mxnet.io

n name usage afterwards. > > -sz > > > On Jun 17, 2020, at 6:07 AM, Shane Curcuru wrote: > > > > On 2020/06/12 22:39:10, Marco de Abreu > wrote: ... > >> The mxnet.io domain is not under control of the ASF. If we say that a > user > >> facing pla

Re: Ownership of discuss.mxnet.io

Hello, Has there been any update on this matter? Best regards Marco Marco de Abreu schrieb am Sa., 13. Juni 2020, 00:39: > Thanks for elaborating! > > You are right, there's no requirement to host on ASF infrastructure. I was > just thinking about what happens when that funding is

Re: [CI] Staggered build pipelines enabled

Hello, I'd like to revisit this decision and review whether the expected benefit (cost reduction) was achieved and how the overall PR validation duration has changed. Could you guys share some information on this matter? Just today, we've had two incidents which were caused by this change: 1.

Re: assimilation of mshadow into the MXNet codebase

Hi Sheng, since this is a "large one off code contribution", the policy [1] states that they should be brought in through a software grant. Best regards, Marco [1]: https://www.apache.org/foundation/how-it-works/legal.html On Fri, Jun 12, 2020 at 11:41 PM Sheng Zha wrote: > To mentors, > >

Re: Ownership of discuss.mxnet.io

members to be automatically authorized? > > This sounds like a good idea though I'm not sure how to proceed. If > someone knows how to proceed I'm happy to help grant necessary access to it. > > -sz > > > On 2020/06/12 22:07:47, Marco de Abreu wrote: > > Hi Sheng, &

Re: Ownership of discuss.mxnet.io

Same questions with regards to https://discuss.gluon.ai/ obviously. -Marco On Sat, Jun 13, 2020 at 12:07 AM Marco de Abreu wrote: > Hi Sheng, > > thanks for the quick response. > > Could you elaborate about the hosting of the forum? Is there the > possibility to move it t

Re: Ownership of discuss.mxnet.io

this under PPMC control for better > discoverability under the mxnet domain name. I'm happy to grant you admin > access if you or any other PPMC members need it. If you feel otherwise, > feel free to propose how you suggest we proceed. > > -sz > > On 2020/06/12 21:07:28, Marco

Ownership of discuss.mxnet.io

Hi everyone, Due to a PR [1] I had a closer look at discuss.mxnet.io which is a forum to discuss about MXNet. It's a very helpful platform and provides great assistance for the community. When I looked into the terms of services [2] though, I noticed that the ASF and MXNet ppmc are mentioned as

Re: [DISCUSS] Deprecating and Forbidding Terraform and Other Services by HashiCorp in MXNet

se version. From the reply I think you only > > read the updated version. Since the current version of their term of use > > doesn't affect our project anymore, I'm OK to leave it as is. > > > > -sz > > > > [1] https://pbs.twimg.com/media/EZLJJwjUYAM8Xk-?forma

Re: [DISCUSS] Deprecating and Forbidding Terraform and Other Services by HashiCorp in MXNet

The statement is specifically about HashiCorp Vault enterprise edition - speak a single module of their enterprise suite which is about credential encryption. I didn't read further, but my first guess is that they are not offering it in China since the Chinese government - as far as I can recall

Re: [Lazy consensus] Removal of all repository.apache.org mxnet artifacts (and their mirrored maven central counterparts)

packages, and less effort than > > re-doing > > all the releases in an ASF-compliant manner. Let's wait another few days > > if any > > MXNet committers, perhaps one that is already familiar with the JVM > > packaging > > and ecosystem, will volunteer to implement

Re: [Lazy consensus] Removal of all repository.apache.org mxnet artifacts (and their mirrored maven central counterparts)

determines the outcome. In > that > case I suggest to change the email title to begin with [VOTE]. Otherwise > I'll > assume the lazy consensus still remains. > > [1]: https://www.apache.org/foundation/voting.html > > On Tue, 2020-05-26 at 23:44 +0200, Marco de Abreu wrote: > > &g

Re: [Lazy consensus] Removal of all repository.apache.org mxnet artifacts (and their mirrored maven central counterparts)

Do we offer any replacement for those deletions or will be break stuff then? If we break anything, I'd -1 until we found a way moving forward to ensure uninterrupted service. On Tue, May 26, 2020 at 7:51 PM Carin Meier wrote: > Does anyone have any bandwidth to update installation

Re: Global Search Now Available on MXNet Website

Really great feature and usability, great job! -Marco Zhao, Patric schrieb am Do., 21. Mai 2020, 08:57: > I have tried it and It's really useful  > > Thanks for the improvements, Yang. > > > -Original Message- > > From: sandeep krishnamurthy > > Sent: Thursday, May 21, 2020 2:42 PM >

Re: [RFC] MXNet website - Global Search Feature

Hi, This sounds exciting. Unfortunately, I can't find the search functionality on the link you've provided. Could you explain it in more detail? I'm using an Android phone with the stock browser btw. -Marco Yang Shi schrieb am Sa., 9. Mai 2020, 09:55: > Hello MXNet Community, > > As you may

Backwards compatibility checker brocken

Hi everyone, The mbcc seems to be broken for quite some time: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/restricted-backwards-compatibility-checker/detail/restricted-backwards-compatibility-checker/1237/pipeline Is this on the radar and being worked on? -Marco

Re: Docker cache not working for new Dockerfiles

Excellent, thanks! Lausen, Leonard schrieb am Mo., 27. Apr. 2020, 21:51: > Hi Marco, > > should be fixed by https://github.com/apache/incubator-mxnet/pull/18179 > > Some earlier steps required for the fix was to update the AMI used by CI > to run > "Docker cache build & publish" to include

Docker cache not working for new Dockerfiles

Hi everyone, due to the recent rebuild of the Dockerfiles, the docker cache is no longer generating the respective images. Is this issue known and being worked on? Best regards, Marco

Re: Update : CI windows-gpu Failure

Done: https://issues.apache.org/jira/browse/INFRA-20085 Since you didn't provide the required events, I took an educated guess. Next time, please include the events. -Marco On Tue, Apr 7, 2020 at 6:57 AM Chaitanya Bapat wrote: > Hello MXNet community, > > > The new AMI will be tested in a

Re: Request for Edit Permissions on Confluence

Hello Conner, Generally Apache prefers people to use their personal email and not their corporate email. You contribute as an individual and not on behalf of your employer. Best regards, Marco Goggins, Connor schrieb am Do., 2. Apr. 2020, 21:00: > Hello, I would like to be given edit

Re: Versioned Dropdown for Python API Docs

Does that mean that the 1.6 branch is in a broken state from a website generation point of view? Speak, if the branch gets checked out entirely, we won't be able to generate the artifacts? -Marco Goggins, Connor schrieb am Mo., 30. März 2020, 21:41: > Hi all, quick status update on the Website

Re: CI Pipeline Change Proposal

Seems even more relevant now that we're maintaining master and 1.7.x and at > least for me, 1.6.x. > > > > On Fri, Mar 27, 2020, 00:55 Marco de Abreu > wrote: > > > What about dependency pinning? > > > > The cache should not be our method to do dependency pinni

Re: CI Pipeline Change Proposal

we'd save build time and things breaking > randomly. Users can use those docker images too. At release time we do a > round of updates and testing when we're ready. Can we find a balance > between caching, prebuilt docker images, freshness, and efficiency? > > > On Thu, Mar

Re: CI Pipeline Change Proposal

nity check first. Even at 10 > > minutes. > > > And also try to fix the docker cache situation, but those can be > separate > > > tasks. > > > > > > On Thu, Mar 26, 2020, 12:52 Marco de Abreu > > wrote: > > > > > > > Jenkins

Re: CI Pipeline Change Proposal

) > > On Thu, 2020-03-26 at 16:06 -0400, Aaron Markham wrote: > > I think it is a good idea to do the sanity check first. Even at 10 > minutes. > > And also try to fix the docker cache situation, but those can be separate > > tasks. > > > > On Thu, Mar 26, 20

Re: CI Pipeline Change Proposal

39 > > We could improve this by not having to build a new container every time. > Also, our CI containers are huge so it takes awhile to pull them down. I'm > sure we could reduce the size by being a bit more careful in building them > too. > > Joe > > On Thu, Mar 26

Re: CI Pipeline Change Proposal

21 47.63% > > We can start by requiring only the sanity job to complete before triggering > the rest, and collect data to decide if it makes sense to change it from > there. Any objections to this approach? > > Thanks. > Joe > > > On Wed, Mar 25, 2020 at 9:35 AM Marco de

Re: CI Pipeline Change Proposal

se as needed, while all of the other parts pass and > don't have to be rerun. > > On Wed, Mar 25, 2020 at 1:32 AM Marco de Abreu > wrote: > > > > We had this structure in the past and the community was bothered by CI > > taking more time, thus we moved to the cur

Re: CI Pipeline Change Proposal

We had this structure in the past and the community was bothered by CI taking more time, thus we moved to the current model with everything parallelized. We'd basically revert that then. Can you show by how much the duration will increase? Also, we have zero test parallelisation, speak we are

Re: MXNet Bot Demo

cost considerations apart from undesirable dev experience) > > @Marco Since I am a non-committer, I guess these 2 clarifications need to > be conveyed to the Apache Infra by someone with Committer access. > > What do you think? > > Thanks, > Chai > > On Sat, 21 Mar

Re: MXNet Bot Demo

Hello, the ticket has been created: https://issues.apache.org/jira/browse/INFRA-20005 Best regards, Marco On Thu, Mar 19, 2020 at 11:49 PM Marco de Abreu wrote: > Sounds like a good plan! > > Please send me the URL (please make sure it's backed by DNS and not just > the

Re: MXNet Bot Demo

lunteering to help enable the web hook on > apache/incubator-mxnet. Let me know if we can sync up on Slack channel to > get the ball rolling. > > Thanks once again for the entire community to step in and help try out this > Bot. > Chai > > On Wed, 18 Mar 2020 at 17:07, Marco d

Re: MXNet Bot Demo

er merge. > Am I understanding this correctly? > > On Wed, 18 Mar 2020 at 04:23, Marco de Abreu > wrote: > > > Thanks Chai, sounds good to me. Could you elaborate a bit on the point > > about triggering a CI run after the PR has been merged? We already to > that

Re: MXNet Bot Demo

; Barring the opt-in vs opt-out debate & idempotency, consensus was quickly > reached for the rest. > > In the coming days, I hope to roll-out this feature into Prod (public > MXNet) for all devs to use. > > Thanks, > Chai > > On Mon, 16 Mar 2020 at 11:57, Marco de Abreu >

Re: MXNet Bot Demo

ot lost). Maybe we could make the bot recognize if the PR > author is new or existing contributor and offer advice based on that? > > > > Thanks > > Przemek > > > > On 2020/03/13 22:06:58, Marco de Abreu wrote: > >> Hi, > >> > >> since it's no lo

Re: Workflow proposal

Considering how unstable our PR as well as our nightly jobs have been so far, is that an assumption we can rightfully make? Also, who'd be responsible for fixing that branch in case a PR actually breaks a nightly test? -Marco On Mon, Mar 16, 2020 at 7:41 PM Pedro Larroy wrote: > The original

Re: MXNet Bot Demo

sound to you? > > Again, thank you all for chiming in and voicing your opinion. Appreciate > it. > We can take ahead these discussions in today's demo meeting. [Design Doc > <https://cwiki.apache.org/confluence/display/MXNET/MXNet+CI+Bot>] [Demo > Video <https://www.youtube

Re: MXNet Bot Demo

retrigger > all CI runs. > > Best regards > Leonard > > On Fri, 2020-03-13 at 08:07 +0100, Marco de Abreu wrote: > > Thanks for the data Sandeep. In these cases it sounds like it would have > > rather been better when people explicitly turned off CI in that case. &g

Re: MXNet Bot Demo

roken by other > commits > > during the two day without being noticed. And finally the PR is merged > with > > underlying problems. > > > > On Fri, Mar 13, 2020 at 6:19 AM Marco de Abreu > > wrote: > > > > > In the end it only comes down to money,

Re: MXNet Bot Demo

overed the new PR branch yet). That's it. > So it shouldn't be a problem for public MXNet repo. > > Thanks, > Chai > > > On Thu, 12 Mar 2020 at 14:22, Marco de Abreu > wrote: > > > Btw you forgot to set a date and time for the metting > > > > >

Re: MXNet Bot Demo

Btw you forgot to set a date and time for the metting On Thu, Mar 12, 2020 at 10:18 PM Marco de Abreu wrote: > Thanks Chai, I generally like the idea of the bot. But I'm not a supporter > of the idea to disable any automatic triggering (disabling the webhook is > also not

Re: MXNet Bot Demo

Thanks Chai, I generally like the idea of the bot. But I'm not a supporter of the idea to disable any automatic triggering (disabling the webhook is also not an option, considering that this will disable master triggers). The CI system has to support the community without requiring people to

Re: Workflow proposal

The biggest issue in an open source project in my opinion is to find someone responsible for keeping these two branches in sync. And I don't mean technically but in the sense of somebody who chases after the issues that arise in that develop branch. Looking at this situation today, we regularly

Re: MXNet CD pipelines cost savings

to reflect only the artifacts published by Jenkins CD. > I hope this brings conclusion to this situation. > > Let me know if there's any further question. > > -sz > > [1] https://github.com/apache/incubator-mxnet/pull/17551 > > On 2020/02/10 23:57:47, Marco de Ab

Re: MXNet CD pipelines cost savings

Thanks for bringing this to our attention. I'm quite devastated that our two vetoes have been ignored and the CodeBuild pipeline is actually supplying our user-facing binaries. Suggesting to turn of the Jenkins based CD now adds insult to injury. I'd like to hear a plan how to make the project

Re: jemalloc 5 incompatibility

Building as part of cmake once upstream is stable sounds like a good approach. Thanks for catching this issue early on! -Marco Lausen, Leonard schrieb am So., 19. Jan. 2020, 11:20: > As of jemalloc 5, jemalloc default build can not be used in libraries that > are > dlopened. However,

Re: Stop redistributing source code of 3rdparty dependencies to avoid licensing issues

I agree with Tianqi. We may change our build system, but this won't free us from the necessity to validate the licenses of our dependencies. The question at this point is whether we are allowed to differentiate between our main-source and hold it to the strict standards while treating the third

Re: CCLA for MXNET

gt; From the Open Source Program Office > <https://developer.yahoo.com/opensource/docs/> at Yahoo --> Oath - -> > Verizon Media > > My work calendar is open for colleagues to see. yo/open-calendars > > > On Tue, Jan 14, 2020 at 3:09 AM Marco de Abreu > wrote: > >

Re: CCLA for MXNET

I've found this resource: https://people.apache.org/unlistedclas.html If in doubt, people can still submit an icla even if they are not a committer. -Marco Michael Wall schrieb am Di., 14. Jan. 2020, 02:08: > I am going to include Justin to get his take on this. Justin, does this > need to

Re: Stopping nightly releases to Pypi

f the reasoning behind all > the the CD churn recently, then this seems to be of some concern. > > -Chris > > On Thu, Jan 9, 2020 at 6:32 AM Marco de Abreu <mailto:marco.g.ab...@gmail.com>> > wrote: > > Great, thanks a lot sheng! > > -Marco > > Sheng Zha m

Re: Stopping nightly releases to Pypi

3-none-manylinux1_x86_64.whl > > > > for URL > > > > > > > > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl > > > > > > > > Please let me kn

Re: Stopping nightly releases to Pypi

Build (you don't support this because it's company owned, did I > understand this correctly?) > 2 - Apache owned Jenkins (can you help with this?) > 3 - Travis CI or similar, which in the end is similar to code build. > 4- Another Jenkins just for CD (who owns?) > > Pedro. > &g

Re: Stopping nightly releases to Pypi

ean and in working order. I don't think users > care where the binary releases are hosted. > > Pedro. > > On Sun, Jan 5, 2020 at 5:56 AM Marco de Abreu > wrote: > > > Apache only cares about source releases as far as official releases are > > concerned. But Apache als

Re: Stopping nightly releases to Pypi

oposal to host this in Apache infrastructure? Maybe I'm missing > something on this conversation > > Pedro. > > > On Fri, Jan 3, 2020 at 3:21 PM Marco de Abreu > wrote: > > > Sam, while I understand that this solution was developed out of > necessity, > &

Re: Stopping nightly releases to Pypi

is always appreciated, the fix still has to conform with the way this project and Apache operates. Next time I'd recommend to contribute time on improving the existing community solution instead of developing an internal system. -Marco Marco de Abreu schrieb am Sa., 4. Jan. 2020, 00:21: >

Re: Stopping nightly releases to Pypi

che repositories, would > that be acceptable from the Apache POV? In the end they should be very thin > and calling the scripts that are part of the CD packages. > > On Fri, Jan 3, 2020 at 6:56 AM Marco de Abreu > wrote: > > > Agree, but the question how a non Amazonian is able

Re: Stopping nightly releases to Pypi

that aligns with Apache values or revert the changes. -Marco Pedro Larroy schrieb am Fr., 3. Jan. 2020, 03:33: > CD should be separate from CI for security reasons in any case. > > > On Sat, Dec 7, 2019 at 10:04 AM Marco de Abreu > wrote: > > > Could you elaborate how a non-Ama

Re: Podling Mxnet Report Reminder - January 2020

Hey sheng, Thanks for driving the report! Shall we maybe mention the reboot of the website and also include some statistics? Best regards Marco Sheng Zha schrieb am Di., 31. Dez. 2019, 13:01: > I just posted the draft at > https://cwiki.apache.org/confluence/display/INCUBATOR/January2020. > >

Re: Custom C++ Operators

Awesome project, love it! It really seems easy to use, great job! -Marco Skalicky, Sam schrieb am Sa., 7. Dez. 2019, 19:50: > Hi MXNet Community, > > We have been working on adding support for custom C++ operators for a > while and are happy to announce that the initial functionality is now >

Re: Stopping nightly releases to Pypi

> upload > attempts of nightly builds to Pypi. > > With consensus established, we can change the CI job to stop trying to > upload > the nightly builds and then request Pypi to increase the limit. Then we > have one > less blocker for the 1.6 release. > > Best regard

Launch of the 2020 ASF Community Survey

Hello everyone, the Apache Diversity and Inclusion department started a survey which would appreciate your participation. The email can be found below: If you have an apache.org email, you should have received an email with an invitation to take the 2020 ASF Community Survey. Please take

Re: Stopping nightly releases to Pypi

ease state so clearly (I'm not sure if "maybe" qualifies as > objection). Though I think it only makes sense with at least 2 options to > vote > on. Status quo is not a meaningful option, as it is already broken. > > Best regards > Leonard > > [1]: https://github.com/pypa

Re: Stopping nightly releases to Pypi

I'm focusing on the POC for now. > > -sz > > On 2019/12/03 18:28:44, Marco de Abreu wrote: > > Excellent! Could we maybe come up with a POC and a quick writeup and then > > start a proper vote after everyone verified that it covers their > use-cases? > > > >

Re: Stopping nightly releases to Pypi

ed DNS server so that China users are directed to that > local mirror. The rest of the world is already covered by the global > cloudfront. > > -sz > > On 2019/12/03 18:22:22, Marco de Abreu wrote: > > Isn't there an s3 endpoint in Beijing? > > > > It seems like

Re: Stopping nightly releases to Pypi

Isn't there an s3 endpoint in Beijing? It seems like this topic still warrants some discussion and thus I'd prefer if we don't move forward with lazy consensus. -Marco Tao Lv schrieb am Di., 3. Dez. 2019, 14:31: > * For pypi, we can use mirrors. > > On Tue, Dec 3, 2019 at 9:28 PM Tao Lv

CI workers down?

Hi, I'm waiting for some PRs to finish validating, but it seems like there are some issues with the UNIX CPU and GPU workers in CI. Is this a known problem? Some jobs have been in the queue for more than 8 hours. Best regards, Marco

Re: Proposal to make MKLDNN as default CPU backend

numerated some use cases). How do you propose to identify the > pip > >> wheels with/without MKLDNN? Previously we had: mxnet-mkl and > > mxnet-cu101mkl > >> with MKLDNN. If the plain “mxnet” pip wheel now contains MKLDNN what do > > you > >> propose we c

Re: Proposal to make MKLDNN as default CPU backend

Hi Patric, First of all, thanks a lot to you and your team for all the effort on MXNet and mkldnn! Generally I'm inclined towards your proposal, but I'm thinking about the non-standard use cases: - AMD CPU - ARM CPU - Windows - GPU and MKLDNN enabled - Fully reproducible results (medical and

Re: BytePS-MXNet Integration

Great proposal, really looking forward to it! Qin, Zhennan schrieb am Mi., 6. Nov. 2019, 07:59: > Hi Yimin, > > Welcome to make contribution to MXNet project! > > From > https://github.com/bytedance/byteps/blob/master/README.md I found

Re: [Discuss] Upgrade MKL-DNN submodule to its v1.0 release

Great job, well done everyone!! Lv, Tao A schrieb am Fr., 1. Nov. 2019, 03:50: > Hi dev, > > The feature branch mkldnn-v1.0 has been merged to master. Really > appreciate your support for this task. > Branch: https://github.com/apache/incubator-mxnet/tree/mkldnn-v1.0 > Project:

Re: MXNet 1.6.0 release

Hi Patric, could you elaborate on the CI? Please feel free to open a separate thread to not derail this one. -Marco Zhao, Patric schrieb am Sa., 26. Okt. 2019, 02:57: > Thanks, Przemek. > > We're catching up for MKL-DNN upgrade parts but currently the unstable CI > is slowdown our development

Re: [DISCUSS] CI Access Control

Added all three of you. You might have to relog. Przemysław Trędak schrieb am Do., 24. Okt. 2019, 01:15: > Oooh, that is why we did not see this button... Could you add me and Dick? > > Thank you! > Przemek > > On 2019/10/23 23:11:32, Marco de Abreu wrote: > > We ca

Re: [DISCUSS] CI Access Control

t-committers/members team? It > doesn't > work for me unfortunately (even though I login to the CI via my Github > account). > The retrigger button simply doesn't show up. > > Are any further steps required? > > Best regards > Leonard > > On Tue, 2019-09-17 at 14

Re: Is MXNet on dockerhub well maintained?

; well? > > On Mon, Oct 21, 2019 at 12:51 PM Marco de Abreu > wrote: > > > Hi Triston, > > > > I think the Docker images were part of the release process, but I might > be > > wrong or they've been neglected since it was a manual process to generate > &g

Re: Is MXNet on dockerhub well maintained?

Hi Triston, I think the Docker images were part of the release process, but I might be wrong or they've been neglected since it was a manual process to generate them. We just merged a PR [1] which adds Docker image publishing to CD. I think there will be a separate announcement once the images

Re: Revisit Maturity Model for MXNet

Hi, I have created a PR to add the instructions: https://github.com/apache/incubator-mxnet/pull/16383 -Marco On Sun, Oct 6, 2019 at 12:07 PM Marco de Abreu wrote: > Excellent, thanks a ton! > > -Marco > > Lieven Govaerts schrieb am So., 6. Okt. 2019, 02:35: > >> Hi Ma

Re: Revisit Maturity Model for MXNet

Excellent, thanks a ton! -Marco Lieven Govaerts schrieb am So., 6. Okt. 2019, 02:35: > Hi Marco, > > On Sun, 6 Oct 2019 at 00:09, Marco de Abreu > wrote: > > > Hi, > > > > These are very good points! I also noticed the security incident > reporting > >

Re: Revisit Maturity Model for MXNet

Hi, These are very good points! I also noticed the security incident reporting when I reviewed it and I agree that it's something we have to work out. I will work on something tomorrow and provide a draft for the community to review. Do you think it's really necessary to have a separate email

Re: Podling Report Reminder - October 2019

Thanks Sheng! The following section might have a copy and paste mistake with the links since they're identical: Our community is planning for the long-term development of MXNet. RFC: https://github.com/apache/incubator-mxnet/issues/16167 Discussion:

Re: new website, docs code freeze

nsibilities. > I'm > > available to help if anybody is stuck. I believe Aaron has updated the > > READMEs on how to test the websites locally, if they're not clear, feel > > free to contribute your own explanations or ask for help directly to me > by > > email or on t

Re: [DISCUSS] Remove amalgamation

wrote: > > > > > > > > > Sorry to chime in. > > > > > > > > > > There is a PR to fix amalgamation. I was pinged several times to > > merge > > > it > > > > > but I don't think I have enough knowledge to do that. So it woul

Re: [Announcement] New Committer - Anirudh Acharya

Welcome! On Sat, Sep 28, 2019 at 12:06 AM Chaitanya Bapat wrote: > Congratulations Anirudh! Well deserved! > > On Thu, 26 Sep 2019 at 10:10, Chris Olivier > wrote: > > > Hi all, > > > > Please join me in welcoming Anirudh Acharya as a new committer of Apache > > MXNet (incubating)! > > > >

Re: [DISCUSS] CI Access Control

the community members have no > > choice but to wait for the issues to be resolved by the current system > > administrators. Other affected community members have no way to help even > > if they wish to. > > > > Given the existing Apache project governance model, I'd

Re: new website, docs code freeze

ogle tracker is not included in the new > > website. > > > > On Tue, Sep 24, 2019 at 4:17 PM Marco de Abreu > > wrote: > > > >> Hello, > >> > >> I checked the Google Analytics statistics and the launch of the new > >> website

Re: new website, docs code freeze

rco: > > Today, I searched for "mxnet conv" and clicked on the first link (Gluon > Neural Network Layers — mxnet documentation) and got a 404. > I suppose documents have different URLs under the new doc system? This may > explain drop in traffic. > > Philip. > > On Tue

Re: new website, docs code freeze

Hello, I checked the Google Analytics statistics and the launch of the new website reduced the traffic by over 80%: [image: image.png] (Please let me know if the image is not visible) How shall we handle this? Best regards, Marco On Mon, Sep 23, 2019 at 7:30 AM Zhao, Patric wrote: > For

Re: [Announcement] New PPMC Member - Tao Lv

Welcome! Zhao, Patric schrieb am Mo., 23. Sep. 2019, 06:32: > Congratulations, Tao! > > > > -Original Message- > > From: Sheng Zha > > Sent: Monday, September 23, 2019 12:07 PM > > To: d...@mxnet.apache.org > > Subject: [Announcement] New PPMC Member - Tao Lv > > > > Hi all, > > > >

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

We only need a mentors vote on general, but it certainly would be appreciated especially considering the licensing issues we're constantly encountering. One part of graduation is having a number of releases that went without issues. -Marco Tao Lv schrieb am Fr., 20. Sep. 2019, 17:10: > Sure.

Re: [DISCUSS] CI Access Control

number of jobs and thus either create immense costs or bring down the system. Also, we'd have to check how we can restrict the trigger permission to specific jobs. -Marco On Tue, Sep 17, 2019 at 2:47 PM Marco de Abreu wrote: > Hi Sheng, > > will I'm in general all in favour of

Re: [DISCUSS] CI Access Control

Hi Sheng, will I'm in general all in favour of widening the access to distribute the tasks, the situation around the CI system in particular is a bit more difficult. As far as I know, the creation of the CI system is neither automated, versioned nor backed up or safeguarded. This means that if

Re: [DISCUSS] Remove amalgamation

Is Amalgamation only used on Android though? Are there any other use cases? -Marco Pedro Larroy schrieb am Mi., 11. Sep. 2019, 11:57: > Hi Anirudh > > Appreciate your feedback and sorry if my email came across that way to you, > I think you might miss some context. I don't think calling

Re: [Announcement] New Committer - Junru Shao

Congratulations! -Marco MiraiWK WKCN schrieb am So., 8. Sep. 2019, 06:10: > Congrats, Junru! > > 发件人: Sheng Zha > 发送时间: 2019年9月8日 11:14 > 收件人: d...@mxnet.apache.org > 主题: [Announcement] New Committer - Junru Shao > > Hi all, > > Please join me in welcoming

Re: [DISCUSS] Remove amalgamation

I can recall that we had quite a few issues where people tried to use amalgamation. Have we identified these use cases so far and documented the alternative. I think the compilation only takes a few seconds and I think we also have some nightly tests for it. So far it seemed very low maintenance,

Re: [VOTE] Python 2 Removal for MXNet 1.6

eonard Lausen > wrote: > > > >> Due to References: header the prior email was still sorted in the > >> discussion thread. Cancelling this and resending without that header. > >> > >> Leonard Lausen writes: > >> > >> > Marco de Abreu wri

Re: [Discuss] MXNet Python < 3.6 Support Deprecation

Pedro, thanks for already starting these efforts, but it might be too early for that. Right now, this is a discussion thread where we try to gather different opinions in order to lay a good base for a future voting thread. In there, we would define the detailed timeline, versions etc. Until the

  1   2   3   4   5   6   >