From 6d598201f9c5b1fd2fc32ef95c1557a7eacab96e Mon Sep 17 00:00:00 2001 From: U8N WXD Date: Thu, 26 Mar 2026 12:10:45 -0400 Subject: [PATCH] Mark popular GSoC 2026 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 4b97b2cc..8cbf0880 100644 --- a/Google-Summer-of-Code-2026.md +++ b/Google-Summer-of-Code-2026.md @@ -365,6 +365,10 @@ 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: @@ -819,6 +823,10 @@ 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) @@ -927,6 +935,10 @@ Milestone 2: ### 3.1. Improve acceptance test infrastructure +> [!IMPORTANT] +> This is a popular project idea. +> Multiple applicants are interested in this project. + **Project Description:** [Acceptance tests](https://github.com/oppia/oppia/wiki/Acceptance-Tests) are end-to-end tests organized by Critical User Journeys (CUJs). However, these tests are not as stable as we are expecting them to be. This project aims to improve the infrastructure of the acceptance tests to make it more stable and easy to manage. This includes but is not limited to migrating to Playwright from Puppeteer to reduce test flakiness, adding workflows to easily update snapshots, and documentation updates. Further, we expect using Playwright to reduce test flakiness, but some flakes will likely persist. This project includes fixing these persistent flakes. To limit the scope of this part of the project, you won't be expected to fix more than 10 persistent flakes (i.e. flakes that aren't fixed by the migration and weren't introduced by your changes). All of the acceptance test infrastructure issues can be found [here](https://github.com/orgs/oppia/projects/8/views/11?sliceBy[value]=[Project]+Fix+infrastructure+issues+in+the+acceptance+tests). **Tracking issues**: