On Mon, Aug 16, 2010 at 12:23 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> My apologies -- I haven't watched the video for a while, so I forgot
> that detail. I'm not sure adopting that policy would help Django,
> though; we have enough of a bottleneck with committers without
> exa
On Mon, Aug 16, 2010 at 10:50 AM, Tobias McNulty wrote:
> On Sun, Aug 15, 2010 at 10:31 PM, Russell Keith-Magee
> wrote:
>>
>> On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli
>> wrote:
>> > - punish dev's who don't fix their bugs quickly after api lock
>> >
>> > (The presentation lacks speci
On Mon, Aug 16, 2010 at 11:08 AM, Mark Bucciarelli wrote:
> On Mon, Aug 16, 2010 at 10:31:11AM +0800, Russell Keith-Magee wrote:
>> On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli wrote:
>>
>> > ?- random api lock (people tend towards complacency)
>>
>> I'm not entirely certain I understand th
On Mon, Aug 16, 2010 at 10:31:11AM +0800, Russell Keith-Magee wrote:
> On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli wrote:
>
> > ?- random api lock (people tend towards complacency)
>
> I'm not entirely certain I understand this point -- or, at least,
> how it would apply to Django.
>
So
On Sun, Aug 15, 2010 at 10:31 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli
> wrote:
> > - punish dev's who don't fix their bugs quickly after api lock
> >
> > (The presentation lacks specifics on the last point. ;)
>
> Which is a
On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli wrote:
> On Sat, Aug 14, 2010 at 03:03:27PM +0800, Russell Keith-Magee wrote:
>>
>> If you have suggestions on how we can improve Django's development
>> process and address these issues, we're happy to hear them.
>>
>
> You may find this interest
