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.
The KServe Models Web App is a crucial front-end interface for managing ML models deployed through KServe, a core component of Kubeflow. However, the application has become outdated, with deprecated dependencies and technical debt. This project aims to modernize and enhance the app by upgrading its tech stack, resolving open issues, and implementing a robust CI/CD pipeline with GitHub Actions. Key improvements include regression testing with Cypress, model editing capabilities, and synchronization with KServe 0.14+. Additionally, the project explores migrating the app from kserve/kserve-models-web to kubeflow/kserve-model-ui for better integration. The deliverables include a stabilized, modernized codebase, improved user experience for ML engineers, and streamlined contributor documentation. This effort will reduce operational overhead, enhance usability, and support Kubeflow’s mission of making ML workflows simpler and more scalable.
The proposed project aims at establishing a port between GHC and [MMTk](https://www.mmtk.io/) -- an external memory management toolkit that provides languages with a set of memory management primitives and garbage collectors. The current existing GHC storage manager (GHCSM) has a sophisticated generational GC; However, it's also optimized and integrated into GHC's runtime, making it difficult to switch to a broader range of collectors. It would be beneficial to generalize GHC's runtime, make it separable from GHCSM, and connect it with a suite of different garbage collections from MMTk. To achieve this goal, we propose to: 1. Refactor GHC's runtime system to more effectively abstract over storage management operations; 2. Introduce a storage management backend using MMTk's trivial no-GC collection plan; 3. Integrate write barriers necessary for generational collection with MMTk; 4. Introduce support for MMTk's semi-space and mark-sweep GC plans.
This project addresses the challenge of bringing 3D-generated marine organisms to life through scalable and automated animation. While recent advances enable the generation of detailed 3D models, these assets often lack realistic motion and require manual rigging and keyframing, limiting their usability in interactive and educational applications. To solve this, the project proposes a skeleton-based procedural animation system built using Python, Blender, and Unity. The system will automatically generate rigs and apply biologically inspired motion using procedural techniques such as kinematic chains and wave-based movement, enabling consistent animation across a wide range of marine organisms. The final deliverables will include a modular animation pipeline, support for multiple movement behaviors (e.g., swimming and idle states), integration with existing 3D generation workflows, and documented demos showcasing real-time visualization in Unity.
WildBerryEye leverages edge computing (Raspberry Pi) and object detection (YOLO) to monitor pollinators like bees and hummingbirds. My project focused on developing a clean, intuitive, and responsive web-based interface to support real-time pollinator detection, data visualization, and system configuration. The final result empowers researchers and contributors to engage with environmental data in an accessible and meaningful way. Specific tasks: - Frontend Development: Continue development to enhance the user interface using React and CSS, ensuring a responsive and user-friendly design. - Backend Development: Expand functionality using Flask, focusing on efficient API endpoints and seamless interaction with the frontend. - Real-Time Communication: Implement and refine real-time updates between the frontend and backend to enhance system responsiveness. - Usability & Design Optimization: Research and propose improvements to the system’s usability, design, and overall user experience.
<p>Migrate Chat, Skill, Account SUSI.AI under a common app SUSI.AI. Create a set of common and modular components. For styling 1 common approach should be used, like styled-components. Enhance Admin section by adding Reported Skills tab, Mail configuration, Email Messages(with reCaptcha configuration), User, Skills Statistics for Admin Panel.</p> <p>Add more functionality to settings for users. Make the whole application mobile responsive. Integrating Redux and removing flux architecture for data flow. Implement stop action, SoundCloud action on chat. Fix preview chat code and scroll interactions.</p> <p>Implement slideshow slider, Google Analytics, multi-search for skills CMS. All the above features will be integrated on frontend as well on the backend. Integrate support for SUSI.AI Speaker with SUSI.AI web client.</p>
To address the challenges identified with the FOSSology scheduler, particularly the limitations stemming from its programming language (C) and its linear queue design, proposed idea is to refactor current scheduler codebase in python and integrating Rocketry to create a more flexible, maintainable, and feature-rich scheduler. 1. Task Scheduling: Implement task scheduling with rocketry, utilizing its cron-style syntax for defining job frequencies. This allows for precise control over when jobs are executed, aligning with FOSSology's existing scheduling requirements. 2. Mutual Exclusivity and Concurrency: Define tasks with mutual exclusivity constraints directly within Rocketry, ensuring that jobs which should not run concurrently are handled appropriately. Utilize Rocketry's support for asynchronous execution to improve the scheduler's efficiency and responsiveness. 3. Error Handling and Logging: Built-in error handling and logging mechanisms to ensure that job failures are captured accurately, and relevant information is logged for debugging purposes.
<p>File fingerprinting is a way to track which version of a file is being used by a job/build, making dependency tracking easy. The fingerprint engine of Jenkins can track usages of artifacts, credentials, files, etc within the system. It does this by maintaining a local XML-based database. This leads to dependence on the physical disk of the Jenkins master. Hence, the core idea of this project is to extend Jenkins core to support storing of fingerprints in an external storage, which would be managed by storage system specific plugins. This would involve designing and creating the external fingerprint storage API. The API would also allow multiple Jenkins instances to store their fingerprints inside a single external storage instance, enabling traceability of artifacts across the CI/CD flow. The project also involves creating two plugins, as reference implementations. These plugins would allow users to store fingerprints inside their Redis and PostgreSQL instances.</p>
<h3>libGPML</h3> <p>Currently it is required to include the whole <a href="https://github.com/PathVisio/" target="_blank">PathVisio</a> core module which is much bigger and already contains PathVisio specific visualization aspects, also with the current data model it is difficult to find out the connections between two elements in the pathway. This automatically makes any graph algorithms which could be used to analyse the pathway very inefficient.</p> <p>A general GPML library should only contain the data model, the functionality to read and write <a href="https://www.pathvisio.org/gpml/" target="_blank">GPML</a> files and relevant importers and exporters to other often used file formats so it can be easily integrated in other applications.</p> <p>The main goal of this project is to create a separate GPML library to read and write GPML files in Java which can be used by PathVisio, the WikiPathways app for Cytoscape and many other applications.</p>
<p>This project aims to make OODT deployment and configuration management simple through implementation of a docker-based deployment tool that integrates with the existing distributed configuration management tool in OODT. The target is to first containerize the major components in OODT (file manager, resource manager and workflow manager) using Docker. Each component will then have its own Dockerfile and Maven build execution using the dockerfile-maven plugin. Next, the initial OODT deployment tool will be created using Kubernetes. Once this is done, the existing OODT Distributed Configuration Management feature will be integrated with this tool to handle dynamic configuration management. As a later step, the deployment could be upgraded to work with Helm or KNative.</p> <p>Through this project, OODT will gain the ability to seamlessly manage OODT components regardless of the deployment environment. Technologies including Docker, Kubernetes and Maven will be required to carry out this project.</p>
<p>Field-Programmable Gate Array(FPGA) is a hardware circuit that a user can program to carry out logical operations. FPGAs are beneficial for prototyping application-specific integrated circuits (ASICs) or processors.</p> <p>The advantage of FPGA being energy-efficient, flexible to reprogram, support parallelism, decreased latency made them widely used in many applications. But the flexibility of FPGAs comes at the price of the difficulty of reprogramming the circuit. FPGA’s are a bit costly and difficult to learn for beginners. Also, students don’t have access to physical FPGA Lab classes in their curriculum amidst this pandemic situation. So there is a massive demand in having an alternative option of having an online simulator for FPGA curriculum development.</p> <p>This project aims to solve the problem by taking advantage of the VIZ Visualization feature in the Makerchip platform and provide visualizations of basic peripherals of an FPGA, thereby mimicking the physical lab experience.</p>
The 52°North Weather Routing Tool (WRT) computes fuel-optimal maritime routes but is entirely configuration-file-driven, making it inaccessible to non-developer users. This project delivers a QGIS plugin that solves this problem. A six-page guided wizard covers route setup with map-click waypoint entry, vessel parameters, weather and depth dataset upload with validation, algorithm selection, and constraint configuration - exporting a ready-to-run JSON config. A dockable weather panel renders NetCDF variables as time-animated layers with spatial subset statistics. A route visualization module displays WRT output with per-waypoint fuel consumption popups and distance calculation. An optional component runs the WRT directly from QGIS via an isolated Python venv, streaming live progress to the canvas. Deliverables: installable QGIS plugin, all four components and full documentation.
Visdom is great for watching training in real time, but once you have dozens of experiments, keeping track of what hyperparameters you used in each one becomes a mess. This project adds an experiment tracking layer to Visdom a SQLite-backed metadata store where every run carries structured hyperparameters, metrics, and tags. I am building a search system so you can query runs with simple syntax like "lr less than 0.01 and accuracy above 90", interactive parallel coordinates plots to visualize the hyperparameter space, and Optuna integration so Visdom can suggest what to try next based on past results. Everything runs locally with zero external dependencies, keeping Visdom's self-hosted philosophy intact. I have already contributed 6 PRs to the Visdom codebase covering backend bug fixes, frontend improvements, test fixes, and Python 3.12+ compatibility, and I have deep familiarity with both the Tornado server and the React frontend.
Visdom is a popular local-first visualization tool for PyTorch users, but it currently requires repetitive manual vis.line() calls for every metric such as loss, accuracy, and learning rate. This creates boilerplate code and slows down experiments. This project will solve the problem by adding deep native integration with both vanilla PyTorch and PyTorch Lightning. I will implement automatic metric detection and logging, a simple context manager and decorator for native training loops, configurable autograd hooks with throttling, learning-rate scheduler tracking, smart multi-run environment versioning, full multi-GPU and distributed support, and complete documentation with tutorial notebooks. The final deliverable will be a production-ready VisdomLogger that gives zero-config automatic logging while keeping full flexibility for advanced users. All features will come with comprehensive tests, a new PyTorch Integration Guide, and working demos.
This project will involve implementing conntrack entry clearing into Netavark, Podman's network management tool. Stale conntrack entries can cause network traffic to be dropped if a UDP port is rebound while a container is running. Netavark is written in Rust, but the Rust netlink bindings (located here - https://github.com/rust-netlink/netlink-packet-netfilter) presently do not include support for Conntrack. As such, the first step of the project will be to expand these bindings to cover Conntrack. Netavark can then make use of the bindings to flush Conntrack entries on network change, and tests implemented to verify this functionality. Expected Outcome: 1. Rust bindings for Conntrack implemented in the rust-netlink (https://github.com/rust-netlink/netlink-packet-netfilter) library 2. Netavark modified to use these bindings to drop Conntrack entries at appropriate times 3. Tests in Netavark repository to verify this functionality
More and more workload is moving towards running on the edge. We saw experiments running Kubernetes on vehicles, fighter jets, 5G antenna and various far edge, near edge and fat edge environments. We would like to see what the challenges are when Knative is run in a resource limited environment. While there are multiple edge-friendly Kubernetes distributions, we would like to see [Microshift](https://github.com/openshift/microshift) used as the base platform. Knative consists of Serving and Eventing modules but focusing on Knative Serving as a first step should be more approachable. The project consists of 2 stages. First one is to run Knative on Microshift with minimal resources. This requires finding out problems here, solving them. A stretch goal is to find out what happens with architectures other than x86_64. - Expected outcome: Having Knative Serving with an ingress layer running on top of Microshift. Having a Hello-World Knative Service running on top. Finding issues blocking the edge setup, and possibly fixing them.
The Gateway API is becoming the standard for Kubernetes service networking, including ingress, traffic routing, and service mesh use cases. While Headlamp has built-in support for Gateway API resources, there is currently no integrated way to visualize and manage service mesh topologies, traffic flows, and policies. This feature aims to enhance Headlamp with a visual and interactive interface for understanding and managing service meshes built on the Gateway API. Expected Outcome: A Headlamp feature that enables users to: 1. Visualize service mesh topologies using Gateway API resources (e.g., Gateways, Routes, Services) 2. Overlay traffic flow data, latency, error metrics, and traffic policies (e.g., splitting, retries, timeouts) on the resource map 3. Leverage existing Headlamp Map and CRD extension capabilities for seamless integration 4. Documentation and possibly a demo video or blog post.
<p>The project aims at dealing with the conversion of <strong>CiceroMark to DOCX (OOXML) and vice versa</strong>. In the first portion, we are gonna improve the add-in by improving the existing features and addition of new features which generally includes the ergo expressions and inline blocks of a template. Apart from these, there will be testing of data to ensure that the correct data is entered into the variable fields to avoid any inconsistency. The second portion involves the conversion of the <strong>OOXML to CiceroMark</strong>. In this, improvements will be made to the OOXML transformer present <a href="https://github.com/accordproject/markdown-transform/tree/algoo-ooxml" target="_blank">here</a>. The current transformer works only for very basic OOXML. We need to extend the functionalities of the transformer to support more ciceromark and commonmark classes like lists, optional, inline, ergo formula blocks. In this way, we will ensure more flexibility and portability with the round trip transformation of the smart clause templates.</p>
<p>Sustainable Computing Research Lab has done researches and project to identify elephants from images and tag them. LabelLab projects is a generalized extension of this. LabelLab focus on creating an mobile and web application to classify and label all kind of animal without being specific to elephant in order satisfy more use cases. LabelLab mobile app’s motivation is to allow user to use the classification model in field using their handheld device. The mobile app will have features take a image and classify it using the classification model and show the necessary information.</p> <p>Currently the classification model is already build. But both the mobile client and backend to integrated mobile client and classification model has to be built from scratch. This is a new project, So requirements of the project should be identified precisely and should be planned for future scalability of the project.</p> <p>I wish to implement the mobile client in Flutter for both Android and iOS and the backend in Node.js.</p>
Hyperledger Cello aims to simplify the deployment and management of blockchain technology across various industries, offering a robust toolkit for creating, managing, and monitoring blockchain networks on demand. Currently, the project is facing an upgrade to Hyperledger Fabric version 2.5 LTS. This upgrade is critical for enhancing the platform's stability, security, and performance, addressing current limitations and opening new avenues for blockchain applications. Interns will contribute directly to Hyperledger Cello by addressing GitHub issues and enhancing the project's features and documentation. Their work will improve the ease of blockchain network management, making blockchain technology more accessible and efficient for users. A significant part of the mentorship involves upgrading Hyperledger Cello to support Hyperledger Fabric version 2.5 LTS. This includes integrating new features, ensuring compatibility, and contributing to the overall stability and performance of blockchain solutions deployed via Cello.
Building on the PINNDE proof-of-concept from GSoC 2025, I propose two directions: (1) systematic improvements to the PINN architecture and training — Fourier feature embeddings, GELU activations, and adaptive collocation — informed by my test task results where GELU+Fourier features reduced physics loss by 10x over the baseline tanh network; and (2) a flow matching reformulation that replaces the O(NM) Monte Carlo score estimate with a simulation-free O(N) training objective, producing straighter transport paths that are easier for the PINN to learn. I will implement quantitative evaluation metrics (MMD, Sliced Wasserstein), benchmark both approaches on the existing 3D toy distributions, and apply the best pipeline to Dataset 1 of the Fast Calorimeter Simulation Challenge 2022. Deliverables: improved PINN architectures with benchmarks, a flow-matching PINNDE training mode, a reusable evaluation module, and results on the Calorimeter Challenge.
JSON Schema Studio visualizes JSON Schemas as interactive graphs, helping developers understand complex structures. While the current version works well, there are areas where rendering correctness and user experience can be improved. This project focuses on ensuring correct dependency-based rendering (especially for $defs), improving graph navigation, and enhancing synchronization between the editor and visualization. It will also address issues like edge collisions and unstable rendering during live edits. Additionally, features like validation error navigation, file upload, and visualization export will be introduced to improve usability. The final deliverables include: - Dependency-aware rendering using topological sorting - Improved graph interaction and navigation - Validation error navigation in the editor - Reduced edge collisions - Stable rendering during live edits - File upload and export support These improvements will make the tool more accurate, interactive, and useful for developers.
I propose a development period of 5 stages to gauge community needs, assess the toolbox, and potentially augment it with additional tests or functions. The first stage is to become more familiar with the glider community and identify what already exists, learning as much as possible prior to making any improvements. The 2nd stage is to address the “Group 1” tests as outlined in GSoC proposal #102 on Github, which are essential to many glider operations and basic data functionality for any following uses. Next, stage 3 will address” Group 2” or “strongly recommended” tests which are significant for data hygiene and identifying problems that likely arise from the sensors themselves, rather than real phenomena. Stage 4 addresses “Group 3” or “suggested” tests, which help anchor the data in reality by testing known oceanographic trends. Finally, stage 5 of this project will seek to expand the toolbox from any discovered shortcomings and synthesize the project into an easily digestible conclusion.
This project intends to implement a Maximum Weighted Matching algorithm for pgRouting within the OSGeo ecosystem, enabling efficient graph-based optimization for spatial networks. Maximum weighted matching is a fundamental problem that identifies a set of non-overlapping edges with maximum total weight, widely applicable in logistics, vehicle assignment, and supply-demand matching. The implementation will include development of a pgr_maximumWeightedMatching() function with a SQL interface and a high-performance C++ backend leveraging Boost Graph Library or optimized custom routines, integrated seamlessly with existing pgRouting structures. The project will also provide support for weighted graphs, comprehensive documentation, unit testing using pgTap, and performance benchmarking on large-scale and real-world datasets. This addition will enhance pgRouting’s analytical capabilities by introducing advanced matching functionality for transportation and network optimization while adhering to project coding standards.
<p>With this proposal I hope to benefit the open-source hardware enthusiast community with work related to the incredible Parallela board used by thousands of students and hobbyists around the world. This project will focus on the integration of the RISC-V rocket core, inside the Zynq FPGA device of Parallela. The RISC-V rocket core is an implementation of the RISV-V ISA that has gotten a lot of attention and support due to being clean, modular and power efficient. This project will allow owners of Parallela boards to write and execute RISC-V programs with minimal effort from their side. The system will work out of the box with a prebuilt binary image ready to be placed in an SD card and users will be able to re-build it with minimal effort. Moreover, a tutorial document will be created to aid inexperienced users make the most of this work and allow them to modify it for their own needs and purposes with custom hardware and / or software code.</p>