Re: Podling Report Reminder - January 2018

2017-12-30 Thread Suk Won Kim 
Hi all,
Bhavin Thaker and I propose the attached podling report draft and would
like your review comments and contributions to the report by 02-Jan, 2018,
since the report is due on 03-Jan, 2018. Mentors, please signoff this draft
via email by 1/2/2018 since we plan to submit the report by 1/3.

Please find the draft below.
https://docs.google.com/document/d/1PGhs96klZB6DXhpK9_biPh4-aCm8-bWwFzexnOW_GMA/edit




On Sat, Dec 30, 2017 at 6:30 AM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 17 January 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, January 03).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/January2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>



-- 
*Sukwon Kim*

Re: Apache MXNet Development Processes: Proposed update

2017-12-30 Thread Bhavin Thaker 
Thank you everybody for your +1 approval, comments and answering the
questions asked.

With zero -1 votes and eight +1 votes that ran over a time period of 15
calendar days, I consider the final outcome as Yes for the proposal.

So, I have updated the Apache MXNet wiki as proposed:
https://cwiki.apache.org/confluence/display/MXNET/Development+Process

Wishing all of you a very happy new year 2018!

Regards,
Bhavin Thaker.

On Fri, Dec 22, 2017 at 12:36 AM, kellen sunderland <
kellen.sunderl...@gmail.com> wrote:

> Sheng’s comments are correct.  GitHub will save review comments for
> ‘outdated’ commits, and they’re surfaced in the interface.  I frequently
> amend then force push (i.e. change history) to address comments in order to
> keep my commits tidy.  It’s always possible to expand a previous version
> selection to see the old comment history.
>
> Example: https://github.com/awslabs/sockeye/pull/31
>
> -Kellen
>
> From: Zha, Sheng
> Sent: Friday, December 22, 2017 12:34 AM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: Apache MXNet Development Processes: Proposed update
>
> About comment on b), I think after rebase the existing review comments
> will remain in the PR even if rebase and history rewriting happens in the
> fork. The corresponding commit may be gone because of the change in commit
> history in the PR fork and thus the link change.
>
> Best regards,
> -sz
> On 12/15/17, 5:38 PM, "Markus Weimer"  wrote:
>
> On Fri, Dec 15, 2017 at 5:00 PM, Bhavin Thaker  >
> wrote:
>
> >a) It is NOT recommended for a committer to merge pull requests
> that the
> >committer authored. Instead the committer MUST get at least one
> approval
> >from another committer to merge his/her pull request.
> >
>
> +1
>
>
> >- b) When you update a pull request with upstream, you MUST use
> rebase
> >to ensure that the pull request is easy to review by the
> community. See
> > the
> >how-to link here:
> >https://mxnet.incubator.apache.org/community/contribute.html
>
>
> Doesn't this potentially erase the review history on GitHub?
>
> Markus
>
>
>
>

Podling Report Reminder - January 2018

2017-12-30 Thread johndament 
Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 17 January 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, January 03).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/January2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC