Re: Graduation resolution proposal

[Jim Apple]

That vote passed. Now the IPMC will recommend to the ASF board that Impala
be created as a TLP.

The board meets once a month, so they will likely be considering Impala TLP
status on either November 15 or December 20. I will let this list know when
I know more.

On Wed, Nov 8, 2017 at 8:56 PM, Jim Apple  wrote:

> We are now on step 3, in which the IPMC votes on the proposed graduation
> resolution:
>
> https://lists.apache.org/thread.html/4abfbf40b7d822cdc19421ea55de21
> f19ce70c4fd73c6f4c8cc98ce8@%3Cgeneral.incubator.apache.org%3E
>
> If it passes, the next step is a board resolution:
>
> http://incubator.apache.org/guides/graduation.html#
> submission_of_the_resolution_to_the_board
>
> On Tue, Oct 31, 2017 at 10:36 PM, Todd Lipcon  wrote:
>
>> Thanks Jim!
>>
>> -Todd
>>
>> On Tue, Oct 31, 2017 at 10:35 PM, Jim Apple  wrote:
>>
>> > I have sent this to general@ for discussion:
>> >
>> > https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc51
>> > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E
>> >
>> > On Sat, Oct 28, 2017 at 8:12 AM, Jim Apple 
>> wrote:
>> > > Below is a graduation resolution I would like to send to
>> > > general@incubator for discussion. It includes the PMC volunteers as
>> > > well as the result of the first PMC chair election, which was me.
>> > >
>> > > Unless there is objection, I'll send this to general@incubator for
>> > > discussion in a couple of days. If you want to participate in that
>> > > discussion at general@incubator, you can subscribe by emailing
>> > > general-subscr...@incubator.apache.org.
>> > >
>> > > As a reminder, the next steps I will take are:
>> > >
>> > > 1. Prepare a charter (i.e. this email)
>> > >
>> > > 2. Start a discussion on general@incubator.
>> > >
>> > > Should the discussion look mostly positive:
>> > >
>> > > 3. Call a vote on general@incubator.
>> > >
>> > > Should that vote succeed:
>> > >
>> > > 4. Submit the resolution to the ASF Board. See more here:
>> > > http://incubator.apache.org/guides/graduation.html
>> > >
>> > > 
>> > ---
>> > >
>> > > Establish the Apache Impala Project
>> > >
>> > > WHEREAS, the Board of Directors deems it to be in the best interests
>> of
>> > > the Foundation and consistent with the Foundation's purpose to
>> establish
>> > > a Project Management Committee charged with the creation and
>> maintenance
>> > > of open-source software, for distribution at no charge to the public,
>> > > related to a high-performance distributed SQL engine.
>> > >
>> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> > > (PMC), to be known as the "Apache Impala Project", be and hereby is
>> > > established pursuant to Bylaws of the Foundation; and be it further
>> > >
>> > > RESOLVED, that the Apache Impala Project be and hereby is responsible
>> > > for the creation and maintenance of software related to a
>> > > high-performance distributed SQL engine; and be it further
>> > >
>> > > RESOLVED, that the office of "Vice President, Apache Impala" be and
>> > > hereby is created, the person holding such office to serve at the
>> > > direction of the Board of Directors as the chair of the Apache Impala
>> > > Project, and to have primary responsibility for management of the
>> > > projects within the scope of responsibility of the Apache Impala
>> > > Project; and be it further
>> > >
>> > > RESOLVED, that the persons listed immediately below be and hereby are
>> > > appointed to serve as the initial members of the Apache Impala
>> Project:
>> > >
>> > >  * Alex Behm 
>> > >  * Bharath Vissapragada  
>> > >  * Brock Noland  
>> > >  * Carl Steinbach
>> > >  * Casey Ching   
>> > >  * Daniel Hecht  
>> > >  * Dimitris Tsirogiannis 
>> > >  * Henry Robinson
>> > >  * Ishaan Joshi  
>> > >  * Jim Apple 
>> > >  * John Russell  
>> > >  * Juan Yu   
>> > >  * Lars Volker   
>> > >  * Lenni Kuff
>> > >  * Marcel Kornacker  
>> > >  * Martin Grund  
>> > >  * Matthew Jacobs
>> > >  * Michael Brown 
>> > >  * Michael Ho
>> > >  * Sailesh Mukil 
>> > >  * Skye Wanderman-Milne  
>> > >  * Taras Bobrovytsky 
>> > >  * Tim Armstrong 
>> > >  * Todd Lipcon   
>> > >
>> > > NOW, THEREFORE, BE IT FURTHER 

Experienced Impala Contributors: writing "New Impala Contributors" walk-throughs

[Jim Apple]

If you are an experienced Impala contributor, and you'd like to help with
community outreach, you can post a walkthrough of a ticket that a newbie
will be able to address in only an hour of your time.

Get started by looking through open tickets labelled "newbie"
https://issues.apache.org/jira/issues/?filter=12341668

Look for a ticket with a few characteristics:

1. It looks like a new contributor could honestly handle this ticket!
Sometimes the "newbie" label is applied overzealously.
2. It looks like a ticket you could write a quick-and-ugly patch for very
quickly. Nobody will have to ever see it but you!
3. It's not essential to the next release - we wouldn't want an experienced
contributor taking on an issue out of urgency and snatching it away from a
new contributor.
4. It's not so out-of-date that it no longer describes the system as it
currently exists.
5. It hasn't been commented on with a walkthrough already.

If you can't find a ticket like this that is labelled "newbie", look for
newer open tickets with priority "Major" or below. The last community
effort to go through open tickets and label some "newbie" may have been
months before you are looking, so there may be good tickets for new
contributors that just haven't been labelled "newbie" yet.

Once you find a ticket you like, get a document ready to take notes in, and
start hacking up a patch, just for yourself, to make sure you know what
direction to point newbies in. Your notes document does not need to include
any of the code you write, only hints and signposts. You don't need your
code or prose to be perfect. Writing a quick-and-dirty patch and doing your
writeup of how you did it should take an hour or less. It's OK to remind
new contributors that they can choose to only partially fix an issue, as
long as the state of the code is still coherent and lends itself to being
fixed more, later.

Once you're done, prepend to your writeup a note about how to get started.
I use the following text, but feel free to improvise:

"If you'd like to contribute a patch to Impala, but aren't sure what you
want to work on, you can look at Impala's newbie issues:
https://issues.apache.org/jira/issues/?filter=12341668. You can find
detailed instructions on submitting patches at
https://cwiki.apache.org/confluence/display/IMPALA/Contributing+to+Impala.
This is a walkthrough of a ticket a new contributor could take on, with
hopefully enough detail to get you going but not so much to take away the
fun."

Append to your writeup a note of encouragement, like "Have fun, and you can
ask d...@impala.apache.org for help if you need a hint!"

Now post your writeup to d...@impala.apache.org. You can email me when
you're done and I will post it two more places:

1. I'll wait a few minutes to see your writeup on
https://lists.apache.org/list.html?d...@impala.apache.org. I'll click the
message title, then click "Permalink", then copy the URL and post that to
the ticket.
2. I'll post to https://helpwanted.apache.org. Here's an example of what it
will look like:
https://helpwanted.apache.org/task.html?b1b131fffb24afb17f52f7aae67beb73034832a7

If you're feeling energetic, feel free to do this cross-posting yourself.

Have fun, and don't hesitate to email me with any questions!