[Python-ideas] Iterative development

[Nick Coghlan]

On 29 January 2014 23:57, Chris Angelico <rosuav at gmail.com> wrote:
> On Wed, Jan 29, 2014 at 11:29 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>> 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.
>
> Then if you care, connect. It's not hidden if you have the power to access it.
>
> Here's a suggestion: Fork Python (that's legal, that's what open
> source means) and start development using the model you advocate. If
> it's massively better than what's happening, (a) developers will flock
> to your model, and (b) the project could be completely handed over to
> you, as happened with GCC.
>
> Or alternatively, explain to us here what the real advantages are of
> your new model. So far, what I've seen is "hey, here's an idea", and
> not "here's what this idea will do to benefit Python"; and the idea
> itself looks more suited to a big business than to open source. Maybe
> someone who's actually used Agile will know what's so wonderful about
> it, but unless every core dev *has*, a bit of explanation will help.

Plenty of us have used it, and we know it's an entirely inappropriate
model for open source development projects with broad asynchronous
participation, as the time commitment needed to make the short cycle
work is antithetical to loose collaboration. It works well for a
focused team supporting a single application to meet the specific
needs of a single business, though.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia