> I second the on the fact that Malcolm's help has been amazing! Now > that we are thinking of splitting the mailing list why don't we > split it according to parts of django! Each one will have a unique > mailing list. django.contib.admin will be one mailing list etc... jk
Breaking it up by components presumes some kind of prior knowledge of the architecture of the framework. As I mentioned in my other post, my experience with the Zend Framework list would suggest that this isn't a good idea. For one thing it doesn't do anything to stop the flow of user questions into the internals discussions and in fact makes them worse as users are even more confused as to where they should ask questions. It would more than likely just increase the need to redirect traffic to the correct list. Nick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
