Why not use the existing Python Cheeseshop (http://cheeseshop.python.org/pypi) for this? Advantages:
1) You don't have to build anything, it's already there. 2) More visibility for Django: with a Django-specific repository, only Django developers will see the packages. In the cheeseshop, all Python developers will see the packages, and could find Django through a contributed package, rather than the other way around. 3) The energy we'd put into a Django-only repository could instead be used to further the cause of the cheeseshop. --Ned. Sean Schertell wrote: > I wonder how many of us are writing nearly identical apps at any > given time. For example, I just hired a guy to write a really basic > newsletter app for my project. Now I'm working on a fairly typical > "upcoming events" schedule. And soon I'll be working on a simple > photo gallery that makes thumbnails as you upload, etc. I'd bet > dollars to donuts that many of you have written these apps already. > > Wouldn't Django be that much sexier if it came with an ever-expanding > repository of apps that we could all share with each other? The fact > that apps are modular plug-and-play in Django is *really* cool (Rails > can't do that). So why not leverage the "pluggability" of Django's > app architecture by making a bunch of these apps public? > > Am I alone on this? If I created such a repository would anyone use it? > > Sean > > > > > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
