I think that there is frustration on the part of the core dev team because people are (intentionally or not) demanding more and more of their time in the form of feature requests without understanding what the costs are and what resources exist.
There is frustration on the part of some Django users who would like to contribute but feel that anyone not in the core dev team is a third-class citizen with a tiny voice, and think that spending any time working on a ticket is slightly less likely to be worthwhile than writing an iPhone app and hoping Apple approves it for the App Store. In my opinion, the problem lies not at either end, but in the middle. The way Trac is currently being used allows anyone at all to give tickets a status that the individual may not actually have the understanding to judge. To compensate for this, the core developers are each forced to rely on one another and their own small circle of lieutenants (as Linus does) to know whose code to actually take the time to evaluate. Ideally, people who want to contribute to Django should be able to adopt any open ticket in the bug tracker, work on it (with any necessary communication with this list), and see their work accepted if it's done well. At present this is not the case. A potential solution is to treat bug tracker permissions a bit more like the "commit bit," where accepting bugs would be limited to people who understand both the process and the direction/vision of Django. This would cost time, but could alleviate the frustration on both sides and ultimately result in more work getting done, not least because more people would be encouraged to participate. These are just my thoughts based mostly on the demoralizing thread Jacob is addressing with this one. I have also found it demoralizing, because it makes me feel like it's not worth aspiring to contribute to Django because there are too many obstacles. Some of Russell's comments do counter that sentiment, but it still seems like there is no way to have any confidence about what to work on without having the insight of a core developer. Again, this is all my opinion and I could be way off. Shawn -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
