Changes between Version 1 and Version 2 of SummerOfCode2025

Timestamp:

Feb 11, 2025, 7:15:05 PM (11 days ago)

Author:

Timothy Schilling

Comment:

Adding two confirmed projects and the other proposed projects that are still pending investigation.

SummerOfCode2025

@@ -123 +123 @@
 In no particular order:
 
-**Projects are still being finalized, the following is a placeholder template**
+== Django Templates: Bring django-template-partials into core ==
+
+|| Difficulty || Medium
+|| Size || 350hrs
+|| Potential Mentors || Carlton Gibson
+|| Key Skills || Django Template Language, template tags
+
+The third-party app django-template-partials allows for reusable named inline partials for the Django Template Language. These named inline partials can be used multiple times within a template or included in other templates. It would be good to have support built-in to core.
+
+Outcome would be a PR adding this into Django.
+
+== Automate processes within Django contribution workflow ==
+
+|| Difficulty || Medium
+|| Size || 350hrs
+|| Potential Mentors || Lily Foote
+|| Key Skills || GitHub actions, scripting, Jenkins
+
+The contribution workflow within Django has several manual processes. These are error prone and take up valuable time from contributors. This project would seek to automate these processes, such as automating releases, identifying active PRs and managing aging PR queue.
+
+Part of this project will involve working with the Fellows to determine which of their tasks and the community's tasks are the best candidates for automation.
+
+Outcome would be one to several PRs automating these workflows, depending on how many are accomplished.
+
+
+----
+
+**The following projects are still being finalized**
+
+
+== Security: Bring CORS and CSP into core ==
+
+|| Difficulty || Medium
+|| Size || 350hrs
+|| Potential Mentors || TBC
+|| Key Skills || HTTP request-response cycle, middleware, decorators
+
+There are third-party apps providing support for [https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS Cross-Origin Resource Sharing (CORS)] `django-cors-headers` and [https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP Content Security Policy (CSP)] `django-csp`, but it would be good to have support built-in to core.
+
+Following the design of the CSRF/clickjacking protection, having safe defaults, and allowing straightforward per-path customisation, via e.g. decorators, would improve the security of all Django projects.
+
+Outcome would be a pair of PRs adding these into Django. 
+
+== Auto-detection of custom migration operations ==
+
+|| Difficulty || Hard.
+|| Size || 350hrs
+|| Potential Mentors || Mariusz Felisiak
+|| Key Skills || Migrations Framework
+
+Allow auto-detection of custom migration operations.
+
+The auto-detector has its change-detection mostly hard-coded: [https://github.com/django/django/blob/main/django/db/migrations/autodetector.py#L104 autodetector.py#L104]
+
+It doesn't seem easy (or even possible with the current approach) to
+allow third-party code to intervene. The list of handlers to generated the individual operations would need to be data-driven, so that custom steps could be added.  
+
+Expected outcome here would be a PR allowing auto-detection of custom migration operations. 
+
+== Improve the Database Cache Backend ==
+
+|| Difficulty || Medium.
+|| Size ||       350hrs
+|| Potential Mentors|| TBC
+|| Key Skills || Cache Framework 
+
+Setting up a shared cache backend is nearly always required, as many
+third-party packages assume the cache works like this (unlike the default
+locmemcache which is per process). DatabaseCache is the easiest such cache
+backend, not requiring any extra infra and working on shared hosts without a
+filesystem. But it could be better.
+
+Django-Mysql has had a much better DB cache backend implementation since 2015: https://adamj.eu/tech/2015/05/17/building-a-better-databasecache-for-django-on-mysql/ . This has never been adapted for the other supported databases but it should be fairly straightforward, mostly some translation of SQL to different dialects.
+
+Expected outcome would be a PR improvement database cache backend. 
+
+As a stretch goal, it would also be nice to hook the database cache tables into
+migrations somehow rather than the current hacky duck typing approach:
+https://github.com/django/django/blob/64b3c413da011f55469165256261f406a277e822/django/core/cache/backends/db.py#L12-L28 ).
+
+== Expand django-stubs coverage ==
+
+|| Difficulty || Hard.
+|| Size ||       Variable
+|| Potential Mentors || Adam Johnson
+|| Key Skills || Python typing and Django-stubs 
+
+[https://github.com/typeddjango/django-stubs django-stubs] is an external project that adds type hints to Django. It may be possible to work on it under GSoC if you can show experience with Python’s type hints and Mypy.
+
+django-stubs uses Mypy’s stubtest tool to check that its type hints align with Django’s source, per [https://github.com/typeddjango/django-stubs/blob/master/CONTRIBUTING.md#testing-stubs-with-stubtest its contributing documentation]. The “todo” list contains ~1600 functions and classes missing type hints. A proposal targeting a specific, significant subset of the missing types is likely to be accepted.
+
+== Configurable Content Type Parsing ==
+
+|| Difficulty || Medium.
+|| Size || 350hrs
+|| Potential Mentors || TBC
+|| Key Skills || HTTP request-response cycle 
+
+For Django 5.0 we're looking to modernize the `HTTPRequest` object, adding a content-type aware `request.data` property. This will parse `request.body` according to the content type.
+
+The initial phase — targeted for before GSoC — will add `request.data` and add support for JSON body handling, but the next phase is to make that fully pluggable with custom parsers.
+
+- Add a list of parsers to the request object, that can be customised — in a middleware for example — at any point prior to accessing `request.data`.
+- Parsers should implement a `can_handle(content_type) -> Bool` method. The first parser returning True will be selected to parse the `request.body`.
+
+Expected outcome is a PR allowing configurable content type parsing. 
+
 
 == [PLACEHOLDER] Project name ==