[Python-ideas] Iterative development

[anatoly techtonik]

On Wed, Jan 29, 2014 at 11:29 AM, Ethan Furman <ethan at stoneleaf.us> wrote:
> On 01/28/2014 11:44 PM, anatoly techtonik wrote:
>>
>> It is a parallel Python development process. It doesn't affect or
>> replace current practice, so nobody gets hurt.
>
> So you're saying that we would have the current model, plus this agile
> model?

I am saying that you're not forced to follow agile model if you don't like it.
You can do what you do as you did before.

>>  It is also about open
>> process, where openness means transparency (eliminate hidden
>> communication),
>
> What "hidden" communication?  Talking in person or on IRC?  Instead of ...
> where?

If information doesn't reach the recipient who want to read it, it is "hidden".
Even if you talk in public channel on IRC, the information is hidden from me
if I was not connected and channel doesn't have public logs.

>> inclusiveness (eliminate exclusive rights and privileges)
> Exclusive rights?  You mean let any piece of code get committed?

There are many exclusive rights that keep people off from contributing.
I don't want to touch them here, because it will move the thread into different
area. To make it more specific "inclusiveness" on the process is the process
too. You start with people who have full exclusive rights and contributing then
compare them to people who are willing to help, but don't do this. Then you
remove the obstacles to include these people.

>>  and accessibility (eliminate awkward practices and poor
>> user experience).
>
> It is not possible to please everyone; it is also not possible to ensure a
> "good user experience" for everyone.

That's a general claim. I am sure that it is possible to reach the point where
everyone agree that their experience is "good enough user experience".

And there is a dedicated time in the process (retrospective) to work on just
on that.

>> The idea is to split development of Python into two weeks cycle.
>
>
> 80 hours?  Do you have any idea how long it takes some of us to put in 80
> hours of Python development time?

It is not development time. These two weeks cycle is just ordinary time, which
may include 15 minutes of development time, a week or nothing. It is up to
you - how much are you willing to spend.