Hi Michael, On 27 May 2016, at 20:44, Michael Manfre <mman...@gmail.com> wrote:
> Regarding feature parity, the initial commit of this non-existent-yet library > will have as many supported features as django-mssql on Django 1.9 and 1.10. > :P Fair enough :-) > The pre-release code will need to be hosted publicly to allow the Microsoft > engineers to contribute (and anyone else willing to do so). Having to host > elsewhere and then move it relatively soon afterwards will likely cause > confusion and unnecessary overhead. When I moved django-mssql from google > code to bitbucket, I was fixing links across the internet for the next ~12 > months. > > Do we want Django to only ever endorse established/mature projects? Or should > there be flexibility to endorse people (and companies) willing to implement a > solution. Actually I’m in favor of putting the SQL server backend in its own repository in the django organization (and also of splitting the Oracle backend in a separate repository, but that’s another story). I’m just slightly worried that we don’t have a well defined rule and that we may refuse this privilege to other projects for seemingly arbitrary reasons. (The key word is “seemingly”.) Until now, we haven’t managed to define what the rules for putting a project in the django organisation on GitHub are. > The current case for the SQL Server backend might be non-standard in that > it's really a continuation of the django-mssql project, albeit as a rewrite > with backing by Microsoft. I can't imagine the Microsoft supported backend > not being the Django endorsed one. There’s a precedent, namely with MySQL: the Oracle supported backend isn’t the Django endorsed one :-) However, I suspect Oracle built it quite some time after Django built its own, so that’s a different situation. Best regards, -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/019F5610-1AAB-4E8B-9273-32EEAD237AC1%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
