Jim can you sign for me? I am trying to get edit access for my new wiki acct.
On Tue, May 2, 2017 at 9:12 PM, Todd Lipcon <[email protected]> wrote: > Signed. Thanks for the reminder > > On Tue, May 2, 2017 at 10:08 AM, Jim Apple <[email protected]> wrote: > > > This is up and ready for mentor sign-off at https://wiki.apache.org/inc > > ubator/May2017 > > > > On Sat, Apr 29, 2017 at 10:06 AM, Jim Apple <[email protected]> > wrote: > > > >> Since there were no volunteers, I did it. Any comments before I post it? > >> I have added some URLs or command lines to make it easier for any future > >> volunteers to replicate the statistics on future reports. > >> > >> Impala > >> > >> Impala is a high-performance C++ and Java SQL query engine for data > >> stored in > >> Apache Hadoop-based clusters. > >> > >> Impala has been incubating since 2015-12-03. > >> > >> Three most important issues to address in the move towards graduation: > >> > >> 1. Growth of the developer community > >> 2. > >> 3. > >> > >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > >> aware of? > >> > >> No > >> > >> How has the community developed since the last report? > >> > >> There have been 267 Commits: > >> git log --format='%ci' | grep -cE '2017-0(2|3|4)' > >> > >> 42 of those commits were by non-committers: > >> git log --format='%ae %ci' | grep -E '2017-0(2|3|4)' | cut -d ' ' -f > >> 1 | sort | uniq -c | sort -n > >> > >> There were 114 emails to the user list. Of the top nine > >> participants, six were not committers: > >> https://lists.apache.org/[email protected]: > >> dfr=2017-2-1|dto=2017-4-30: > >> > >> There are six new committers: > >> https://lists.apache.org/[email protected]:dfr > >> =2017-2-1|dto=2017-4-30:%22has%20invited%22 > >> <https://lists.apache.org/[email protected]. > org:dfr=2017-2-1%7Cdto=2017-4-30:%22has%20invited%22> > >> > >> Two new contributors have announced plans to take on large > >> development efforts (JSON support and ppc64le support). > >> > >> How has the project developed since the last report? > >> > >> Two of the "three most important issues to address in the move > >> towards graduation" from our last report in February have been > >> completed: The bug tracker was transitioned to issues.apache.org, > >> and the documentation now describes Apache Impala specifically, not > >> any non-Apache extensions. The documentation has also been posted to > >> http://impala.incubator.apache.org/docs/build/html/index.html and > >> http://impala.incubator.apache.org/docs/build/impala.pdf. > >> > >> Many commits have landed since our last report towards increasing > >> the performance of metadata. > >> > >> How would you assess the podling's maturity? > >> Please feel free to add your own commentary. > >> > >> [ ] Initial setup > >> [ ] Working towards first release > >> [X] Community building > >> [X] Nearing graduation > >> [ ] Other: > >> > >> Once the developer community has grown a bit, Impala will be ready > >> to contemplate graduation. > >> > >> Date of last release: > >> > >> 2017-01-22 > >> > >> When were the last committers or PPMC members elected? > >> > >> 2017-04-24 > >> > >> Signed-off-by: > >> > >> [ ](impala) Tom White > >> Comments: > >> [ ](impala) Todd Lipcon > >> Comments: > >> [ ](impala) Carl Steinbach > >> Comments: > >> [ ](impala) Brock Noland > >> Comments: > >> > >> IPMC/Shepherd notes: > >> > >> > >> > >> On Thu, Apr 27, 2017 at 8:11 AM, Jim Apple <[email protected]> > wrote: > >> > >>> I have been doing these for the past few quarters. Would anyone else > >>> like to try? It will take less than an hour, and I can help if you > need it. > >>> > >>> Quarterly reporting is required from all Apache projects, even > graduated > >>> ones, so this is good practice if you want to be on the PPMC (or PMC > after > >>> we graduate) or even the PMC Chair, who is responsible for most PMC > >>> paperwork after graduation. > >>> > >>> On Wed, Apr 26, 2017 at 5:41 PM, <[email protected]> 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 May 2017, 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, May 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/May2017 > >>>> > >>>> 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 > >>>> > >>> > >>> > >> > > > > > -- > Todd Lipcon > Software Engineer, Cloudera >
