> Yes, the current name is ambiguous. So is every other possible name. Just as a comment from a newbie from over the fence:
As a PHP/Zend Framework developer playing with Django I actually thought the Django list names and setup to be very simple in comparison to the Zend Framework ones which are broken up by component. The traffic in the ZF mailing lists has had an inevitable increase in questions from those new to the framework and I've found it is no longer easy to keep up with the internal development of the framework through these lists. In comparison the Django lists are a lot easier to follow, so I really don't think you have a problem at all. As Russell says, whatever name you choose will be ambiguous anyway. Also, developer (of Django) and user (of Django) are fairly standard names for these kind of lists in my experience. In short: No confusion for this user. 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 -~----------~----~----~----~------~----~------~--~---
