I'd like to make a wiki page on what the criteria are for becoming an official Impala committer. Before doing so, I thought we could talk about what should go in that page.
I went to a talk by some experienced ASF people on other projects (Spark, Hadoop, etc.) who said: 1. Every committer should be "an easy person to work with". 2. One mitigating factor to the risk of adding a new committer is that committers rarely go overboard and start committing code that is beyond their expertise. 3. Some projects want committers to be an expert in one area of the code. 4. Other people have the view that someone should be voted into a committer once it saves time to make them a committer. Making someone a committer can save time in a few ways: for instance, they can take on more responsibility, taking some work off the shoulders of the other committers. 5. Many projects will make someone a committer, or even a PMC member, if they are not committing new features but instead are contributing by filing bugs, triaging bugs, reviewing code, writing documentation, and so on. My plan for this [DISCUSS] thread is that we can chat for a while if anyone disagrees with any of these or wants to add something else. Once the thread quiets down, I'll write the wiki page and send the link to ts thread. After that, anyone with a wiki account will be able edit the page. Thoughts?
