On 8/1/07, mamcx <[EMAIL PROTECTED]> wrote: > > So, I can devote dev time to fix the non-sql server support. I have > read the code, see all the patch (and be confused for its). I'm not a > python guru but have 3 years of expertise in develop against Sql > server.
Volunteers are always welcome. > So, how proceed? To how I need to talk? As always, the best option is "Just do it". You don't need official permission to start work. Code speaks louder than words - if you want SQL Server support, write it. This doesn't mean your changes will get applied to the trunk any time soon. I would place the likelyhood of a patch of this magnitude getting merged into trunk in the next three weeks at somewhere between "unlikely" and "not a chance in the world". As an example, the Oracle patch took almost 6 months to get merged - and I'd consider that to be a pretty good example of a 'fast' time frame. However, this doesn't stop you from working on the patch, and using it in your own projects. You can keep your local version of Django-with-SQL-Server running happily, and upload updated patches to the Trac repository as required. When you have demonstrated to the community that you are able to produce good patches, and you are able to dedicate the time required to maintain the patch over the long term, we can look at merging the branch into the trunk. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
