It would be nice to take advantage of differing priorities rather than discourage them. I think that's the way it's meant to work, but in this case the requestor doesn't have the expertise to finish the job?
Just my unrequested two cents, Matt -----Original Message----- From: django-developers@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Marty Alchin Sent: Thursday, October 04, 2007 2:27 PM To: django-developers@googlegroups.com Subject: Re: Still no favicon - Re: Visual recognition of Django website I'll preface my thoughts with the disclaimer that I have authority here, I'm just somebody who's been watching this discussion. First, this isn't a bug in any sense of the word. It has nothing to do with any breakage of code. It's a feature request. Let's just get that straight. Feature requests should always get lower priority, plain and simple. While I can appreciate the desire of some to have a favicon, and I can also understand the frustration at not hearing much from those in charge, but there seems to be some confusion as to how things work here. Yes, there has been discussion, and yes, there has been general agreement on it, among those who want to see it happen (which actually surprises me). However, a lack of negative response does not automatically imply approval by anyone, especially not those in charge. So the logic of "we think it's great and nobody disagreed, so it should be applied immediately" is completely false. If that was the way it worked for other tickets, I'd have nightmares about it myself, and I'm not even a core developer. The general rule of thumb, as far I as I understand it, is that the burden of proof is on those in support of the ticket. Sure, you might have a lot of support, but if that support isn't greater than the reluctance to implement it, it won't get done. No amount of silence from one party will change that. If the core devs aren't convinced (and they'll tell you when they are), it won't happen. Also, allow me to try to explain why it's rude to bring things like this up in this manner. Take a look at how many times the core developers respond to emails on django-developers on an average day. I don't have numbers off-hand, but I typically see about 5-10 emails per day from each of Malcolm, Russell and Jacob, and there are others who are active as well. What this means is that they do in fact check their email. If they send an email before yours and another after it, the odds are astronomically high that they read your email along the way. Replying about it every few days just comes across as a child tugging on her parents' pant legs to get an ice cream cone. Add to that the language like "why hasn't anything happened yet?" and that child is now saying "BUT BUT BUT I WANT IT!!!!!1". Now, I'm not saying any of you are children, nor saying that you act like children. But you have to realize that things like this have the same effect on people as the child I described. These people have a lot to deal with, and every time they have to stop and read yet another email complaining about the lack of a favicon, they lose time, they lose patience, and they lose the momentum they had on their other endeavors. I don't mean to speak for anyone but myself, but I'm playing the odds when I say: they're listening, and they heard you. -Gul P.S. I apologize in advance if this offends anyone. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
