Hey William,
Thanks for pointing this inconsistency out out.
Best Regards,
Myrle
On Fri, Aug 9, 2019 at 12:22 AM William Shen
wrote:
> Not sure where this thread is heading toward, but I find the role
> definition listed on
> http://www.apache.org/foundation/how-it-works.html#roles clarifying
Not sure where this thread is heading toward, but I find the role
definition listed on
http://www.apache.org/foundation/how-it-works.html#roles clarifying and
well defined, though they seem to vary slightly from what is on
https://community.apache.org/contributors/. Not sure which one is more
> Currently, I have heard some ideas or attitudes that I consider to be
overly motivated by fear of unlikely occurrences.
> And I've heard some statements disregard widely accepted principles of
inclusiveness at the Apache Software Foundation.
> But I suspect that there's more to the attitude of
On Tue, Aug 6, 2019 at 7:57 PM Sean Owen wrote:
> On Tue, Aug 6, 2019 at 11:45 AM Myrle Krantz wrote:
> > 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
On Tue, Aug 6, 2019 at 11:45 AM Myrle Krantz wrote:
> 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
On Tue, Aug 6, 2019 at 6:11 PM Sean Owen wrote:
> On Tue, Aug 6, 2019 at 10:46 AM Myrle Krantz 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
On Tue, Aug 6, 2019 at 10:46 AM Myrle Krantz 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
> 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 님이
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
So I’d like to add non-coding committers, I think there is great value in
both recognizing them and eventually having a broader PMC (eg maybe someone
who’s put a lot of time into teaching Spark has important things to say
about a proposed release, perhaps important enough for a binding vote).
On Tue, Aug 6, 2019 at 5:36 PM Sean Owen 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
On Tue, Aug 6, 2019 at 1:14 AM Myrle Krantz wrote:
> If someone makes a commit who you are not expecting to make a commit, or in
> an area you weren't expecting changes in, you'll notice that, right?
Not counterarguments, but just more color on the hesitation:
- Probably, but it's less obvious
My 2 cents as just one of contributors of Apache Spark project.
The thing is, what's the merit for both contributors and PMC members on
granting committership on non-code contributors. I'd rather say someone is
a good candidate to be invited as a committer to co-maintain a part of code
repository
I usually make such judgement about commit bit based upon community
activity in coding and reviewing.
If somebody has no activity about those commit bits, I would have no way to
know about this guy,
Simply I can't make a judgement about coding activity based upon non-coding
activity.
Those bugs
Hey Hyukjin,
Apologies for sending this to you twice. : o)
On Tue, Aug 6, 2019 at 9:55 AM Hyukjin Kwon wrote:
> Myrle,
>
> > We need to balance two sets of risks here. But in the case of access to
> our software artifacts, the risk is very small, and already has *multiple*
> mitigating
So, here's my thought:
1. Back to the original point, for recognition of such people, I think we
can simply list up such people in Spark Website somewhere. For instance,
Person A: Spark Book
Person B: Meetup leader
I don't know if ASF allows this. Someone needs to check it.
2. If we need
Myrle,
> We need to balance two sets of risks here. But in the case of access to
our software artifacts, the risk is very small, and already has *multiple*
mitigating factors, from the fact that all changes are tracked to an
individual, to the fact that there are notifications sent when changes
Hey Sean,
Even though we are discussing our differences, on the whole I don't think
we're that far apart in our positions. Still the differences are where the
conversation is actually interesting, so here goes:
On Mon, Aug 5, 2019 at 3:55 PM Sean Owen wrote:
> On Mon, Aug 5, 2019 at 3:50 AM
On Mon, Aug 5, 2019 at 9:55 AM Sean Owen wrote:
> On Mon, Aug 5, 2019 at 3:50 AM Myrle Krantz wrote:
> > So... events coordinators? I'd still make them committers. I guess I'm
> still struggling to understand what problem making people VIP's without
> giving them committership is trying to
On Mon, Aug 5, 2019 at 3:50 AM Myrle Krantz wrote:
> So... events coordinators? I'd still make them committers. I guess I'm
> still struggling to understand what problem making people VIP's without
> giving them committership is trying to solve.
We may just agree to disagree, which is fine,
On Sun, Aug 4, 2019 at 10:06 PM Sean Owen wrote:
> Oops, I also failed to copy dev@
>
> On Sun, Aug 4, 2019 at 3:06 PM Sean Owen wrote:
> >
> > On Sun, Aug 4, 2019 at 1:54 PM Myrle Krantz wrote:
> > >> No, I think the position here was docs-only contributors _could_ be
> > >> committers. The
On Sun, Aug 4, 2019 at 11:21 AM Myrle Krantz wrote:
> Let me make a guess at what you are trying to accomplish with it. Correct me
> please if I'm wrong:
> * You want to encourage contributions that aren't just code contributions.
> You recognize for example that good documentation is
Hey Sean,
On 2019/08/02 13:20:56, Sean Owen wrote:
> Yes, there's an interesting idea that came up on members@: should
> there be a status in Spark that doesn't include the commit bit or
> additional 'rights', but is formally recognized by the PMC? An MVP,
> VIP, Knight of the Apache Foo
Yes, there's an interesting idea that came up on members@: should
there be a status in Spark that doesn't include the commit bit or
additional 'rights', but is formally recognized by the PMC? An MVP,
VIP, Knight of the Apache Foo project. I don't think any other project
does this, but don't think
(Let's move this thread to dev@ now as it is a general and important
community question. This was requested on members@)
On Thu, Aug 1, 2019 at 10:20 PM Matei Zaharia wrote:
>
> Our text on becoming a committer already says that we want committers who
> focus on our docs:
25 matches
Mail list logo
