On Tue, Aug 6, 2019 at 6:11 PM Sean Owen <sro...@apache.org> wrote: > On Tue, Aug 6, 2019 at 10:46 AM Myrle Krantz <my...@apache.org> wrote: > >> You can tell there's a range of opinions here. I'm probably less > >> 'conservative' about adding committers than most on the PMC, right or > >> wrong, but more conservative than some at the ASF. I think there's > >> room to inch towards the middle ground here and this is good > >> discussion informing the thinking. > > > > > > That's not actually my current reading of the Spark community. My > current reading based on the responses of Hyukjin, and Jungtaek, is that > your community wouldn't take a non-coding committer no matter how clear > their contributions are to the community, and that by extension such a > person could never become a PMC member. > > > > If my reading is correct (and the sample size *is* still quite small, > and only includes one PMC member), I see that as a serious problem. > > Again if "non-code" means "no interaction with the project repo", no I > do not hear support for making said person a committer for all the > reasons you've heard here. I don't support it. > > Wait, didn't we just get done agreeing that's a reasonable position if > not one you hold? I'm quite confused. > It's fine to invite the board, members to come participate here as you > have just done separately, but you're now portraying this as a serious > offense, despite your comments here? >
I think both representations of my position are inaccurate. I had understood your position to be that you would be willing to make at least some non-coding contributors to committers but that your "line" is somewhat different than my own. My response to you assumed that position on your part. I do not think it's good for a project to accept absolutely no non-code committers. If nothing else, it violates my sense of fairness, both towards those contributors, and also towards the ASF which relies on a pipeline of non-code contributors who come to us through the projects. For more documentation on the definition of a committer at Apache, read here: https://community.apache.org/contributors/ "Being a committer does not necessarily mean you commit code, it means you are committed to the project and are productively contributing to its success." I also don't yet see a "serious offense" here. My e-mail to board@ is simply a heads up, which I do owe the rest of the board when I'm interacting with one of our projects. Here are my exact words: "Most of that discussion is fairly harmless. Some of it, I have found concerning." Right now, I'm still trying to approach Spark's position with a learning-and-teaching mindset. Does that make it clearer? Best Regards, Myrle
