> What I've said here, repeatedly, is that if there's this problem, I > want to see examples of it, because I haven't so far, and if I'm going > to understand that there is a problem and understand where it comes > from, I *need* to see examples. There's a big, big difference between > that and "no-one is allowed to criticize Django". > > But apparently I'm just digging myself a big deep hole the more I say, > so I'll stop talking now and let others work this out.
Ok, I agree we should put this to rest for a while. But I think you need to take my comments and the other two postes *as examples*. We *are* your examples right there. And I certainly do not expect my voice alone to make anyone change their mind about anything. My example and the other two just get added to the pile labelled "people who think the dev policy should be more open" and filed for future reference. Maybe six months down the road, people will be saying, gee we had a lot of those type of posts, maybe it's true. Or we will be a minority. But really, there's no point in telling us we're wrong when we state our own perceptions, and then ask us to produce more examples, 'cause that's what we are. And we must keep in mind that people will also make more positive noise then negative noise. So for everyone who actually takes the time to say something, there are probably ten others thinking it and just leaving. Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
