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.
Onboarding new end users into a sophisticated system like Knative Eventing presents significant challenges, especially as it involves understanding not only the operational components but also a distinct architectural style - event driven architecture (EDA). These issues are also seen in the current documentation which is often too technical and not geared towards practical guidance. This project seeks to perform a thorough investigation into the barriers that prevent smooth user onboarding and sustained engagement. By identifying these obstacles and developing clearer, more actionable onboarding materials, we aim to enhance the ease of entry and ongoing use of Knative Eventing for all users. Expected Outcome: 1. Produce a detailed report based on user research that outlines the current onboarding experience for new users of Knative Eventing. This report will highlight key barriers and challenges in the documentation and setup process, and recommend actionable improvements to make the onboarding process more user-friendly and less technically daunting. 2. Implement the proposed changes within the Knative community by developing comprehensive onboarding materials and enhancing existing documentation to better support new users.
The goal of the project is to extend the low-cost DIY robot kit for educators, including the designs, tutorials, and basic use-case scenarios. All of the parts of the modular DIY robot kit are 3D-printable, and together with basic low-cost electronics and sensors are used to assemble the robot, for a successful operation. Extensive and simple guidelines of how to print and assemble the robot are to be provided, so that non-expert staff in robotics, electronics or IoT programming, will be able to follow them successfully. In addition, the Blockly graphical UI will be extended with configurable blocks that will allow the easy though fine-grained operation of the robot. This project will be developed in collaboration with Open Technologies Alliance (GFOSS), as it will be based on the previous GSoC projects of the applicants of 2019 and 2021. It will refine the robot assembly guidelines, manual for the installation of the software stack (which will be automated as much as possible in order to support the continuous integration of software updates), and will extend the stack both in terms of the front-end of Google Blockly and the back end code in order to facilitate the robot operation and programming.
pyGAM currently produces anti-conservative p-values for smooth terms due to several deviations from the statistical theory outlined in Wood (2013b). In particular, it assumes a simple chi-squared reference distribution, ignores effective degrees of freedom corrections, and does not properly handle penalization-induced rank deficiency. This project will correct the statistical inference pipeline in pyGAM by implementing five key fixes: (1) proper computation of effective degrees of freedom, (2) stable pseudoinverse truncation, (3) replacement of the chi-squared approximation with a weighted mixture using the Liu-Tang-Zhang method, (4) QR-based covariance handling, and (5) correct treatment of unknown-scale families. The result will be a refactored inference module that produces well-calibrated p-values, along with a comprehensive validation suite comparing type-I error and power against mgcv. Stretch goals include incorporating smoothing parameter uncertainty corrections and exploring REML-based smoothing. Deliverables include a refactored statistics() pipeline, extensive tests, and improved documentation.
<p>Very often even if an application has a robust backend, the user interface is often the factor that decides whether it will be taken up or not by the end user. Or in other words, apps definitely get points for being pretty. The Zulip mobile application can be regarded as a work-in-progress. I shall work the on the following areas and improve it so the application may move closer towards completion.</p> <ul> <li><p>Overhaul and rebuild several major elements of the interface to achieve a more even, symmetric and uniform look.</p> </li> <li><p>Adopt principles of Material Design for the application.</p> </li> <li><p>Fix many small but annoying issues such as broken alignment in some menus, ripple and other effects overflowing into other elements, non-standard icons, animation delays, asymmetric margins etc.</p> </li> <li><p>Improve support for different resolutions and pixel densities so nothing is out of place on a 18.5:9 or 18:9 display, or in landscape mode.</p> </li> <li><p>Add to the documentation and improve it where possible.</p> </li> </ul>
This project aims to improve the handling of transposed diffuse irradiance and optical loss modeling in the pvlib-python package. Currently, pvlib’s transposition models provide inconsistent output, with some providing only total sky diffuse radiation (e.g. isotropic), while others allow for outputting the isotropic, circumsolar, and horizon components. Due to this, the ModelChain workflow only allows users to define a single angle of incidence (AOI) model, and then applies the resulting incident angle modifier (IAM) to total irradiance, limiting physical accuracy. The proposed GSoC project will start by standardizing the outputs of diffuse transposition models already implemented in pvlib, introducing a consistent interface to return circumsolar, isotropic, and horizon components. Building on this, the project will extend ModelChain to support component-specific IAM calculations, enabling more accurate modeling of optical losses by distinguishing between direct and diffuse contributions. These enhancements will improve both the flexibility and accuracy of pvlib simulations while maintaining full backward compatibility. The project will include comprehensive testing and documentation to ensure reliability and ease of use.
GDB-UI currently supports only one user at a time because the backend shares a single global GDB controller across all requests. When two users debug simultaneously, the second session silently destroys the first with no error or warning. This proposal implements a three-phase solution. Phase 1 replaces the global controller with a thread-safe SessionManager that gives each user their own isolated GDB instance via a UUID session_id. A working implementation is already open as PR #131 with 15 passing tests, security fixes, and a live demo page. Phase 2 introduces WebSocket streaming with a per-session reader thread architecture so GDB output reaches the frontend in real time without blocking the server. Phase 3 moves each project into an isolated Docker container using the Docker SDK exec_start socket API for interactive GDB attachment, solving file descriptor exhaustion at the OS level. Deliverables: merged SessionManager with full test coverage, WebSocket streaming with reconnection handling, Docker sandbox with resource limits, security audit, and handover documentation.
SQLancer randomly generates test cases consisting of potentially hundreds or thousands of SQL statements. In order to efficiently identify bugs in these statements, automatic reduction is needed to systematically remove the bug inducing statements until a minimal bug-triggering test case is derived. To improve the efficiency and effectiveness of SQLancer for bug detection and resolution in various DBMSs, I propose to undertake the following tasks: 1. Implement delta-debugging algorithms for statement reduction in SQLancer to improve efficiency and speed. 2. Define parser-tree transforms to simplify SQL statements. Since SQL syntax varies among DBMSs, generic parser-tree transforms that can be applied across multiple DBMSs will be implemented, such as removing expression nodes or removing certain clauses from the statement. 3. Generalize statement reduction to additional DBMSs by adding bug reproducers to them. The deliverables for this project include: 1. A delta-debugging algorithm that can reduce the bug-inducing statement. 2. Generic parser-tree transforms that simplify SQL statements. 3. Support of statement reduction for more DBMSs.
This project focuses on improving the Ceph Dashboard by completing the migration from Bootstrap to the Carbon Design System and ensuring a consistent user experience across all components. Currently, the dashboard exists in a hybrid state with mixed UI frameworks, leading to inconsistencies, increased maintenance overhead, and a fragmented user experience. The proposed solution involves fully refactoring legacy UI components to Carbon, standardizing the frontend architecture using the lazy-loaded RoutedModule pattern, and replacing modal-based workflows with dedicated routed pages for better scalability and performance. Additionally, the project will address broken unit and end-to-end tests, expand test coverage for critical modules, and ensure long term stability through reliable CI validation. Key deliverables include a fully carbonized and consistent UI, improved application performance through modular routing and lazy loading, and a robust testing suite including unit and e2e tests covering previously untested areas. These improvements will enhance usability for end users, reduce technical debt, and make the codebase more maintainable and contributor-friendly.
<p>The development of the freely available, open-source, RTEMS, solved one of the biggest obstacles that beamline researchers used to face in buying commercial Real Time operating systems that used EPICS base software. However, with both EPICS and RTEMS gearing up for their latest stable releases, i.e, EPICS7 and RTEMS5 respectively, they should be made fully compatible to ensure continuous support in the newer versions. This project aims to solve this problem and create a vertically integrated BSP Build Set which will be able to create a bootable BSP image with EPICS7+RTEMS 5 that can run in a simulator. RTEMS provides RTEMS Source Builder which is a tool to build packages from source and adding packages like EPICS to the RSB as libraries is called vertical integration. This project will create build sets that stack library dependencies vertically to create a stack. The main goals of this project are to make progress for some low-barrier simulation approaches like qemu/i386, qemu/xilinx_zynq and powerpc/psim used by EPICS community and then later on move to real hardware systems.</p>
<p>GeneTech allow users to develop genetic logic circuits only by specifying a Boolean function. The tool first performs Boolean optimisation, followed by synthesis and technology mapping. Currently, a user can define the desired behavior in the standard Boolean notation. I would like to add the support for designing a circuit via drag and drop method on a design canvas. This functionality would allow users, specially electrical/electronic engineers, to design a genetic circuit by constructing the circuit schematic on a design canvas using drag-drop-wire approach. GeneTech will then transform the circuit schematic into the corresponding genetic circuit and represent it in the standard SBOL notation. The results produced by the current version of GeneTech do not include the DNA basepair encoding of circuit components. I would like to update the tool to be able to embed the DNA sequence of generated circuits in the SBOL file.</p> <p>Most of the code-base of GeneTech is currently a pre-compiled version of the Java code which adds additional overhead and dependencies. We would also like to convert the Java code to Python and reduce dependencies along the way</p>
This proposal aims to upgrade and expand existing open-source tutorials and examples to support the new unified Gemini SDKs for JavaScript/TypeScript and Python. My approach involves three key components: (i) Cookbook Migration: Migrate existing Python examples in the Gemini Cookbook to idiomatic JavaScript/TypeScript. I will ensure the code follows best practices in both languages and is thoroughly documented like the already existing cookbook examples. (ii) New Tutorials & End-to-End Examples: Develop fresh, comprehensive tutorials demonstrating a variety of Gemini use cases. Examples include building a chatbot, creating a text summarization tool, and generating images from text prompts. Each tutorial will include step-by-step instructions, code samples, and in-depth explanations of underlying Gemini concepts. Deliverables include: - A set of migrated and newly developed code examples in both Python and JavaScript/TypeScript. - Comprehensive, user-friendly tutorials and documentation that clearly explain the code and underlying concepts. - Updated examples for existing open-source libraries utilizing the Gemini SDK, with clear migration guides.
This project aims to design and implement a complete chat moderation and editing system for Jitsi Meet. Currently, Jitsi’s chat supports basic messaging but lacks important features such as message editing, deletion, moderation controls, and search, which are essential in modern communication platforms. The goal of this project is to introduce these missing capabilities using XMPP standards like XEP-0308 (message editing), XEP-0424 (message retraction), and XEP-0425 (moderation). The implementation will follow a structured approach, starting from the XMPP layer in lib-jitsi-meet and extending to the Redux and UI layers in jitsi-meet. Key features include message editing, message deletion, moderator-controlled actions, chat muting, user reporting, message search, and reply threading. Additionally, server-side enforcement using Prosody plugins will be explored to ensure reliable moderation. This project will improve user experience, provide better control in meetings, and bring Jitsi’s chat system closer to modern messaging standards while maintaining consistency with its existing architecture.
Agentic AI is commonly used to predict and resolve problems before they occur, requiring access to data in near real-time. However, traditional patterns for reacting to data changes come with major disadvantages, exacerbating the challenge of building resilient, near real-time distributed systems. These patterns include polling, which is simple to implement but has a fundamental tradeoff between minimizing load on data sources and minimizing data staleness. Change data capture (CDC) avoids the aforementioned issues, but requires teams to build and maintain custom infrastructure. Using Drasi’s ability to track derived entities (via Continuous Queries) and Dapr Agents’ out-of-the-box durability for agents and agentic workflows, this proposed integration would help developers build scalable, event-driven AI systems in products and internal platforms. To accomplish this, Drasi would need a new ”proxy” service that routes events to multiple publish-subscribe (pub/sub) topics. Dapr workflows and agents would consume from these topics via workflow decorator functions and agent middleware, supporting Drasi and providing the groundwork to integrate other backends.
<p>Object detection and recognition are central problems in computer vision literature and essential for a vision based library. Recent advances in Covolutional Neural Networks (CNN)s have made the detection have made the recognition problem tractable for large number of object categories that would have been very expensive with model based classification approaches. In this project I will implement state-of-art object recognition as well as object detection/localization technique for RoboComp library. The implementation will support both real images and rendered images from CAD model. The implementation will be based on CUDA library and allow user to train and test his models. Also, a caffe independent pure RoboComp based implementation for forward pass will be developed for a selected CNN. Another component based on open scene graph will designed that would allow reading of CAD models and interfacing with current RoboComp simulation framework. Selection of rich textured CAD models is an crucial for any detection algorithm. Therefore, the proposed project will accompany a dataset of cleaned and textured CAD models for 5 object categories.</p>
<h3>ZT is Zulip's own Terminal client, which is a one of a kind, user-first and user-friendly <em><strong>TUI</strong></em> based chat application powered by Python module <em><strong>urwid</strong></em>.</h3> <p>The restrictive nature of a terminal application makes it all the more challenging and interesting to work on. Making ZT intuitive for every kind of person, <em>"techy"</em> or not, is the general vision of my project. This project mainly focuses on improving:</p> <ul> <li><strong>Message Rendering</strong> capabilities <em>(Syntax Highlighting, Display Emojis)</em></li> <li>general <strong>UI Navigability</strong> and <strong>Usability</strong> <em>(Dynamic Layout, Tabs, Focus Highlighting, SearchBox)</em></li> <li><strong>Internal Refactors</strong> for better code management <em>(Themes, Buttons & Panels , Keypress)</em></li> <li>certain <strong>Event Handling</strong> functions <em>(Typing Notification)</em></li> <li>and some <strong>Bugfixes</strong>.</li> </ul>
<p>The ardupilot features are already numerous and I already worked on helping ardupilot to have good compatibility with ROS. Ardupilot rover version (APMRover2) is well behind Arduplane and ArduCopter in capabilities as they attract more attention from developers. One obvious example is that Rover has only a very basic avoidance system (turn 45° on obstacle). It is also missing some autonomous features (on spot turn etc.), and more significantly is missing a proper motor configuration abstraction layer. While ArduCopter is capable of being configured in 4,6,8 motors copter with brushed (PWM) or brushless motor (RC PWM), the rover version is still limited to two modes: rover with propulsion and a steering servo (normal mode) and tank mode (skid steering mode), with only support on brushless motor. My proposal to this GSOC is split in two parts. Firstly, reduce the gap between the APMRover2 and the other vehicles to provide a good generic UGV platform capable of multiple configurations, with advance feature such as avoidance. Secondly, provide a good set of tutorials on the usage of ROS and ardupilot either for single unit control or on simulated unit on Gazebo simulator!</p>
<p>In this project I wish to develop a Mobile App for Mind The Word . I would be using Apache’s Cordova for developing the hybrid app as it would be easy to maintain and develop a cross platform app. Since the browser such as Chrome (for Android and iOS) do not support extensions, MTW cannot be implemented directly.In order to use our app, a user has 3 options.</p> <ul> <li>In the browser (e.g. chrome) , the user can choose to share the current page and then in the sharing options popup menu , the user can select MTW .</li> <li>The user can also copy the url to clipboard. Then as the user opens MTW App , a notification is shown at the bottom of the app with a message such as 'Open the copied url webpage ? ' . </li> <li>The user can manually enter the url in the address bar of MTW App.</li> </ul> <p>Any of the above 3 options, opens the InAppBrowser inside the MTW App and the mtw script is injected in webpage.The MTW App would include almost all the options (such as blacklist words, save learnt words etc ) available in the web extension.</p>
<p>pygeoapi is a python server implementation of OGC RESTful API standards. The current implementation of OGC Features API in pygeoapi supports only read operations. I propose to implement simple transactions (create, replace, update, delete) in pygeoapi OGC Features API in accordance with <code>OGC API - Features - Part 4: Simple Transactions</code> proposal. This involves the following:</p> <ul> <li>Create a sample openapi specification doc in accordance with <a href="https://github.com/opengeospatial/ogcapi-features/tree/master/extensions/transactions" target="_blank">Simple Transactions Proposal</a></li> <li>Generate the proposed openapi doc from pygeoapi config</li> <li>Define REST endpoints for simple transactions (POST, PUT, PATCH, DELETE) in Flask and Starlette</li> <li>Update pygeoapi core API to handle feature transactions</li> <li>Implement simple transactions in schemaless data providers - GeoJSON, CSV</li> <li>Implement simple transactions in schemaful data providers - PostgreSQL, SQLite</li> </ul>
<p>While there are a multitude of open source ML methods for prediction of various structural or biological related attributes, there are no open source pipelines or APIs which allow to performing a one command task for running multiple/equivalent methods and join the results in a way that facilitates comparisons and further dissemination. This limits any type of structural/comparative biology analyses, as one would need to install and run >50 software and put together all the results using in-house scripts.</p> <p>This project aims at developing a scalable workflow that receives the protein FASTA file and runs a series of structural and phenotype related predictors, generating a knowledge dataset that will facilitate further exploration and comparisons according to the following categories of features: secondary structure, solvent accessibility, disordered regions, PTS modifications or binding sites.</p> <p>Deliverables of this project consists of 8 modules for each analysis type organised as Docker images, a Python library for processing inputs & outputs of the included methods and a CWL pipeline that will facilitate a one-line command run of all the predictors (default or custom configuration).</p>
This project focuses on systematically expanding regression test coverage for the ESP codebase by targeting high-risk, untested logic paths rather than merely increasing overall coverage percentage. Through detailed codebase exploration, critical gaps have been identified in components such as lottery assignment logic, class registration flows, and mailman integrations. These areas involve complex logic, invariants, and edge cases that currently lack sufficient test coverage and pose a high risk of silent regressions. The project introduces invariant-based testing for the lottery system to ensure correctness properties such as no conflicts, no overcapacity, and valid grade constraints across arbitrary inputs. Additionally, integration tests will be implemented for mailman functionality using mocking to validate subprocess interactions without external dependencies. A reusable testing infrastructure will be developed to support scalable regression testing, along with targeted performance checks to detect potential degradations in critical views. The outcome will be a robust regression testing framework that transforms fragile, untested paths into enforceable guarantees, significantly improving system reliability and maintainability.
<p>The <strong>Open Event</strong> Project offers event managers a platform to organize all kinds of events including concerts, conferences, summits and regular meetups. The various components support organizers in all stages from event planning to publishing, marketing and ticket sales. Automated web and mobile apps help attendees to get information easily.</p> <p>There are two major divisions of this project:</p> <ol> <li>Implementation of numerous features on the <strong>Open Event Server</strong> in order to make it feature complete. Some of the features that we aimed for were integration of <em>payment system</em>, <em>tickets</em>, <em>taxes</em>, <em>promo codes</em> etc. </li> <li>Integration of missing endpoints and related features on the <strong>Open Event Frontend</strong> and <strong>Open Event Orga</strong> app. Some of the features that we aimed for in the <em>frontend</em> were the implementation of <em>promo codes</em>, <em>notifications</em> while <em>tracks</em> and <em>speakers</em> endpoints were targeted for the orga app.</li> </ol>
<p>Interactive visualization can provide intuitive insights for experiment setups and results in many domains, including High Energy Physics. Therefore, Virtual Point1 (VP1) was developed by ATLAS for 3D event display. Nevertheless, it seems a pity that it is based on an old graphics engine(OpenInventor) and resides in a big project(full ATLAS experiment software stack) with many dependencies.</p> <p>To get free of these limitations, GeoModelExplorer, a super-lighter version of VP1 has been developed, with a strong focus on the visualization of geometry data. Some of the important next steps are to replace the old 3D engine, improve existing functions and add more features. All of them are waiting for development.</p> <p>In this project, I will take these steps one by one, integrate the modern graphics engine Qt3D, improve the geometry rendering effects, extend the mesh I/O abilities, and add smooth animation for view inspections. There will be a large amount of design and engineering work but I will take extreme care. This project will eventually make contributions as part of the current software modernization effort in ATLAS.</p>
<p>Each operating system has its own "packages" that allow installing different applications to extend the features in the device. Android is not an exception, and their package type is the .apk file type (Android Application Package). This file has been present in Android since the very beginnings, allowing the development of several applications.<br> And App Inventor has the ability to build the app projects into those .apk files, as it is an Android app creator.</p> <p>Google, as the owner of Android, always tries to optimize its environment by protecting the users and enhancing the development ecosystem, among other things. So, they wanted to make a change. In Google I/O 2018, Google introduced the .aab file format (Android App Bundle).<br> This new format is being used by Google Play Store, and Google is encouraging everyone to use it when distributing apps.</p> <p>This project proposal intends to bring the option of exporting app projects in MIT App Inventor as .aab files, which make their distribution more straightforward in Google Play Store.<br> Moreover, if App Inventor had support for .aab files, it would be possible to make use of the App Signing by Google Play.</p>
I propose to enhance the Mifos Initiative's Kotlin Multiplatform (KMP) Multi-Module Project Generator to streamline cross-platform application development and make it more valuable for developers. My plan is to create a customizable Material Design 3 component layer for a consistent UI across platforms, implement a unified configuration system, and enhance GitHub Actions workflows for comprehensive CI/CD. I'll develop pre-built infrastructure components (networking, database, storage), streamline dependency management with Gradle plugins, improve the sync directories system, add a type-safe API client with Ktorfit, and automate library publishing to Maven Central. With my experience in Kotlin (3+ years) and Kotlin Multiplatform (2+ years), plus my extensive contributions to Mifos projects, I have the technical foundation to implement these enhancements successfully. I've created a detailed 15-week implementation plan with clear deliverables for each stage. These improvements will transform the KMP Project Generator into a more powerful and user-friendly tool, benefiting both the Mifos ecosystem and the broader KMP community by reducing development time and ensuring best practices across platforms.