which, for instance, blocks the release months. Sometimes it requires to
>> rewrite whole PRs with courtesy
>> (rather than, for instance, reverting). This is already happening and it
>> brings some overhead to the dev.
>> Yes, maybe the volume matters to handle those issues.
>>
&
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 di
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, b
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
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
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, but
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 contribu
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
