poorvith-mp · Sep 19, 2026
diff --git a/Contributing-code-to-Oppia.md b/Contributing-code-to-Oppia.md
@@ -89,16 +89,16 @@ As a new contributor, if you run into any problems along the way, we're here to
 
 You can also browse good first issues for each of the core Oppia Web teams to find something you'd enjoy working on! Please only choose issues that have **not yet** been assigned, unless the issue is a "checkbox issue" with multiple claimable parts. Here are the project boards for the different teams:
 
-- Learner and Creator Experience (LaCE): https://github.com/orgs/oppia/projects/3/views/10, typically frontend or full-stack
+- LEAP Team (Learners, Educators, Allies, and Parents): https://github.com/orgs/oppia/projects/3/views/10, typically frontend or full-stack
 - Developer Workflow: https://github.com/orgs/oppia/projects/8/views/10, typically backend or frontend
-- Contributor Dashboard: https://github.com/orgs/oppia/projects/18/views/14, typically frontend or full-stack
+- CORE Team (Creators, Operations, Reviewers and Editors): https://github.com/orgs/oppia/projects/18/views/14, typically frontend or full-stack
 
 ### How to tackle good first issues
 
 When you've found a good first issue you'd like to tackle, please investigate it first to understand why the issue is happening. Here are some things you should do:
 
 - Read the entire discussion thread to understand what has been tried so far.
-- Try to reproduce the issue on your local dev server. (For Contributor Dashboard issues, the [[Contributor Dashboard onboarding guide|Contributor-dashboard]] has some useful setup information. For Learner and Creator Experience related issues, you can refer to the [[LaCE onboarding guide|LaCE-onboarding-guide]].)
+- Try to reproduce the issue on your local dev server. (For CORE Team issues, the [[Contributor Dashboard onboarding guide|Contributor-dashboard]] has some useful setup information. For LEAP Team related issues, you can refer to the [[LEAP onboarding guide|LaCE-onboarding-guide]].)
 - Figure out why the problem is happening, and [find the relevant code in the Oppia repository to change|Find-the-right-code-to-change]. If you have trouble with this, feel free to ask on [GitHub Discussion](https://github.com/oppia/oppia/discussions) and explain what you've tried doing so far.
 - Try and get a fix working on your local dev server. You will need to do this in order to claim the issue (see below).
 

diff --git a/Google-Summer-of-Code-2020.md b/Google-Summer-of-Code-2020.md
@@ -399,7 +399,7 @@ There are several serious issues with current saving/migration workflows in the
 
 The aim of this project is to fix any three of these issues.
 
-**Team**: Learner and Creator Experience
+**Team**: LEAP Team (Learners, Educators, Allies, and Parents)
 
 **Potential Mentors**: @seanlip (primary), @kevintab95, @aks681
 
@@ -421,7 +421,7 @@ Your proposal should include clear explanations for how you plan to solve each o
 
 This project aims to introduce SVG rendering for all LaTeX expressions in explorations, so that MathJax can be removed as a dependency from the learner pages (which has the nice side effect of making the explorations load faster).
 
-**Team**: Learner and Creator Experience
+**Team**: LEAP Team (Learners, Educators, Allies, and Parents)
 
 **Potential Mentors**: @kevintab95 (primary), @aks681
 
@@ -472,7 +472,7 @@ Recently there was a concern raised with the workflow for uploading files. The c
 
 The aim of this project is to introduce an SVG diagram editor in the rich-text editor (RTE). Creators can use this to create custom diagrams for their lessons in the browser itself. The images produced would then be stored as SVGs for use in the lesson.
 
-**Team**: Learner and Creator Experience
+**Team**: LEAP Team (Learners, Educators, Allies, and Parents)
 
 **Potential Mentors**: @kevintab95 (primary), @aks681
 
@@ -500,7 +500,7 @@ Currently, the only way for a user to save their progress in an exploration is t
 
 This project also aims to add functionality in the corresponding user's profile page to support the upgrading of "lightweight accounts" into "full accounts" later on, if the user wants to link a google account to it and gain, e.g. editing privileges.
 
-**Team**: Learner and Creator Experience
+**Team**: LEAP Team (Learners, Educators, Allies, and Parents)
 
 **Potential Mentors**: @aks681 (primary), @seanlip
 
@@ -593,7 +593,7 @@ A few things should be considered while writing the design doc:
 The aim of this project is to redesign the topic, exploration, story and skill editor pages so they are more visually appealing and work better on mobile, while retaining all of their features. Some initial mocks that we created visualizing these changes can be found here ([desktop](https://xd.adobe.com/view/3940de63-c416-4008-4b32-a73dc43fd7a1-4f71/), [mobile](
 https://xd.adobe.com/view/84eb3b8d-3d19-4971-7e79-9ff756b25c83-f2da/grid)); please note that these mocks will be updated over time as we finalize the design. (Feel free to suggest changes to the mocks if you think that would enhance the creator experience, or ask any questions on the oppia-gsoc-discuss@ mailing list.)
 
-**Team**: Learner and Creator Experience
+**Team**: LEAP Team (Learners, Educators, Allies, and Parents)
 
 **Potential Mentors**: @aks681 (primary), @kevintab95
 
@@ -677,7 +677,7 @@ This project aims at improving the frontend test coverage of controllers and dir
 
 Ensure that the entire Oppia website is fully accessible to screen readers (i.e., all pages should score 100% on the Chrome browser’s inbuilt Accessibility audit tool), and that automated tests are put in place to ensure this is the case going forward.
 
-**Team**: Learner and Creator Experience
+**Team**: LEAP Team (Learners, Educators, Allies, and Parents)
 
 **Potential Mentors**: @kevintab95 (primary), @aks681
 

diff --git a/Google-Summer-of-Code-2021.md b/Google-Summer-of-Code-2021.md
@@ -13,7 +13,7 @@
     -   [Developer Experience Team](#developer-experience)
     -   [Data and Stability Team](#data-and-stability-team)
     -   [Automated QA Team](#automated-qa-team)
-    -   [Learner and Creator Experience Team](#learner-and-creator-experience-team)
+    -   [LEAP Team (Learners, Educators, Allies, and Parents)](#leap-team-learners-educators-allies-and-parents)
     -   [Contributor Experience Team](#contributor-experience-team)
     -   [Android Team](#android-team)
     -   [Oppiabot Team](#oppiabot-team)
@@ -592,7 +592,7 @@ We are looking for 1-3 students to work on this project. Each student will work
 
 ---
 
-## Learner and Creator Experience team
+## LEAP Team (Learners, Educators, Allies, and Parents)
 
 ### Generalised migration flow for all models using JsonProperty fields
 

diff --git a/Google-Summer-of-Code-2022.md b/Google-Summer-of-Code-2022.md
@@ -11,8 +11,8 @@
 - [Selection Criteria](#selection-criteria)
 - [Communication](#communication)
 - [Oppia's Project Ideas List](#oppias-project-ideas-list)
-  - [Learner and Creator Experience (LaCE) team](#learner-and-creator-experience-lace-team-1)
-  - [Contributor Dashboard team](#contributor-dashboard-team-1)
+  - [LEAP Team (Learners, Educators, Allies, and Parents)](#leap-team-learners-educators-allies-and-parents-1)
+  - [CORE Team (Creators, Operations, Reviewers and Editors)](#core-team-creators-operations-reviewers-and-editors-1)
   - [Angular team](#angular-team-1)
   - [Backend team](#backend-team-1)
   - [Developer workflow team](#developer-workflow-team-1)
@@ -296,7 +296,7 @@ The following is a list of Oppia's 2022 GSoC project ideas. You are welcome to c
 
 Please note that the list of project ideas below is not set in stone: more projects may be added later, and some project descriptions may also change a bit, so check back regularly. In addition, the mentor assignments listed below are provisional, and may change depending on which proposals are eventually accepted.
 
-### Learner and Creator Experience (LaCE) team
+### LEAP Team (Learners, Educators, Allies, and Parents)
 
 1.1. [Learner diagnostic tests](#11-learner-diagnostic-tests)
 
@@ -316,7 +316,7 @@ Please note that the list of project ideas below is not set in stone: more proje
 
 1.9. [Onboarding improvements](#19-onboarding-improvements)
 
-### Contributor Dashboard team
+### CORE Team (Creators, Operations, Reviewers and Editors)
 
 2.1. [Contributor recognition infrastructure](#21-contributor-recognition-infrastructure)
 
@@ -353,7 +353,7 @@ Please note that the list of project ideas below is not set in stone: more proje
 6.3. [Accessibility improvements](#63-accessibility-improvements)
 
 
-## Learner and Creator Experience (LaCE) team
+## LEAP Team (Learners, Educators, Allies, and Parents)
 
 ### 1.1. Learner Diagnostic Tests
 
@@ -779,7 +779,7 @@ This project will involve two major parts:
 ---
 
 
-## Contributor Dashboard Team
+## CORE Team (Creators, Operations, Reviewers and Editors)
 
 ### 2.1. Contributor Recognition Infrastructure
 

diff --git a/Google-Summer-of-Code-2023.md b/Google-Summer-of-Code-2023.md
@@ -104,7 +104,7 @@ A: Definitely not! Here are the [selection criteria](#selection-criteria) we use
 **Q: What are the minimum number of PRs that one should have?**
 
 A: You should have at least 2 PRs merged, but they don't need to be large. Beyond that, remember that quality is more important than quantity. It is better to submit a non-trivial PR rather than a one-line wording change. Start with starter issues, then move ahead with prioritized issues from the team that is offering the project you are interested in.
-Here are the boards of the respective teams: [LaCE Quality](https://github.com/orgs/oppia/projects/3/views/8), [Developer Workflow](https://github.com/orgs/oppia/projects/8/views/11), [Contributor Experience](https://github.com/orgs/oppia/projects/18/views/4).
+Here are the boards of the respective teams: [LEAP Quality](https://github.com/orgs/oppia/projects/3/views/8), [Developer Workflow](https://github.com/orgs/oppia/projects/8/views/11), [CORE](https://github.com/orgs/oppia/projects/18/views/4).
 
 **Q: What is the total number of contributors that will be accepted?**
 
@@ -287,7 +287,7 @@ The following is a list of Oppia's 2023 GSoC project ideas. You are welcome to c
 
 Please note that the list of project ideas below is not set in stone: more projects may be added later, and some project descriptions may also change a bit, so check back regularly. In addition, the mentor assignments listed below are provisional, and may change depending on which proposals are eventually accepted.
 
-### Learner and Creator Experience (LaCE) team
+### LEAP Team (Learners, Educators, Allies, and Parents)
 
 1.1. [Implementing the “Needs Guiding Responses” section of the lesson analytics dashboard](#11-implementing-the-needs-guiding-responses-section-of-the-lesson-analytics-dashboard)
 
@@ -303,7 +303,7 @@ Please note that the list of project ideas below is not set in stone: more proje
 
 1.7 [User feedback reporting UI on Web](#17-user-feedback-reporting-ui-on-web)
 
-### Contributor Dashboard team
+### CORE Team (Creators, Operations, Reviewers and Editors)
 
 2.1. [Contributor Dashboard Admin Stats Table](#21-contributor-dashboard-admin-stats-table)
 
@@ -327,7 +327,7 @@ Please note that the list of project ideas below is not set in stone: more proje
 
 4.5. [Normalize Usage of Feature Flags](#45-normalize-usage-of-feature-flags)
 
-## Learner and Creator Experience (LaCE) team
+## LEAP Team (Learners, Educators, Allies, and Parents)
 
 ### 1.1. Implementing the “needs guiding responses” section of the lesson analytics dashboard
 
@@ -625,7 +625,7 @@ To prevent bots from spamming the feedback channel use [Google reCAPTCHA](https:
 
 **Useful resources:**
 
-## Contributor Dashboard team
+## CORE Team (Creators, Operations, Reviewers and Editors)
 
 ### 2.1. Contributor Dashboard Admin Stats Table
 

diff --git a/Google-Summer-of-Code-2024.md b/Google-Summer-of-Code-2024.md
@@ -107,7 +107,7 @@ A: Definitely not! Here are the [selection criteria](#selection-criteria) we use
 
 **Q: What are the minimum number of PRs that one should have?**
 
-A: You should have at least 2 PRs merged, but they don't need to be large. Beyond that, remember that quality is more important than quantity. It is better to submit a non-trivial PR that tackles an important issue rather than a one-line wording change. Start with starter issues, then consider focusing on issues labelled "high priority" and priority" from the team that is offering the project you are interested in. You can see a list of these issues on the respective teams' project boards: [LaCE](https://github.com/orgs/oppia/projects/3/views/8), [Dev Workflow](https://github.com/orgs/oppia/projects/8/views/11), [Contributor Dashboard](https://github.com/orgs/oppia/projects/18/views/4), [Android CLaM](https://github.com/orgs/oppia/projects/4/views/3), [Android Dev Workflow](https://github.com/orgs/oppia/projects/10/views/1).
+A: You should have at least 2 PRs merged, but they don't need to be large. Beyond that, remember that quality is more important than quantity. It is better to submit a non-trivial PR that tackles an important issue rather than a one-line wording change. Start with starter issues, then consider focusing on issues labelled "high priority" and priority" from the team that is offering the project you are interested in. You can see a list of these issues on the respective teams' project boards: [LEAP](https://github.com/orgs/oppia/projects/3/views/8), [Dev Workflow](https://github.com/orgs/oppia/projects/8/views/11), [CORE](https://github.com/orgs/oppia/projects/18/views/4), [Android CLaM](https://github.com/orgs/oppia/projects/4/views/3), [Android Dev Workflow](https://github.com/orgs/oppia/projects/10/views/1).
 
 **Q: What is the total number of contributors that will be accepted?**
 
@@ -165,7 +165,7 @@ In order to ensure a well-rounded engineering experience, GSoC contributors will
 - Read and understand parts of the codebase related to their project
 - Receive code reviews for all code they write for their project
 - Write automated tests for their projects
-- Meet regularly with other contributors on their Oppia development team (LaCE, Contributor Dashboard, Dev Workflow, Android)
+- Meet regularly with other contributors on their Oppia development team (LEAP, CORE, Dev Workflow, Android)
 - Meet 1:1 with their mentors regularly to get developmental feedback
 - Give presentations and demos of their projects
 - Participate in release testing and documentation initiatives
@@ -292,7 +292,7 @@ The following is a list of Oppia's 2024 GSoC project ideas. You are welcome to c
 
 Please note that the list of project ideas below is not set in stone: more projects may be added later, and some project descriptions may also change a bit, so check back regularly. In addition, the mentor assignments listed below are provisional, and may change depending on which proposals are eventually accepted.
 
-### Learner and Creator Experience (LaCE) team
+### LEAP Team (Learners, Educators, Allies, and Parents)
 
 1.1. [Infrastructure and navigation for multiple classrooms](#11-infrastructure-and-navigation-for-multiple-classrooms)
 
@@ -306,7 +306,7 @@ Please note that the list of project ideas below is not set in stone: more proje
 
 1.6. [Improvements to the exploration editor page](#16-improvements-to-the-exploration-editor-page)
 
-### Contributor Dashboard team
+### CORE Team (Creators, Operations, Reviewers and Editors)
 
 2.1. [Show AI-powered and cached translation suggestions to translation submitters](#21-show-ai-powered-and-cached-translation-suggestions-to-translation-submitters)
 
@@ -325,7 +325,7 @@ Please note that the list of project ideas below is not set in stone: more proje
 4.2. [Multiple classrooms support](#42-multiple-classrooms-support)
 
 
-## Learner and Creator Experience (LaCE) team
+## LEAP Team (Learners, Educators, Allies, and Parents)
 
 ### 1.1. Infrastructure and navigation for multiple classrooms
 
@@ -803,7 +803,7 @@ For (b):
 </details>
 
 
-## Contributor Dashboard (CD) team
+## CORE Team (Creators, Operations, Reviewers and Editors)
 
 ### 2.1. Show AI-powered and cached translation suggestions to translation submitters