On Mon, Nov 5, 2018 at 12:44 PM Dave Fisher wrote:
>
>
>
> > On Nov 5, 2018, at 8:35 AM, Christopher wrote:
> >
> > On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz
> > wrote:
> >>
> >> Hi,
> >>
> >> On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote:
> >>> ...it would be a mistake if ASF were
> On Nov 5, 2018, at 8:35 AM, Christopher wrote:
>
> On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz
> wrote:
>>
>> Hi,
>>
>> On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote:
>>> ...it would be a mistake if ASF were to try to impose a more spammy
>>> workflow to dev@ onto every PMC, as
On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz
wrote:
>
> Hi,
>
> On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote:
> >...it would be a mistake if ASF were to try to impose a more spammy
> > workflow to dev@ onto every PMC, as a requirement...
>
> FWIW I didn't suggest imposing anything like
Hi,
On Sat, Nov 3, 2018 at 8:37 PM Joan Touzet wrote:
> ...In a way, it feels a bit like having had bypass surgery, I
> guess :)
Indeed, thank you very much for sharing this!
I think the conclusion at this point is that large code drops are not
*necessarily* damaging to a community but handling
Hi,
On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote:
>...it would be a mistake if ASF were to try to impose a more spammy
> workflow to dev@ onto every PMC, as a requirement...
FWIW I didn't suggest imposing anything like that - my only concern is
that it should be possible to follow the action
