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 extend the existing functionality("fesErrorMonitor") of the p5.js Friendly Error system and add a new feature that will allow the Friendly Error System to read the user's code, analyse it for mistakes and log a friendly message for the same.</p>
<p>Memory errors at the kernel of operation system are a kind of bugs that lead to grave consequences but are hard to detect. Debug and disclose of kernel memory corruptions often requires specially compiled kernel.</p> <p>I want to perform static verification of the Linux kernel latest release on memory errors by LDV project environment. I'll analyse results of static verification, provide patches to kernel for true errors and offer improvement to LDV staff to reduce false alarms.</p>
When DNS queries fail due to policy-based restrictions (e.g., BLOCKED, CENSORED, FILTERED), DNS resolvers can attach Extended DNS Error (EDE) codes along with structured JSON metadata in the response. This proposal aims to extend Chromium's DNS stack to parse and log Structured DNS Error (SDE) and Public DNS Error (PDE) content embedded in these EDE responses. The project involves extracting JSON metadata from the extra_text field for specific EDE and exposing them through the NetLog system. These improvements will provide more transparent diagnostics and support future UX enhancements. Deliverables: Full support for parsing SDE extra text and PDE, integration with Chromium's DNS resolution pipeline, NetLog exposure of parsed fields, and unit tests to ensure robust and secure behavior.
The Folksonomy Engine does not support intuitive property suggestions and reusable web components. In order to enhance usability and scalability, the system requires improved property suggestion mechanisms, more effective handling of nested values, and an easier-to-use interface for data contribution and analysis.\n \n To address the challenges in data contribution, consistency, and exploration, the project will develop new API features and create a reusable web interface. The proposed solution includes developing new API features and a reusable web interface. The main goal is to get as many contributors as possible to use this, making it easy and accessible for everyone to contribute.\n \n New API Features:\n - Suggestions based on popularity and categories\n - Adding User roles\n - Improved handling of nested property values\n - Adding moderation for bulk property, value management\n - Tools for exploring and merging values\n \n Improved Reusable JavaScript-based Web Interface:\n - For display and editing of data\n - Integrating folksonomy-editor to main project\n - Potential formalization of property definitions
This project bridges the gap between complex frameworks and basic, non-standard code. I will develop a modular, message-based flight software for the Open-Source CubeSat FlatSat Testbed using FreeRTOS. The goal is to create a 'sweet spot' firmware: accessible for students to learn, yet compliant with professional aerospace standards. By implementing a publish-subscribe 'Software Bus,' the system ensures that hardware drivers and mission logic are decoupled and interchangeable. This results in a scalable, flexible architecture that can evolve alongside the CubeSat hardware. Deliverables: Message Dispatcher: A thread-safe Software Bus for modular communication. Hardware HAL: Thread-safe STM32 drivers for the FlatSat sensor suite. Standards Core: PUS-compliant Telemetry, Telecommand, and Error Handling (FDIR). Testing: Unit testing and documentation of end result
This proposal targets the HSF 2026 idea Clad as a first class gradient engine in libtorch, a 350-hour project intended to make compiler-generated gradients available from LibTorch and, eventually, easier to reuse from the ROOT ecosystem. My goal is to build a practical and well-scoped integration path that allows a LibTorch C++ training loop to call Clad-generated derivative code for a small but meaningful subset of workloads. The primary implementation path is to wrap Clad-generated backward logic inside torch::autograd::Function, because the PyTorch C++ frontend explicitly supports custom autograd functions and presents them as the standard way to integrate optimized forward and backward code in extensions. If time permits and the API proves cleaner, I will also evaluate a custom-operator path based on the PyTorch C++ extension mechanisms. This proposal is intentionally scoped as a proof of concept, not as a general replacement for LibTorch autograd. A realistic first milestone is to differentiate selected training kernels or small model components written in C++, expose them to LibTorch, and measure where compiler-generated derivatives are correct, maintainable, and competitive. This produces a concrete result for mentors and also establishes a clear baseline for future work on broader operator coverage, deeper ROOT integration, or GPU support.
This project aims to modernize MetaCall's rs_loader by migrating it to the latest rustc compiler internals. The current implementation relies on outdated APIs, making it incompatible with newer Rust versions. The project will focus on updating compiler integration, replacing AST-based traversal with HIR-based extraction, and adapting to changes in rustc_driver and related components. The approach includes analyzing breaking changes, incrementally migrating core modules (lib.rs, middle.rs, ast.rs), and ensuring compatibility with modern Rust toolchains. Deliverables include a fully working rs_loader compatible with the latest rustc version, improved type and function extraction using HIR, and updated documentation for maintainability.
<p>Currently Oppia.org hosts its blog on a separate blogging site, "Medium". I would prefer to have the blogging interface directly on Oppia.org so that it is connected to the rest of the site. This will enable the content of the site to be on one platform altogether. The aim of this project is to add a “blog” dashboard hosted on Oppia.org, that enables its user to create and edit blogs on the website itself.</p>
<p>The project requires to build an architecture for validating args of handler class. After building the architecture, some of the handler class in the codebase should be updated so that they abide with the new architecture.</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
<p>The aim of the project is to improve the usability aspect of TEAMMATES. In particular, tweak the UIs to prevent regular users being overwhelmed with advance features. Also, improve the availability and accuracy of user help. This includes goals such as improving usability of UI, providing context-specific help, improving user guide, reducing brittleness of documentation to name a few.</p>
Oppia currently features a classroom page for Math lessons, which is prominently accessible via the home page, navigation bar, community library, and learner dashboard. Oppia also plans to create classrooms for other subjects. This proposal aims to facilitate the creation of new classrooms directly from the Oppia website. Curriculum Admins will be able to change the publication of a classroom and update all of its properties. These classrooms will then be made available to learners from the community library, the new classrooms page, splash page, and from the learner dashboard. This project also involves updating the topic and skill dashboard to support topic filtering by classroom name and showing classroom details in the topic editor and topic viewer.
<p>A lesson translation dashboard for oppia's audio translators. This dashboard will help audio translators to do translation in a much better way. Through this project a lot of new features will be added to the translation dashboard:</p> <ul> <li>Translation status of the entire exploration in the preferred language.</li> <li>Translation status of each state in the preferred language.</li> <li>Translation status of each component of the state (content/responses/hints/feedback).</li> <li>Audio recording.</li> <li>Bulk audio upload.</li> <li>Progress bar for the translation work.</li> </ul>
<p>This project will improve Oppias ability to support users with physical, visual, or hearing disabilities. It aims to fix any issue caught by audits and improve the accessibility of the site. For physically impaired users, it aims to implement new and more advanced keyboard navigation features based off of facebook's. To help the developer maintain this standard, this project will create automated tests to ensure that any future frontend changes will not lower Oppia’s accessibility score below an acceptable score.</p>
<p>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</p>
Oppia's Exploration Player has several issues affecting the learning experience. Learners struggle to distinguish between hints and solutions, and the audio player is hard to find on desktop and takes up too much space on mobile, reducing content visibility. Progress tracking is unclear, and navigation between lessons is difficult. On mobile, limited space and a cluttered UI make it challenging to focus on the content. This proposal aims to redesign the player for better clarity, usability, and efficiency, ensuring a smoother experience across all platforms.
<p>In this project i will be focusing on adding some more type of interactions which will result usage of android app along with them i will adding one more type to the backend of the project which is written in python and angular js</p>
<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>Why me?</p> <ul> <li>I already have multiple contributions to HubTurbo.</li> <li>I have experience building software alone and with others.</li> <li>Managed to maintain high academic achievement while also fulfilling previous 2 points.</li> </ul> <p>Purpose / Vision</p> <ul> <li>Improve general usability of HubTurbo.</li> <li>Make it easier for devs to account for usability.</li> </ul> <p>Feature categories</p> <ul> <li>Improving user's experience of finding features when needed.</li> <li>Improve user's experience learning about features.</li> <li>Improve user's experience using the feature.</li> <li>Track details of user experience for developer consideration.</li> </ul>
<p>Diagrams and figures aid in learning and understanding concepts better. Giving creators the ability to draw images for the lessons would allow flexibility and ensure that the concepts of the lessons are conveyed clearly without fading the core ideas. So I believe that the concept of adding a svg editor to the application would help the creators convey the lessons better.</p>
The goal of this project is to migrate the exploration editor page from angularJs to angular. Users will be able to experience faster page transitions and a better overall user experience after this project is completed. This project also involves switching from webpack to angular CLI, Because of its simplicity and features, migration to angular CLI will improve the entire development experience. After completion of the project, new programmers starting with oppia will be able to grasp the codebase easily.
<p>The aim of this project is to provide lesson creators a tool for visualizing how learners play through their explorations. In particular, it would be nice if the creator could see problematic playthroughs of the learners. These could be the playthroughs that lead learners to quit the lesson early, or submit multiple incorrect answers consecutively, or to repeatedly traverse a set of cards in a cyclic fashion.</p> <p>The playthrough identification is targeted at individual learners whereas the current statistical data aggregation provides the creator with bulk numbers recorded. Through this tool, the creators can effectively identify problematic areas in their lessons and address them appropriately.</p>
<p>Increase unit tests coverage of AngularJS and Angular 2+ frontend controllers and directives to 100%.</p>
<p>Proposal for "Creator Dashboard" project</p>