I have a bit of confusion about how possibly "non-trivial" patches are supposed to be handled.
Common practice here seems to be that if someone wants to propose a change and has a patch ready, they open a ticket first and then a discussion here. The docs indicate that if the patch is non-trivial (for some definition of non-trivial), the author should show that a discussion of alternate solutions occurred here. I assume that the ticket description is where this evidence goes. My question is: if I have a non-trivial patch, does the alternate- solutions discussion need to occur before I post my patch to Trac, or is it all right to create the ticket first and follow up with linkage later? Finally, I'd like to offer up a patch to contrib.admin, and I'm wondering if it would be classified as non-trivial. It allows a custom "base_site" template to be specified in an AdminSite instance. The patch modifies the admin templates which extend "admin/ base_site.html" to extend a "base_site_template" context variable instead, and adds an optional argument to a handful of view functions in contrib.auth and contrib.admin. Is this kind of change considered non-trivial? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
