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>The projects aims at incorporating Firebase Analytics and Crashlytics into Oppia's Android application to send usage data to a central location while ensuring that no sensitive information leaves the phone. It also aims at offline storage of event and crash stats in case of network connectivity issues. The implementation of such features will lead to a constructive and insightful decision making process and therefore promise a better end-user experience.</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>
<p>Improve the performance and scalability of TEAMMATES.</p> <ol> <li>Migrate Storage component to Objectify API<ul> <li>Rewrite entire Storage layer to use Objectify instead of JDO</li> <li>Deploy change and divert small amount of live traffic to new version for testing</li> <li>Turn on Objectify global cache (uses memcached); do similar isolated testing</li> <li>Fix issues surfaced during live testing (if any), then fully deploy new version</li> </ul> </li> <li>Write performance profiling tests for Storage and Logic components<ul> <li>All methods in Storage and Logic API to be profiled for cost and performance</li> <li>Use remote API client for client-driven testing</li> <li>Use task queues for app-driven testing</li> <li>Results to be used as a benchmark when making changes to the architecture</li> </ul> </li> <li>Redesign schema<ul> <li>Determine entity groups based on GAE transaction limits and our usage</li> <li>Use conceptual relationships as much as possible while keeping within limits</li> <li>Plan for extensibility: should be able to support new features like LTI compliance without too much effort</li> </ul> </li> </ol>
<p>A feature to the lesson player that allows students to explain how they arrived at a (wrong) answer. The aim of this feature is to encourage reflection on the student's part, as well as provide (anonymized) information to creators about student misconceptions, so that the creator can improve Oppia’s feedback for future students.</p>
<p>Oppia's lessons can require between 15 minutes and an hour of time depending on a number of factors from learners: understanding of the material, literacy capabilities, and general focus. One potential behavior in the app is that we don't save the user's progress if they navigate away from an exploration (lesson) which, given how long lessons can take, is expected to be a frustrating experience. To mitigate this, we'd like to introduce support for a lightweight checkpointing system wherein users' saved state is fully retained if they navigate away from a lesson & back.</p>
<p>The project is about replacing the current pseudo Role based Access Control System of oppia and replace it with Action based Access Control System</p>
The app is currently limited to displaying a single list of basic numeracy topics. Together, these topics comprise what we call a 'classroom'. With this proposal, my aim is to introduce support for more than just mathematics topics by revising the core home screen & navigation flows to support topics grouped by their classroom. Future classrooms will include science, financial literacy, and more.
<p>The project enhances the current implementation of the comment feature.</p> <p>Features to consider:</p> <ol> <li>Ability for respondents to add comments for their own responses e.g. to add an explanatory comment when answering an MCQ question.</li> <li>Ability for instructors to add comments from more places. </li> <li>Possible extension: Ability to know if the comment/response was read by the student.</li> </ol>
<p>My project involves fixing UI issues across the entire TEAMMATES platform, including overhauling the instructor help page, allowing respondents to submit each question on a feedback session individually, providing more contextual help and other improvements. The goal is to make the TEAMMATES platform even more user-friendly and accessible.</p>
<p>This project enhances current comments feature being used in the application, by implementing features :-1) Allowing student to submit their explanation on particular feedback response.2) Allow instructors to add comments from more places.3) Fixing other miscellaneous issues related to comments feature</p>
'Helping learners when they get stuck' aims to implement numerous improvements to make the core learner experience more adaptive, effective and engaging. This project ensures that no learner ever feels stuck and can progress even when external assistance might not be available.
<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>In this proposal, I discuss my approach on improving the existing reporting platform with more data formats to download, with more visualizations and more statistics.</p>
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>The primary goal of this project is to engage the learners in a long term learning relationship with Oppia by providing them with their personal learning space - the 'Learner Dashboard'. The dashboard will keep track of the explorations and collections completed by learners, the explorations and collections that are currently in progress, the creators to whom the learner has subscribed to and the list of feedback threads which he/she needs to read or respond to. In addition, learners can also create their own curated list of explorations and collections which they may want to play later.</p> <p>The learner dashboard will help provide an enriching learning experience and will bridge the gap between learners and creators. It'll be at the heart of the learning process and help the learner learn faster. In addition, this project will create the foundation for implementing a rich set of features like recommending the right next courses for individual learners and many other such exciting possibilities. This project, I believe, would mark a major milestone in accomplishing Oppia's mission - 'to help anyone learn anything they want in an effective and enjoyable way'.</p>
<p>In this proposal, 3 features will be proposed. All proposed feature are based on the needs for user to key in the panel filter faster and easier.</p> <p>The first proposed feature is to provide a dropdown list of possible filter expression based on the partially input expression. This feature will help the user to recall label spelling and enter the filter expression faster. The second proposed feature is to have an interactive tutorial for first-time user. The tutorial will guide the user step-by-step on various syntax on writing the filter expression. The last proposed feature is to allow user to create filter expression by using a GUI wizard. The wizard will allow drag and drop of labels to create filter expression for issues.</p>
The objective of this project is to streamline the installation of Oppia's development server by utilizing Docker to containerize the application. Additionally, all GitHub Actions will be consolidated into a single build step that generates a cached docker image, speeding up the testing process on GitHub-hosted servers. By dividing the application into several Docker containers, users can enjoy a more seamless and efficient experience when setting up their development environment, removing the existing installation process that poses a significant barrier for new contributors.
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.
<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>
Currently, Oppia has a pre-push hook which runs frontend unit tests on all files and lacks any backend unit tests in the pre-push hook which can lead to a lack of response for developers until it reaches the Github CI. Furthermore backend unit tests take quite long and similarly End-to-End, lighthouse and acceptance tests on the Github CI are all ran regardless of the PR's changes; all of these problems lead to developer distress. This proposal seeks to solve these problems by running frontend unit tests only on changed files and adding backend unit tests in the pre-push hook, to run similarly on only changed files. It also seeks to reduce Github CI and pre-push hook runtimes by optimizing backend unit tests. Alongside this, this proposal will reduce Github CI usage by running End-to-End, lighthouse and acceptance tests on only PRs which need them.
<p>Adding new features to addressbook so that it can be more useful for CS2103T students morphing it for their own project.</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>
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>My project concentrates on adding more features to existing question types. These features are:</p> <ul> <li>Add weight feature for MCQ questions</li> <li>Add weight feature for MSQ questions</li> <li>Add weight feature for Rubric questions</li> <li>Add more statistics (Per Recipient Statistics, Weighted percentage) for MCQ, MSQ questions.</li> </ul>