Michael Radziej wrote: > I like Django, perhaps I rather contribute > more tiny stuff of which I feel that it will get integrated, and I have > my own patchset for Django. So what? It works fine for me. Why should I > turn to a different framework when I like the concept and code (and the > docs!), only because the tickets queue up?
It's not bad for you (I'm also in this position having Django a bit patched for my projects). It's bad for Django because it leads to contributors refusing to submit their patches to Django and just live with their own local patches. Submitting a proper patch is a bit harder then just leaving it for your own use because you don't have to describe it to anyone else. > And I really, really, really wouldn't think Django core developers were > arrogant or even unfriendly. In fact there is nothing about arrogance or unfriendlieness of people whom we all know by their work here. This is one particular aspect of Django that some of us think can be improved. And it is such aspect that can be improved only by project leaders, that's all. > Sometimes your decisions will unavoidably turn out to be wrong, > but it's all the way better than a wild patchwork of different > attitudes, styles and architectures in the code. With this I agree wholeheartedly :-). Strong leadership is what makes Django the best framework. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
