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.
OpenYurt is an open-source edge cloud-native platform designed to streamline application management and resource orchestration in edge computing scenarios. This project aims to enhance the yurt-dashboard (the core management interface of OpenYurt) by implementing internationalization support, integrating edge AI capabilities, and upgrading core API versions to improve global accessibility, technical innovation, and system stability. The project will leverage the React frontend framework, Golang backend services, and Kubernetes ecosystem toolchain to provide developers with a more efficient edge cloud-native experience. Expected Outcome: 1. i18n Implementation: Extract existing Chinese text and complete English translations using LinguiJS framework Implement frontend language-switching functionality with dynamic user selection 2. Edge AI Integration: Containerize and develop deployment templates for at least 3 open-source edge AI applications in the dashboard 3. API Modernization: Align with OpenYurt' latest API standards to ensure platform compatibility and security.
<p>Everyone wants to focus on improving their model performance, but a significant portion of their time is used up while searching for a proper dataset and then preparing it. TensorFlow datasets (TFDS) library is a huge relief for all the researchers trying to avoid data preprocessing.<br> So to make TFDS users’ life even more comfortable, I would like to propose the following features and improvements:</p> <ul> <li>Load datasets without reading the dataset generation code. (This will unlock backward compatibility and cross-language support for reading datasets)</li> <li>Implement folder-based methods to prepare custom Image datasets, Translation datasets, etc.</li> <li>Add a command-line tool to simplify the procedure to add new datasets in TFDS.</li> <li>Simplify the procedure to add datasets outside TFDS.</li> <li>Improve Windows compatibility.</li> <li>Improve the TFDS catalog.</li> <li>More user and contributor friendly documentation and tutorials.</li> <li>Solve tfds issues :-)</li> </ul>
<p>Traversal-based graph algorithms are good at extracting “subgraphs of interest” when applied to large networks. However, applying known algorithms may not be enough every time to extract the useful information. Some specialized queries may be helpful in this sence to extract more useful or more specific information. Actually, these types of queries are already implemented inside the PATIKAweb software that is a result of the study done by Doğrusöz et al. in Java programming language. The aim of this project is to move these implementations into the common use of developers by making an extension to Cytoscape.js, which is a commonly used graph drawing library written in Javascript. Cytoscape.js already includes some basic graph traversal algorithms such as DFS, BFS, Dijkstra, Bellman-Ford, Kruskal etc., but I believe that these specialized queries will provide a good functionality to be used in not only in biological networks, but also in other types of networks. With the advantage of compound node support in Cytoscape.js, these specialized traversal algorithms will also be easily applied to the large networks with compound node content.</p>
<p>EASE is a scripting project for eclipse which allows users to execute scripts from local and remote sources. It is a threat to user in executing scripts from unknown sources especially scripts stored on remote server. One way to provide authenticity and integrity is digital signature. I would like to work with EASE Eclipse community to extend project to provide signing and verifying script functionality to users. For providing signing feature, we can use java security API. It provides simple classes and methods to perform wide range of things like signing files using private key of user, export certificates, import certificates, verify signature, generating public and private keys, etc. User will be uploading his script on server, from where remote users can directly access such scripts through code and verify them before execution to know their credibility. I plan to provide several UI enhancements to support script signing efficiently. With successful completion of this project, EASE users will be able to judge nature of script before execution.</p>
This project addresses the critical need for a software-defined ground station receiver to support the LibreCube proto-LC2302, an open-source UHF CubeSat communications module. To solve this, we propose the development of a resilient receiver architecture utilizing Software-Defined Radio (SDR) and the GNU Radio framework. The system will ingest baseband IQ data, perform signal demodulation, and execute a complete Consultative Committee for Space Data Systems (CCSDS) decoding chain, including frame synchronization, deframing, and forward error correction (FEC). Key project deliverables include fully functional GNU Radio flowgraphs for both live SDR reception and recorded playback, curated test datasets, and comprehensive documentation. Furthermore, the project explores the optional development of custom C++ Out-of-Tree (OOT) blocks for supplementary processing, alongside integration with the Yamcs mission control suite. Ultimately, this work provides an end-to-end telemetry acquisition system, bridging the gap between open-source space hardware and standardized communication protocols.
Drupal's AI Content Strategy module does a great job telling editors what to write, but the moment it hands off, editors are left staring at a blank field with no actual help getting words on the page. This project builds a content generation assistant that sits directly inside Drupal field widgets, letting editors prompt an AI model and insert the result without ever leaving the editing interface. The module will be built around a clean plugin architecture that supports OpenAI GPT, Anthropic Claude, Hugging Face, and Google Gemini as interchangeable providers, with a React-based prompt dialog giving editors control over tone, length, and style. A REST endpoint will bridge the frontend widget to the backend provider system, and the module will include generation history tracking, rate limiting, and cost cap controls for site administrators. By the end of GSoC, the project will ship as a fully documented, publicly released Drupal module that closes the gap between strategic content recommendations and actual content creation.
This project developed an open-source code sample for batch question answering on long-form transcripts (such as lectures or documentaries) using Google Gemini APIs. It delivers a modular pipeline for batch predictions with asynchronous processing, long-context handling through transcript chunking and fallback strategies, a context caching system to reduce token usage, support for interconnected and multi-turn questions, and structured Markdown/JSON output with timestamp references. Several stretch goals were also completed, including Streamlit user interfaces for batch runs and cache management, efficiency benchmarking with reproducible token savings, and cache-aware batching strategies. During testing, the project surfaced two important API issues: an explicit caching bug on free-tier accounts (escalated internally as a P0 issue) and the lack of documentation around batch API availability on free-tier accounts. This work provides a practical reference for developers building educational tools, video summarization assistants, and retrieval-augmented generation (RAG) systems with Gemini.
This project addresses the inverse problem of estimating physiological parameters that characterize the permeability of the blood-brain barrier (BBB) from MRI data. These parameters cannot be measured directly and must be inferred from signal progression over time in techniques such as Dynamic Contrast-Enhanced MRI (DCE-MRI) and Arterial Spin Labeling (ASL). The estimation is complicated by measurement noise, model ambiguity, and the sensitivity of parameter estimates to small variations in the data. To improve robustness and accuracy, this project will implement a Bayesian framework that incorporates prior physiological knowledge and observed MRI signals to estimate the posterior distribution of the parameters. For the pharmacokinetic modeling the Tofts model for DCE-MRI and perfusion modeling for ASL will be used. Markov Chain (MCMC) sampling and gradient-based optimization methods may improve the robustness of the reconstruction. Deliverables include: --- An extensible implementation of the BBB modeling pipeline using OSIPI tools --- Support for both DCE-MRI and ASL data --- Parameter estimation via Bayesian inference and optimization --- Comprehensive documentation and integration into the OSIPI project.
This project implements a browser-native genomic feature search system for efficiently querying large GFF3 annotation datasets without requiring backend infrastructure. Traditional approaches either rely on slow client-side parsing or require server-side APIs, both of which introduce scalability and maintenance challenges. The proposed solution converts GFF3 files into an indexed SQLite database offline and performs full-text search queries directly in the browser using SQLite WASM within a Web Worker. The system integrates with JBrowse to enable seamless navigation from search results to genomic locations, providing a responsive and interactive user experience. To support large metagenomic datasets, the system will incorporate range-based loading and progressive data access strategies. The final outcome will include a production-ready indexing pipeline, a browser-based query engine, performance benchmarks, and a reusable React component that can be integrated across multiple EMBL-EBI web applications without requiring backend services.
<p>Interactive data exploration is an increasingly important component of data science. Interact.jl and Escher.jl are good libraries that have the potential to be extremely powerful for these tasks, but currently Interact only supports IJulia and Escher suffers some stability issues. WebIO.jl looks to be a promising path forward for building web based components that are created by or interface with Julia. Rebuilding Interact.jl on top of WebIO.jl will bring Interact beyond IJulia, to the Atom/Juno IDE and to desktop apps with Electron/Blink.jl. Additionally it should enable Escher.jl to reuse much of Interact, which will likely reduce Escher’s size and complexity significantly, increasing its stability. Furthermore, by removing its dependence on Jupyter and IPywidgets, Interact will gain flexibility to produce more complex UIs which intermix displayed data such as plots, and UI controls. Finally, I plan to add some automated UI testing which hopefully will assist in improving the stability of not just Interact and Escher, but potentially IJulia, Juno, and Blink as well.</p>
<p>The Proposal focuses on the improvement of App Inventor in the following aspects: Component Enhancements and Runtime Instantiation. Component Enhancement mainly targets the improvement in the features of components (ListView) so that the user can add more forms of information into the component. The Proposal focuses on the improvement of Listview so that after the final enhancements, the user can add Images and Text in the order they wish. Runtime Instantiation of Components enables the user to instantiate components by just using the blocks. This in turn gives the user, the ability to add components at runtime and instantiate them when necessary. This feature can boost the memory management in App inventor by assigning memory when needed. The proposal also marks the enhancement of file access. The app inventor currently doesn't support the access of External Storage in general. The proposal focuses on adding this feature so that many apps such as file managers can be made. Now, app inventor need not call an intent to access a file. Finally the proposal focuses on adding animation properties to the components so that the user is able to give a "Living" feel to their application.</p>
The objective of the "Physics-based Sonar Simulation for Underwater Robotics" project is twofold: firstly, to transition to ROS2 and integrate with the latest Gazebo simulation environment, and secondly, to substantially enhance the plugin's functionality. A key goal is to diversify the range of sonar models within the simulation, thereby significantly extending its relevance and efficacy across a variety of underwater conditions and operational scenarios. This strategic expansion aims to provide a more versatile and comprehensive tool for simulating dynamic underwater environments, facilitating advanced research and development in autonomous underwater navigation and obstacle avoidance. Deliverables: 1. A fully migrated and functional physics-based sonar simulation plugin within the ROS 2 framework and the LTS version of the new Gazebo. 2. Enhanced performance and capabilities of the plugin to support higher refresh rates. 3. A comprehensive suite of tests and validations conducted in simulated environments, ensuring reliability before real-world deployments. 4. Extended functionality through the inclusion of additional sonar types, catering to a broader spectrum of research and operational needs.
Smart home environments are increasingly popular, integrating a wide range of IoT devices to enhance user experience. However, the complexity of managing these devices limits the realization of their full potential. SmAuto, originally developed by the ISSEL research team at AUTH, is a Domain Specific Language (DSL) that simplifies the creation of complex automation scenarios for smart environments through a textual and web-based low-code interface. Currently, SmAuto lacks features such as integration with external REST data sources, time delays, semantic annotations, and direct access to HomeAssistant (HA) entities, restricting its utility in advanced smart home setups. This project aims to enhance SmAuto by: Extending the DSL to support the REST protocol for accessing external data sources. Introducing auxiliary concepts like Delay, Switches, and Compute nodes to enrich automation workflows. Integrating SmAuto into HomeAssistant as an open-source addon, enabling users to design and deploy automations graphically using SmAuto’s low-code environment and HA’s existing entities.
<p><strong>Open Source Programs</strong> is a project which aims towards simplifying the management work of the mentors and organizations. The goal is to make reviewing and notifying simpler, systematic and manageable. This will help in <strong>easy processing and hosting</strong> of the Open Source Programs be it a 4-week or a 6-month long program. In this GSoC period, I plan to build a Minimal Viable Product (MVP) as the first version of the application.</p> <ul> <li>Digitalize <strong>student progress tracking</strong></li> <li>Automated updating of Progress Sheets along with the feature of manual editing</li> <li>Build MVP based prototype/wireframes with simplified and minimum navigation</li> <li><strong>Discussion Forum</strong> (real-time) for each project, where the selected student and mentors discuss the project, milestones, goals and so on.</li> <li>Complete APIs with CRUD views.</li> <li>Add Frontend to support APIs and WebSocket agent.</li> <li>Add relevant documentation and tests for the same.</li> </ul>
OpenMRS currently utilizes Hibernate Envers to track database changes, offering robust audit capabilities. However, the system lacks a user-friendly way for administrators to view, filter, and interact with audit logs. This project proposes building a backend module that exposes audit log data in a meaningful way through a legacy UI-based audit log viewer, REST endpoints for external access, and an extension that tracks read operations on selected entities—something Envers does not support out-of-the-box. The solution will include: 1. Audit log retrieval and visualization within the legacy UI 2. Custom tracking of read operations using Hibernate event listeners or an alternative approach 3. Filtering capabilities (by user, date, and entity) 4. RESTful APIs for external access to audit data 5. A well-documented architecture, extensible to other OpenMRS modules By the end of this project, OpenMRS administrators will have a comprehensive and usable interface to audit system activity, improving transparency, traceability, and compliance with healthcare data standards.
<p>BuildingSMART organisation is currently working and about to publish new <a href="https://github.com/buildingSMART/IDS" target="_blank">IDS</a> (Information Delivery Specifications) which in simple terms is a machine-readable standard for building information modelling (BIM) requirements. Thanks to IDS, it is possible to automatically verify exchange requirements of BIM models delivered in IFC format.</p> <p>In my project, I will first focus on the validation process using IfcOpenShell to make sure it fully supports the new XSD (XML schema definition) of IDS and create sample IDS files to test it against. Furthermore, I aim to enhance this feature with BIM Collaboration Format (<a href="https://technical.buildingsmart.org/standards/bcf/" target="_blank">BCF</a>) output of such verification, which will be integrated into the BIMTester tool.</p> <p>The last step would be to allow for easier creation of IDS files by non-coding users. The idea is to add the authoring functionality of BIMTester web UI. This is where the work overlaps with the project of another GSoC student.</p>
<p>DigiKam is a famous open source photo management software. Face engine is a tool helping users recognize and label faces in photos. Following the advance of Deep Learning, digiKam development team has been working on the Deep Learning implementation of Faces engine since 2018. During the past few years, with the huge effort of digiKam developers and the great support from users, the Faces engine has been improved gradually.</p> <p>However, the Faces engine still has some issues that were not yet eliminated. For example, in the core algorithm, we still get many false positives because the faces engine tries to include all the faces to the known range of labels. In the face pipeline, a lot of implicit memory conversion between QImage, DImg and OpenCV Mat, which for some reasons, adds noise to the images.</p> <p>Therefore, for this 2021 Google Summer of Code, we are going to improve the detection/recognition performance with outlier faces suppression (i.e. new faces should not be counted as untagged faces), the ability to work on large datasets, and an ease-of-use face workflow improvement.</p>
OpenStreetMap (OSM) commonly stores names of streets, places, and points of interest in their local language and script. As a result, users searching in unfamiliar regions may receive results that are unreadable—especially when those names are rendered in non-Latin scripts like Cyrillic, Arabic, or Chinese. This project will enhance Nominatim, OSM’s geocoding engine, by adding transliteration support to its search results. The goal is to detect when names are in a script unfamiliar to the user and provide a readable transliteration alongside the original. This involves detecting the script of place names, selecting an appropriate transliteration library (e.g., pyicu, unidecode), and integrating a new transliterated_name field into Nominatim’s output format. The solution will be designed to be modular and extensible to multiple languages and target scripts. Deliverables include a working transliteration pipeline, user-configurable options, improved search result formatting, robust test coverage, and complete documentation. This will make OpenStreetMap data more accessible to users worldwide by bridging language and script barriers during location search.
This project addresses the lack of RNTuple support in JSROOT, a critical gap hindering browser-based visualization and analysis of high-energy physics (HEP) data. My Solution: By developing a JavaScript parser for RNTuple’s binary format, extending JSROOT’s interface to mirror its `TSelector` API for TTrees, and integrating visualization tools (histograms, scatter plots), researchers will gain seamless access to RNTuple data directly in web browsers. Key deliverables include: 1. Validated Parser: Tested against ROOT-generated datasets (via C++ macros) for accuracy. 2. JSROOT Integration: A `TRootupleSelector` interface enabling reuse of existing visualization modules. 3. Interactive Visualizations: Histograms, scatter plots, and UI features (tooltips, zoom) for real-time data exploration. 4. Optimized Performance: Stress-tested with 1M+ entries, cross-browser compatibility (Chrome, Firefox, Safari, Edge). This work will bridge the gap between RNTuple and browser-based HEP analysis, enhancing accessibility for global researchers.
Panel and HoloViews are powerful Python visualization libraries but they have no MCP integration today. AI agents can write visualization code but the result never renders inline in the chat. There is no way to create, update, or interact with a live dashboard from within an LLM conversation. This project builds an MCP Apps-compatible server for Panel and HoloViews that changes that. MCP Apps let tools return sandboxed, embedded interfaces that render directly inside MCP clients like VS Code, Claude Desktop, and Cursor, with bidirectional communication between the interface and the host. The goal is to turn Panel and HoloViews into first-class interactive UIs inside any agent conversation. The project will deliver three things: a CSP-compliant sandboxed rendering path for MCP Apps covering the full hvPlot and HoloViews chart surface, a bidirectional postMessage protocol so widgets can communicate with the agent in real time, and cloud-native dataset support for Parquet, Zarr, and the Earthmover marketplace. All work will be delivered as tested, documented PRs to the HoloViz ecosystem.
Music Blocks and Turtle Blocks lack a structured version control system, making it difficult for users to manage project history, collaborate, and contribute effectively. This project aims to integrate Git-based version control, allowing users to track changes, fork projects, submit pull requests, and collaborate seamlessly. To achieve this, I will develop a backend API that interacts with GitHub or GitLab, enabling repository creation, commit tracking, forking, and merging. A user-friendly frontend UI will be implemented to provide an intuitive experience for project management. Deliverables: -A backend API supporting Git operations (repository creation, commits, forks, PRs, merges) -A frontend "Git Menu" for managing project versions, viewing history, and contributing. -A "Projects" page displaying repositories with commit history and branches. -Robust testing and documentation to ensure maintainability. -Initial user testing with community contributors and educators. The goal is to use GitHub as a back-end and database and use Git's powerful features to make learning more effective for students.
<p>The Performance Farm is an useful way to test Postgres' functionalities while changes are being made, to analyze its efficacy on different operating systems. To further support the community effort, this project has to be extended building a database and a website on top of it, to make results easier to browse and display.</p> <p>My goal is making a web application using Python to interface server and client. The code will be scalable, portable and light-weight, while providing users a functional interface to interact with the performance data.</p> <p>The website will rely on a database, with optimised structure and queries to guarantee speed and an efficient use of the resources. The Django framework will be deployed so that the browser can send requests of search, review and storage.</p> <p>The application will also take care of parsing, users handling and securing connections, implementing RESTful API and respecting web standards.</p> <p>All changes will be subject to testing and bug fixes, to have a complete and coherent project with a clear documentation so that the final product is easy to set up and maintain.</p>
<p>MapAction’s mission is to provide people dealing with humanitarian emergencies with supportive maps as quickly as possible. Currently most of such maps are produced manually by experts. The problem is this process might take hours while each spent minute costs people’s lives. Thus, automatization of map producing is mandatory. That’s why MapChef was created. MapChef works with recipes to create maps. In the wild, however, data is not represented in MapChef’s desired format. It must be prepared. And since manual data acquisition and preprocessing is time-consuming, creating a pipeline for automatization of this work is highly desired. Recently, a series of data pipelines has been implemented.</p> <p>At the moment MapAction’s data pipeline framework can deal with two types of data: country boundaries from HDX and roads from OSM. This project aims to extend this pipeline to other types of data. Achieving this will increase the quality of the automatically generated maps. As a result, MapAction will be able to provide people responding to crisis with significantly more vital information immediately after an emergency.</p>
This project aims to implement a native Java based LDAP authentication provider in Uyuni to eliminate dependency on OS level authentication mechanisms such as SSSD and PAM. The solution will enable administrators to configure LDAP integration directly through the web UI while supporting automatic mapping of LDAP groups to Uyuni roles. The implementation will extend the existing authentication flow by integrating LDAP authentication within UserImpl.authenticate without requiring major refactoring. It will include secure bind and search operations, efficient connection pooling, and seamless coexistence with existing local and PAM based authentication methods. Additionally, the project will introduce dynamic RBAC mapping where LDAP groups are mapped to Uyuni roles at login time, ensuring correct permissions without manual intervention. A configuration interface in the Admin Setup section will allow administrators to manage LDAP settings and role mappings easily. The final deliverable will be a scalable, maintainable, and secure authentication system that improves usability and enterprise readiness of Uyuni.