On Wed, Apr 29, 2009 at 3:13 AM, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > > On Tue, 2009-04-28 at 14:38 -0400, Nathan Auch [Sybase] wrote: >> Hi Russ, >> >> Thanks for taking the time to respond. We will finish off the SQL >> Anywhere work in Django and then follow the procedure you outlined. It >> sounds like starting with a externally maintained module and seeing >> where that takes us is the way to go. > > I would modify Russell's checklist very slightly... creating a patch in > Trac isn't going to be particularly helpful initially (I'm not quite > sure why he made that point #2 ahead of point #3 -- when the latter is > generally more important for an external feature -- but there may be > something I'm misunderstanding).
My reasoning here was that creating and maintaining a patch is one way to demonstrate that someone is committed to Django support. You are correct that an external (e.g., Google code) project would probably be preferable, and is just as good at demonstrating long-term commitment. Russ %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
