GSoC 2026 Proposal Review | Enhance Multi-Language Support (Anas Ayman) #6173
|
"Hi everyone! 👋 I am Anas, a CS student applying for GSoC 2026 Android track. Proposal Link: [ |
Replies: 1 comment 4 replies
|
Hi @AnasAyman13, thank you for your interest in contributing to Oppia via GSoC. Please look at our GSoC wiki for information on how to get started with GSoC at Oppia in 2026. Please also note that the contributer application deadline is on the 31st of March. |
|
Hi @adhiamboperes, thank you for the reminder! I have already gone through the GSoC wiki, followed the contribution guidelines, and submitted my application on the GSoC portal. I have also opened PR #6171 as a technical Proof-of-Concept for my proposal (demonstrating the languages.proto updates and Activity refactoring on Windows). I would highly appreciate it if you or any of the Android mentors could take a quick look at the PR or the attached proposal when you have a moment. Thanks again for your time! |
|
@AnasAyman13 I left a comment on #6172 with more specific information, but I want to also provide some additional feedback here. Your proposal needs to follow the Oppia GSoC project template and all of the instructions listed there, see: https://github.com/oppia/oppia/wiki/Google-Summer-of-Code-2026#gsoc-proposal-template. As I mentioned in my other reply, you're welcome to propose your own project but be aware that it's a bit of an uphill battle because there's substantially more complexity to navigate that we do for you for projects already on the ideas list, and there's no guarantee of a matched mentor (mentors also need to be interested in the projects). Finally, this project in particular doesn't quite fit, I think, because we already support the functionality that you're proposing to implement (or, rather, it doesn't seem that we actually need more than what we have supported in the app today--the privacy policy and terms of service activities are already always in English for their main texts as expected). |
|
Hi @BenHenning, thank you so much for the detailed feedback! Regarding the proposal, I completely understand. The 'English-only enforcement' was intended as a technical Proof-of-Concept to demonstrate my ability to navigate the complex codebase, modify Protos, and resolve Windows/Bazel build issues. Given your feedback, I will immediately pivot my proposal to focus on Project 4.1 (Support for Lesson Progress, Study Guides, and Worked Examples). I believe my recent experience with the Activity architecture and Proto updates directly aligns with the requirements of that project. I will update my draft following the official template and share it for review shortly. Thank you for guiding me in the right direction! |
|
Got it @AnasAyman13. Glad to help. One more thing you clarify: we require applicants to merge at least 2 PRs as part of their application for the organization, and we're generally looking at PRs that directly align with the required skills for the project being proposed. A proof-of-concept draft PR does provide some signal, but it doesn't cover all of the required skills of either 4.1 or 4.2, and it doesn't show that you can go through the code review and merge process. I just wanted to point out this specific part of the list of requirements. You may not have enough time to fully merge 2 PRs before the deadline, but I want to emphasize that showing you can both write code and iterate on it after receiving feedback gives us a lot of signal into what it will be like working together all summer, and that carries a lot of weight when we're considering applicants. Hope this helps. |
Hi @AnasAyman13, thank you for your interest in contributing to Oppia via GSoC. Please look at our GSoC wiki for information on how to get started with GSoC at Oppia in 2026. Please also note that the contributer application deadline is on the 31st of March.