James Bennett wrote: > I would like to see examples of this; I have a pretty comprehensive > set of ego searches and tag subscriptions for Django-related postings, > and I don't get the "Django is closed, don't bother trying to get > involved" vibe as much as you apparently do.
Smart people don't usually write things like this at all, if they feel that their contribution is not valued they just go away. James, you're undoubtedly closely familiar with Django's Trac so you know how many patches live there for long time without any attention. You can safely consider everyone who made them offended (to some extent). You might not get this feeling from blog posts because Django is still a young project _and_ has really good community that is patient and is hard to piss off. The problem of long waiting patches is not unique to Django, it's a common thing in Open Source. It's inevitable in any project where there are less reviewers than contributors because people's time is limited. Everybody understands it but the huge difference here is that people should simply feel in control, they should know what happens to their work: - was it noticed - was it reviewed - are there any problems with it And this is what Django is now lacking. I'll take one of my own patches as an example (not trying to push it anywhere though). It's http://code.djangoproject.com/ticket/2606 -- a template tag {% url %} that brings reverse lookups to templates. I have first posted it as a code example for someone's question on django-users, then Adrian noticed it and asked if I want to submit it to Django. Sure! I've made a patch, filed a ticket and replied to the list about it. And then there was no reaction. Now I don't know why is that. Is it time? Is it low priority? Is it because of I couldm't come up with tests for this feature? This lack of information is what makes people talk about 'closed doors'. And to not sound as a whining asshole (though it might be already too late for me :-) ) I'd like to propose something to improve situation. May be it would be possible to have somewhat strict list of bugs and features that core reviewers will look and review patches in that exact order. This queue will give every contributor an idea of when a train will come to their station. I understand that this will limit the 'fun' part of your jobs but this is always a compromise that a team should make. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
