Hi Russ,Tim That is a great idea. I am going to try to engage with the team at Microsoft who is in charge of the sponsorship. I plan on attending the conference so I will see some of you there.
@Tim: I agree that a lot of ground work needs to be done in terms of testing out the current third party adapters and deciding which one/ones should we adopt and extend. I know Michael Manfre has a lot of expertise here. I will do my due diligence and test out the existing solutions but if Michael could share some of his findings, that would be great. If anyone else also wants to take a stab at testing and using the existing adapters for a sample app, that would be great as well. I will try to share my learnings soon. Here are the ones I am going to test, am I missing any? 1. Django-mssql <https://bitbucket.org/Manfre/django-mssql/src> 2. Django-pymssql <https://github.com/aaugustin/django-pymssql> 3. Django-pyodbc-azure <https://github.com/michiya/django-pyodbc-azure> 4. Django-pyodbc <https://github.com/avidal/django-pyodbc> Thanks, Meet That is a great idea. I am going to try to get hold of On Monday, August 31, 2015 at 4:58:40 PM UTC-7, Russell Keith-Magee wrote: > > Hi Tim, Meet > > I know this is very late to be mentioning, but one idea that worth > raising: DjangoCon US is next week (in Austin). Thursday and Friday > are coding sprints, where there will be many people (including a good > chunk of the core team) looking for projects to hack on. > > Microsoft is already a sponsor of DjangoCon itself; if we can get some > engineers from the Azure team (assuming there aren't already some > coming), we can start some of this prep work. > > Yours, > Russ Magee %-) > > On Tue, Sep 1, 2015 at 3:46 AM, Tim Graham <timog...@gmail.com > <javascript:>> wrote: > > To arrive at the best solution, I think a lot of discussion needs to > happen > > on this mailing list before October. As for me, besides the name of some > > existing packages that offer SQL Server/Azure support, I know very > little > > about the current landscape so I really wouldn't have anything to offer > in a > > discussion, but there are others on this list who definitely do. > > > > The existing Microsoft database backends have come out of specific > developer > > needs and I think it would maximize success if your team were personally > > invested in the backend by building a Django application backed by SQL > > Server/Azure. If I were a Microsoft engineer responsible for this > project, I > > would start by building a small Django application to solve some problem > > that my team has. Then I would test it out with all the third-party > backends > > for Microsoft databases previously mentioned to get a feel for how they > > work. I should learn enough to at least participate in a discussion with > > other Django developers about the direction of this project. Ideally, I > > would be able to learn enough to write up a Django Enhancement Proposal > [1] > > that summarizes the landscape and describes what an "official solution" > > should look like. > > > > If you are relying on members of the Django team to do all this upfront > > work, then please tell us so we can see if someone will do it. If you > are > > expecting to get all this done in a couple days in Seattle, this doesn't > > seem feasible to me. However, if we have a working proposal by > mid-September > > that the community can review and give feedback on, then I think our > time > > together in October could be productive. I don't know anything about the > > background of your team, but it seems pretty unlikely that any sort of > > coding sprint would be useful unless the work and learning I described > > happens well before the workshop. > > > > [1] https://github.com/django/deps/ > > > > > > On Monday, August 31, 2015 at 3:07:28 PM UTC-4, Meet Bhagdev wrote: > >> > >> Hi Tim, > >> Thanks for bringing it up. Yes, we will have developers who will engage > >> with Django developers (like yourself) during the workshop. > >> > >> The goals of the October workshop are to: > >> > >> 1) Get to know each other and begin building a relationship > >> > >> 2) Get in a room with Microsoft developers and discuss the current > >> landscape > >> > >> 3) Work on half day coding sprint(s) with Microsoft developers to > get > >> started with contributions > >> > >> 4) Establish a plan for how Microsoft can best contribute to > Django, > >> and ensure we have great integration between Azure SQL and MSSQL and > Django > >> by maintaining our contributions > >> > >> > >> The key takeaway is that we want to contribute to existing solutions to > >> improve the Django and MSSQL/Azure SQL story. To do so we want to > understand > >> the current landscape, the gaps, and the next steps to make this happen > (the > >> right way). > >> > >> > >> We are currently in the planning stages and would love to get feedback. > >> What do you think about the goals mentioned above? Is there anything > you > >> like to add/remove? > >> > >> > >> We can definitely make attending via Skype an option for attendees > unable > >> to make it in person. > >> > >> > >> Best, > >> > >> Meet > >> > >> > >> On Monday, August 31, 2015 at 11:33:40 AM UTC-7, Tim Graham wrote: > >>> > >>> By "we" do you mean the engineers at Microsoft who will be working on > >>> this? Will they be doing any planning for this before the meet up in > >>> October? I'd like to know more specifics about the agenda and goals > for the > >>> workshop. > >>> > >>> Also, I wanted to make sure my question about a videoconferencing > option > >>> for Django developers interested in participating in the discussion at > that > >>> time but unable to travel to Seattle didn't get lost. > >>> > >>> On Tuesday, August 25, 2015 at 7:53:48 PM UTC-4, Meet Bhagdev wrote: > >>>> > >>>> > >>>> Absolutely agree with Tim here. We need to start exploring all the > cool > >>>> open sourced third party adapters. Borrowing/adopting them definitely > seems > >>>> like the way to go about things instead of re inventing the wheel. I > tried > >>>> doing some research and came across the following: > >>>> > >>>> 1. Django-mssql > >>>> > >>>> 2. Django-pymssql > >>>> > >>>> 3. Django-pyodbc-azure > >>>> > >>>> 4. Django-pyodbc > >>>> > >>>> > >>>> Am I missing any? > >>>> > >>>> Best, > >>>> Meet > >>>> > >>>> On Monday, August 24, 2015 at 11:12:44 AM UTC-7, Tim Graham wrote: > >>>>> > >>>>> I guess the first step is to identify which third-party backend(s) > >>>>> we'll target to adopt officially (or at least borrow from heavily). > For > >>>>> example, will we need separate backends for MSSQL and Azure? > (Knowing > >>>>> nothing about the landscape myself, this question could be > nonsensical.) Is > >>>>> this discussion something that should happen before the October > summit? It > >>>>> seems to me the face-to-face time will likely be more productive if > we have > >>>>> some of the high-level details ironed out. > >>>>> > >>>>> By the way, is videoconferencing an option for Django developers > >>>>> interested in participating in the discussion at that time but > unable to > >>>>> travel to Seattle? > >>>>> > >>>>> On Saturday, August 22, 2015 at 5:53:37 PM UTC-4, Shai Berger wrote: > >>>>>> > >>>>>> On Saturday 22 August 2015 13:28:31 Aymeric Augustin wrote: > >>>>>> > >>>>>> > > >>>>>> > >>>>>> > There isn’t such a clear story for running Django on Linux. This > led > >>>>>> > me to > >>>>>> > >>>>>> > write https://github.com/aaugustin/django-pymssql. Alternatives > >>>>>> > include > >>>>>> > >>>>>> > https://github.com/denisenkom/django-sqlserver and > >>>>>> > >>>>>> > https://github.com/lionheart/django-pyodbc. > >>>>>> > >>>>>> > >>>>>> > >>>>>> There's also django-pyodbc-azure, a fork of django-pyodbc > (actually, > >>>>>> the current django-pyodbc is also a fork of the original project, > which has > >>>>>> been discontinued). I took the liberty to forward the message to > that > >>>>>> project. > >>>>>> > >>>>>> > >>>>>> > >>>>>> Shai. > > > > -- > > 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-develop...@googlegroups.com <javascript:>. > > To post to this group, send email to django-d...@googlegroups.com > <javascript:>. > > Visit this group at http://groups.google.com/group/django-developers. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/django-developers/9a79aa2d-ad82-4905-8bcc-835911c21103%40googlegroups.com. > > > > > > For more options, visit https://groups.google.com/d/optout. > -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f5f53970-df70-4a6d-9fc5-192dcd79cfac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
