> Then there is also the question on how to ensure continued commitment from Microsoft -- what happens when Microsoft (or the current PM/PO or whatever) looses interest?
IMO. This is the biggest one. What I'd expect to see here is MS taking up a long-term corporate sponsorship of the DSF, demonstrating a commit, and giving the DSF resources to ensure the backend was covered. Every time that's been mentioned though it's like crickets — zero response. Certainly zero positive response. (I appreciate that's got to come from **someone's** budget, but no more than engineering time.) Kind Regards, Carlton On Fri, 1 Apr 2022 at 12:13, Florian Apolloner <f.apollo...@gmail.com> wrote: > Hi Waren, > > On Thursday, March 31, 2022 at 6:30:06 PM UTC+2 vwa...@gmail.com wrote: > >> We'd love to hear thoughts and feedback around the possibility of moving >> forward with a DEP enhancement proposal, with a commitment from Microsoft >> to providing continued dedicated support for the 1st party backend through >> the Django project itself (rather than the 3rd party repo). >> > > As pointed out by Adam I do not think the backend is ready for core. At > the minimum it would need to support most of what Django offers. Then there > is also the question on how to ensure continued commitment from Microsoft > -- what happens when Microsoft (or the current PM/PO or whatever) looses > interest? The backend would be in Django then and we can't easily kick it > out. > > Given the backend APIs and the recent enhancements by Tim to allow > backends to define which tests they can't pass etc I do not see any strong > technical argument for including a new backend in core at all. Aside from a > selling argument for Microsoft that Django includes the backend in core, > what do we gain? It is not like one usually uses Django without installing > any 3rd party dependencies, so installing one more certainly won't hurt. > > Cheers, > Florian > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/826cc91f-1621-4255-8679-ef7e8da1cc09n%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/826cc91f-1621-4255-8679-ef7e8da1cc09n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJwKpyQfT1MAgHmg-3NFiWZ4rohK5ejNbq_hLHJheidWRS3BnQ%40mail.gmail.com.
