Changes between Version 9 and Version 10 of SummerOfCode2022

Timestamp:

Feb 25, 2022, 1:56:17 AM (3 years ago)

Author:

Carlton Gibson

Comment:

Add estimates of projects sizes and difficulties.

SummerOfCode2022

@@ -140 +140 @@
 Carrying-on and extending that work would be a great addition. 
 
+(Hard project. 350hr project)
+
 == Window expressions improvements ==
 
 Add support for filtering against window expressions (see #28333), for `EXCLUDE` and currently not covered `RowRange()` cases (see #29850). 
+
+(Hard project. 350hr project)
 
 == Django Benchmarking ==
@@ -167 +171 @@
 Creating a test harness using (say) [https://locust.io Locust.io] would make a great project. 
 
+(Likely medium difficulty. Could be scoped as a 175hr or a 350hr project)
+
 == Typed Django ==
 
@@ -175 +181 @@
 If you're interesting in this, open a discussion on the django-stubs repo or [https://gitter.im/mypy-django/Lobby the project chat].
 
+(Likely Hard project. Could be scoped as a 175hr or a 350hr project)
 
 == Database-level Cascades == 
@@ -185 +192 @@
 Adjusting `DatabaseSchemaEditor.sql_create_fk()` to be able to use the native options is the beginning. 
 
+(Hard project. 350hr project)
 
 == Per field-instance lookups == 
@@ -193 +201 @@
 
 Implementing that would be a lovely addition to the ORM. 
+
+(Hard project. 350hr project)
 
 == Add rate-limiting to core == 
@@ -200 +210 @@
 
 Contrasting with the third-party [https://django-ratelimit.readthedocs.io/en/stable/index.html django-ratelimit] to determine what's the appropriate scope for what we'd want in the core framework would be important, and a good source of stretch-goals. 
+
+(Hard project. 350hr project)
 
 == Or Create Your Own ==
@@ -211 +223 @@
 needs to be both on Django itself here, and achievable in the timescale of
 GSoC.
+
+(Could be scoped as a 175hr or a 350hr project)
+