Changes between Version 2 and Version 3 of SummerOfCode2027

Timestamp:

Nov 9, 2026, 9:22:40 AM (32 hours ago)

Author:

Sarah Boyce

Comment:

--

SummerOfCode2027

@@ -128 +128 @@
 The project ideas below will list key skill, but all assume a knowledge of Python, and familiarity with Django itself. 
 
+== Add migration hooks for Django and third-party apps ==
+
+|| Difficulty || Hard
+|| Size || 350hr
+|| Mentors || (need confirmation)
+|| Key Skills || Django ORM, migrations
+
+Introduce an API for apps to respond to migration operations with additional operations. Adapt `django.contrib.contenttypes` and `django.contrib.auth` to use it, making content types and permissions available to subsequent data migrations.
+
+The design should account for reversing and squashing migrations, database routing, and apps being added to existing projects. The expected outcome is a tested and documented API usable by Django and third-party apps.
+
+References:
+ * [https://code.djangoproject.com/ticket/29843#comment:9 Ticket #29843: Create permissions using migration operations]
+ * [https://forum.djangoproject.com/t/can-the-migration-system-be-extended-by-third-party-apps/44009/4 Forum discussion: Extending the migration system]
+
+== Develop scalable pagination for large querysets ==
+
+|| Difficulty || Hard
+|| Size || 350hr
+|| Mentors || (need confirmation)
+|| Key Skills || Django ORM, SQL, database performance
+
+Develop a third-party pagination package that avoids expensive counting and large offsets, with cursor-based pagination as a promising approach. The design should address ordering, navigation in both directions, and supported queryset limitations.
+
+The expected outcome is a published package with tests, documentation, and performance benchmarks, accompanied by a Django blog post inviting feedback to inform development and possible inclusion in Django.
+
+References:
+ * [https://code.djangoproject.com/ticket/37220 Ticket #37220: Scalable pagination]
+ * [https://code.djangoproject.com/ticket/26451 Ticket #26451: Historical pagination discussion]
+
+== Composite Foreign Keys ==
+
+|| Difficulty || Hard
+|| Size || 350hr
+|| Mentors || (need confirmation)
+|| Key Skills || Python, Django ORM, SQL, database constraints, migrations
+
+Add support for foreign keys referencing composite primary keys, building on draft PR #18868. This includes database constraints, validation, and migrations.
+
+The design should address explicit field mappings, fields shared between relationships, and whether automatic field creation is feasible. It should also consider a standalone `ForeignKeyConstraint` and how composite relationships interact with virtual fields and the usual `<field>_id` attribute.
+
+The expected outcome is a tested and documented API supporting composite foreign keys across Django's supported database backends.
+
+References:
+ * [https://code.djangoproject.com/ticket/35956 Ticket #35956: Add composite foreign keys]
+ * [https://github.com/django/django/pull/18868 Draft PR #18868]
+
+== Add translation catalog checks and statistics to makemessages ==
+
+|| Difficulty || Medium
+|| Size || 175hr
+|| Mentors || (need confirmation)
+|| Key Skills || gettext, Django management commands, internationalization
+
+Extend `makemessages` to check whether translation catalogs are up to date and report translation statistics without modifying `.po` files.
+
+The work includes defining command options and reliable exit codes for automated checks. Checks should distinguish outdated catalogs from incomplete translations and ignore differences caused solely by generated metadata.
+
+The expected outcome is tested and documented functionality suitable for local development and continuous integration.
+
+References:
+ * [https://code.djangoproject.com/ticket/26803 Ticket #26803: Add a statistics option to makemessages]
+
+== Migrate Django's translation workflow to Weblate ==
+
+|| Difficulty || Medium
+|| Size || 175hr
+|| Mentors || (need confirmation)
+|| Key Skills || Python, gettext, Git, translation platforms, technical writing
+
+Migrate Django and documentation translations from Transifex to Weblate, coordinating the transition with translation maintainers and available hosting capacity.
+
+Update `scripts/manage_translations.py` and the tooling in `django/django-docs-translations`. Validate that catalogs are preserved, translated documentation builds, and translation updates can be incorporated into releases.
+
+The expected outcome is a working Weblate workflow, tested integration tooling, and guidance for translators and maintainers.
+
+References:
+ * [https://forum.djangoproject.com/t/improving-the-process-of-incorporating-translations-to-django/26140/19 Forum discussion and hosting arrangements]
+ * [https://github.com/django/django-docs-translations Django documentation translations repository]
+ * [https://github.com/django/django/blob/main/scripts/manage_translations.py Django translation management script]
+
+== Add interactive ORM examples to Django's documentation ==
+
+|| Difficulty || Medium
+|| Size || 175hr
+|| Mentors || (need confirmation)
+|| Key Skills || Django ORM, Sphinx, JavaScript, technical writing
+
+Integrate DryORM into Django's documentation so readers can experiment with ORM examples and inspect their results without setting up a local project.
+
+The work would include agreeing on the integration approach, preparing runnable examples with models and sample data, and adding documentation tooling to maintain them. The design should account for Django versions, accessibility, and keeping the documentation usable without the external service.
+
+The expected outcome is a tested integration demonstrated on selected ORM documentation pages, with guidance for contributors adding further examples.
+
+References:
+ * [https://github.com/django/new-features/issues/203 Proposal #203: Include DryORM tool in the documentation]
+ * [https://dryorm.xterm.info/ DryORM]
+
+== Add built-in Cross-Origin Resource Sharing (CORS) support ==
+
+|| Difficulty || Medium
+|| Size || 175hr
+|| Mentors || (need confirmation)
+|| Key Skills || Python, HTTP, Django middleware, async programming
+
+Bring the core functionality of `django-cors-headers` into Django, allowing projects to configure cross-origin access without an additional dependency.
+
+The work would include agreeing on requirements and configuration, implementing middleware for synchronous and asynchronous requests, and providing a migration guide for existing package users. The design should cover allowed origins, credentials, preflight requests, and interaction with existing middleware.
+
+The expected outcome is tested and documented CORS support, with configuration examples and guidance explaining its relationship to CSRF protection.
+
+References:
+ * [https://github.com/django/new-features/issues/8 Proposal #8: Bring django-cors-headers features into Django]
+ * [https://github.com/adamchainz/django-cors-headers django-cors-headers]
+
+== Implement DEP 15: Improved startproject interface ==
+
+|| Difficulty || Medium
+|| Size || 175hr
+|| Mentors || (need confirmation)
+|| Key Skills || Python, Django management commands, project templates, technical writing
+
+Implement the improved `startproject` interface described in DEP 15, making it easier to start Django projects with simpler layouts while preserving backwards compatibility.
+
+The work would include updating command options and project templates, testing the generated projects, and documenting the supported layouts. Particular attention should be given to the experience of beginners and consistency with existing Django tooling.
+
+The expected outcome is a tested and documented implementation of DEP 15, with examples explaining how to create and develop projects using the new interface.
+
+References:
+ * [https://github.com/django/deps/blob/main/accepted/0015-extended-startproject.rst DEP 15: Improved startproject interface]
+
 
 == [PLACEHOLDER] Project name ==