> well, then I do. I´m scared away. why? exactly because of what james > is writing here. > it seems that noone except the "core developers" are allowed to > criticize django - whenever something like this comes up on the list, > there´s someone who fights the arguments tooth and nail. there´s no > discussion culture on this list ... as iain already pointed out, it´s > too much about "being right" IMHO.
Sigh. If that were true: * Django wouldn't be open source. * Django wouldn't have a public bug tracker. * Django wouldn't have two public discussion lists. * Django wouldn't have a public IRC channel. * None of the "core developers" would allow comments on their blogs. People criticize Django all the time, and the criticism often leads to real improvements. If that weren't true, we wouldn't have an i18n system, we wouldn't have had the magic-removal branch, we wouldn't have lots of things that are in Django right now. What I've said here, repeatedly, is that if there's this problem, I want to see examples of it, because I haven't so far, and if I'm going to understand that there is a problem and understand where it comes from, I *need* to see examples. There's a big, big difference between that and "no-one is allowed to criticize Django". But apparently I'm just digging myself a big deep hole the more I say, so I'll stop talking now and let others work this out. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
