mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bhavin Thaker <bhavintha...@gmail.com>
Subject Re: PROCESS: Contacting the Apache Infra team
Date Fri, 06 Oct 2017 16:35:35 GMT
Hi All,


Instead of this email getting lost in the hundreds of emails on dev@,
should we have an *Apache way guidelines wiki page for MXNet* based on the
various dos and don’ts learnt?



We are in incubating phase and likely to make some mistakes and learn from
them. However, we also want to learn from the mistakes of other Apache
projects and also contribute to that guidelines list.


Later, we can propose our guidelines page to contribute back to the *main
Apache guidelines page for incubating projects*.


Bhavin Thaker.

On Thu, Oct 5, 2017 at 10:24 PM, Sebastian <ssc.open@googlemail.com> wrote:

> I'm happy to help out with filing INFRA tickets for anyone working in a
> European time zone.
>
> Best,
> Sebastian
>
>
> On 06.10.2017 07:13, Henri Yandell wrote:
>
>> Hi Apache MXNet Committers and Contributors,
>>
>> As a community we've been sending a lot of requests (JIRA, HipChat etc) in
>> the direction of the Apache Infra team without discussing them first here.
>> As a community we are causing them a lot of work corralling topics that
>> would be better sorted out on our dev@ list first.
>>
>> We also have contributors who are contacting the Infra team without being
>> representatives of the project (i.e. committers). Contributors - your
>> energy is very much appreciated, but there is no way for Infra to know who
>> you are.
>>
>> Going forward, please raise _all_ Infra topics on the dev@ list for
>> initial
>> discussion. Once its been discussed as a community, one of the 5 mentors
>> for the project will make the request on the Infra JIRA. If a contributor
>> is subsequently looking to assist Infra (and because mentors aren't
>> infinitely scalable), my expectation is for a mentor to then introduce
>> that
>> contributor to Infra on their Hipchat if deeper conversation is needed.
>>
>> Thank you,
>>
>> Hen
>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message