2007/9/20, Marty Alchin <[EMAIL PROTECTED]>: > > One thing we have to keep in mind here is that people regularly use > the SVN version of Django, so it needs to be working as well as > possible, all the time. This is unlike many other projects, where the > repository (be it SVN or CVS) is always considered a work-in-progress, > where users are urged to proceed at their own risk, dodging serious > bugs and incomplete features along the way. > > Sure, it doesn't always work out perfectly. As you mentioned, there > are times where trunk is broken and a committer is necessary in order > to fix it. However, more committers isn't a solution to that > particular problem. We'd probably just end up with a lot of extra > committers, all scrambling to put together a quick fix to the problem, > with little regard to fixing it right. Given that fixes need to fix > the root problem, while also not breaking anything else, it's > something that does need a bit of care, caution and communication. > Fewer committers actually helps here, since the core devs can be more > certain of their commitment to communication. This is solved with 1) responsibilities management, 2) responsibilities, roles and clearly described areas of work and interest and 3) channel for urgent communications.
> For what it's worth, "everyone can do what they want, and we will > commit/change only that > we want" doesn't sound like anarchy to me, it sounds a bit like a > benevolent oligarchy. And, while oligarchies have proven to have > faults in the Real World, I've found them (and even dictatorships) to > be far more effective in online collaboration than democracies. I've > been invovled in many projects, some on each side of the coin, and far > more got done when there was a small group (or single person) who > could make a final judgement. As long as those people do in fact > listen to the rest of us, and they take us into account, it typically > turns out for the best. Yes, I remember "I think we don't need it [favicon]" by Jacob :) Final judgement is great. Long judging and deciding process on each simple question is bad. I love fast feedbacks. If you are not responding for a long time, you appears to be dead and becoming rotten :) Django project is evolving great, but just too slow for me. And process is very ineffective. Read in thread written month ago, that only 1/4 to 1/5 patches are committed unchanged. 20% efficiency, right? Average ticket commit time is >2 month. Is there any way to improve these numbers? Is there collector for important quantity indicators anywhere? Is there process of improving process going on? That's signs of bad management, that is typical to open-sources projects. I read about one undoubtedly good process enhancement month ago - divide bugs and features. Why it's still not implemented??? Great, discussed, agreed, but nobody did nothing to implement it! Bad management, again :( And there is sorting by ticket priority in trac not working for ages. So, are all django tickets equal? Should we use combinatorics or quantum mechanics rules to count probability that django triager/committer will look this ticket at this time? How django could afford production line in addition to bee hive? Of course, to live without release dates is good. But look, django lives without priorities either! > P.S. I apologize for contributing to what is undoubtedly going to turn > into a flame war. At least, Jacob answered on the main question, so go on with flame and offtopics :) P.S. I'm intentionally not talking about good things in Django. I know them. I love django. I'm intentionally discussing bad things and how we can improve them. I will try to turn flame war into constructive process in this thread. -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
