On Tue, 2008-12-16 at 21:18 -0600, Arien wrote: > On Tue, Dec 16, 2008 at 8:36 PM, Malcolm Tredinnick > <malc...@pointy-stick.com> wrote: > > > > All of this is predicated on using the word "Django" in the name, which > > is the bit I have a problem with. > > How is this different from, e.g., any of these? > > http://code.google.com/hosting/search?q=django-
Take your pick: (a) It's not, really. People could do a much better job of naming their packages. (b) All of those packages are designed to run using Django, the Python web framework. > > > Choose a different name for it. If you implement a web server in Perl > > are you going to call it "Apache::*", if it does some of the same things > > as Apache (e.g. using the HTTP protocol)? No, you're going to find a > > proper name and then mention in the docs that it does some of the same > > things as Apache, or in similar ways to Apache. That avoids any > > confusion between your product and the actual Apache product. > > http://search.cpan.org/search?query=Apache&mode=module Already answered in early mails. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
