Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<p>This project aims to improve backend test coverage to 100%, and then migrate the backend codebase to be simultaneously compatible with both Python 2 and Python 3, while putting measures in place (like lint checks) to ensure that the backend code always remains compatible with both python 2 and python 3, regardless of subsequent developer changes. The reason these two projects are linked is because one prerequisite for a safe migration is to have full test coverage, so it's important to make sure that the backend coverage is 100% before migrating.The project would then make sure that all libraries Oppia uses are compatible with python 3. This project would also standardize all scripts in the codebase to be written in Python (currently, there is a mixture of bash and Python being used). The project would end with creating a small list of remaining steps that need to be taken for a final migration to python 3 (once a solution is found for the GAE dependency issues).</p>
<h5>End-to-End Testing Support</h5> <p>Oppia Android's current testing corpus includes unit tests using the Robolectric testing framework & integration tests using the Espresso testing framework (to ensure that the app operates as expected in a real Android environment). The current tests have a few limitations: they do not correctly facilitate cross-activity navigation flows which actual users will be triggering, and they do not verify that the app can interact with Oppia's backend correctly.</p> <p>To prepare for the global launch of the app, we need end-to-end tests that:</p> <ul> <li>Verify that the app works as a user would expect by playing through select critical user journeys</li> <li>Verify that the app operates as expected when interacting with a local developer instance of the Oppia backend server</li> </ul> <p>We expect that the tests will be written using UiAutomator & are set up for interacting with a local development server (see <a href="https://developer.android.com/studio/run/emulator-networking.html" target="_blank">relevant documentation</a>).</p> <p>Note that this project requires running Linux with virtualization support (in order to run an Android emulator). You will need to make sure your computer supports <a href="https://help.ubuntu.com/community/KVM/Installation" target="_blank">KVM</a> and is running Linux.</p>
This project focuses on redesigning the Oppia Topic Page to make it more intuitive and easier for learners to navigate. Currently, lessons are presented in a story-centric layout, while practice and revision content are separated into different tabs, which can cause learners to miss important activities and struggle to decide what to do next. The redesign introduces a unified interface where lessons, practice, and revision content are combined into a single continuous flow. Learners will see a structured, scrollable sequence of lesson and practice cards with clear progress indicators and actions such as start, resume, and review. It also improves how language options are displayed and selected directly on the Topic Page.
The Angular team plans to halt Protractor development at the end of 2022. The aim of this project is to set up the WebdriverIO with Github Actions, and complete the migration of the existing e2e tests to WebdriverIO. Also, document the usage of this new tool.
The Platform Parameters Dashboard project aims to enhance Oppia Android's developer options by introducing a user interface for managing platform parameters and feature flags. This dashboard will enable developers to dynamically view, override, and reset parameter values, facilitating real-time feature flag toggling without modifying source code. The implementation includes persistent storage of overrides, force synchronization with the Oppia Web backend, and comprehensive unit testing to ensure reliability. This feature will significantly improve debugging capabilities and streamline testing of various app configurations.
<p>This project aims to write frontend tests to fully cover each service, directive, and components in order to ensure that the quality of code throughout the codebase is maintained saving time for developers and providing a better, bug-free experience to the user.</p>
The aim of the project is to make it possible for teachers, tutors, and parents to support students who are using Oppia to learn. To solve this we are therefore planning to introduce Learner Groups, a feature which allows facilitators to provide recommendations and goals to help guide learners, and which allows learners to optionally share their progress so that facilitators can provide them with additional support. Specifically, facilitators should be able to create learner groups and invite learners to join them, and learners should be able to sign up for these groups. Facilitators should be able to monitor the progress of learners in their learning group and identify opportunities to help them.
<p>This proposal outlines the steps that I plan to take in order to enhance the customization of the Sessions feature. It explores a possible approach in implementing a feature that would allow the Feedback Session Creator to specify which Feedback Giver should give feedback to which Feedback Recipient on a per-question basis.</p>
Learners are currently recognized for progress at the individual lesson (exploration) level, but there is no structured way to celebrate or assess their understanding across multiple lessons. This limits motivation and fails to capture long-term learning achievements. To address this, the project introduces multi-lesson assessments that evaluate a learner's mastery of a group of related skills. Learners will be able to take these assessments at any time to measure their overall progress. Upon completion, they will receive a passing score page that can be showcase their achievement, helping to boost motivation and engagement. This system also lays the foundation for future enhancements such as certificate generation. Deliverables: Milestone 1: Assessment Creation & Management (Lessons Team) Frontend interface for creating, editing, viewing, and deleting certificate assessment offerings Validation mechanisms to prevent invalid configurations (e.g., insufficient questions per skill, missing descriptions) User feedback system for successful or failed save actions Backend infrastructure to store and manage assessment offerings Milestone 2: Learner Assessment Experience Frontend interface for learners to discover, attempt, and view assessment results Display of assessment attempt history for learners Backend systems for generating assessments dynamically Storage and management of learner responses and assessment results
The current onboarding workflow that the Oppia Android app offers is not intuitive enough. Users get confused or spend more time than necessary figuring out the features and how to navigate in the app due to lack of a better onboarding workflow. Sometimes users do not use a feature available to them that can ease their learning journeys due to lack of information. To ensure first time users have the best experience possible and to create an onboarding experience that is: Engaging but not time-consuming Educational but not text-heavy Interactive but not complicated Does not take too much time or clicks, especially if it is not interactive Does not add unnecessary visual or cognitive complexity Easily dismissible at all parts of the experience The app should show the onboarding flow the first time the user experiences whichever screen contains the interactive elements that should be explained. Each of these experiences may lead to multiple parts of the UI being highlighted, and should follow a predefined linear flow. There should be an option to cancel out of the flow, and the app should not show it again if the flow is either canceled or completed. Users should be able to access the onboarding flow if they cancel accidentally or forget something and want to go over it again.
<p>This is a TEAMMATES project proposal designing solutions for increasing the coverage of Java code and implementing Recycle Bin feature. The detailed designs are shown in steps inside the proposal.</p>
<p>This project aims at implementing two new interactions- <em>Number with Units</em> and <em>Drag and Drop Sorting</em> interactions. It will create a new learner experience at Oppia in the form of interactions inside the explorations and will aim at improving the learner's skills.</p>
<p>Oppia uses a bot to interact with developers when issues and pull requests are made. This Project aims at improving the functionalities of the bot, and moving some of the functionalities to use GitHub actions.</p>
<p>The project aims to provide a hassle-free solution to the process of enrolling the student in a course by the instructor and provide end-users with a spreadsheet-like experience. Improving the overall UI by implementing a spreadsheet like an interface for adding students in a particular course. The features that will be covered are -</p> <ul> <li>Add a new entry of data in the existing record.</li> <li>Modify any existing entry of students present in the data file.</li> <li>Delete an entry from the data input.</li> <li>Search for any existing entry present in the record.</li> </ul>
<p>A lot of parents tend to buy their kids tablet devices to help them learn new things through educational apps. Oppia is one of them, but it doesn't support tablet designs yet. And this project meets this problem.<br> Supporting tablet interfaces for the Oppia android application will give the users a better experience.</p>
<p>This project aims to introduce frontend routing in oppia using the angular router. This will replace the current backend routing system which uses more resources on both server and the client. After the completion of this project, users will be able to experience quick page changes and a better user experience overall. This project also involves migration from webpack to angular cli. Migration to angular cli will improve the overall development experience with its simplicity and code generation. The new developers starting up with oppia will find the codebase much easier to understand.</p>
<p>Oppia brings forth a platform to conduct comprehensive courses in the form of classrooms. A classroom contains many different topics in it. At present, there is no way for a learner to track their progress in different classrooms. This project aims to solve this and also incorporate planning and recommendation of topics, subtopics and stories to the learners.</p>
<p>This project aims to add three new math-based interactions. They will replace the current math interaction which is buggy and provides only one rule to detect learner answers. The new interactions will solve all the issues that the current interaction has. They will also provide a more versatile rule-set to detect a variety of learner answers. This will allow the creators to provide relevant feedback for the different kinds of answers that a learner can give. With this project, I aim to make the math experience of learners and creators in Oppia as smooth and fruitful as possible.</p>
<p>One key part in ensuring a development team reaches optimal efficiency is by ensuring there are reasonable checks in place to avoid regressing previous fixes, reducing trivial verification during code reviews, and ensuring that team members are utilizing best practices. Oppia-Android already has the static analysis tools present, but there are still numerous essential static analysis checks which the project currently lacks. The default behavior of these linting tools is not enough to meet all the best practices. This project aims to add all those essential static analysis checks which the project currently lacks so that the development team reaches optimal efficiency</p>
<p>This Project aims to help the developers in the Oppia Android team build features, solve issues and commit them into the develop branch without affecting the releasable code. In other words, with the help of these parameters, developers will be able to keep their code up-to-date with the develop branch even if the feature that they are working on isn't completed yet and shouldn't get merged into the release-ready code. These parameters will also help us have more granular control over different parts of the codebase. We will have a medium to tweak the App behaviour remotely without the need for a new release.</p>
<p>This proposal aims to add a new Skills construct at a global level that would replace the existing refresher explorations method that is employed for specific answer groups in questions. Along with this, pretests can also be added to explorations testing particular skills. For this, a skill editor is created for skill creation. The questions for the skills will be from the common Questions construct in the back end. In the future, collections are to be removed and replaced by topics and stories, and hence this project lays the foundation for that also by creating a topic and story editor (and the backend constructs for the same) as well as integrating skills with those.</p>
<p>As part of this project, I want to add support for more variety of formats both for downloading data and for importing data into Teammates. Also, I will work on features, which give more granular control for reports customising.</p>
The aim of this project is to provide two enhancements to the exploration editor page (for creating lessons) for lesson creators: (a) Development of a new "Git-Blame" like feature allowing users to see and navigate through the history of changes to a specific state card of an exploration. (b) Modification in the existing "version-comparison feature" allowing users to see the changes in the metadata properties of an exploration such as title, category etc., while comparing two versions of an exploration. The proposal contains details of calculation of the data related to the history of changes with the help of a beam job. It also contains details about unit tests and end-to-end tests used for testing the correctness of the changes.
Currently, the study guides are made of a single long monolithic content field which makes it hard for the learners to focus and difficult for the translators to translate. Also, worked examples can only be added to skills. This project aims to restructure the study guides to have multiple short sections and make their translations follow the pattern of other entities in the codebase. It also aims to create a WorkedExample Rich Text Editor component for the Skill and Subtopic Editor Pages.