Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

Your premium companion for discovering, matching, and tracking paid open-source mentorship programs and verified starter issues.

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Accessibility Statement

Made with love bySubhranshu Sekhar Dash

© 2026 Contribo. Built for the global open-source community.

PlatformProjects

Explore Projects

Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.

Confused which project to choose or don't know which one you are most suitable to work on?

Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.

Match with Orbit AI
Filters Clear
5976 Projects Found
Sort by

Mapping the RISC-V Extensions Landscape Mentorship Project

Intermediate
•Varies

Ready to Apply?

Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.

Start Proposal
Proposal Status
0% ProgressNot Started
Accepted Proposals
3 SimilarView →
Proposal Guide
Tailored DocsOpen →
Checklist & Review
Readiness AuditCheck →
175h (Medium)

<p>The RISC-V Extensions Landscape is an open-source, interactive web tool that serves as a single searchable reference for the entire RISC-V Instruction Set Architecture ecosystem. It visualizes all ratified, draft, and discontinued extensions, displays per-instruction 32-bit encoding diagrams with match/mask values, and supports filtering by RISC-V profiles (RVA20, RVA22, RVA23, RVB23). The project is live at https://rpsene.github.io/riscv-extensions-landscape/ and built with React, Tailwind CSS, and Webpack.</p><p><br></p><p>The core challenge is that only 83 of 220 cataloged extensions (38%) have their instruction details fully mapped. The remaining 137 extensions exist in the catalog but lack instruction encodings, leaving significant gaps in supervisor-level extensions (trap, interrupt, memory), vector subsets, and vector cryptography bundles. Additionally, 104 extension tags from the upstream riscv-opcodes project remain unlinked due to naming mismatches between the source data and the catalog, preventing automated synchronization.</p><p><br></p><p>The mentee will work on three main tasks: (1) reconcile the 104 mismatched extension tags from riscv-opcodes with the catalog's naming conventions, enabling the sync script to automatically populate instruction data; (2) research and map instructions for the remaining extensions, particularly supervisor-level extensions that define CSR behaviors and vector subset extensions that represent subsets of the V extension; and (3) improve the sync tooling to detect gaps and generate coverage reports automatically. The mentee will gain hands-on experience with the RISC-V ISA, open-source data engineering, and React-based visualization tools.</p><p>&nbsp;</p>

TBA
Proposal

AI Model Service Auto Selection by Modality

advanced
LibreHealth•2023Varies350h (Large)

The LibreHealth Radiology AI Model service aids radiologists with AI to produce fast and accurate medical diagnoses. It communicates with LibreHealth RIS module to output labels on DICOM viewer. Currently, CheXnet model is integrated to the AI Model service, but the proposal expands to apply other models to imaging modalities like Mammo, Head CT, Abdomen CT. The project aims to understand what radiologists need in terms of AI and implement it. The goal is to help radiologists perform better by implementing algorithms for new imaging modalities. To tackle the problem we start by looking at research that have looked deep into model architectures and methods that work well with imaging modalities, for example Alexnet have proven to work on modalities like Head CT. We then collect the imaging data necessary to train out models and also decide on the method of training like transfer learning on pretrained models or do we go ahead with training a model from scratch. Appropriate feature engineering and tuning will be part of the problem solving process. Once we establish a model to perform well on a modality we proceed to integrate the model to the AI Model service application. The deliverables will include - Collate information on data sources, methods and models that will be used for implementation and review with mentor(s) - For any modality, start with data preparation, feature engineering, training and evaluation until satisfactory performance is achieved. Here we will trial different augmentation techniques and hyperparameter tuning methods. - Integrate the model inferencing code and retraining code to the application for all modalities - Add methods to the Flask API to appropriately call the specific AI model for a modality. Modify existing methods as necessary so as to include the new AI models - Perform unit tests, integration tests, functional tests and end to end tests for the implementations. Necessary coding standards will be used.

mysqljavascriptjava+6
Student: Rohan Satya Isaac
Code
Proposal

IBus Customize

intermediate
openSUSE Project•2021$3k–$6.6k175h (Medium)

<p>Currently (Before GSoC 2021 during application), the <a href="https://en.wikipedia.org/wiki/Intelligent_Input_Bus" target="_blank">IBus</a> theme follows the global <strong>GNOME-Shell theme</strong> in GNOME and the global <strong>GTK theme</strong> in other desktop environments, and IBus lacks customization for users in GNOME.</p> <h4>Main Focus</h4> <p>This project aims to make IBus themes separate from the current <strong>GNOME-Shell theme</strong> and <strong>GTK theme</strong> so that users can customize it with other <strong><a href="https://www.gnome-look.org/browse/cat/134/" target="_blank">GNOME-Shell themes</a></strong> and <strong><a href="https://www.gnome-look.org/browse/cat/135/" target="_blank">GTK themes</a></strong>.</p> <h4>Other Goals</h4> <p>Improve the UI usability for IBus in GNOME. That is, to add more features, including customization of orientation, animation, font, opacity. Support right-click to switch the input source or open the tray menu, scroll to switch among pages or candidates, fix candidate box and IME switch list order, ASCII mode auto-switch, reposition, show or hide candidate box page buttons, set system tray settings, input source indicator with settings. Theme and background picture follow GNOME Night Light Mode, and so on. These customizations will make users find IBus in GNOME familiar if they have just switched from another platform. Eventually, an extension providing full customization of appearance, behavior, system tray, input source indicator for IBus will be available.</p> <h4><a href="https://github.com/IBus-Customize" target="_blank">Archived Codebase</a></h4>

pythonlinuxjavascript+11
Student: Songlin Jiang
Code
Proposal

Automated Documentation Sync Bot for Krkn-Chaos Projects (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>The krkn-chaos/website repository hosts the unified documentation for the entire krkn-chaos ecosystem (krkn, krkn-hub, krknctl, krkn-ai, krkn-operator, cerberus, etc.) as a Hugo/Docsy site deployed at krkn-chaos.dev. Currently, when changes are made to any of these upstream projects — such as adding a new scenario, modifying configuration options, or updating CLI flags — someone must manually open a PR against the website repo to update the corresponding docs. This is tedious, easy to forget, and often leads to documentation drift where the docs no longer match the actual tool behavior. This issue proposes building a bot or GitHub Action-based workflow that detects documentation-impacting changes in upstream krkn-chaos repositories and automatically creates a draft PR on the website repo with the relevant documentation updates. The bot would analyze the scope of the change (e.g., new config fields, updated parameters, new scenario) and generate or update the corresponding Hugo content files, following the existing content structure and conventions (tabbed scenario layouts, parameter tables, etc.).</p><p><br></p><p>Expected Outcome:&nbsp;</p><p>&nbsp;- Build a GitHub Action or bot that triggers on merged PRs in upstream krkn-chaos repos and automatically creates draft documentation PRs on the website repository following existing Hugo/Docsy content conventions.</p><p>&nbsp;- Support common change types including new or updated config fields, CLI flag changes, new chaos scenarios, and modified parameter tables.</p><p>&nbsp;- Enable interactive refinement of generated documentation PRs through review comments, similar to code review bots like CodeRabbit.</p><p><br></p>

TBA
Proposal

Project 11 - Composable Kale Notebooks with Visual Pipeline Editor

intermediate
Kubeflow•2026Varies175h (Medium)

Kale compiles a single Jupyter notebook into a Kubeflow Pipeline by parsing cell tags, detecting data dependencies with PyFlakes, and generating KFP DSL. But real ML work rarely fits in one notebook ,teams split preprocessing, training, and evaluation across separate notebooks, and today there's no way to compose them through Kale without dropping down to the KFP SDK manually. This project extends Kale with multi-notebook composition and a visual pipeline editor. Each notebook declares typed inputs and outputs (KFP artifacts like Dataset, Model, Metrics or parameter types). A new workflow compiler processes multiple notebooks and compiles them into a single Kubeflow Pipeline, with each notebook becoming a KFP sub-pipeline that preserves its internal steps. A visual editor built as a JupyterLab DocumentWidget handles assembly ,drag notebooks onto a canvas, connect typed ports, compile and run. Deliverables: #1.Notebook interface declaration system (backend + frontend) — explicit typed inputs/outputs per notebook, integrated into existing NotebookConfig and the Kale sidebar UI #2. Workflow data model and .kale-workflow file format with DAG validation (cycle detection, type checking, reference resolution) #3. Workflow compiler that processes each notebook through the existing NotebookProcessor → Compiler pipeline, wraps output as sub-pipelines, and generates a top-level KFP pipeline wiring them together through artifacts #4. CLI support: kale --workflow path/to/workflow.json #5. Visual DAG editor in JupyterLab using React Flow — drag-and-drop from file browser, typed port connections, properties panel, compile/run actions via Kale's existing RPC layer #6. End-to-end tests on a real KFP cluster, user documentation, and example workflows

pythontensorflowkubernetes+5
Student: Yash_vrd
Code

Linux-Intelligence-OCR-Solution(LIOS) - Enhancement

advanced
Zendalona•2025Varies350h (Large)

Summary: The goal of this project is to improve the Linux-Intelligent OCR Solution (LIOS), an open-source tool for text extraction from images, scanned documents, and PDFs using Tesseract and Cuneiform OCR engines. The primary focus will be on enhancing usability, accessibility, and performance, particularly for visually impaired users, while also addressing several existing issues. Problem: LIOS is a powerful tool, but there are several issues that hinder its usability and accessibility. These include problems with the UI/UX design, scanner compatibility, OCR integration, and the lack of proper error handling, which often leads to crashes. Additionally, there are several other bugs that need attention, such as issues with text focus, icon display, and preview functionality. Solution: The project will focus on addressing these issues and improving the overall user experience: UI/UX Improvements: Simplify the interface and improve accessibility, particularly for low-vision users. Bug Fixes & Code Refinements: Address the following specific issues: Text Focus: Ensure the textview regains focus after using Goto Line and Goto Page. Tab Focus: Improve tab focus handling for better navigation. Icon Display: Fix the larger icon issue in the icon view for consistent UI presentation. Print Preview: Fix the Print Preview functionality, which currently isn’t working as expected. Error Handling: Implement proper error handling to prevent crashes and unexpected behavior. Image Rotation: Resolve the automatic deletion issue when rotating selected areas of the image. Find/Replace Accessibility: Ensure the Find and Find & Replace features are fully accessible and functional. Scanner Compatibility: Improve compatibility with various scanner models, ensuring better cross-platform support. Tesseract Integration: Enhance the detection of Tesseract data paths for more accurate OCR functionality.

pythonjavascriptandroid+2
Student: Nihal_Rodge
Code
Proposal

macOS app bundle (175 hours)

intermediate
Synfig•2025Varies175h (Medium)

The current macOS app bundle creation process for Synfig relies on an outdated Bash script that is slow, error-prone with incorrect paths, and lacks code signing, hindering efficient distribution and user trust. This project aims to replace the script with a robust, automated solution to streamline bundle generation, ensure macOS security compliance, and enhance the native user experience. By leveraging Python for dependency collection, C++ for environment setup, and CMake/CPack for packaging, the project will deliver a signed, distributable SynfigStudio.app bundle. Key improvements include faster dependency gathering, proper code signing, embedded environment setup, Python/lxml integration, and macOS-native interface enhancements. Approach: • Develop a Python script to efficiently collect and stage dependencies, optimizing with caching and parallelization. • Implement code signing in reverse dependency order using codesign, including Python and lxml binaries. • Remove the external launcher script by embedding environment setup in the C++ entry point. • Package Python and lxml into the bundle, ensuring compatibility and signing. • Integrate CPack into CMake to generate a polished .dmg installer. • Enhance the UI with macOS-native menu bar and window behaviours using GTK. Deliverables: • A CMake/CPack-based build system producing a signed SynfigStudio.app bundle. • A Python script for automated dependency collection and path rewriting. • Code signing support for all binaries, including Python and lxml. • Embedded environment setup within SynfigStudio, eliminating the launcher script. • A bundled Python runtime with lxml, fully signed and functional. • A distributable .dmg installer generated via CPack. • macOS-native UI improvements (e.g., menu bar, shortcuts, dialogs boxes). • Comprehensive documentation covering installation, usage, and build instructions.

c++gtkgtkmm+2
Student: Nitish Itankar
Code
Proposal

Developing Distributed Algorithm for Metagenomic Error Correction and Assembly

beginner
Alaska•2025Varies90h (Small)

Metagenomic assembly is essential for understanding microbial communities, but existing tools often struggle with fragmented genomes, misclassified errors, and scalability issues. My goal is to develop a distributed algorithm for error correction and assembly, making it easier to process large and complex metagenomic datasets efficiently. To achieve this, I plan to use distributed computing frameworks like Dask to improve scalability, ensuring that even terabyte-scale datasets can be handled smoothly. I also aim to design better error correction techniques to preserve low-abundance species and improve assembly accuracy. Additionally, I want to explore GPU acceleration and machine learning to refine error detection and optimize processing times. At the core of my approach is a distributed de Bruijn graph assembly algorithm that constructs graphs from k-mers while clustering and annotating nodes based on coverage, GC content, and paired-end data. Unlike existing tools like Velvet (designed for single-genome assembly) and MetaVelvet (for metagenomic assembly), my method will efficiently break down graphs into species-specific subgraphs, reducing errors and improving the quality of the final assemblies. This will lead to better contig generation, taxonomic classification, and error correction, while also ensuring the method scales well for large datasets. Deliverables: 1. A distributed error correction module that improves accuracy while retaining biologically important data. 2. An optimized assembly pipeline to generate high-quality contigs and scaffolds for taxonomic and functional analysis. 3. A novel species-aware de Bruijn graph decomposition to improve metagenomic assembly and reduce errors. 4. Scalability improvements to ensure smooth performance across HPC clusters and cloud platforms. 5. AI/ML enhancements to improve error correction and sequencing accuracy. 6. Comprehensive documentation and testing to make the tool easy to use and reproducible.

pythonmysqljava+2
Student: Gauri Ket
Code

Edge-Cloud Collaborative Framework for Embodied AI Applications (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>This project aims to explore how KubeEdge can support real-world embodied AI applications, where intelligent devices such as robots, inspection systems, or autonomous mobile platforms need to perceive, process, and respond in edge environments.</p><p>The mentee will select a representative embodied AI scenario and build an end-to-end edge-cloud collaboration solution with KubeEdge. The solution should cover device or data source access, edge-side data processing, lightweight AI inference, cloud-edge synchronization, and system behavior under unstable network conditions.</p><p>Through this project, the community will gain a reproducible reference implementation that demonstrates how KubeEdge can be used as the infrastructure foundation for embodied AI workloads.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Select a specific scenario related to embodied intelligence.</p><p>&nbsp;- Set up the KubeEdge edge-cloud environment: complete the deployment and configuration of CloudCore and EdgeCore, enable edge node access, and verify status synchronization and basic communication capabilities.</p><p>&nbsp;- Implement a closed loop for device access and edge AI inference: complete device or data source access, data collection, device status modeling, deployment of edge-side AI inference services, and inference result reporting.</p><p>&nbsp;- Verify edge-cloud collaboration and edge autonomy: implement cloud-side model delivery, configuration updates, and data aggregation, and verify continuous edge operation and recovery synchronization under weak network or disconnected scenarios.</p><p>&nbsp;- Provide reproducible engineering assets and evaluation documents, including architecture diagrams, KubeEdge configuration files, deployment and validation scripts, sample data, running instructions, and performance and reliability evaluation reports.</p><p><br></p>

TBA
Proposal

Package LLM Inference Libraries

intermediate
Debian•2025Varies175h (Medium)

Package Large Language Model (LLM) inference libraries, in particular vLLM. It is needless to explain how LLMs are important. Currently, the Debian archive only has PyTorch, but downstream applications are still missing. One of the most promising downstream applications is LLM inference. There are already people working on llama.cpp and Ollama, but vLLM still lacks lots of dependencies to land onto Debian. For multi-GPU inference and concurrency, vLLM has its advantages over llama.cpp. The missing packages are, for instance, transformers, huggingface-hub, etc. This project involves the Debian packaging work for vLLM and its dependencies that are missing from Debian, as well as fixing issues (if there are any) in existing packages to make vLLM work. Timelplan ~ 5/8: Start with the architecture-independent package and non-cuda variant. 5/8 ~ 6/1: I will start with the architecture-independent package and non-cuda variant. I already created the package for huggingface-hub so I think this is a good start and doesn't take much time. By this time, I will finish the package for tokenizers packaging. 6/1 ~ 6/30: Create the package for the transformers package. Then I will finish rest of the package for the vLLM package. 6/30 ~ 7/18: I will try to build the vLLM package with cuda variant. Now, I already checked that vllm works on CUDA 12.4 so I will try to build the package with CUDA 12.4 with a specific GPU(Maybe T4?). 7/18: Mid-term evaluation 7/19 ~ 7/30: Try to build the vLLM package with multiplatform. I will try to build the package with different CUDA versions and different architectures, including a multi-GPU environment. I will get the feedback from the mentor and continue to the next step. 8/1 ~ 8/25: I will try to finish the project as soon as possible and try to fix the issue. If I have some more time, I will continue with the SGLang packaging. 8/25 - 9/1: submit final work product.

pythonjavascriptc/c+++8
Student: k1000dai
Code
Proposal

RISC-V ACT Framework Enablement and M-Mode Firmware Validation on Hardware Board Mentorship Project

Intermediate
•Varies175h (Medium)

<p><span style="color: rgb(67, 67, 67);">The RISC-V ecosystem currently lacks a streamlined and reproducible workflow for executing Architecture Compliance Tests (ACT) on real hardware platforms such as the Vision five 2, Milk-V Jupiter board. While ACT frameworks are widely used in simulation environments, running these tests directly on hardware involves complex boot flows (SPL, OpenSBI, U-Boot), firmware configuration, and low-level debugging. This creates a barrier for developers and new contributors who aim to validate RISC-V implementations in practical environments.</span></p><p><br></p><p><span style="color: rgb(67, 67, 67);">This mentorship project aims to bridge that gap by developing a minimal and reusable M-mode firmware runner capable of loading and executing ACT ELF binaries on the hardware platform. The mentee will explore the board’s boot architecture, implement ELF loading mechanisms, handle trap/debug scenarios (e.g., illegal instructions, FPU enablement), and establish communication via UART for result reporting. A key focus will be enabling reliable PASS/FAIL detection using the standard tohost interface and ensuring execution correctness through memory and cache coherency handling.</span></p><p><br></p><p><span style="color: rgb(67, 67, 67);">The project will follow a structured implementation path: initial environment setup and ACT framework familiarization, followed by firmware development and debugging, and finally automation and documentation. The mentee will create scripts to run multiple ACT tests, capture logs, and generate validation reports. All deliverables will be open-sourced, including firmware, tooling, and step-by-step documentation, contributing a practical reference workflow for RISC-V hardware validation and supporting broader community adoption as per Company Policy.</span></p>

TBA
Proposal

Quantum Resource Analysis and Benchmarking

advanced
Machine Learning for Science (ML4SCI)•2026Varies350h (Large)

Frameworks like PennyLane and Qiskit handle circuit construction and simulation well but provide almost no tools for measuring the quantum resources a circuit uses. No unified library exists to assess profiling entanglement, magic, or Bell nonlocality. I propose a PennyLane-based library computing four resource classes through a single resource_profile() API: entanglement (Meyer–Wallach, Von Neumann entropy, concurrence), magic (Stabilizer Rényi Entropy), mana (discrete Wigner negativity for qudits), and Bell nonlocality (CHSH values). Since PennyLane QNodes are differentiable, the measures inherit gradient access for tracking resource shifts during training. I also propose benchmarking across QAOA for MaxCut, Quantum Phase Estimation, VQE for molecular ground states (H₂, LiH), and quantum autoencoders for BSM event detection following Duffy et al. (arXiv:2407.07961). The study would record resource trajectories per epoch and test whether the resource decrease Duffy et al. observed generalizes, via Spearman correlations and Mann–Kendall trend tests. This project grows out of my prior work. My Quantum Encoding Atlas library (DOI: 10.5281/zenodo.18780936) benchmarks 16 encodings across PennyLane, Qiskit, and Cirq, and my 12 QMLHEP15 evaluation tasks span quantum circuits, GNNs, equivariant QNNs, RL for PQC optimization, and contrastive learning. Running those benchmarks I identified SRE as a missing diagnostic, which inspired me towards this project. Deliverables: 1. Python package on PyPI with entanglement, magic, mana, and nonlocality modules. 2. Circuit profiler for epoch-level resource tracking. 3. Benchmarking dataset for all four algorithms. 4. Resource–performance correlation analysis. 5. API docs and Jupyter notebook tutorials. 6. Two blog posts per ML4SCI requirements. Stretch: tensor network SRE approximations beyond 10 qubits and integration with Knipfer et al.'s agent-based VQC design (arXiv:2602.19387).

pythonmachine learningc+++2
Student: ashutoshm1771
Code

Plugin Developer Playground: Interactive UI Schema Editor (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>OpenEverest is an open-source cloud-native database platform that helps developers deploy and manage PostgreSQL, MySQL, MongoDB, and other databases on Kubernetes. In V2 it uses a plugin architecture where database providers define their UI through declarative YAML schemas (UISchema in Provider CRD). Currently, plugin developers have no integrated tool for developing and testing these schemas — the only way to see the rendered result is to deploy a full Provider CRD into a running Kubernetes cluster, making the development cycle slow and error-prone. This project aims to build a Plugin Developer Playground — a page inside OpenEverest where plugin developers can write UISchema YAML, see the rendered form in real time, validate the schema structure, inspect the post-processed API payload, and save/share schemas, all without deploying to a cluster. The mentee must solve the CSP compatibility problem by either choosing a CSP-compliant code editor or proposing an isolation architecture (e.g., sandboxed iframe) that keeps the main application's strict security posture intact.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Split-pane YAML editor with syntax highlighting and live form preview using the existing `UIGenerator` component</li><li>Real-time schema validation: YAML parsing errors and structural validation against the `TopologyUISchemas` type, with inline error markers in the editor</li><li>Live form rendering with stepper navigation through schema sections and topology switching</li><li>Dynamic field support: existing API provider fields load real data from the running OpenEverest instance; new/unknown provider types can be mocked</li><li>Output panel displaying the JSON payload after form data post-processing</li><li>CSP-compliant solution</li><li>Unit tests for core logic (schema validation, persistence, mock data injection) and component tests for key panels</li><li>Plugin developer guide for using the playground and the UISchema format</li></ul>

TBA
Proposal

Integrating Kmesh into Headlamp UI (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>[Headlamp](https://headlamp.dev) is an open-source, extensible Kubernetes web UI offering easy cluster management, multi-cluster support, RBAC, and a plugin system for adding custom functionality. Users who work with Kmesh today have to switch back and forth between Headlamp (for general Kubernetes resource management) and CLI tools / `kubectl` (for Kmesh-specific inspection), which creates a fragmented workflow and a poor user experience. There is currently no simple visual way to view Kmesh resources, inspect waypoints and related components, understand overall mesh status, or troubleshoot issues quickly from within an interface users already use. This project proposes building a Headlamp plugin for Kmesh that brings Kmesh resources directly into the Headlamp UI, providing lightweight visibility of Kmesh resources alongside other Kubernetes resources. The full-featured Kmesh dashboard remains the place for advanced operations; the Headlamp plugin focuses on reducing context switching and improving ease of use for day-to-day workflows.</p><p><br></p><p><br></p><p>Expected Outcome:</p><p><br></p><p>&nbsp;- A Headlamp plugin (TypeScript/React) that registers Kmesh CRDs and surfaces them as first-class resources in the Headlamp UI.</p><p><br></p><p>&nbsp;- List and detail views for core Kmesh resources (e.g., waypoints and eBPF map)</p><p><br></p><p>&nbsp;- Visual indicators of mesh status: per-resource health, readiness, and recent Events; cluster-level summary of Kmesh components.</p><p><br></p><p>&nbsp;- Inspection helpers: pretty-printed YAML, related-pod views, and quick links to associated workloads/services.</p><p><br></p><p>&nbsp;- Documentation (README, screenshots, install guide) and a published plugin (Helm/manifest or Headlamp plugin registry entry).</p><p><br></p><p>&nbsp;- Unit/component tests for the plugin and an end-to-end smoke test against a kind/minikube cluster running Kmesh.</p>

TBA
Proposal

Repository Service for TUF (RSTUF) 2026 Mentorship Project

Intermediate
•Varies175h (Medium)

<p><span style="background-color: transparent; color: rgb(0, 0, 0);">The purpose of this project is to enhance the (</span><a href="https://openssf.org/projects/repository-service-for-tuf/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">Repository Service for TUF RSTUF</a><span style="background-color: transparent; color: rgb(0, 0, 0);">) implementation by tackling critical areas that would significantly improve its functionality, scalability, and ease of adoption. RSTUF is designed to manage content distribution efficiently using the TUF (</span><a href="https://theupdateframework.io/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">The Update Framework</a><span style="background-color: transparent; color: rgb(0, 0, 0);">), but it currently has areas where improvements in delegation flexibility, performance, testing, and documentation are needed. This project will allow RSTUF to handle larger and more complex scenarios, while providing an improved experience for both developers and adopters.</span></p><p><br></p><h2><strong style="background-color: transparent; color: rgb(0, 0, 0);">Goal</strong></h2><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Add support for more signing schemes for hash-bin delegations under custom delegations: </strong><span style="background-color: rgb(255, 255, 255); color: rgb(0, 0, 0);">Enhance the flexibility of RSTUF’s delegation model to allow for more fine-grained delegation control</span></p><p><strong>TUF visualizer</strong>: Integration of a community-developed visualizer into RSTUF's deployment</p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Improve documentation to facilitate easier adoption</strong><span style="background-color: transparent; color: rgb(0, 0, 0);">: Enhance the user-facing documentation to make it clearer, more comprehensive, and more accessible for new adopters, thus accelerating the onboarding process.</span></p>

TBA
Proposal

LFDT - Improving Hyperledger Solang Through Comparative Analysis with the Soroban Rust SDK Mentorship Project

Intermediate
•Varies175h (Medium)

<p>Hyperledger Solang is a Solidity compiler to multiple non-EVM targets, including Stellar's Soroban. The Soroban VM is inherently different than the EVM. Also, How Solang translates Solidity to Soroban's WASM is different from the Rust SDK: A different storage layout, different encoding/decoding mechanisms and different optimizer passes as well.</p><p><br></p><p>The main smart contracts SDK for Soroban is&nbsp;<a href="https://github.com/stellar/rs-soroban-sdk" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">the Rust soroban SDK</a>. The purpose of this mentorship is to do an in-depth evaluation of Solang's soroban contracts runtime cost and behavior against the main Rust SDK. This evaluation is critical to Solang's health: We need a reproducible way to validate the design choices of how Solang handles storage operations and encoding/decoding on Soroban.</p><p><br></p><p>The mentorship will be in 3 stages:</p><ol><li>Getting familiar with Solang's code base. This could be done by implementing a Soroban specific feature in Solidity. This task will touch all stages of the compiler, thus enabling the mentee to get familiar with the code base as well as concepts around the Soroban VM and Solidity.</li><li>Implement a differential testing tool for the currently supported Soroban Solidity contracts. The tool should take an input a Solidity contract and a Rust contract, and should provide:</li><li class="ql-indent-1">Runtime cost comparisons, ideally by deploying to Solang's mock Soroban VM.</li><li class="ql-indent-1">Behavioral comparison.</li><li class="ql-indent-1">An interpretation of <span style="color: rgb(31, 35, 40);">the runtime cost for each contract, i.e number of Soroban host function calls, guest memory used, etc...</span></li><li>Publish a list of recommendations that Solang (or the Rust SDK) should improve. Recommendations should be backed up with evidence from the tool defined at stage 2</li></ol><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/74" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/74</a></p>

TBA
Proposal

LFDT - Implementation of a ZK-SNARK Token Driver for Hyperledger Fabric using gnark Mentorship Project

Intermediate
•Varies175h (Medium)

<p>This project aims to implement a new privacy-preserving token driver for the Hyperledger Fabric Token SDK. The architecture will follow the blueprint established in the paper "Privacy-preserving auditable token payments in a permissioned blockchain system" (Androulaki et al.), which outlines a token management system tailored for enterprise networks that requires binding tokens to user identities while supporting fine-grained auditing functionalities for AML/KYC compliance.</p><p><br></p><p>While the original paper relies on specific zero-knowledge proofs and commitments, this mentorship project will adapt the cryptographic backend to utilize zk-SNARKs via gnark, a high-performance ZK-SNARK library written in Go by Consensys. The mentee will be responsible for designing the required ZK circuits for minting, transferring, and auditing tokens, and subsequently integrating these circuits into a fully functional token driver within the Fabric Token SDK framework.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain a comprehensive understanding of the Hyperledger Fabric Token SDK architecture and the role of token drivers.</li><li>Develop practical expertise in Zero-Knowledge Proofs (zk-SNARKs) and circuit design using the gnark library.</li><li>​- Understand the cryptographic mechanisms behind privacy-preserving enterprise blockchains, including UTXO models, Pedersen commitments, and identity-bound token ownership.</li><li>Enhance skills in writing highly optimized, concurrent, and secure Go code for distributed systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>Fully functional gnark circuits implementing the logic for token issuance, private transfers, and auditor revelation as described in the blueprint paper.</li><li>A new ZK-SNARK token driver completely integrated into the Hyperledger Fabric Token SDK.</li><li>A comprehensive test suite, including unit and integration tests for the driver and circuits.</li><li>​- Performance benchmarks evaluating proof generation times, verification times, and transaction throughput compared to existing FTS token drivers.</li><li>Technical documentation detailing the circuit design, driver architecture, and usage instructions.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/67" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/67</a></p>

TBA
Proposal

Relationships and Solutions Architecture of Cloud Native Deployments (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This project focuses on expanding Meshery Relationships across a wide range of technologies, including Kubernetes and major cloud providers, to better model their interactions and improve user insights. There is a growing need to accurately model these relationships to provide better insights and control over deployments.</p><p><br></p><p>&nbsp;The next phase focuses on Cloud Solution Architecture through workload design by creating and publishing Meshery designs that use the newly developed relationships to represent real-world deployments. These designs will be turned into structured tutorials with hands-on labs using Meshery Playground, offering step-by-step guidance and interactive learning. All content will be reviewed by maintainers and published in Meshery’s official documentation</p><p><br></p><p>Responsibilities:</p><p>&nbsp;- Research and Analyze Technologies: Dive deep into various cloud-native technologies (e.g., different compute services, databases, messaging systems, network services, etc.) to understand their components and how they interconnect.</p><p>&nbsp;- Develop Relationship Definitions: Create and contribute relationship definitions, typically in JSON or YAML format, to the Meshery models.</p><p>&nbsp;- Model Inter-Technology Interactions: Focus particularly on defining relationships between components from different technologies (e.g., how a Kubernetes deployment relates to an AWS RDS instance, or how a Linkerd service interacts with a Prometheus monitoring component).</p><p>&nbsp;- Document New Relationships: Clearly document the newly defined relationships, their purpose, and how they are represented within Meshery designs, contributing to the official Meshery documentation.</p><p>&nbsp;- Create and publish designs that use newly developed relationships.</p><p>&nbsp;- Create and publish hands-on tutorials using Meshery Playground, featuring step-by-step guides and interactive labs that enable learners to apply concepts without the hassle of any configuration.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A multitude of new intra- and inter-service relationships defined across AWS, Azure, and GCP.</p><p>&nbsp;- Creation and publishing of real-world workload designs that represent cloud solution architectures using the newly defined relationships.</p><p>&nbsp;- Tutorials reviewed by various project maintainers and then published in guides/tutorials.</p><p>&nbsp;- Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.</p><p><br></p>

TBA
Proposal

AI-Powered Trace Analysis Phase 2 - Skills Framework (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Jaeger is the industry-standard platform for distributed tracing. As microservice architectures grow complex, finding root causes in massive trace data becomes increasingly difficult. While Phase 1 of this initiative established a baseline AI assistant for natural language search, the system currently relies on hard-coded capabilities. This project (Phase 2\) aims to transform the Jaeger AI agent from a static chatbot into an extensible, user-programmable platform. The primary objective is to implement a "Self-Service Skills" framework, architecturally similar to "Claude Code Skills." This will allow end-users to teach the Jaeger AI new debugging workflows (e.g., "Analyze Critical Path" or "Detect N+1 Queries") by simply adding configuration files containing system prompts and logic rules, without needing to recompile the Jaeger binary. The applicant will build this extension within the Jaeger v2 (OpenTelemetry-based) architecture, utilizing **LangChainGo** to orchestrate interactions with Language Models (SLMs/LLMs). This project bridges the gap between generic AI reasoning and domain-specific observability expertise.</p><p><br></p><p>**Expected Outcome:**</p><p>&nbsp;- **Skills Engine Implementation:** An approach compatible with our [BYOA (bring your own agent)](https://docs.google.com/document/d/1qD0OpyRfq-JbO6MCB5gmVxsdPcpPhxz1R_pPnKDdYOg/edit?tab=t.0#heading=h.qgr5ifum0a9m) direction that dynamically discovers, validates, and loads user-defined "Skills" (prompts and tool definitions) from configuration.</p><p>&nbsp;- **Smart Analysis Features:** A polished implementation of Natural Language Search and Contextual Trace Explanation that intelligently leverages these loaded skills.</p><p>&nbsp;- **Local-First Support:** Verified compatibility with local model runners (e.g., Ollama, Llama.cpp) to ensure deterministic performance without sending data to public clouds.</p><p>&nbsp;- **UI Integration:** Enhancements to the Jaeger React UI to expose these AI capabilities and visualize the "reasoning steps" taken by the agent.</p><p>&nbsp;- **Documentation:** A complete guide for users on "How to Author Custom AI Skills for Jaeger."</p><p>- **Learning Opportunities:**</p><p>&nbsp;- **Agentic AI Architecture:** Learn to design stateful AI agents in Go that utilize "Tool Calling" and "Reasoning Loops" rather than simple text generation.</p><p>&nbsp;- **OpenTelemetry Internals:** Gain deep familiarity with the OpenTelemetry Collector architecture, as Jaeger v2 is built directly on top of it.</p><p>&nbsp;- **Cloud-Native Engineering:** Experience contributing to a graduated CNCF project, including navigating code reviews, writing design docs (RFDs), and adhering to open-source best practices.</p><p>&nbsp;- **Full-Stack Development:** Practical experience bridging a complex Go backend with a modern React frontend.</p><p><br></p>

TBA
Proposal

LFDT - Extending Hiero Enterprise Java with Smart Contract Event and Log APIs Mentorship Project

Intermediate
•Varies175h (Medium)

<p>The&nbsp;<a href="https://github.com/hiero-ledger/hiero-enterprise-java" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">hiero-eneterprise-java</a>&nbsp;project provides a layer on top of Hiero SDKs to integrate Hiero functionality in enterprise java applications that are based on frameworks like JakartaEE, Microprofile, Quarkus or Spring Boot. Instead of just defining the SDK API, the project creates a layer on top of it by providing services and repositories for an easier and integrated interaction with any Hiero based network.</p><p><br></p><p>The project invests in rich and easy to use APIs to interact with smart contracts. While deploying smart contracts and calling functions of contracts is already part of the project, the log and event functionality of smart contracts is missing. This functionality allows smart contract functionalities to share information with external observers of the contract. Hiero events and logs of smart contracts can be accessed by the&nbsp;<a href="https://github.com/hiero-ledger/hiero-mirror-node" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">Hiero mirror node</a>. Sadly the workflow is very complex, and now easy to use API exists to easily receive events for a specific smart contract instance.</p><p><br></p><p>This project should extend hiero-enterprise-java by providing a new public API and implementation for events and log observation of smart contracts.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Understanding smart contracts and Solidity as smart contract language.</li><li>Understanding best practices for creating smart contracts.</li><li>Deploy smart contracts and interact with smart contracts on an Hiero based network.</li><li>Understand the Hiero SDKs.</li><li>Understand the Hiero Mirror Node.</li><li>Learn about hiero-eneterprise-java and best practices for providing functionality to enterprise Java frameworks.</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><p>The successful completion of this project will result in new code and modules in the hiero-eneterprise-java project. Tests, documentation and samples of the new functionality are part of the expected outcome.</p><p><br></p><p>Mostly, all new content will be part of the hiero-eneterprise-java project (excluding stand alone examples).</p><p><br></p><p>We expect that events and logs of any deployed smart contracts can be observed by the API (by using callbacks).</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/70" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/70</a></p>

TBA
Proposal

Minder 2026 Mentorship Project

Intermediate
•Varies175h (Medium)

<p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Program Overview</strong></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">This proposal outlines a 12-week mentorship program focused on significantly enhancing the rule testing and Continuous Integration (CI) tooling for Minder's security policies. The project will primarily involve the go programming language, with secondary exposure to rego, python, and shell scripting. The successful completion of this project will provide Minder users with a robust, automated, and maintainable framework for ensuring the quality and correctness of custom security rules.</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">This opportunity is open for a single mentee with some previous GitHub and medium-sized project experience.</span></p><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Program Goals</strong></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">The primary goals of this 12-week engagement are to:</span></p><p><br></p><ol><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Improve Rule Testing Tools: Develop a standalone testing command for Minder rules.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Robust Testing: Allow for the definition and execution of multiple distinct test cases against a single rule.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Focus on Local Execution: Tests should be able to execute locally without requiring network access to external resources.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Support Diverse Data Ingestion: Design the framework to accommodate tests for rules covering all current data ingestion methods: REST API, Git repositories, and declared </span><a href="https://docs.mindersec.dev/understand/data_sources" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(31, 31, 31);">data sources</a><span style="background-color: transparent; color: rgb(31, 31, 31);">.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Provide Automated CI Tooling: Implement CI workflows to automatically detect and run tests.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Update Existing Rules: Migrate and update existing tests within the github.com/mindersec/minder-rules-and-profiles repository to utilize the new framework.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Documentation and UX: Create documentation for the new tooling and address potential client-side UX issues related to testing.</span></li></ol><p><br></p><p><br></p>

TBA
Proposal

SONiC OS Profiling Mentorship Project

Intermediate
•Varies175h (Medium)

<p>*APPLICATIONS ONLY OPEN TO US BASED COLLEGE STUDENTS*</p><p><br></p><p>1. Problem Statement</p><p><br></p><p>Today, SONiC KVM-based PR testing validates functional correctness (test pass/fail) but does not track resource consumption or performance characteristics over time. This creates several blind spots:</p><p><br></p><ul><li>Performance regressions (CPU spikes, memory leaks, excessive I/O) introduced by PRs go undetected until they reach production or nightly pipelines.</li><li>There is no historical baseline of resource utilization per feature branch, making it impossible to distinguish normal variance from genuine degradation.</li><li>Nightly test environments lack systematic profiling, so gradual performance erosion across releases is invisible until a tipping point is reached.</li><li>Root-cause analysis of production incidents is hampered by the absence of correlated profiling data from the CI/CD stage where the regression was introduced.</li></ul><p><br></p><p>Without a structured profiling database and automated anomaly detection, the team operates reactively—discovering performance issues in production rather than catching them at the PR gate.</p><p><br></p><p>2. Proposed Solution</p><p><br></p><p>Build an end-to-end performance profiling pipeline that runs alongside SONiC KVM-based test execution, stores results in a centralized database, and automatically flags regressions at the PR gate.</p><p><br></p><p>2.1 High-Level Architecture</p><p><br></p><p>The solution is composed of four core components that integrate into the existing CI/CD and nightly test workflows:</p><p><br></p><ul><li>Profiler Container – A lightweight Docker container packaging the community profiler (e.g., py-spy, perf, cProfile) that runs in sidecar mode alongside the SONiC KVM during test execution.</li><li>Profiling Database – A remote time-series/relational database (e.g., PostgreSQL + TimescaleDB or InfluxDB) that stores per-run profiling snapshots keyed by feature branch, commit SHA, test case, and timestamp.</li><li>Analysis Engine – A statistical analysis module that performs comparative, clustering, and outlier detection on profiling data to identify spikes against historical baselines.</li><li>PR Gate Integration – A CI pipeline step that queries the analysis engine after test completion and fails the PR if any metric exceeds the configured threshold.</li></ul><p><br></p><p>3. Mentorship Objectives</p><p><br></p><ul><li>Help the mentee learn about SONiC OS architecture, container ecosystem, and KVM-based testing infrastructure.</li><li>Help the mentee gain hands-on experience with performance profiling tools (py-spy, perf, pidstat) and statistical analysis techniques.</li><li>Help the mentee understand CI/CD pipeline integration and automated quality gates.</li><li>Work with virtual SONiC testbeds (vsonic) to develop and validate the profiling pipeline without physical hardware.</li><li><strong>This is a summer term program, Mentees are expected to work 40~ hours a week</strong></li></ul>

TBA
Proposal

Policy-as-Code Engine for Open Source AI Agent Orchestration (Unpaid)

Intermediate
•Varies175h (Medium)

<p>Open source projects face an urgent governance gap as AI coding tools (Claude Code, GitHub Copilot, Cursor, Qwen Code) act on codebases with no shared coordination layer, no policy enforcement, and no auditable trail. The result is PR floods, duplicate issue work, and maintainer burnout.</p><p><br></p><p>GitMesh is an LFDT-native multi-agent orchestration runtime that closes this gap. This mentorship will implement&nbsp;Phase 1 (GitHub/GitLab Forge Integration)&nbsp;and&nbsp;Phase 2 (Policy-as-Code Engine)&nbsp;— building the&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">forge-sync</code>&nbsp;bidirectional webhook service, the&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">policy-engine</code>&nbsp;OPA integration with YAML-to-Rego auto-compilation, an append-only audit log with policy enforcement metadata, and a three-view maintainer dashboard. Real infrastructure, deployed to a live LFDT lab.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Build a bidirectional webhook-based forge integration (GitHub/GitLab) with event-triggered agent wakeups.</li><li>Design a policy-as-code engine using OPA with YAML-to-Rego auto-compilation and real-time evaluation middleware.</li><li>Implement an append-only audit log capturing policy version and enforcement outcome for every agent action.</li><li>Build a maintainer approval dashboard (Active Agents, Pending Approvals, Audit Log) with mobile-first UX.</li><li>Learn AI agent coordination patterns — atomic checkout, budget enforcement, heartbeat scheduling.</li><li>Gain exposure to LFDT identity extension points (Hyperledger Identus, AnonCreds, Sigstore) planned for the future trust layer.</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ol><li>Forge Integration Service&nbsp;— Bidirectional GitHub/GitLab webhook receiver and outbound action service (post comment, add label, request review, close issue). Includes raw webhook storage and event-triggered agent wakeup support.</li><li>Policy Engine&nbsp;— OPA integration with YAML-to-Rego auto-compilation. Policy evaluation middleware injected into all agent heartbeats and API routes.</li><li>Audit Log Enhancement&nbsp;—&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">policyVersion</code>&nbsp;and&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">policyOutcome</code>&nbsp;columns on the activity log. Append-only, exportable as JSON/CSV, filterable by agent/action/time/outcome.</li><li>Three-View Maintainer Dashboard&nbsp;— Active Agents (status, budget), Pending Approvals (mobile-first), Audit Log (policy filtering).</li><li>Default Policy Template Library&nbsp;— Five ready-to-use YAML rulesets (no-merge-without-approval, no-CI-modification, security-advisory-gate, budget-hard-stop, triage-scope-limits).</li><li>Documentation&nbsp;— Architecture diagram, developer onboarding guide, YAML policy authoring reference, end-to-end test scenarios.</li></ol><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/81" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/81</a>.</p>

TBA
Proposal

DPU-Accelerated OVS Offload Mentorship Project

Intermediate
•Varies175h (Medium)

<p>About the project</p><p>OPI (Open Programmable Infrastructure), a Linux Foundation project, defines vendor-neutral</p><p>standards and tooling for DPUs / IPUs. This internship produces a reference blueprint for</p><p>running VM networking through OVS that is fully hardware-offloaded to a DPU - first under</p><p>vanilla KVM on RHEL, then under OpenShift Virtualization. NVIDIA BlueField-3 (BF3) is the</p><p>reference platform because it ships a complete, mature stack (OVS-DOCA, vDPA, and DPF).</p><p>The blueprint then generalizes to a second DPU / IPU vendor (Intel IPU or Marvell Octeon).</p><p>What you&amp;#39;ll work on</p><p>The work runs as two tracks. Track 1 (BF3) is the proven reference; Track 2 ports it to a second</p><p>vendor and surfaces the gaps that need upstream work.</p><p>Track 1 - BF3 reference</p><p>• KVM on RHEL with OVS fully offloaded to BF3 in DPU mode via OVS-DOCA. KVM / libvirt</p><p>guests attach over vDPA so the guest runs stock virtio-net while the datapath is</p><p>accelerated in hardware. Validate offload is actually in hardware, baseline performance,</p><p>and exercise live migration. This is the reference blueprint.</p><p>• OpenShift Virtualization on BF3 via NVIDIA DPF, with accelerated OVN-Kubernetes</p><p>(OVS-DOCA) offloaded to the DPU and KubeVirt VMs riding the offloaded fabric.</p><p>Track 2 - second vendor (Intel IPU or Marvell Octeon)</p><p>• KVM on RHEL with OVS offload and vDPA using the vendor&amp;#39;s stack (Marvell: in-kernel</p><p>octeon_ep vDPA driver and Octeon SDK; Intel: IPDK / P4 and IDPF). Document the deltas</p><p>from the BF3 reference.</p><p>• OpenShift Virtualization on the second vendor via the OPI / Red Hat DPU Operator.</p><p>Identify and contribute the work needed to reach full primary-datapath OVS offload and</p><p>KubeVirt enablement, since the operator today centers on network-function offload and</p><p>service function chaining rather than the full offloaded OVN datapath that DPF provides on</p><p>BF3.</p><p><br></p><p>Required</p><p>• Linux, Red Hat family (RHEL 9 / 10): systemd, networking stack, kernel modules, and</p><p>hands-on troubleshooting</p><p>• KVM / libvirt / QEMU: VM lifecycle, virtio / vhost, and vDPA (vhost-vdpa) concepts</p><p>• OVS: bridges, flows, OpenFlow, datapath internals, and hardware-offload concepts</p><p>(switchdev / eswitch mode, VF / SF representors)</p><p>• Kubernetes: core concepts, CRDs, operators, and CNI / pod networking - enough to grow</p><p>into OpenShift Virtualization and OVN-Kubernetes</p><p>• Networking fundamentals: L2 / L3, VLAN, VXLAN / Geneve, SR-IOV (PF / VF / SF), and</p><p>throughput / pps testing</p><p><br></p><p>2</p><p><br></p><p>Preferred (a plus)</p><p>• OVS-DOCA and the DOCA SDK / DPF (DOCA Platform Framework) on BlueField</p><p>• vDPA hands-on: mlx5_vdpa, octeon_ep, vhost-vdpa, libvirt vDPA, and vdpa netlink /</p><p>iproute2</p><p>• OVN / OVN-Kubernetes; OpenShift / OpenShift Virtualization (CNV / KubeVirt)</p><p>• OPI DPU Operator, and vendor offload stacks: Intel IPDK / P4 / IDPF, Marvell Octeon</p><p>SDK</p><p>• Go (operator development), Python, and Bash</p><p>• Prior open source contribution (public Git workflow, mailing lists / Slack); familiarity with</p><p>OPI</p><p><br></p><p><br></p>

TBA
Proposal
Showing 5953 - 5976 of 5976 Projects
247248249
Proposal
Proposal
Proposal