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:
>
> >
to
it then the community 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
that
this is Tomato 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
ying that trademarks 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
> apparentl
t 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
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
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 hap
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:
com/gluon/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.
> Th
(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
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 legal
OK("
>
>1. Your application must have material additional functionality,
>beyond the included portions of the SDK.")
>
> but I not don't understand the legal lingo
>
> @Hen : Could you provide input to this?
>
> Thanks, Naveen
>
> On Mon, Dec 1
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 stories/tasks
given over the last 2 years.
Hen
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 <
> dz
g for help).
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/br
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
> ho
Nice to Haves small 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
wr
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
>
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
e again. Can we get a trademark C&D 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/1
Please all go read: https://www.apache.org/foundation/policies/conduct.html
* Be open.
* Be empathetic, welcoming, friendly, and patient.
* Be collaborative.
* Be inquisitive.
* Be careful in the words that you choose.
I'm not seeing evidence of this right now.
Hen
intaining CI, helping people on Slack). 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:
&g
process, this is
about whether the 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 of
forward faster, as is vital to make
> it easier to contribute so we can attract more users.
>
+1. The podling pmc needs to find consensus on the become-committer stage.
Hen
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
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 pr
ert. At best
'github:john-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 "[MXNE
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 some
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
itter-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, 20
igned 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 prob
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:
>
>
> htt
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,
>
> This PR from the Intel folks is adding supp
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 gener
this issue with readthedocs before? Should we be
sending them a Trademark takedown request?
Thanks,
Hen
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
> of
> a file with categor
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
e. 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 wrote:
>
> > Agreed.
> >
> > RCs are for the project contributors to rev
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 wrote:
> I have mentioned this before and I still think that the default MX
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 used for other purposes
> than
.
Hen
On Mon, Apr 30, 2018 at 1:23 PM Gautam 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 waiting to merge for almost 4
Will there be a write up/presentation upload for those unable to attend?
On Sun, Apr 15, 2018 at 4:47 PM Steffen Rochel
wrote:
> All - updated agenda published at:
> https://www.meetup.com/Apache-MXNet-Seattle-meetup/events/249178668/
>
> If you are interested and available, please RSVP if you h
gt; to be on that platform directly.
> >
> > Can a China user access the Apache blog site that Hen mentioned? Also,
> > I'm not familiar with the Apache blog and how you contribute. I don't
> > see info about it on Confluence or elsewhere. Certainly sounds like
> >
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
wrote:
> Thank you Henri, Pedro.
> Yes, we are only referring to the one documentatio
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 have particular preferences or
they show restraint 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 o
Will review to tonight.
Noting that I’m going to -1 any report in the future that is written by a
non-committee.
Hen
On Mon, Apr 9, 2018 at 11:28 AM Steffen Rochel
wrote:
> Dear mentors - I posted the MXNet podling report at
> https://wiki.apache.org/incubator/April2018#p
Noting that the linked FAQ is for CC-BY-SA and unmodified media (ie:
images, sound, video); so it's not relevant.
I think this is worth raising on legal-discuss@. CC-BY software is an
issue, but resolved.html hasn't stated anything regarding CC-BY for a
documentation file.
Hen
On
lease [ ] 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, 20
-- 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 <
dev-ow...@mxnet.incubator.apache.org>
Hi Folks,
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"
> wrote:
>
> > Lol, at least Link this thread please to show
someone adding the tests back later, that’s
just a good intention.
Hen
On Thu, Feb 1, 2018 at 11:11 Mu Li 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
> agreement with Da
se
text. If two components don't have exactly the same license text then they
are not the same license. Most commonly nowadays that means that you can't
merge BSD licenses together, and sometimes can't merge MIT together
(depending on variants and how you handle the copyright statement
enses.
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
wrote:
> Marco,
> Thanks a lot for looking through this ! Some com
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 a page on Apache
> wiki so
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
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 yo
the plan 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
ho is ultimately responsible to the board for the project. Very
occasionally a chair may have to do something without consulting with the
PMC as a whole, and they're expected to get it right.
Hen
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 wrote:
>
>> Hi Sergey,
>>
>
ht in, instead focusing on contributor/author.
Are you good if I change the code to list you (and anyone else who works on
it and wants to add themselves) to the AUTHORS section of the
README.md/MXNet.pm, and remove the explicit Copyright statement?
Thanks,
Hen
Sorry, I should have cc'd dev@ on this.
-- Forwarded message --
From: Hen
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 don't think n
would be
good.
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-r
What's the license of each?
By submodule do you mean git pointing to a url of a specific tag/branch, or
copying the actual code directly in?
On Tue, Nov 21, 2017 at 4:51 PM, Stephen Bull wrote:
> I like 3rdparty, and definitely helps newcomers too. As long as it's kept
> relatively clean and up
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
wrote:
>
>
> Am 16. November 2017 23:04:05 MEZ schrieb "Lupesko, Hagay" <
> lupe...
its projects; DMLC does not appear to have source headers on their
files, its equivalent of Apache's legal committee should strongly think
about that standardizing on that for all its projects imo);
4) There is no NOTICE file (again, imo the DMLC legal thinkers should
strongly think about having NOTICE files imo).
So agreed that there's a change to make, but there's no requirement to keep
author's names in files. Note that there is a practice (and it's a
recommended or even mandatory legal practice, I'm not sure which) to keep a
Copyright Owner's name in a file, but author and copyright owner are
different concepts.
Hen
+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, No
onfer
with security@ on the process.
Hen
On Tue, Nov 7, 2017 at 1:45 PM, Chris Olivier wrote:
> Do we need a vote for a critical patch release?
>
> On Tue, Nov 7, 2017 at 12:08 PM, Meghna Baijal >
> wrote:
>
> > Hi All,
> > A patch release is being planned for
I thought a patch release was exactly the same as a full release; except
that there is less discussion of the features involved.
Did you see a more lightweight release process described somewhere? I'd
expect an RC and vote.
Hen
On Tue, Nov 7, 2017 at 12:08 PM, Meghna Baijal
wrote:
>
/0.12.0/
Note that you have to have a delay between publishing your release, and
announcing your release, so that the mirrors have time to sync. I believe
that's 24 hours.
Hen
On Wed, Nov 1, 2017 at 12:27 PM, Chris Olivier
wrote:
>
>
> A Link to the Download is here: http://www.a
d hardware, or can we have this
two tier approach?
Hen
On Fri, Oct 20, 2017 at 1:01 PM, sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:
> Hello all,
>
> I am hereby opening up a discussion thread on how we can stabilize Apache
> MXNet CI build system.
>
> Probl
. This is also 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
t's been a long time with some basic
things not done yet.
Hen
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 wrote:
> Confirmed on the email.
>
> Can you sign in at blogs.apache.org using your Apache LDAP credentials
> please?
>
> That will add you to the pool o
out the new version, and your
recruiting pipeline.
Hen
On Mon, Oct 30, 2017 at 4:08 PM, Suk Won Kim wrote:
> Created a page in cwiki for a draft of blog post for MXNet v0.12 release.
> https://cwiki.apache.org/confluence/display/MXNET/
> Draft+of+blog+post+for+MXNet+v0.12+release
>
> Thanks.
> --
>
> *Sukwon Kim, *
>
Confirmed on the email.
Can you sign in at blogs.apache.org using your Apache LDAP credentials
please?
That will add you to the pool of users, and then one of the mentors can add
you to the blog :)
Hen
On Tue, Oct 31, 2017 at 2:08 PM, sandeep krishnamurthy <
sandeep.krishn...@gmail.com>
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 impacting
> development. I prop
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:
> Hello,
>
> Trying to subscribe
Related question - which committer wants to publish the blog? It needs to
be a member of the project.
On Mon, Oct 30, 2017 at 4:41 PM, Sally Khudairi wrote:
> Thanks, Sukwon; hello Chris and MXNet pPMC.
>
> I have been discussing this with Sukwon and have agreed on the
> following tactics:
> 1)
https://issues.apache.org/jira/browse/INFRA-15407
On Mon, Oct 30, 2017 at 12:12 PM, Hen 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 ahead and open a JI
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 wrote:
> Hi all,
> Meghna is going to execute the MXNet
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 of builds:
>
> * Have terraform
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
ache.
One of the issues raised in 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
t
runs
under different community rules) thinks another.
Something is rotten.
One solution: The MXNet community forks the DMLC code it relies on into the
MXNet codebase and moves on without being tied down by the decisions of a
non-compatible community.
Hen
On Thu, Oct 19, 2017 at 11:59 AM, Tianqi
> > On Mon, Oct 16, 2017 at 10:34 PM Mu Li wrote:
> >
> > > there are several private channels on apache-mxnet.slack.com, how we
> are
> > > going to deal with it?
> > >
> > > On Mon, Oct 16, 2017 at 10:19 PM, Hen wrote:
> > >
> > &
+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 would like to suggest to shut down
> > apache-mxn
88 matches
Mail list logo
