I do have ideas but no idea about how viable they are in a GSoC context. Nevertheless I will put write them down here, maybe we can find smaller scopes if needed and if not, it still serves as a list of things that I'd think to be interesting:
* Probably my number one since it kinda is a blocker for me: We need a connection pool in Django for async to work. That said connection pools are hard to get right ( https://github.com/brettwooldridge/HikariCP/blob/dev/documents/Welcome-To-The-Jungle.md and https://www.psycopg.org/articles/2021/01/17/pool-design/ ). * Production ready webserver (https://groups.google.com/g/django-developers/c/q20_Cxske88). Maybe only focus on a smaller part first, like reading env variables / config files. * Depending on how far we get with `request.data` in the meantime, maybe put the second steps (adjustable parsers etc) in as GSoC project? * I haven't talked with anyone about this one yet, so it might be completely bonkers: I think openid connect is here to stay for a while and I'd love to see first class support in core for it. I am looking at this from an enterprise perspective though; I do not expect a user to choose where to login out of many options but rather provide a replacement for the default username/password login in an enterprise environment. Most solutions there support openid connect. Please note that I am not suggesting to support generic OAuth2/SAML and whatnot -- there are great 3rd party packages for that already (which also include support for openid connect). I'd just love to be able to install arbitrary Django projects and point them to the central authentication server. I hope this provides some ideas to get more ideas rolling :) Cheers, Florian On Tuesday, November 15, 2022 at 10:11:45 AM UTC+1 carlton...@gmail.com wrote: > Hi all. > > Google Summer of Code (GSoC) for 2023 has just been announced. > > https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html > > Django has participated many times, and it's been a real boon. Recent > successes include: > > * The django-stubs mypy plugin. > * The cross-db JSON field. > * The Redis cache backend. > * Per model-class (field instance) custom lookups > * Setup of the django-asv benchmarking project. > * ... > > Application deadline for Orgs is February 7. I'll begin working on it > after the New Year. > > Main bit is an ideas list for projects. The GSoC guide has a Writing a > Good Ideas List > section. > > > Projects should take ~175 hours or ~350 hours for GSoC contributors to > complete. > > i.e. "short" or "long" projects. > https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list > > I'm writing here *to solicit input on project ideas*. > > I put "Technical Board?" in the subject because we're short a list of > project > ideas for the technical direction of Django going forward, and maybe > thinking > in terms of GSoC could be a way of bootstrapping that. The "?" is because > that's not > meant to exclude other input. > > Here's last year's list for reference: > https://code.djangoproject.com/wiki/SummerOfCode2022 > > - Some of those were done: benchmarking (but that could be built on) and > per-instance > field lookups. > > - Rate-limiting is a no-go I think: we couldn't come to any decent > agreement on scope, > so it's better to live as a third-party package. > > - I've tried to include folks from the wider ecosystem in previous years. > Two years ago > we had both Wagtail and django-stubs projects. Wagtail then (last year) > applied in their own right, to great success. I'd like to offer that help > again to e.g. Jazzband or other established projects, assuming > maintainers > feel they have the capacity to mentor. (It's a minor increment to my > effort > for a good return I think.) > > > No urgency but, can I ask you to put your grey cells into action? 🙂 > > > Thanks. > > Kind Regards, > > Carlton > -- 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/2b3650c6-d340-4464-96f2-e6722a8e415an%40googlegroups.com.
