Re: Severe legal issues with releases on repository.apache.org

On Sat, May 9, 2020 at 10:50 PM Tianqi Chen wrote: > > Seems the conclusion so far is only release source through apache and > release the binary builds as third party(as a different community, a > company or individual) Yes, that is the precedent established in multiple projects. I think it

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

Hi, I was trying to follow the build instructions[0] on Ubuntu 18.04. However, I a stumped at step 2: `cp config/config.cmake config.cmake` The file `cmake.conf` does not seem to exist in the tarball on the dist sit. `find . -name "cmake.conf" -print` finds nothing. In fact, the `config` folder

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

On Mon, Jan 20, 2020 at 1:17 PM Lausen, Leonard wrote: > If I don't misremember, our mentor Markus Weimer suggested at KDD 2019 in a > conversation that it's easiest to stop bundling non-ASF 3rdparty code. You do not misremember :-) If possible, it is easiest for everyone involved to c

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

> Shall we provide pip wheels for later release votes? Apache projects generally do not provide binaries as "signed off" release artifacts. That being said, binaries are commonly provided and marked as "convenience binaries". Hence, no vote is necessary on them, nor are they "official" releases.

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

ipate in voting. > > > >>> > > > >>> Best, > > > >>> Haibin > > > >>> > > > >>> On Fri, Jan 10, 2020 at 3:50 PM Haibin Lin > > > > > >>> wrote: > > > >&g

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

+1 (binding) I tested on Ubuntu 18.04 on the Windows Subsystem for Linux. Tested: * Built from source using the instructions here [0] * Ran the tests in `./build/tests/mxnet_unit_tests` * SHA512 of the archive Not tested: * Language bindings * CUDA or other GPU acceleration *

Re: MXNet Podling Report - October

Sorry about not signing in time. I messed up my email filters somehow and the reminder did not make it to my inbox. I'll fix that :) -- Markus On Wed, Oct 10, 2018 at 6:45 AM Bob Paulin wrote: > Hi, > > I reviewed the report but it appears to be final now so it doesn't look > like I can edit

Re: Suggestions on how to increase community involvement on Apache MXNet incubating?

I really like most of what has been said, and the below might be a bit of a repeat, but through a different lens. One key aspect to consider when thinking about participation in OSS projects is the journey a contributor makes, which starts before even using the software. Each of the steps of the

Re: Podling Report Reminder - January 2018

to Incubator Wiki sometime today - mentors can then > > sign off. > > > > On Sun, Dec 31, 2017 at 12:38 PM, Markus Weimer <mar...@weimo.de> wrote: > > > >> Thanks for putting this together! I made a pass and left one comment. > >>

Re: Podling Report Reminder - January 2018

On Sun, Dec 31, 2017 at 9:42 AM, Suneel Marthi wrote: > I'll post the report to Incubator Wiki sometime today - mentors can then > sign off. > Thanks! Markus

Re: [DISCUSSION] Adding labels to PRs

Option 2 works for us over in REEF. We are a bit (too) religious about it [0], but it creates really nice commit messages[1]. We require each commit message to start with a one line summary which names the JIRA in brackets and describes the change, e.g. `[REEF-1234] Added integration with mxnet`.

Re: Podling Report Reminder - July 2017

On Wed, Jul 5, 2017 at 3:30 PM, Suneel Marthi wrote: > Thanks Dom, the report has been filed. > > Mentors, please sign-off on the report. Thanks and done! Markus

Re: Test

Yes, it came through. -- Markus On Sun, Jun 25, 2017 at 8:29 PM, Chris Olivier wrote: > Does this email work? I am having trouble subscribing

Re: Draft of March 2016 Podling Report

On 2017-03-01 22:13, Suneel Marthi wrote: Thanks Henry. Done, other mentors please go ahead and sign the report. Thanks for drafting! I signed. Markus