On 7/24/07, Toby Dylan Hocking <[EMAIL PROTECTED]> wrote: > Furthermore, is there a formal process for integrating into > django.contrib? How has it worked in the past?
At the moment there isn't a formal process; when it's come up before, the most common suggestion seems to have been that an application should exist standalone for a while first; this is useful in a couple of ways: 1. It lets you figure out if the app is useful/popular enough to nominate for django.contrib. 2. It lets you respond to feedback without having to worry about introducing backwards-incompatible changes to something that's being distributed with Django. It's true that in the past a couple of things have gone more or less directly into django.contrib (databrowse and sitemaps), but that process probably doesn't scale all that well ;) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
