> I'd just like to point out a counter-example to those arguing that the > core developers don't listen to criticism. There was a post recently > to django-users called "Why I'm giving up on Django" :
Agreed. I would like to point out that I am not saying the core doesn't listen. I'm not trying to make all or nothing criticisms here. I think there are far more ways that Django is doing things right than wrong, or I wouldn't be taking the time to make any of these posts, I'd go elsewhere! > I have to say that I think you're confusing arrogance with a desire to > do things *RIGHT*, and a lack of time on the part of the core devs. This however is part of the issue. With rapid growth comes that lack of time for the founders. And one of the possible solutions to precisely that, is to spend *more* time on that which encourages the recruitment of more developers. Again, long term goals vs short term needs. When a company/project grows, inevitably the founders run out of time to do work in the same way they can at the beginning. And they have three choices: a) spend time managing and learning to be managers, and thus do less do less coding/inventing/whatever it was b) get other people to do the above, and lose some control of the process ( hopefully they do a good job of picking them ) c) ignore the need, and stall their project by not doing the above, possible sinking it completely if the scenario is bad enough ( I do not think that is the likely scenario with Django, but I have seen it happen in other businesses ) Nobody *likes* doing a) or b), but at some point they become necessary. You absolutely can't have a growing project succeed to its potential without at some point having to make that shift. The fact that the problem here has been quoted as "lack of time on the part of the core devs" precisely illustrates my point. Growth has produced so much else that needs to be done ( PR, docs, seminars, management, more code to keep up on, etc ) that the core as it is now can not adequately keep up with patch submissions. Which is necessary so as not to alienate new patch submitters. If you want to grow, that has to change somehow because obviously more dev time is needed, and new core developers are going to come out of the pool of new patch submitters. Django *has* deliberately gunned for rapid growth, there has been major PR blitz and now it's gone boom. The requisite less than fun re-org that goes with rapid growth has to happen too. I hope that others at least see discussion of the process of dev as also being important to have on a dev list, as that process can not be static. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
