Re: Broken Link

2017-10-23 Thread kenneth mcfarland
That works great, thank you!

On Oct 23, 2017 7:57 PM, "Mostafa Mokhtar"  wrote:

> This link should work:
>
> cidrdb.org/cidr2015/Papers/CIDR15_Paper28.pdf
>
> Will try to update the link in http://impala.apache.org/overview.html.
>
> On Mon, Oct 23, 2017 at 7:52 PM, kenneth mcfarland <
> kennethpmcfarl...@gmail.com> wrote:
>
> > Hi Impala Crew,
> >
> > I really wanted to read about the architecture as I'm new, curious, and
> > decide to take a swing at IMPALA-5392.
> >
> > This link on the /overview page is busted:
> >
> > http://www.cidrdb.org/cidr2015/Papers/CIDR15_Paper28.pdf
> >
> > Thanks in advance,
> >
> > Kenny
> >
>


Re: Broken Link

2017-10-23 Thread Mostafa Mokhtar
This link should work:

cidrdb.org/cidr2015/Papers/CIDR15_Paper28.pdf

Will try to update the link in http://impala.apache.org/overview.html.

On Mon, Oct 23, 2017 at 7:52 PM, kenneth mcfarland <
kennethpmcfarl...@gmail.com> wrote:

> Hi Impala Crew,
>
> I really wanted to read about the architecture as I'm new, curious, and
> decide to take a swing at IMPALA-5392.
>
> This link on the /overview page is busted:
>
> http://www.cidrdb.org/cidr2015/Papers/CIDR15_Paper28.pdf
>
> Thanks in advance,
>
> Kenny
>


Broken Link

2017-10-23 Thread kenneth mcfarland
Hi Impala Crew,

I really wanted to read about the architecture as I'm new, curious, and
decide to take a swing at IMPALA-5392.

This link on the /overview page is busted:

http://www.cidrdb.org/cidr2015/Papers/CIDR15_Paper28.pdf

Thanks in advance,

Kenny


Re: Podling Report Reminder - November 2017

2017-10-23 Thread Jim Apple
Thanks - added to wiki with those two sign-offs

On Mon, Oct 23, 2017 at 11:31 AM, Brock Noland  wrote:

> Same for me
>
> On Mon, Oct 23, 2017 at 1:28 PM, Todd Lipcon  wrote:
>
> > Looks good to me. Feel free to add my sign-off when you post to the wiki.
> >
> > -Todd
> >
> > On Sat, Oct 21, 2017 at 4:34 PM, Jim Apple  wrote:
> >
> > > Please review:
> > >
> > > 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:
> > >
> > >   Our graduation proposal is in the works.
> > >
> > > 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 279 Commits:
> > >git log --format='%ci' | grep -cE '2017-(08|09|10)'
> > >
> > >  62 of those commits were by non-committers:
> > >git log --format='%an %ci' | grep -E '2017-(08|09|10)' | tr -d
> > '0-9\-' |
> > > cut -d ' ' -f -2 | sort | uniq -c | sort -n
> > >
> > > Of the 37 patch authors, 16 were not committers at the beginning of
> this
> > > reporting period.
> > >
> > >  There are three new committers members and one new PPMC member:
> > >
> > > https://lists.apache.org/list.html?d...@impala.apache.org:
> > > dfr=2017-8-1|dto=2017-10-31:%22has%20invited%22
> > >
> > > Impala has done a fourth release with a third release manager.
> > >
> > > Impala has begun graduation procedures: we have held a community
> > discussion
> > > and a community vote on graduation, both unanimous. We have established
> > our
> > > intended PMC. Next, we will draft our charter and hold a discussion on
> > > general@incubator.
> > >
> > > How has the project developed since the last report?
> > >
> > > Impala has removed the old unpartitioned hash and aggregation nodes,
> > relics
> > > from years ago that were kept around for backwards compatibility: the
> new
> > > buffer management makes these obsolete. Code generation for decimal and
> > > timestamp types has been added to the text scanner, increasing the
> > > performance of some queries by up to 19%. More robust query plans in
> case
> > > of data skew have made some aggregations eight times as fast. A number
> of
> > > large changes are in-flight, including changes to equivalence class
> > > computation in the planner, more decimal semantics adjustments, min-max
> > > filters for Kudu, and multi-threaded metadata loading that increases
> the
> > > performance of some metadata operations by 8x.
> > >
> > > How would you assess the podling's maturity?
> > > Please feel free to add your own commentary.
> > >
> > >  [ ] Initial setup
> > >  [ ] Working towards first release
> > >  [] Community building
> > >  [X] Nearing graduation
> > >  [ ] Other:
> > >
> > > Date of last release:
> > >
> > >  2017-09-14
> > >
> > > When were the last committers or PPMC members elected?
> > >
> > >  2017-09-29
> > >
> > > Signed-off-by:
> > >
> > >  [ ](impala) Tom White
> > > Comments:
> > >  [ ](impala) Todd Lipcon
> > > Comments:
> > >  [ ](impala) Carl Steinbach
> > > Comments:
> > >  [ ](impala) Brock Noland
> > > Comments:
> > >
> > > On Sat, Oct 21, 2017 at 3:43 PM,  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, 15 November 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, November 01).
> > > >
> > > > 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 

Re: Time for graduation?

2017-10-23 Thread Jim Apple
As a clarification: Todd, Marcel, and I are "vote monitors", but we can't
see who voted for whom or even who has cast a vote.

On Mon, Oct 23, 2017 at 11:17 AM, Todd Lipcon  wrote:

> Thanks for setting this up, Jim! Can confirm that the vote request came
> through.
>
> -Todd
>
> On Mon, Oct 23, 2017 at 11:14 AM, Jim Apple  wrote:
>
> > I have sent out the Chair election ballot via steve.apache.org to people
> > who will be listed in our resolution as PMC members, via email addresses
> (@
> > apache.org). Please vote. The vote closes Friday.
> >
> > On Fri, Oct 20, 2017 at 10:19 PM, Jim Apple 
> wrote:
> >
> > > I have a resolution with a blank space for chair, and the community
> voted
> > > unanimously to graduate.
> > >
> > > I also have a set of people who will make up the PMC (should we
> > graduate),
> > > based on their responses to the email I sent.
> > >
> > > We have two volunteers for PMC chair. I'll call a vote with potential
> PMC
> > > members as voters, starting on Monday using https://steve.apache.org/,
> > > following examples from other ASF projects.
> > >
> > > On Thu, Oct 12, 2017 at 3:24 PM, Jim Apple 
> wrote:
> > >
> > >> I think it would be a good time to graduate. I'm very proud of the
> > >> progress the community has made in terms of acting in an Apache way.
> > >>
> > >> Some logistics:
> > >>
> > >> I would be happy to serve as an initial chair.
> > >>
> > >> I'll draft a resolution, with a blank space for chair. This doesn't
> mean
> > >> we have to agree now is the time to graduate, but we'll have it
> > available
> > >> for discussion and revision whenever we are ready.
> > >>
> > >> If we decide to graduate now, maybe we could email everyone who is on
> > the
> > >> PPMC, ccing private@, to see if they are still interested in being on
> > >> the PMC, and taking no response to mean "yes" until we hear otherwise,
> > in
> > >> case someone is on vacation away from email, or in the hospital, or
> > >> something.
> > >>
> > >> Also, mentors are traditionally included in a graduating podling's
> PMC,
> > >> right?
> > >>
> > >> On Thu, Oct 12, 2017 at 2:17 PM, Todd Lipcon  wrote:
> > >>
> > >>> Hey Impala community,
> > >>>
> > >>> It's been a while that all of the Impala infrastructure has been
> moved
> > >>> over, and the community appears to be functioning healthily,
> generating
> > >>> new
> > >>> releases on a regular cadence as well as adding new committers and
> PPMC
> > >>> members. All of the branding stuff seems great, and the user mailing
> > list
> > >>> has a healthy amount of traffic and a good track record of answering
> > >>> questions when they come up.
> > >>>
> > >>> As a mentor I think it's probably time to discuss graduation. The
> > project
> > >>> is already functioning in the same way as your typical Apache TLP and
> > it
> > >>> seems like it's time to become one.
> > >>>
> > >>> Any thoughts? If everyone is on board, the next step would be:
> > >>>
> > >>> 1. Pick the initial PMC chair for the TLP. According to the published
> > >>> Impala Bylaws it seems that this is meant to rotate annually, so no
> > need
> > >>> to
> > >>> stress too much about it.
> > >>>
> > >>> A couple obvious choices here would be Marcel (as the original
> founder
> > of
> > >>> the project) or perhaps Jim (who has done yeoman's work on a lot of
> the
> > >>> incubation process, podling reports, etc). Others could certainly
> > >>> volunteer
> > >>> or be nominated as well.
> > >>>
> > >>> 2. Draft a Resolution for the PPMC and IPMC to vote upon.
> > >>> -- the resolution would include the above-decided chair as well as
> the
> > >>> list
> > >>> of initial PMC, etc.
> > >>> -- the Initial PMC could be just the current list of PPMC, or you
> could
> > >>> consider adding others at this point as well.
> > >>>
> > >>>
> > >>> I can help with the above process but figured I'd solicit opinions
> > first
> > >>> on
> > >>> whether the communit feels it's ready to graduate.
> > >>>
> > >>> Thanks
> > >>> Todd
> > >>>
> > >>
> > >>
> > >
> >
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>


Re: Podling Report Reminder - November 2017

2017-10-23 Thread Brock Noland
Same for me

On Mon, Oct 23, 2017 at 1:28 PM, Todd Lipcon  wrote:

> Looks good to me. Feel free to add my sign-off when you post to the wiki.
>
> -Todd
>
> On Sat, Oct 21, 2017 at 4:34 PM, Jim Apple  wrote:
>
> > Please review:
> >
> > 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:
> >
> >   Our graduation proposal is in the works.
> >
> > 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 279 Commits:
> >git log --format='%ci' | grep -cE '2017-(08|09|10)'
> >
> >  62 of those commits were by non-committers:
> >git log --format='%an %ci' | grep -E '2017-(08|09|10)' | tr -d
> '0-9\-' |
> > cut -d ' ' -f -2 | sort | uniq -c | sort -n
> >
> > Of the 37 patch authors, 16 were not committers at the beginning of this
> > reporting period.
> >
> >  There are three new committers members and one new PPMC member:
> >
> > https://lists.apache.org/list.html?d...@impala.apache.org:
> > dfr=2017-8-1|dto=2017-10-31:%22has%20invited%22
> >
> > Impala has done a fourth release with a third release manager.
> >
> > Impala has begun graduation procedures: we have held a community
> discussion
> > and a community vote on graduation, both unanimous. We have established
> our
> > intended PMC. Next, we will draft our charter and hold a discussion on
> > general@incubator.
> >
> > How has the project developed since the last report?
> >
> > Impala has removed the old unpartitioned hash and aggregation nodes,
> relics
> > from years ago that were kept around for backwards compatibility: the new
> > buffer management makes these obsolete. Code generation for decimal and
> > timestamp types has been added to the text scanner, increasing the
> > performance of some queries by up to 19%. More robust query plans in case
> > of data skew have made some aggregations eight times as fast. A number of
> > large changes are in-flight, including changes to equivalence class
> > computation in the planner, more decimal semantics adjustments, min-max
> > filters for Kudu, and multi-threaded metadata loading that increases the
> > performance of some metadata operations by 8x.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >  [ ] Initial setup
> >  [ ] Working towards first release
> >  [] Community building
> >  [X] Nearing graduation
> >  [ ] Other:
> >
> > Date of last release:
> >
> >  2017-09-14
> >
> > When were the last committers or PPMC members elected?
> >
> >  2017-09-29
> >
> > Signed-off-by:
> >
> >  [ ](impala) Tom White
> > Comments:
> >  [ ](impala) Todd Lipcon
> > Comments:
> >  [ ](impala) Carl Steinbach
> > Comments:
> >  [ ](impala) Brock Noland
> > Comments:
> >
> > On Sat, Oct 21, 2017 at 3:43 PM,  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, 15 November 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, November 01).
> > >
> > > 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/November2017
> > >
> > > 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 

Re: Podling Report Reminder - November 2017

2017-10-23 Thread Todd Lipcon
Looks good to me. Feel free to add my sign-off when you post to the wiki.

-Todd

On Sat, Oct 21, 2017 at 4:34 PM, Jim Apple  wrote:

> Please review:
>
> 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:
>
>   Our graduation proposal is in the works.
>
> 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 279 Commits:
>git log --format='%ci' | grep -cE '2017-(08|09|10)'
>
>  62 of those commits were by non-committers:
>git log --format='%an %ci' | grep -E '2017-(08|09|10)' | tr -d '0-9\-' |
> cut -d ' ' -f -2 | sort | uniq -c | sort -n
>
> Of the 37 patch authors, 16 were not committers at the beginning of this
> reporting period.
>
>  There are three new committers members and one new PPMC member:
>
> https://lists.apache.org/list.html?d...@impala.apache.org:
> dfr=2017-8-1|dto=2017-10-31:%22has%20invited%22
>
> Impala has done a fourth release with a third release manager.
>
> Impala has begun graduation procedures: we have held a community discussion
> and a community vote on graduation, both unanimous. We have established our
> intended PMC. Next, we will draft our charter and hold a discussion on
> general@incubator.
>
> How has the project developed since the last report?
>
> Impala has removed the old unpartitioned hash and aggregation nodes, relics
> from years ago that were kept around for backwards compatibility: the new
> buffer management makes these obsolete. Code generation for decimal and
> timestamp types has been added to the text scanner, increasing the
> performance of some queries by up to 19%. More robust query plans in case
> of data skew have made some aggregations eight times as fast. A number of
> large changes are in-flight, including changes to equivalence class
> computation in the planner, more decimal semantics adjustments, min-max
> filters for Kudu, and multi-threaded metadata loading that increases the
> performance of some metadata operations by 8x.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>  [ ] Initial setup
>  [ ] Working towards first release
>  [] Community building
>  [X] Nearing graduation
>  [ ] Other:
>
> Date of last release:
>
>  2017-09-14
>
> When were the last committers or PPMC members elected?
>
>  2017-09-29
>
> Signed-off-by:
>
>  [ ](impala) Tom White
> Comments:
>  [ ](impala) Todd Lipcon
> Comments:
>  [ ](impala) Carl Steinbach
> Comments:
>  [ ](impala) Brock Noland
> Comments:
>
> On Sat, Oct 21, 2017 at 3:43 PM,  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, 15 November 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, November 01).
> >
> > 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/November2017
> >
> > 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


Re: Time for graduation?

2017-10-23 Thread Todd Lipcon
Thanks for setting this up, Jim! Can confirm that the vote request came
through.

-Todd

On Mon, Oct 23, 2017 at 11:14 AM, Jim Apple  wrote:

> I have sent out the Chair election ballot via steve.apache.org to people
> who will be listed in our resolution as PMC members, via email addresses (@
> apache.org). Please vote. The vote closes Friday.
>
> On Fri, Oct 20, 2017 at 10:19 PM, Jim Apple  wrote:
>
> > I have a resolution with a blank space for chair, and the community voted
> > unanimously to graduate.
> >
> > I also have a set of people who will make up the PMC (should we
> graduate),
> > based on their responses to the email I sent.
> >
> > We have two volunteers for PMC chair. I'll call a vote with potential PMC
> > members as voters, starting on Monday using https://steve.apache.org/,
> > following examples from other ASF projects.
> >
> > On Thu, Oct 12, 2017 at 3:24 PM, Jim Apple  wrote:
> >
> >> I think it would be a good time to graduate. I'm very proud of the
> >> progress the community has made in terms of acting in an Apache way.
> >>
> >> Some logistics:
> >>
> >> I would be happy to serve as an initial chair.
> >>
> >> I'll draft a resolution, with a blank space for chair. This doesn't mean
> >> we have to agree now is the time to graduate, but we'll have it
> available
> >> for discussion and revision whenever we are ready.
> >>
> >> If we decide to graduate now, maybe we could email everyone who is on
> the
> >> PPMC, ccing private@, to see if they are still interested in being on
> >> the PMC, and taking no response to mean "yes" until we hear otherwise,
> in
> >> case someone is on vacation away from email, or in the hospital, or
> >> something.
> >>
> >> Also, mentors are traditionally included in a graduating podling's PMC,
> >> right?
> >>
> >> On Thu, Oct 12, 2017 at 2:17 PM, Todd Lipcon  wrote:
> >>
> >>> Hey Impala community,
> >>>
> >>> It's been a while that all of the Impala infrastructure has been moved
> >>> over, and the community appears to be functioning healthily, generating
> >>> new
> >>> releases on a regular cadence as well as adding new committers and PPMC
> >>> members. All of the branding stuff seems great, and the user mailing
> list
> >>> has a healthy amount of traffic and a good track record of answering
> >>> questions when they come up.
> >>>
> >>> As a mentor I think it's probably time to discuss graduation. The
> project
> >>> is already functioning in the same way as your typical Apache TLP and
> it
> >>> seems like it's time to become one.
> >>>
> >>> Any thoughts? If everyone is on board, the next step would be:
> >>>
> >>> 1. Pick the initial PMC chair for the TLP. According to the published
> >>> Impala Bylaws it seems that this is meant to rotate annually, so no
> need
> >>> to
> >>> stress too much about it.
> >>>
> >>> A couple obvious choices here would be Marcel (as the original founder
> of
> >>> the project) or perhaps Jim (who has done yeoman's work on a lot of the
> >>> incubation process, podling reports, etc). Others could certainly
> >>> volunteer
> >>> or be nominated as well.
> >>>
> >>> 2. Draft a Resolution for the PPMC and IPMC to vote upon.
> >>> -- the resolution would include the above-decided chair as well as the
> >>> list
> >>> of initial PMC, etc.
> >>> -- the Initial PMC could be just the current list of PPMC, or you could
> >>> consider adding others at this point as well.
> >>>
> >>>
> >>> I can help with the above process but figured I'd solicit opinions
> first
> >>> on
> >>> whether the communit feels it's ready to graduate.
> >>>
> >>> Thanks
> >>> Todd
> >>>
> >>
> >>
> >
>



-- 
Todd Lipcon
Software Engineer, Cloudera


Re: Time for graduation?

2017-10-23 Thread Jim Apple
I have sent out the Chair election ballot via steve.apache.org to people
who will be listed in our resolution as PMC members, via email addresses (@
apache.org). Please vote. The vote closes Friday.

On Fri, Oct 20, 2017 at 10:19 PM, Jim Apple  wrote:

> I have a resolution with a blank space for chair, and the community voted
> unanimously to graduate.
>
> I also have a set of people who will make up the PMC (should we graduate),
> based on their responses to the email I sent.
>
> We have two volunteers for PMC chair. I'll call a vote with potential PMC
> members as voters, starting on Monday using https://steve.apache.org/,
> following examples from other ASF projects.
>
> On Thu, Oct 12, 2017 at 3:24 PM, Jim Apple  wrote:
>
>> I think it would be a good time to graduate. I'm very proud of the
>> progress the community has made in terms of acting in an Apache way.
>>
>> Some logistics:
>>
>> I would be happy to serve as an initial chair.
>>
>> I'll draft a resolution, with a blank space for chair. This doesn't mean
>> we have to agree now is the time to graduate, but we'll have it available
>> for discussion and revision whenever we are ready.
>>
>> If we decide to graduate now, maybe we could email everyone who is on the
>> PPMC, ccing private@, to see if they are still interested in being on
>> the PMC, and taking no response to mean "yes" until we hear otherwise, in
>> case someone is on vacation away from email, or in the hospital, or
>> something.
>>
>> Also, mentors are traditionally included in a graduating podling's PMC,
>> right?
>>
>> On Thu, Oct 12, 2017 at 2:17 PM, Todd Lipcon  wrote:
>>
>>> Hey Impala community,
>>>
>>> It's been a while that all of the Impala infrastructure has been moved
>>> over, and the community appears to be functioning healthily, generating
>>> new
>>> releases on a regular cadence as well as adding new committers and PPMC
>>> members. All of the branding stuff seems great, and the user mailing list
>>> has a healthy amount of traffic and a good track record of answering
>>> questions when they come up.
>>>
>>> As a mentor I think it's probably time to discuss graduation. The project
>>> is already functioning in the same way as your typical Apache TLP and it
>>> seems like it's time to become one.
>>>
>>> Any thoughts? If everyone is on board, the next step would be:
>>>
>>> 1. Pick the initial PMC chair for the TLP. According to the published
>>> Impala Bylaws it seems that this is meant to rotate annually, so no need
>>> to
>>> stress too much about it.
>>>
>>> A couple obvious choices here would be Marcel (as the original founder of
>>> the project) or perhaps Jim (who has done yeoman's work on a lot of the
>>> incubation process, podling reports, etc). Others could certainly
>>> volunteer
>>> or be nominated as well.
>>>
>>> 2. Draft a Resolution for the PPMC and IPMC to vote upon.
>>> -- the resolution would include the above-decided chair as well as the
>>> list
>>> of initial PMC, etc.
>>> -- the Initial PMC could be just the current list of PPMC, or you could
>>> consider adding others at this point as well.
>>>
>>>
>>> I can help with the above process but figured I'd solicit opinions first
>>> on
>>> whether the communit feels it's ready to graduate.
>>>
>>> Thanks
>>> Todd
>>>
>>
>>
>