Regardless of whether it should be on the site or not, I think there's an fundamental open-source concept missing from this conversation. If you think the Django site needs a favicon, a good first step would be to provide one. That's not guarantee it'll be used, of course, but if it's so important, make one up and it'll make your argument more convincing. Not only that, the Django guys then don't have to make one up themselves, something which they're obviously not terribly concerned with doing.
You'll notice that, despite this recommendation, I don't include an example favicon in my email. The reason is simple: I don't really care whether the site has one or not. I just think that if you're going to request something, provide whatever you can, and it'll go that much better. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
