On a broader note, let me give you a bit of history. I started my career as a customer service person. I managed Staples Business Services department in my local Staples. Before I decided to learn programming a couple years ago at 24, I learned a valuable lesson:
-- No matter what industry you're in, or what your title is, your real job is "Sales Person". Your second job is "Customer Service", and finally your third job is "[Insert Job Title Here]". When my clients come to me and say "MY SITE SHOULD DO THIS!" my first response isn't "YOU'RE WRONG!". I understand that they're my clients, and they are always right in their own eyes. It's my job to find out where their pain point is, and see if there is a better remedy than what they're suggesting. If there is not, then it's my job to decide if they're truly wrong. If I find out they're not wrong, and I don't have a better remedy, I typically cave to their request rather than going back and changing my proposal to exclude their current request. I'm not saying that the core developers should think of their free, public contributions as a paying client, but it might be good to exercise a little restraint when you feel "annoyed". If I didn't feel so pushed back by the core team, I'd become a big contributor, but instead of writing code, I spend all of my free time arguing, if just to get somebody to level with me and give me a good reason why they're turning my away. I don't claim to be an expert, but in my own eyes, my ideas are gold until somebody can give me a good explanation of why they're not. In the team development process, this constructive feedback is called problem solving. Look at what I was able to achieve in 5 minutes with James' feedback: http://groups.google.com/group/django-developers/browse_thread/thread/f8c747a26aa5d8ed/1397a0785cb09a36 (bottom). If my new version is still bad, take 30 seconds for some more feedback. repeat this across a slough of tickets, and before you know it you have hundreds of problem solvers like me, with vested interests, developing Django piece by piece. -- 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.
