Re: [DISCUSS] Becoming a Committer

I’m a good case study here. I have contributed a lot to the HBase project but almost none of it code. But I’ve helped move the project forward and I think I’ve added value. I wouldn’t have been considered for the PMC without the commit bit even though almost nothing I’m doing in the PMC capacity r

Re: [DISCUSS] Becoming a Committer

Hey Csaba, I think you might be falling into a common-trap :). A committer's "status" is often acquired via repeated contributions of code to a project -- you're absolutely right. This stems from the fact that, most times, people contribute to a project via code. Committership (for HBase) is

Re: [DISCUSS] Becoming a Committer

Wow, this list just made me think. Is the Committer status clearly a reward for contributing in any way? Or is it a very pragmatic decision by the PMC that some fellow needs right to commit? I think it's kind of both but the ratio should be clear and consensual. People who answer questions, fil

Re: [DISCUSS] Becoming a Committer

Hi all, There was a lot of engagement on this discussion on the mailing list, but less so on the JIRA. Can interested folks make some time to take a look? I'd like to make sure that we have a lot of buy in before adding this content to the official docs, since it impacts the entire community. Th

Re: [DISCUSS] Becoming a Committer

Yep, filed https://issues.apache.org/jira/browse/HBASE-18974 to track adding to the docs. On Sun, Oct 1, 2017 at 7:20 AM, Chia-Ping Tsai wrote: > The is a great discussion. And i love misty's list. > Don't let this die. What about putting the summary in our docs? > > -- > Chia-Ping > > On 2017-0

Re: [DISCUSS] Becoming a Committer

The is a great discussion. And i love misty's list. Don't let this die. What about putting the summary in our docs? -- Chia-Ping On 2017-09-30 02:34, Andrew Purtell wrote: > This conversation is in a good place. I apologize for the tone of my > earlier allergic reaction but not the content. I h

Re: [DISCUSS] Becoming a Committer

This conversation is in a good place. I apologize for the tone of my earlier allergic reaction but not the content. I hope that is acceptable. On Fri, Sep 29, 2017 at 11:01 AM, Mike Drob wrote: > To bounce off of what Yu Li said earlier - I see Hadoop has adopted very > similar language to the

Re: [DISCUSS] Becoming a Committer

To bounce off of what Yu Li said earlier - I see Hadoop has adopted very similar language to the Spark list: http://hadoop.apache.org/committer_criteria.html I especially like the examples at the bottom. They are four diverse paths, and there is no expectation that this is an exclusive list. If we

Re: [DISCUSS] Becoming a Committer

Good discussion. Thanks Mike for kicking it off. The Misty list is great. I find myself giving double kudos for non-code or feature contribs; e.g. stuff like test-fixing, patches that fix bugs found in production or patches from operators that ease their day-to-day burden, voting on releases, doc

Re: [DISCUSS] Becoming a Committer

bq. As a relatively new member in the HBase community and a non-committer, once the new member decides that he/ she wants to become a Committer, it will be helpful to have a list of PMC members that he/ she can communicate with and get feedback from time to time. Feedback may include potential adju

Re: [DISCUSS] Becoming a Committer

Hi, Thank you all for a good discussion here. Issues with both having and NOT having documented specific criteria are well articulated here. As a relatively new member in the HBase community and a non-committer, once the new member decides that he/ she wants to become a Committer, it will be helpf

Re: [DISCUSS] Becoming a Committer

I feel like I inject this note into all discussions like this, but I'm going to do it again. "Act like a committer" does not ONLY mean to produce code for HBase. It means to support the project. This may mean any of the following, plus a long list of other things I'm sure I'm not thinking of right

Re: [DISCUSS] Becoming a Committer

On 9/20/17 10:54 PM, Mike Drob wrote: The original impetus for me to ask the community about this came when a junior coworker asked me nearly the same question: "Hey, you're a committer, I'm interested in becoming a committer too, what should I do?" Telling him to act like a committer was helpful

Re: [DISCUSS] Becoming a Committer

Allow me to quote the relative instructions in Spark (from https://spark.apache.org/committers.html): === Becoming a Committer To get started contributing to Spark, learn how to contribute – anyone can submit patches, documentation a

Re: [DISCUSS] Becoming a Committer

Hi Andrew, Thanks for taking the time to respond. I certainly did not mean offense by starting this discussion - it largely stems from my own ignorance, which I hope is forgivable. Nor do I have any negative experiences to point to, and agree with you that I do not believe there is a "problem to c

Re: [DISCUSS] Becoming a Committer

>> If you are such a paid professional, sure, it's no problem >> for you, but you're already getting paid to be here. You can specify separate levels for paid and non-paid professionals For example, for paid professional, at least one meetup/conference presentation is a must, one major feature is

Re: [DISCUSS] Becoming a Committer

Again, the presumption of bad intent. It's poisonous, IMHO. I think this viewpoint needs to be justified. What actions have the HBase PMC taken, or not taken, that cause you to suspect this? Experiences in other communities where there has been bad faith are regrettable but not germane, unless the

Re: [DISCUSS] Becoming a Committer

> ​ This translates immediately to number of hours (days, weeks, months and even years) spent on HBase development This is a terrible criteria because it means only paid professionals are likely to clear the bar. It's exactly these kinds of perverse outcomes I am worried about going about this ex

Re: [DISCUSS] Becoming a Committer

The most important criterion that make sense is the level of involvement in HBase development: 1. Number of JIRAs resolved 2. Number of major features implemented 3. Number of new LOC added to code base This translates immediately to number of hours (days, weeks, months and even years) spent on H

Re: [DISCUSS] Becoming a Committer

Any subjective criteria, such as "acting like a committer" open wide room for а power abuse of PMC members. My 2c -Vlad On Wed, Sep 20, 2017 at 3:05 PM, Andrew Purtell wrote: > By the way I think "act like a committer and you'll become a committer" is > pretty good advice for anyone looking to

Re: [DISCUSS] Becoming a Committer

By the way I think "act like a committer and you'll become a committer" is pretty good advice for anyone looking to enter into participation in an open source community, and a reasonable yardstick to judge candidates who have been nominated. I also have no objection to documenting a list of favorab

Re: [DISCUSS] Becoming a Committer

> will lead to folks motivated wrongly, similar to oft maligned "resume driven development?" I find the need to have this discussion mildly offensive. Have we been unfair in offering committership? Do you have a specific example of something that looked improper? Can you name a committer whom you

[DISCUSS] Becoming a Committer

Hi folks, I've been chatting with folks off and on about this for a while, and was told that this made sense as a discussion on the dev@ list. How does the PMC select folks for committership? The most common answer is that folks should 'act like a committer' but that's painfully nebulous and eas