On Wed, Aug 02, 2017 at 12:27:52AM -0700, Henri Yandell wrote:
> Following up on this - the first 3 reports in a new podling, or a new TLP
> PMC, are made monthly. Then it moves to quarterly.
> So MXNet doesn't have to report monthly again until it graduates.
> The quarterly cycle for MXNet
On Fri, Aug 04, 2017 at 12:42:12AM -0700, Henri Yandell wrote:
> I worry that it creates a high barrier to entry.
+1 from my side to that worry.
I'm currently in the process of creating a slide deck and wanted to use the
mxnet logo as part of that presentation.
So I want ahead and opened
I found a directory listing including a test directory. Is that expected?
Clicking on the "test" directory
On Thu, Aug 10, 2017 at 12:31:23PM -0700, Bhavin Thaker wrote:
> The criteria should look not only at Quantity but at the Quality of work as
Just as one additional data point:
http://community.apache.org/newcommitter.html is the Apache Community
Development Project's guidelines.
On Thu, Jul 13, 2017 at 09:30:33AM +0200, Sebastian Schelter wrote:
> This mail is a little bit off-topic, but I would like to share a story that
> shows how important it is for open source projects to move to their own
> infrastructure (like the one provided by the ASF) and not rely on the
Other projects are using dedicated lists like issues@ for this.
What workflow did you use so far to keep up with what's going on in the project?
Am 28. Juli 2017 22:24:54 MESZ schrieb Dom Divakaruni
>Can we please do this?
>> On Jul 28,
Am 4. August 2017 13:27:16 MESZ schrieb Chiyuan Zhang :
>1. There are some people who contribute to MXNet due to something else
>(e.g. he used MXNet in his project and would like to contribute back
>examples, or bug fix, or new operators, etc.)
Many Apache projects are
On Fri, Aug 04, 2017 at 12:27:16PM +0100, Chiyuan Zhang wrote:
> Suppose we lower the standard or completely remove the formal standard for
> committers, then we could probably be able to get more committers from the
> first type. But that might not necessarily be good to us
Can you elaborate
On Thu, Jun 15, 2017 at 06:49:21AM +0200, Suneel Marthi wrote:
> anyone with apache.org shuld be able to register on slack - Sebastian was
> asking me the same question in Berlin last week.
> Suggest leave the channel open to anyone registering with apache.org email.
Is there a way to make it
First of all, great to read there are people with interest and time to update
Am 12. September 2017 19:00:21 MESZ schrieb Seb Kiureghian :
>The pPMC would like to update the website.
This wording is worrying to me. It sounds like a decision was made out of
Am 4. Dezember 2017 01:08:37 MEZ schrieb Hen :
>Basically a reminder that it should be a PMC decision, or if needing to
>move quickly a decision of the PMC Chair (mentors while a podling).
Remember that for provenance reasons all communication on github is mirrored on
Am 16. November 2017 23:04:05 MEZ schrieb "Lupesko, Hagay" :
>Today AWS announced contributing ONNX-MXNet,
Just for clarification: this package is going to be/ intended to be contributed
where to? Or do you mean "published under a free and open source license"?
Just a quick heads-up: we'll have several senior Apache ppl in Berlin on
November 20th for http://fossbackstage.de
The location is two UBahn stops east of the Amazon offices. The event is free
as in free beer. While I will pick up printed batches in an hour you can still
sign up and show
Am 4. Dezember 2017 01:08:37 MEZ schrieb Hen :
>That gives me a chance to mention a PMC Chair's role.
>When MXNet graduates, one of the initial PMC members will be nominated
>the board to be the chair. That chair is a VP/Officer of the 501(c)(3)
>is the one who is
I would like to share some inspiration:
I do believe in pulling people in quickly, in giving them responsibility early,
on rewarding contributions in a timely manner.
Apache was born out of a collaboration of people
As an aside: if you want to learn more on the background of Apache, or free and
open source in general join us at Http://fossbackstage.de in Berlin in walking
distance from U2 stop Eberswalder Str.
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
I'm not Hen, but:
Everyone who has an Apache.org address, that is every committer, has to sign
this. The documents are tracked centrally in
Am 9. Januar 2018 18:25:50 MEZ schrieb Mu Li :
>We should encourage to contract a specific contributor for issues and
My head translates "encourage to contact specific contributor" into "encourage
to contact specific contributors inbox". This translated version is
Another two side notes:
Even if there are maintainers, if for instance there's a security issue in
module X the entire PMC will be held accountable for fixing it. So for instance
the maintainer being offline is no excuse for not taking care of it. "That's
not my issue" is not a valid answer.
Am 16. Januar 2018 01:40:48 MEZ schrieb Steffen Rochel
># Anybody can add themselves or a team as additional contributors
># to get notified about changes in a specific package.
># See https://help.github.com/articles/about-teams how to setup teams.
Am 15. Januar 2018 04:59:19 MEZ schrieb Chris Olivier :
>+1 for the line: # Anybody can add themselves
+1 to this line, maybe add that the project intends to use to codeowner
function as a notification mechanism.
This can be very handy also for new committers trying to
Am 2. Februar 2018 01:20:31 MEZ schrieb Sheng Zha :
>Specifically, for merging PRs, if there are open review comments and
>changes afterwards didn’t address the comments, we should have a
>grace-period of 24 hours for commenters to respond to the changes.
On Thu, Aug 02, 2018 at 03:29:48PM -0700, Steffen Rochel wrote:
> I would like to thank all attendees, especially Ming Zhang for the deep
> dive in the challenges he is facing.
> Please see hangout notes at
Am 2. August 2018 20:33:44 MESZ schrieb Ivan Serdyuk
>I have a single global question: I am looking for a global plan for
>covering MXNet, for developer meetups.
Can you elaborate what you mean by global plan for covering mxnet for developer
> There are various APIs, for
Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang
>My concern is where should my code be finally merged. This bot is not a
>part of MXNet framework but it serves MXNet community. For now, a good
>option is to have a separate repo for infrastructure.
As this would be something that serves
Am 8. August 2018 21:34:47 MESZ schrieb Tianqi Chen :
>As far as I understand, these are packages that are build on top of
>and runs on MXNet,
Going through the hosted subdomains that seems not quite correct (or the
content hosted is not entirely correct):
"Welcome to the MxNet
On Wed, Aug 08, 2018 at 02:39:22PM -0700, Mu Li wrote:
> > Going through the hosted subdomains that seems not quite correct (or the
> > content hosted is not entirely correct):
> > "Welcome to the MxNet discussion forum." Is what I get as a greeting
> > navigating to discuss.mxnet.io
I had a bit of time recently to walk through some of the getting started docs.
First time setup of mxnet is really well described and worked seamlessly.
Next step was going through some getting started examples - the straight dope
docs linked from the mxnet setup page were useful for that.
Am 8. August 2018 21:17:44 MESZ schrieb Mu Li :
>MXNet's website is http://mxnet.incubator.apache.org/. I own mxnet.io,
>which was mxnet's main site before, but now we are using its subdomains
>host various packages in the mxnet ecosystem.
I'm still confused: There's what looks like
On 18/07/18 23:30, Mu Li wrote:
A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK.
What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
Your suggestion triggered my question because:
There's also a couple Apache ppl not involved with mxnet and not subscribed
here. Want to invite them as well?
Maybe also get your meetup listed there:
Am 1. März 2018 05:58:26 MEZ schrieb Steffen Rochel :
Am 20. Juni 2018 17:43:35 MESZ schrieb Steffen Rochel :
>After a reasonable time like 6 months we can evaluate the adoption of
>and effort to support and can make an informed, data driven decision
In addition to adoption, I would add "amount of users converted to
Am 10. Oktober 2018 04:31:49 MESZ schrieb Chris Olivier :
>is it convenient to define the difference and the rights and privileges
>each? write access, private list, voting and veto power, etc?
+1 - also, likely it would make sense to also list the responsibilities of each.
Am 10. Oktober 2018 11:04:30 MESZ schrieb kellen sunderland
>impression is there's a high degree of knowledge and experience
>make strategic design decisions on the project.
This statement indicates a certain understanding of what a PMC actually does.
As a first step,
On 28/09/18 11:27, kellen sunderland wrote:
I'd love to see some more
sustained contribution from other open source communities to help us out in
That's not exactly the model I have seen to work. What I have seen works
really well at other projects is pulling users in as
Am 10. Oktober 2018 16:16:47 MESZ schrieb sandeep krishnamurthy
>However, like others suggested, success of this whole effort will be
>on defining clear responsibility of PMC, committers and path for the
>community to be part of committers and PMC.
PMC member and chair are ASF
On 2018/10/10 09:04:30, kellen sunderland wrote:
> When it comes to responsibilities one high-level suggestion I'd make is
> that core members retain decision making abilities for the 'big' decisions
> where experience is required.
Written from the PMC point of view:
Every individual member
On Thu, Sep 27, 2018 at 08:32:53AM -0400, Steffen Rochel wrote:
> Congratulation to all contributors to the project, well deserved!
> Let's consider the recognition as
Mail list logo