From ea807c68a95bbdcc0e1fa27affc0e43a26013ca2 Mon Sep 17 00:00:00 2001 From: Hasitha Kaushan <41409951+chris7716@users.noreply.github.com> Date: Thu, 19 Mar 2026 21:58:57 +0530 Subject: [PATCH 1/3] Update trending projects --- Google-Summer-of-Code-2026.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Google-Summer-of-Code-2026.md b/Google-Summer-of-Code-2026.md index 7ac9b35d..ee69b855 100644 --- a/Google-Summer-of-Code-2026.md +++ b/Google-Summer-of-Code-2026.md @@ -580,6 +580,10 @@ Milestone 2: ### 1.3. Re-design the topic page +> [!IMPORTANT] +> This is a popular project idea. +> Multiple applicants are interested in this project. + **Project Description:** Based on user feedback, on the current topic page, users often overlook the Practice and Revision tabs completely. Additionally, the functionality in those tabs is not correlated with the available lessons, making it unclear to learners when they should review or practice those skills. The aim of this project is to update the design of the topic page to present a more integrated view of the lessons, practice sessions, and links to revision cards (subtopic pages), so that learners can practice the skills they learned in the relevant lesson. Additionally, it is disappointing for learners to find that the languages that they would want to use for translations and voiceovers are missing only after they start the lesson, so the new design incorporates these selections within the topic page itself and follows the overall site language as a default. @@ -1038,6 +1042,10 @@ Milestone 2: ### 3.2. Consolidate entity migration jobs +> [!IMPORTANT] +> This is a popular project idea. +> Multiple applicants are interested in this project. + **Project Description:** The Oppia codebase includes several different versioned entities which store learning material: explorations, skills, stories, subtopic pages, questions, topics, and collections. The infrastructure to maintain each of these versioned entities has been developed separately, and is a bit patchy (for example, migrations of old snapshots have not been implemented for some of the entities). This is making it difficult to remove some of the old version upgrade functions in the codebase which are no longer needed. @@ -1151,6 +1159,10 @@ In addition to your implementation approach, please also: ### 3.3. Standardize and validate domain objects and storage models +> [!IMPORTANT] +> This is a popular project idea. +> Multiple applicants are interested in this project. + **Project Description:** Oppia's production data is organized using [NDB storage models](https://github.com/oppia/oppia/wiki/Storage-models#storage-model-concepts), which in simple terms can be thought of as objects having different properties. For instance, data related to a user can be stored in a UserSettingsModel with properties like username, user ID, etc. From b8b9cfe3cf90687a4179bdacff3eb10e077f63c0 Mon Sep 17 00:00:00 2001 From: Hasitha Kaushan <41409951+chris7716@users.noreply.github.com> Date: Thu, 19 Mar 2026 22:14:51 +0530 Subject: [PATCH 2/3] Remove incorrect popular notes --- Google-Summer-of-Code-2026.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/Google-Summer-of-Code-2026.md b/Google-Summer-of-Code-2026.md index ee69b855..776f541e 100644 --- a/Google-Summer-of-Code-2026.md +++ b/Google-Summer-of-Code-2026.md @@ -823,10 +823,6 @@ Milestone 2: ### 2.2. Extend translation infrastructure to exploration metadata and skills -> [!IMPORTANT] -> This is a popular project idea. -> Multiple applicants are interested in this project. - **Project Description:** Currently, we have two main mechanisms for translating content at Oppia: translatewiki and the contributor dashboard. Translatewiki handles content that is not user-generated, for example the text on the homepage at oppia.org. The goal of this project is to extend the contributor dashboard to handle other kinds of user-generated content in our curated curriculum, specifically the following: - exploration metadata (e.g. titles and tags) @@ -1042,10 +1038,6 @@ Milestone 2: ### 3.2. Consolidate entity migration jobs -> [!IMPORTANT] -> This is a popular project idea. -> Multiple applicants are interested in this project. - **Project Description:** The Oppia codebase includes several different versioned entities which store learning material: explorations, skills, stories, subtopic pages, questions, topics, and collections. The infrastructure to maintain each of these versioned entities has been developed separately, and is a bit patchy (for example, migrations of old snapshots have not been implemented for some of the entities). This is making it difficult to remove some of the old version upgrade functions in the codebase which are no longer needed. @@ -1159,10 +1151,6 @@ In addition to your implementation approach, please also: ### 3.3. Standardize and validate domain objects and storage models -> [!IMPORTANT] -> This is a popular project idea. -> Multiple applicants are interested in this project. - **Project Description:** Oppia's production data is organized using [NDB storage models](https://github.com/oppia/oppia/wiki/Storage-models#storage-model-concepts), which in simple terms can be thought of as objects having different properties. For instance, data related to a user can be stored in a UserSettingsModel with properties like username, user ID, etc. From 6a42f065c5f8446e22103163d39605ca216206e4 Mon Sep 17 00:00:00 2001 From: Hasitha Kaushan <41409951+chris7716@users.noreply.github.com> Date: Thu, 19 Mar 2026 22:21:23 +0530 Subject: [PATCH 3/3] Remove incorrect popular notes --- Google-Summer-of-Code-2026.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/Google-Summer-of-Code-2026.md b/Google-Summer-of-Code-2026.md index 776f541e..4b97b2cc 100644 --- a/Google-Summer-of-Code-2026.md +++ b/Google-Summer-of-Code-2026.md @@ -365,10 +365,6 @@ If you need clarification on any of these ideas, feel free to open a thread in G ### 1.1. Web user feedback -> [!IMPORTANT] -> This is a popular project idea. -> Multiple applicants are interested in this project. - **Project Description:** Learners (and other relevant users) should have an easy way to report issues with the platform so that we can quickly catch and resolve these issues in a scalable manner. Links to PRD and mocks: