> I wonder which project nominees non-coding only committers but I at least know multiple projects. They all have that serious problem then.
I mean It know multiple projects don't do that and according to what you said, they all have that serious problem. 2019년 8월 7일 (수) 오전 1:05, Hyukjin Kwon <gurwls...@gmail.com>님이 작성: > Well, actually I am rather less conservative on adding committers. There > are multiple people who are active in both non-coding and coding activities. > I as an example am one of Korean meetup admin and my main focus was to > management JIRA. In addition, review the PRs that are not being reviewed. > As I said earlier at the very first time, I think committers should > ideally be used to the dev at some degrees as primary. Other contributions > should be counted. > > I wonder which project nominees non-coding only committers but I at least > know multiple projects. They all have that serious problem then. > > 2019년 8월 7일 (수) 오전 12:46, Myrle Krantz <my...@apache.org>님이 작성: > >> >> >> On Tue, Aug 6, 2019 at 5:36 PM Sean Owen <sro...@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. >> >> How do the other PMC members and community members see this? >> >> Best Regards, >> Myrle >> >
