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>Kuadrant's MCP Gateway is an Envoy-based gateway for Model Context Protocol (MCP) servers that provides routing, policy enforcement, and tool federation. As the agentic ecosystem grows, we're looking to extend the gateway's capabilities beyond MCP to support other agentic protocols. The A2A (Agent-to-Agent) protocol is an emerging standard for inter-agent communication with capabilities like long-running tasks, streaming, and agent discovery via agent cards. This project will investigate how A2A support can be added to the gateway alongside MCP, then build a proof-of-concept demonstrating federated agent discovery and A2A request routing through the gateway. The mentee will work closely with mentors throughout — collaborating on the design doc, pairing on implementation decisions, and spiking on specific pieces as needed to validate assumptions early. They will also engage with the broader Kuadrant community through PR reviews, design discussions, and community calls.</p><p>- Expected Outcome:</p><p> - Analysis of the A2A protocol with a gap assessment comparing A2A and MCP traffic patterns (request/response vs long-running tasks, push notifications, multi-modal artifacts)</p><p> - Design document covering A2A routing through ext_proc, federated agent card serving in the broker, session handling implications, and CRD design</p><p> - Federated agent card endpoint in the broker that aggregates upstream A2A agent cards</p><p> - A2A request routing through the Envoy ext_proc path, with appropriate header handling and policy enforcement</p><p> - CRD design (new resource or MCPServerRegistration extension) for registering A2A agents with the gateway controller</p><p> - E2E tests demonstrating A2A agent discovery and task execution through the gateway</p><p><br></p>
<p>GeNN uses the power of GPU parallelism to accelerate simulations. Currently GeNN only supports CUDA limiting its use to NVIDIA GPUs only. The projects focuses on adding OpenCL support to make it useful for any GPU.</p>
This project will focus on implementing the backend infrastructure necessary to manage Workload Description Space (WDS) operations. The backend will support UI functionalities such as workload deployment and visualization. Objectives: - Develop API endpoints for workload deployment to WDS. - Implement workload status tracking and log retrieval. - Ensure efficient workload resource retrieval. Expected Outcomes - A robust WDS backend to support UI functionalities. - Secure API integrations for workload management. - Efficient backend processes for workload deployment and tracking.
This project aims to implement a Near-to-Far Field Transformation (NFFT) feature in gprMax. This will enable users to compute the far-field radiation patterns and radar crosssections(RCS) from the near-field data. It will expand gprMax’s capabilities for antenna design, scattering analysis, etc. I propose to implement the Near-to-Far Field Transformation (NFFT) module and its integration at several key points in the existing workflow: - Adding the NFFT command - Module for Field Sampling during FDTD - Post-Processing & Far-Field Calculation - Integration with the API - Validation and Testing - Documentation and Review
<p>IPSec standards are produced and maintained by <a href="https://ietf.org/" target="_blank">Internet Engineering Task Force</a> which are implemented by many software including <a href="https://libreswan.org/" target="_blank">Libreswan</a>. <a href="https://www.openiked.org/" target="_blank">OpenIKED</a> is one such native implementation of <a href="https://tools.ietf.org/html/rfc7296" target="_blank">IKEv2</a> on OpenBSD. My project’s purpose is to enable Interop tests where one end is Libreswan on Linux and the other is the native IKE daemon on OpenBSD. This helps us test Linux kernel to BSD kernel and understand several issues with Linux when inter-operating with with Non-Linux Operating Systems.</p>
OpenVINO GenAI currently supports text-to-video generation via the LTX pipeline but lacks image conditioning. This project adds Image-to-Video (I2V) generation, enabling users to produce videos from an input image combined with a text prompt, running on Intel CPU and GPU. The implementation follows the HuggingFace Diffusers LTXImageToVideoPipeline reference: the input image is VAE-encoded once, and the resulting latent is prepended as frame 0 along the frame axis of the packed latent tensor throughout the denoising loop. Deliverables include: VAE encoder support in AutoencoderKLLTXVideo, a generate(image, prompt, config) overload in both C++ and Python APIs, strength-based timestep scheduling, C++ and Python samples, WWB and LLM benchmarking updates, and a cross-language test suite validating numerical consistency between C++ and Python implementations.
Accurately classifying particle collisions—whether distinguishing quark- from gluon-initiated jets or isolating Higgs events from complex backgrounds—requires models that capture both fundamental conservation laws and the inherent geo- metric invariances of the detector environment. This work presents a hybrid self-supervised framework that leverages physics-informed deep learning to ad- dress these challenges. Our approach utilizes a masked transformer encoder to learn conservation of momentum and energy by reconstructing masked particle features, while a Lorentz-Equivariant Geometric Algebra Transformer (L-GATr) encodes the space-time symmetries present in collision events. By integrating these complementary embeddings into task-specific cross-attention decoders, the framework effectively fuses physical and geometric information to enhance event classification and mass reconstruction, thereby advancing the performance and interpretability of machine learning in high-energy physics.
WasmEdge provides several AI frameworks as WASI-NN plugins to enable the power of AI/LLM applications for developers and users. We are always eager to add new backends to improve coverage of all models and hardware. BitNet.cpp, released by Microsoft, offers the ability to run 1-bit LLMs quickly without a GPU. We would like to support this framework so that people with limited resources, such as CPU-only hardware, can enjoy the amazing world brought by LLMs. Expected Outcome: i. A new WASI-NN plugin supports BitNet. ii. Use the pure C++ interface from BitNet without any Python dependencies. iii. The plugin must run the model listed in the BitNet repository, e.g., BitNet b1.58 2B4T - Scaling Native 1-bit LLM. iv. A tutorial and example for demonstration. v. A CI workflow for building, testing, and releasing the built assets.
Hyperledger Aries currently support only Hyperledger Indy blockchain. Verifiable credential(VC) and decentralised identifier(DID) standard & specification emerged in last few years. Trust over IP , Sovrin network, covid credential initiative are using Indy & Aries technology framework. Hyperledger Fabric general enterprise blockchain framework and most used Hyperledger project, latest Forbes Blockchain 50 report shows that 60% companies using Hyperledger Fabric for their enterprise grade blockchain. All the major cloud provides fabric as BaaS( Blockchain as a Service). Currently every identity/credential application using Indy/Aries stack to build W3C complaint VC & DID applications. There will be huge adoption and applicability of Hyperledger Fabric & Aries integration project. As per Hyperledger project governance there should be Hyperledger project interoperability to huge adoption of Hyperledger technologies. Mentee will learn: 1) Hyperledger Fabric Architecture & SDK/API 2) Hyperledger Aries Javascript framework 3) VC/DID standard and Application Expected Outcome Hyperledger Aries & fabric Wrapper or Aries will have support to use Hyperledger Fabric as Blockchain for storing credentials.
Currently, the KCL IDE plug-in based on Jetbrains LSP cannot support all versions of Jetbrains IDE, so migrate the KCL IDE plug-in to Lsp4IJ to support all versions of Jetbrains IDE. Expected Outcome: KCL IDE plug-in is migrated to Lsp4IJ
The Open World Holidays Framework is an essential open-source tool that provides accurate holiday data for over 160 countries. However, it currently lacks comprehensive support for several underrepresented countries, which limits its utility for users seeking to understand global holiday practices. This proposal aims to enhance the framework by integrating holiday data for 12 additional countries: Fiji, Antigua and Barbuda, Benin, Bhutan, Cabo Verde, Central African Republic, Comoros, Ivory Coast, Democratic People's Republic of Korea, Democratic Republic of the Congo, Equatorial Guinea, and Eritrea. To achieve this, I will conduct thorough research to gather accurate holiday data from authoritative governmental sources, ensuring linguistic accuracy through credible translations. The integration process will involve developing a structured approach to accommodate both fixed and floating holidays, as well as regional variations. I will leverage my previous contributions to the framework, particularly my work on Fiji, as a foundation for this project. The deliverables for this project will include: - Integrated holiday data for the 12 new countries within the Open World Holidays Framework. - Comprehensive unit and integration tests to ensure the accuracy and compatibility of the newly added data. - Updated documentation that reflects the new country support and provides clear usage instructions for users. By expanding the framework's coverage, this project will not only enhance its functionality but also promote cultural awareness and inclusivity, making it a valuable resource for users worldwide.
<p>The Kuadrant Console Plugin provides a web interface for managing API gateway policies in OpenShift, but currently relies heavily on YAML editing for most policy types. While DNSPolicy and TLSPolicy already have user-friendly form-based interfaces with dual Form/YAML views, validation, and guided workflows, the remaining core policies (RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC) still require users to manually write YAML. This creates a steep learning curve and error-prone configuration experience. This project aims to bring RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC policies to feature parity with the existing DNS and TLS form implementations. Form designs will be provided by the Kuadrant team. The mentee will implement these designs as PatternFly-based form interfaces following the established patterns from the DNS and TLS policy forms. These forms will allow users to configure policies through validated form fields while maintaining the flexibility to switch to YAML view for advanced use cases. The forms must support both creation and editing of policies, include proper field validation, handle complex nested structures (such as rate limit configurations and authentication rules), and synchronize seamlessly between form and YAML representations using the same patterns already proven in the DNS and TLS implementations.</p><p><br></p><p>Expected Outcome:</p><p> - Form-based creation and editing interfaces for RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC policies implemented using the same patterns, components, and structure as the existing DNSPolicy and TLSPolicy forms</p><p> - Dual view toggle (Form View / YAML View) with bidirectional synchronization using js-yaml for all five policy types</p><p> - Field validation following the established validation pattern covering required fields, numeric constraints, conditional dependencies, and Kubernetes resource naming conventions</p><p> - PatternFly component integration matching existing forms: expandable sections for complex nested configurations, validated text inputs, dropdowns for enum fields, and reuse of gateway selection components</p><p> - Policy-specific form fields for: rate limit units and counters (RateLimitPolicy), token-based rate limiting (TokenRateLimitPolicy), authentication strategies and credentials (AuthPolicy), plan tiers and quotas (Plan), and OIDC provider configurations (OIDC)</p><p> - Error handling using the existing error modal and inline validation message patterns</p><p> - Internationalization support for all form labels and validation messages using i18next following the existing localization structure</p><p> - Both create (`/~new`) and edit (`/:name/edit`) routes for each policy type matching the DNS/TLS routing pattern</p><p> - Unit and component tests covering form validation, YAML synchronization, and error states following the established testing patterns</p><p><br></p>
This project will add screenshot functionality to SupportTool. It can help users take screenshots when reporting the issues they encountered. Users can also blur the areas they choose in the screenshots to ensure privacy.
<p>Most of existing PRU applications utilize (waste) one PRU core for data transfer. The goal of this project is to enable usage of EDMA controller for copying of data to and from main memory (DDR), which would allow applications to use both cores for computation.</p>
<p>Ruby has no native ByteArray or ByteBuffer types, unlike Java. While it'd be great to have something like this in core Ruby, the next best place would be in the New IO for Ruby project, which provides a thin wrapper around Java NIO. The goal of this project would be to wrap Java ByteBuffers (particularly direct ByteBuffers) in a Ruby class that can also be implemented in pure Ruby which hooks into nio4r and can be used directly with nio4r's Java NIO backend.</p>
Gradle is a build automation tool known for its flexibility to build software. A build automation tool is used to automate the creation of applications. The building process includes compiling, linking, and packaging the code. The process becomes more consistent with the help of build automation tools. Currently, SymbolicPathFinder is using Ant as a build automation tool but the Gradle resolves all the issues faced by building tools like Maven and ANT. It is Well-Known to be highly customizable for different projects dealing with various technologies. We can customize the project according to the needs of the project. Gradle is popular for providing high-speed performance, nearly twice as fast as Maven. Gradle makes building common types of projects easy by adding layers of conventions and pre-built functionality through plugins. We can apply all those to enhance our SPF project. At the end of this project, we will get High performance, Build Scan, incremental build (that states it executes the tasks). Some steps to Implement this project : 1. Create Gradle build from scratch. 2. Restructuring of the project. 3. Implement a continuous integration (CI) pipeline. 4. Improve Junit Testing. 5. Update Documentation.
The proposal aims to describe briefly my approach to implement OpenSSH connection multiplexing in libssh. It goes over the required components and functions and how they work in order to achieve connection multiplexing. The project aims to deliver multiplexing multiple sessions using only one TCP connection.
The Verilog feature in CircuitVerse has been a great experimental addition till now. It has allowed users to write, experiment, and test their Verilog code along with graphical circuit design using CV simulator. But currently, the Verilog feature is full of bugs, unstable, and unreliable which leads to its failure and causes loss of trust in CircuitVerse among its userbase. The project aims to fix the bugs, make the Verilog feature stable, refine the Verilog interface, make it more intuitive, enable users to generate, view, edit, test circuits comprehensively, and fix the testbench generation feature for Verilog code. Other goals include adding detailed documentation for Verilog and added improvements to assist users. Additional enhancements like adding play/pause functionality to simulator, and implementing full-screen view for the Boolean Logic Table is also covered in this project.
The wasm-Signature proposal is specifically about embedded digital signatures in WebAssembly modules, not about package/OCI signatures. When distributing WebAssembly modules, it will be nice if we can have a way to verify. To achieve this target, we choose a Wasm-Signature proposal as our implementation standard. With this proposal, WasmEdge can provide `sign` and `verify` features.
<p>For now <code>HEAD</code> formulae can't be upgraded by just running <code>brew upgrade <formula> --HEAD</code>. The only way to upgrade <code>HEAD</code> formula is to uninstall it and install once again or using <code>reinstall</code> which is almost the same thing. This is not very convenient. We don't know if it's time to upgrade formula, we don't have other versions. We don't reinstall stable formula to upgrade them and the same way we don't need to reinstall head formula to upgrade them. The outcome of the project is to provide <code>HEAD</code> versions and the ability to upgrade them.</p>
<p>Backend for some most popular cloud services: Google Drive, Dropbox, OneDrive. Integrating it with vlmc user interface.</p>
<p>This project focus on implementing asyncio’s coroutine and event loop (both timer & socket based) for voc in JVM. Successful implementation of asyncio in voc will greatly benefit toga_android development and enable user to write concurrent functions (using asyc def/await) in Python and execute them in Java Virtual Machine after transpilation by voc.</p>
At current state of the product, listens on ListenBrainz are collected in the UTC instead of their local timestamp, without taking DST in to consideration. Adding timezone preference for users and adding the time zone field in submitted listens will contribute to the analysis and thus provide better user experience. This project aims to add users’ timezone preference paired with their submitted listens. The main work involves making an appropriate table in Postgres to store timezones, designing a react UI page and implementing the corresponding API endpoints. The stretch goal is to include local timestamp in the API, and extract the timezone information from that timestamp to store in the database. The expected outcome is a finished feature ready to be merged into production code.