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.

PlatformProgramsOrganizations

Explore Organizations

Discover open-source organizations actively accepting contributors across GSoC, ESoC, LFX Mentorship, Outreachy, and more.

Clear all
Active:Program: LFX Mentorship
AI powered mainframe data modernization (unpaid) logoAI powered mainframe data modernization (unpaid)AI-Powered Operations Agent for Hyperledger Cello (Unpaid) logoAI-Powered Operations Agent for Hyperledger Cello (Unpaid)AI-assisted extraction of architectural parameters from RISC-V specifications logoAI-assisted extraction of architectural parameters from RISC-V specificationsAI-assisted extraction of architectural parameters from RISC-V specifications - Part II logoAI-assisted extraction of architectural parameters from RISC-V specifications - Part IIBGP-LS Cli dev & testing on 7-node vSONiC topo logoBGP-LS Cli dev & testing on 7-node vSONiC topoBiniBFT - Testing, Integration, and Documentation (Unpaid) logoBiniBFT - Testing, Integration, and Documentation (Unpaid)Broadening the RISC-V High Precision Code Base and Reach logoBroadening the RISC-V High Precision Code Base and ReachCloud Native Computing Foundation logoCloud Native Computing FoundationCreating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalar logoCreating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalarDPU Operator Enhancement logoDPU Operator EnhancementDPU-Accelerated OVS Offload logoDPU-Accelerated OVS OffloadDrasi logoDrasiAI powered mainframe data modernization (unpaid) logoAI powered mainframe data modernization (unpaid)AI-Powered Operations Agent for Hyperledger Cello (Unpaid) logoAI-Powered Operations Agent for Hyperledger Cello (Unpaid)AI-assisted extraction of architectural parameters from RISC-V specifications logoAI-assisted extraction of architectural parameters from RISC-V specificationsAI-assisted extraction of architectural parameters from RISC-V specifications - Part II logoAI-assisted extraction of architectural parameters from RISC-V specifications - Part IIBGP-LS Cli dev & testing on 7-node vSONiC topo logoBGP-LS Cli dev & testing on 7-node vSONiC topoBiniBFT - Testing, Integration, and Documentation (Unpaid) logoBiniBFT - Testing, Integration, and Documentation (Unpaid)Broadening the RISC-V High Precision Code Base and Reach logoBroadening the RISC-V High Precision Code Base and ReachCloud Native Computing Foundation logoCloud Native Computing FoundationCreating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalar logoCreating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalarDPU Operator Enhancement logoDPU Operator EnhancementDPU-Accelerated OVS Offload logoDPU-Accelerated OVS OffloadDrasi logoDrasiAI powered mainframe data modernization (unpaid) logoAI powered mainframe data modernization (unpaid)AI-Powered Operations Agent for Hyperledger Cello (Unpaid) logoAI-Powered Operations Agent for Hyperledger Cello (Unpaid)AI-assisted extraction of architectural parameters from RISC-V specifications logoAI-assisted extraction of architectural parameters from RISC-V specificationsAI-assisted extraction of architectural parameters from RISC-V specifications - Part II logoAI-assisted extraction of architectural parameters from RISC-V specifications - Part IIBGP-LS Cli dev & testing on 7-node vSONiC topo logoBGP-LS Cli dev & testing on 7-node vSONiC topoBiniBFT - Testing, Integration, and Documentation (Unpaid) logoBiniBFT - Testing, Integration, and Documentation (Unpaid)Broadening the RISC-V High Precision Code Base and Reach logoBroadening the RISC-V High Precision Code Base and ReachCloud Native Computing Foundation logoCloud Native Computing FoundationCreating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalar logoCreating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalarDPU Operator Enhancement logoDPU Operator EnhancementDPU-Accelerated OVS Offload logoDPU-Accelerated OVS OffloadDrasi logoDrasi

Showing 1–120 of 511 organizations

Browse projects
AI powered mainframe data modernization (unpaid) logo

AI powered mainframe data modernization (unpaid)

Linux Foundation

<p>Artificial Intelligence (AI) presents an opportunity to accelerate and de‑risk mainframe data modernization by automating the most complex and labor‑intensive aspects of understanding, extracting, and rebuilding legacy workloads.</p><p>This project will deliver a comprehensive framework that guides organizations through understanding legacy mainframe data structures, mapping those datasets to modern cloud‑based platforms, and applying effective methods for data transfer, quality checks, and validation. As part of this effort, the participant will also develop a demonstration application that showcases the practical implementation of key elements of the framework, illustrating how each component works together to support a successful modernization journey.</p><p><br></p><p>Deliverables:</p><p>A technical framework</p><p>A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>

research skillstechnical writtingai+4
1 active years2026
Explore
AI-Powered Operations Agent for Hyperledger Cello (Unpaid) logo

AI-Powered Operations Agent for Hyperledger Cello (Unpaid)

Hyperledger

<p>Hyperledger Cello is an enterprise-grade Blockchain-as-a-Service (BaaS) platform that provides a comprehensive REST API for managing the full lifecycle of Hyperledger Fabric networks (Network, Node, Channel, Chaincode). However, all current operations require users to interact manually through the Dashboard, which presents a steep learning curve for newcomers.</p><p><br></p><p>This project aims to implement an AI-powered operation agent with chatbot interface for Hyperledger Cello. It consists of two components:</p><p><br></p><ol><li>AI Agent Backend: A Python service that wraps Cello's existing REST APIs into LLM. It accepts natural language requests, invokes Cello operations, and returns structured responses. It also provides AI-assisted fault log summarization for common Fabric failures.</li><li>Chatbot UI&nbsp;— A chatbot interface integrated into Cello's existing Dashboard (React), allowing users to interact with the AI agent.</li></ol><p><br></p><p>The combined system enables a natural language-driven operational workflow:</p><p><br></p><p>User (chat message) → Chatbot UI → AI Agent → Cello REST API → Fabric Infrastructure</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Open Source Collaboration: Familiarity with Hyperledger Cello workflow, code review standards, and CI pipeline.</li><li>Full-Stack Engineering: Experience building a production-integrated feature spanning a Python backend and a React frontend.</li><li>Applied AI Engineering: Proficiency in LLM Tool Calling integration, streaming response handling, and prompt engineering.</li><li>Blockchain Infrastructure: Hands-on understanding of Hyperledger Fabric network topology, node types, and Chaincode lifecycle.</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Deliverable: AI Agent Backend</li><li>Acceptance Criteria: Python service exposing a chat API endpoint; supports natural language execution of core Cello operations (list/create networks, manage nodes, query channels and chaincodes)</li></ul><p><br></p><ul><li>Deliverable: Chatbot UI (Dashboard)</li><li>Acceptance Criteria: Chat panel integrated into Cello's existing React Dashboard; supports streaming responses; maintains multi-turn conversation context</li></ul><p><br></p><ul><li>Deliverable: Documentation</li><li>Acceptance Criteria: Setup guide for the AI agent</li></ul>

python programming in djangobasic react knowledgefamiliarity with git / github workflows+7
1 active years2026
Explore
AI-assisted extraction of architectural parameters from RISC-V specifications logo

AI-assisted extraction of architectural parameters from RISC-V specifications

RISC-V

1) Develop prompts & context size for LLMs that identify architectural parameters in the RISC-V privileged and unprivileged spec. a) Give examples from the manually created list (in UDB). b) Identify with textual excerpt from the specs. c) Classify the parameters as either dependent on a configuration, named or unnamed. 2) Use those prompts to collect a list of parameters using at least two different LLMs and the parameters documented in UDB. 3) Refine the prompts to address any differences between LLM and UDB results, as needed. a) Filter out any hallucinations as negative examples, e.g. doesn’t fall into any of the 1(c) categories or falls into the wrong category (could be context size dependent). b) Use some missing parameters as further prompt examples. 4) Create a Github PR to insert tags into the spec for each parameter in the resulting list, giving unique names to unnamed parameters according to the tag format spec, and using existing parameter names as examples.

llms for textual gen-aicoding assistantsgenerative ai or “classical ai”, especially natural language processing+4
1 active years2026
Explore
AI-assisted extraction of architectural parameters from RISC-V specifications - Part II logo

AI-assisted extraction of architectural parameters from RISC-V specifications - Part II

RISC-V

<p>This mentorship proposal extends an effort already underway to extract architectural parameters from the RISC-V ISA Manual using AI. It originally started as an RVI Mentorship for Spring 2026, and continued under the Parameter SIG. Although the results have improved steadily, we need further improvement in quality and implementation robustness. Hence the Fall mentorship proposes to:</p><p><br></p><p>1) Continue trying to find architectural parameters with LLMs in the RISC-V privileged and unprivileged spec, extending the initial work done in Spring 2026 mentorship. Use as training examples subsets of parameters from the manually created lists (and try to recreate the full lists) from the following efforts:</p><p><br></p><p>a. ISA Manual (per-chapter params in yaml format)</p><p>b. Google Drive (“keyword_matches” spreadsheet)</p><p>c. UDB yaml (enhance the current parameter recall process).</p><p><br></p><p>2) Extend the current classification scheme for parameters as needed.</p><p><br></p><p>3) Develop AI coding agents and skills for reproducible runs and reusable workflows (extending the prompt and context management in the current flow).</p><p><br></p><p>4) Explore integration of the tools developed for the ISA Manual based flow (in 1.a) to export the parameters in UDB yaml format.</p><p><br></p><p>5) Create a Github PR to publish the final reviewed parameter files in the appropriate repo and follow up with the maintainers on merging them.</p><p>&nbsp;</p>

generative aiisa specificationsparameterized modeling
1 active years2026
Explore
BGP-LS Cli dev & testing on 7-node vSONiC topo logo

BGP-LS Cli dev & testing on 7-node vSONiC topo

Linux Foundation

<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN THE UNITED STATES*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link-State Protocol (BGP-LS) is a critical protocol for modern network management and SDN-style controller integration, enabling the distribution of network topology information. Currently, SONiC's BGP-LS implementation lacks comprehensive CLI tools for configuration and monitoring, making it difficult for network operators to effectively deploy and troubleshoot BGP-LS in production environments. Additionally, there is insufficient testing infrastructure to validate BGP-LS functionality in complex multi-node topologies.</p><p>This mentorship program aims to address these gaps by developing a complete CLI interface for BGP-LS operations and establishing a robust 7-node testing framework based on vSONiC instances. This will significantly improve SONiC's BGP-LS usability and reliability, making it production-ready for enterprises and service providers who rely on topology discovery for traffic engineering and network automation.</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><ul><li>Develop a comprehensive CLI interface for BGP-LS configuration, monitoring, and troubleshooting in SONiC</li><li>Design and implement a 7-node test topology to validate BGP-LS functionality in complex network scenarios</li><li>Create automated test cases covering BGP-LS neighbor establishment, topology advertisement, and failure scenarios</li><li>Document CLI usage and testing procedures for community adoption and future development</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Complete BGP-LS sonic-cli implementation with commands for neighbor configuration, status checking, and topology visualization</li><li>Functional 7-node test environment with automated deployment scripts and topology configurations</li><li>Comprehensive test suite covering at least 15-20 BGP-LS scenarios including normal operations and edge cases</li><li>Technical documentation including CLI user guide, test topology design document, and contribution guidelines for future enhancements</li><li>Merge CLI codes into SONiC repo</li><li><strong>Program Length: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and/or C++ programming</li><li>Understanding of BGP routing protocols and network topology concepts</li><li>Familiarity with Linux CLI development and command-line interface design patterns</li><li>Experience with network testing frameworks (pytest, ansible Framework) or willingness to learn</li><li>Basic knowledge of SONiC architecture or similar network operating systems</li><li>Strong documentation and communication skills</li></ul>

pythonc++
1 active years2026
Explore
BiniBFT - Testing, Integration, and Documentation (Unpaid) logo

BiniBFT - Testing, Integration, and Documentation (Unpaid)

Linux Foundation

<p>To test the BiniBFT consensus developed, and to make it as a standalone plugin, and to document the algorithm and process.</p><p><br></p><p>Check&nbsp;<a href="https://github.com/BiniWorld/Hyperledger-BiniBFT/tree/binibft" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">GitHub branch</a>&nbsp;for the BiniBFT consensus developed, and&nbsp;<a href="https://github.com/BiniWorld/Hyperledger-BiniBFT/tree/main" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">GitHub page</a>&nbsp;for the previous work.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Deep understanding of consensus mechanisms</li><li>Testing and comparing different consensus algorithms</li><li>Developing standalone consensus plugins</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>To test the BiniBFT consensus developed</li><li>Integrate it to Fabric</li><li>Develop it into standalone plugin</li><li>Documentation</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/79" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/79</a>.</p>

godeep understanding of public and private consensus
1 active years2026
Explore
Broadening the RISC-V High Precision Code Base and Reach logo

Broadening the RISC-V High Precision Code Base and Reach

RISC-V

<p>We plan to refactor and recode Community AI / ML and HPC (double precision) applications to port them to RISC-V this summer. This is a large, potentially daunting effort but we anticipate building scripts and methods to be able to substantially automate the process. Priority will be given to codes that make the most impact. Here is the initial list of 400 codes we are optimizing and compiling for RISC-V this summer: <a href="https://tinyurl.com/2aau5b9r" rel="noopener noreferrer" target="_blank" style="background-color: rgb(255, 255, 255); color: rgb(17, 85, 204);">https://tinyurl.com/2aau5b9r</a><span style="color: rgb(34, 34, 34);">&nbsp;</span></p><p><br></p>

c++linuxversion control+2
1 active years2026
Explore
Cloud Native Computing Foundation logo

Cloud Native Computing Foundation

Cloud Infrastructure

The Cloud Native Computing Foundation (CNCF) hosts critical components of global cloud infrastructure, including Kubernetes and Prometheus.

gogolangkubernetes+2
1 active years2026
Explore
Creating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalar logo

Creating an Execution-Driven Version of Olympia, the Performance Model of example RISC-V superscalar

RISC-V

Performance models are essential tools in both academia and industry for analyzing the efficiency of superscalar processor micro-architectural features. Olympia is a widely adopted performance model within the RISC-V community. Performance models can be categorized as either trace-driven or execution-driven. Trace-Driven Models rely on an instruction trace, which is simply a sequence of retired instructions. Execution-Driven Models (EDM), in contrast, use the program binary and associated data. This allows EDMs to simulate not only the sequence of retired instructions but also speculatively fetched and executed instructions resulting from mis-speculations like branch mis-predictions and memory-dependency mispredictions. Consequently, execution-driven simulations offer greater accuracy in prediction. Currently, Olympia only supports trace-driven simulations. The central objective of this project is to develop an execution-driven version of Olympia using an outside functional modeling driver such as Pegasus or Whisper. The Olympia project must remain agnostic to the functional driver of EDM. Specifically, a user of Olympia should be able to provide their own functional model backend to drive EDM. The simulated frontend and backend must remain agnostic to the fact that it is running in EDM. To enable this, a generic API for EDM (virtual interface) must be developed to connect the Olympia model to the driver.

computer architecturec++performance modeling+1
1 active years2026
Explore
DPU Operator Enhancement logo

DPU Operator Enhancement

Linux Foundation

OPI project is aiming to expand the OpenShift DPU Operator to support NVIDIA, xSight, and/or Mangoboost hardware. The ideal candidate needs to be comfortable at the intersection of infrastructure software and hardware offloading. The expected skill set is a combination of low-level hardware abstraction skills and high-level Kubernetes operator patterns. Technical skills: Golang expertise Github, CI/CD, Linux Networking expertise (Strong understanding of SR-IOV, OVS-DPDK, and virtual functions (VFs)) Familiarity with the OPI APIs and how DPUs handle networking and storage offloading. Experience with developing Kubernetes Operators. Experience with operator-sdk or controller-runtime. They must understand Custom Resource Definitions (CRDs), Reconcile loops, and watch patterns. Understanding Vendor SDKs (ex: DOCA). Optional - Comprehensive knowledge of the OpenShift ecosystem

golanglinux networkingkubernetes operators+4
1 active years2026
Explore
DPU-Accelerated OVS Offload logo

DPU-Accelerated OVS Offload

Linux Foundation

<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>

linuxkvm/qemuovs+6
1 active years2026
Explore
Drasi logo

Drasi

Cloud Native Computing Foundation (CNCF)

Drasi is a Data Change Processing platform that enables developers to detect and react to meaningful data changes using declarative Cypher queries. Drasi excels at complex change detection with unique features like `drasi.trueFor()` (detecting conditions that persist over time) and absence-of-change detection (alerting when expected events don't occur). However, it currently lacks native connectivity to IoT protocols. Drasi Lib provides Drasi's powerful graph-aware decision engine as an embeddable Rust library that can run completely offline on constrained hardware—enabling edge computing scenarios where logic runs directly on sensors and gateways. IoT applications fundamentally need to detect state transitions, but developers typically must write boilerplate code and manage state persistence manually. Drasi's diff-engine handles state management and change computation automatically, emitting events only when meaningful changes occur. MQTT (Message Queuing Telemetry Transport) is the de-facto standard protocol for IoT, used by AWS IoT Core, Azure IoT Hub, and virtually every IoT deployment. Adding MQTT support to Drasi Lib will unlock the entire IoT ecosystem for Drasi users. In this project, the mentee will build a suite of lightweight Rust crates that enable Drasi Lib to communicate with MQTT brokers. They will create connectors to ingest sensor data (MQTT Source), execute local actions (Shell Reaction), and close the control loop (MQTT Reaction).

rustmqtt protocolpub/sub patterns+3
1 active years2026
Explore
Enable ISIS functionality on Sonic logo

Enable ISIS functionality on Sonic

Linux Foundation

<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS LOCATED IN CHINA*</strong></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Problem Statement</strong></p><p><br></p><p><span style="color: rgb(0, 0, 0); background-color: transparent;">IS-IS (Intermediate System to Intermediate System) is a link-state routing protocol used as an Interior Gateway Protocol (IGP) in TCP/IP networks.&nbsp;It is widely used in large enterprise networks, ISP backbone networks, and data center networks.&nbsp;It calculates the shortest path using the SPF algorithm, supports a hierarchical structure (Level-1/Level-2), and is known for its high scalability, reliability, and fast convergence.</span></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Mentorship Objectives</strong></p><p><br></p><p><span style="color: rgb(0, 0, 0); background-color: transparent;">ISIS, as a widely used IGP protocol, is already supported in FRR, the routing suite used by Sonic. However, Sonic does not yet support directly enabling and using ISIS protocol functionalities. We need to build the initialization, startup, configuration deployment of isisd in Sonic, and implement the ISIS functionality CLI in Sonic. </span></p>

dockerdevice driversai-based coding+3
1 active years2026
Explore
Encrypted Portable Identity for AI Agents, Soul Protocol (Unpaid) logo

Encrypted Portable Identity for AI Agents, Soul Protocol (Unpaid)

Linux Foundation

<p>AI agents can't move between platforms. When a user switches runtimes, their agent's memory, personality, and learned behavior disappear, locked into whatever system created them. There's no open standard for encrypting and exporting an agent's cognitive state.</p><p><br></p><p>Soul Protocol defines a&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;file format: an encrypted, portable container for agent identity and memory. It provides core primitives (create, read, write, export, import, encrypt, verify) without prescribing personality models, memory backends, or domain structures.</p><p><br></p><p>This project implements the encryption and portability layer: AES-256-GCM encrypted&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;file export/import, machine-derived key management, digital signature verification on import, and a cross-runtime test suite that validates&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;files across PocketPaw, LangChain, and CrewAI.</p><p><br></p><p>Reference implementation:&nbsp;<a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/github.com/pocketpaw/pocketpaw" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">PocketPaw</a>, 533+ stars, 3,200+ PyPI downloads and growing, 31 contributors, 2,000+ tests, 7-layer security architecture with Guardian AI.</p><p>Academic context: "Everything is Context" (arXiv:2512.05470) formalizes context engineering for agents but treats them as stateless tools. Soul Protocol adds a persistent identity layer, portable, encrypted, and owned by the user.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Understand encryption primitives for portable file formats (AES-256-GCM, PBKDF2 key derivation) and how they apply to identity systems</li><li>Study protocol design principles for thin open standards, looking at how MCP and W3C DID succeeded through minimal interfaces</li><li>Build cross-runtime compatibility layers in Python targeting multiple agent frameworks (PocketPaw, LangChain, CrewAI)</li><li>Practice test-driven development with 90%+ coverage on security-critical code</li><li>Write technical specifications and documentation for an open standard</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Encrypted&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;file format specification (AES-256-GCM, machine-derived PBKDF2 keys, Ed25519 signature verification)</li><li>Python SDK:&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">soul.export(encrypted=True)</code>&nbsp;and&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">soul.import(path, key)</code>&nbsp;with complete key management</li><li>Cross-runtime test suite validating&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;portability across PocketPaw, LangChain, and CrewAI</li><li>Developer documentation, quickstart guide, and specification document</li><li>Blog post documenting the mentorship experience, technical decisions, and lessons learned</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/75 " rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/75</a></p>

python 3.11+understanding of symmetric encryption (aes-gcm) and key derivation functions (pbkdf2/scrypt)familiarity with json schema design and file format specifications+5
1 active years2026
Explore
Extending language and library support in CBOMkit logo

Extending language and library support in CBOMkit

Linux Foundation

<h3>Description</h3><p>This mentorship project combines both hands-on development and exploratory research.</p><p>CBOMkit currently supports cryptographic detection and analysis for Java, Python, and Go ecosystems. However, a significant portion of production systems relies on other programming languages like C/C++ (used especially in systems programming, embedded environments, and high-performance applications) and widely rely on crypto libraries like OpenSSL.</p><p><br></p><p>On the development side, the mentee will extend CBOMkit to support C/C++, with a primary focus on detecting usage of OpenSSL APIs, and cryptographic primitives. This includes adding C/C++ language support, designing detection logic in sonar-cryptography, integrating it into CBOMkit’s architecture, developing test cases and validating against real-world C/C++ projects, ensuring practical applicability and robustness.</p><p><br></p><p>Additionally, mentee will also test some other policies through existing Open Policy Agent (OPA) integration feature of CBOMkit.</p><p><br></p><p>On the research side, the mentee will analyze additional cryptographic libraries in the C/C++ ecosystem such as wolfSSL, libsodium, BoringSSL, and Botan, along with exploring language support for Rust and its associated cryptographic libraries. The goal is to evaluate their feasibility for future integration into CBOMkit.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Understand analysis techniques for detecting cryptographic usage</li><li>Gain hands-on experience with cryptographic libraries such as OpenSSL in C/C++</li><li>Learn how to extend and contribute to a production-grade open-source security tool</li><li>Develop skills in designing test cases and validating tools on real-world codebases</li><li>Learn how policy-based security analysis works using Open Policy Agent (OPA)</li><li>Conduct technical research and evaluate cryptographic libraries and programming language for integration</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>C/C++ language support integrated into sonar-cryptography</li><li>OpenSSL detection module with meaningful coverage</li><li>integration with CBOMkit</li><li>Test suite for validating detection accuracy</li><li>Validation report using real-world C/C++ projects</li><li>Research document comparing additional libraries (wolfSSL, libsodium, BoringSSL, Botan) and language(Rust with its library) for integration feasibility</li><li>Blog post(s) or technical documentation describing implementation and findings</li><li>Evaluation with other policy through OPA</li></ul><h3><br></h3><h3>Recommended Skills</h3><ul><li>Proficiency in java with good understanding of C/C++</li><li>Experience with OpenSSL and general cryptographic APIs</li><li>Good understanding of cryptographic concepts (encryption, hashing, key exchange)</li><li>Experience with static analysis or code parsing (preferred but not mandatory)</li><li>Familiarity with Open Policy Agent</li><li>Familiarity with Git and open-source contribution workflows</li></ul><h3><br></h3><h3>Additional Information</h3><ul><li><a href="https://github.com/cbomkit/sonar-cryptography/blob/main/docs/LANGUAGE_SUPPORT.md" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://github.com/cbomkit/sonar-cryptography/blob/main/docs/LANGUAGE_SUPPORT.md</a></li><li><a href="https://github.com/cbomkit/sonar-cryptography/blob/main/docs/DETECTION_RULE_STRUCTURE.md" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://github.com/cbomkit/sonar-cryptography/blob/main/docs/DETECTION_RULE_STRUCTURE.md</a></li></ul>

proficiency in java with good understanding of c/c++experience with openssl and general cryptographic apisgood understanding of cryptographic concepts (encryption, hashing, key exchange)+7
1 active years2026
Explore
Fablo logo

Fablo

Linux Foundation

<p>Fablo is a tool mostly used for local development and in CI. It starts a Hyperledger Fabric network from a single configuration file, and supports various features that makes the development easier (REST API, network snapshots, advanced topology configuration, hooks, etc). It supports Hyperledger Fabric in versions 2.x and 3.x. Last year we were able to ensure feature parity between versions.</p><p><br></p><p>The target user of Fablo is the developer who works with the local Hyperledger Fabric network to either experiment with various topologies or work on contracts. The goal of this internship is to improve the overall developer experience by:</p><p><br></p><ul><li>Ensuring we have up to date and more approachable documentation, kept up to date with the help of AI CI workflows.</li><li>Improving Fablo distribution by supporting npm package along with existing Docker image distribution.</li><li>Resolving friction that is related to random errors, or slow responsiveness of the network setup.</li></ul><p><br></p><p>While a significant part of the proposal is improving the documentation Fablo, the most focus is on automating the process of keeping documentation up to date. This is why the primary focus of this proposal is coding.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Designing and implementing GitHub Actions workflows</li><li>Using AI agent workflows in real use cases</li><li>Creating concise and approachable documentation</li><li>Debugging and resolving complex issues</li><li>Experience with Hyperledger Fabric network topology, setup and configuration</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>GitHub Pages with documentation</li><li>GitHub Actions using AI workflows to keep the documentation up to date</li><li>Agent skill file for Fablo</li><li>An additional channel of distributing Fablo (npm)</li><li>PRs with fixes towards reducing developer friction</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/84" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/84</a>.</p>

using ai agents, and knowing their limitationscommand line and working with linux or os x environmentsfamiliarity with continuous integration (ci) workflows+8
1 active years2026
Explore
Fluid logo

Fluid

Cloud Native Computing Foundation (CNCF)

To enhance code quality, maintainability, and developer experience, Fluid plans to migrate its unit testing framework from Testify to Ginkgo + Gomega—a more expressive and behavior-driven testing stack widely adopted in the Go ecosystem. Concurrently, we aim to significantly improve unit test (UT) coverage, raising it from the current 57% to at least 75%, thereby reducing regression risks and strengthening overall system reliability Expected Outcome: 1. Deliver comprehensive migration guidelines, coding best practices, and hands-on team training for Ginkgo + Gomega adoption. 2. Achieve a measurable increase in unit test coverage—from 57% to 75%—across core modules of the Fluid codebase.

fluidgokubernetes+8
1 active years2026
Explore
Formal Methods for Comprehensive Testing of BGP Link-State (BGP-LS) logo

Formal Methods for Comprehensive Testing of BGP Link-State (BGP-LS)

Linux Foundation

<p>*THIS APPLICATION IS ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link State (BGP-LS) is a northbound information exchange protocol extension. It allows external clients to subscribe to and collect link-state data (topology, traffic engineering metrics, segment routing SIDs, etc.). Originally designed as an export mechanism, BGP-LS is being increasingly used as a critical feed-back component in the operation and management of cloud network infrastructures. For example, TE controllers may rely on such information to respond to real-time connectivity and traffic status. Thus, the accuracy and reliability of BGP-LS is of foundational importance.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The objective of this mentorship is to develop systematic tests and validations for the BGP-LS implementation. More specifically, it needs to address complexities at various levels to achieve high coverage of the implementation. For example, at the high level, the stateful nature of the protocol extension itself, as well as the dynamic, disaggregated changes in a router's internal states, require thorough exploration of the handling of diverse interaction scenarios and even inconsistent states. At the low level, data processing utilities, such as the parsing of internal routing data formats, also requires systematic testing to validate the handling of both normal and abnormal data.&nbsp;</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>A set of formal models describing both the expected high-level interactions and low-level processing logics of BGP-LS.</p><p>Benchmarks containing diverse interaction sequences and input data, providing comprehensive behavior and code coverage.</p><p>Testing infrastructures to execute, evaluate, and refine these tests.</p><p><strong>*Program Term: Summer - Fall (May - November) 20 hours of work each week*</strong></p><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and C/C++</li><li>Basic knowledge of IP networking and routing</li><li>Basic understanding of distributed systems and concurrency</li><li>Ability to navigate and understand complex codebases</li></ul>

pythoncc++
1 active years2026
Explore
Formal Methods for Refactoring logo

Formal Methods for Refactoring

Linux Foundation

<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>Software refactoring and restructuring is common in the open-source development of SONiC. Existing code structure may limit the adoption of new usage scenarios or protocol features, necessitating its refactoring into a better logical structure. For example, the ongoing RIB/FIB project intends to separate the RIB and FIB maintenance code in Zebra and move the latter down to SONiC’s fpmsyncd component. Since fpmsyncd resides in SONiC code space, it allows FIB to construct SONiC specific forwarding chain, and handle route convergence based on SONiC’s requirements.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>A central requirement in such refactoring is to ensure that behavior changes are exactly as expected. In the RIB/FIB example, it requires that normal executions must be equivalent before and after the refactor. The objective of this mentorship is to devise a systematic approach to validate behavioral equivalence during SONiC refactoring. More specifically, it involves applying formal methods to mathematically describe the intended behavior, compare two distinct setups, and generate comprehensive tests to ensure the consistency before and after the refactor. This will serve as an exemplar of the formal-methods-based correctness paradigm in production code development.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Abstract formal models describing expected behavior of the relevant RIB/FIB operations.</li><li>Testing infrastructure that supports parametrized testing of individual modules and execution sequences across modules.</li><li>A test generation framework and the resulting high-coverage benchmark to validate the correctness of the RIB/FIB implementation.</li><li>*<strong>Program Term: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of network forwarding and routing</li><li>Comfort with hands-on systems work under technical guidance, including system setups, trouble shooting, etc.</li><li>Strong communication skills</li></ul>

pythoncc++
1 active years2026
Explore
GitMesh logo

GitMesh

Linux Foundation

<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>

interest in decentralized identity, verifiable credentials, or open source governancebasic understanding of policy/authorization systemsai agent tool exposure (claude code, copilot, cursor)+8
1 active years2026
Explore
Headlamp logo

Headlamp

Cloud Native Computing Foundation (CNCF)

Build a Headlamp plugin to surface Kubeflow resources (Pipelines, Katib, PipelineRuns, Notebooks, TFJob/PyTorchJob/TrainJob, Spark) so operators and ML engineers can discover, monitor, and manage ML workloads alongside standard K8s resources. Link to Kubeflow UIs when deeper functionality is needed. - Expected Outcome: - New Kubeflow sidebar with cross-namespace lists for Pipelines (Experiments, Runs), Katib experiments, Notebook servers, Training and Spark jobs. - Detail pages per resource showing metadata, status, metrics, logs and common actions (start Run, open Jupyter, view best hyperparams). - Links/embed to Kubeflow Central Dashboard or Pipelines UI for advanced tasks. - Headlamp Map integration: show relations to Deployments/Pods, Argo workflows, Spark driver/executors. - Metrics via Prometheus or /metrics: basic charts for experiment objectives and pod resource use. - Polished UX: icons, pagination, filtering, error handling. - Outreach: README/User Guide and a demo blog post with screenshots.

kubernetestypescriptreact+26
2 active years2026
Explore
Hyperledger Foundation logo

Hyperledger Foundation

Blockchain & Ledgers

Hyperledger Foundation is a global enterprise-grade blockchain consortium hosted by the Linux Foundation.

gorusttypescript+1
1 active years2026
Explore
Implementation of Tightly-Coupled Data-Flow Integrity in RISC-V logo

Implementation of Tightly-Coupled Data-Flow Integrity in RISC-V

RISC-V

<p>Data-Flow Integrity (DFI) offers robust protection against memory corruption by ensuring that runtime data flow matches a program's static data-flow graph. However, software DFI suffers from prohibitive overhead. Recent hardware solutions attempt to mitigate this by using decoupled coprocessors (e.g., RvDfi) or alternative architectures, but a tightly coupled approach that extends the ISA directly within the pipeline offers a compelling opportunity to optimize performance and area.</p><p><br></p><p>In a collaboration between the SUSHI research team (Inria Rennes) and the Barcelona Supercomputing Center (BSC), this mentorship implements tightly-coupled DFI in the open-source RISC-V Sargantana core. To ensure a realistic scope, the project is structured in two phases. Phase 1 focuses on hardware: the mentee will collaborate with a student at SUSHI who developed preliminary RTL modifications for the CVA-6 core. This accelerates porting and optimization of these ISA extensions for Sargantana.</p><p><br></p><p>Once the hardware is stable, Phase 2 explores the software stack. To keep the project tractable, the goal is an initial, proof-of-concept toolchain integration. The mentee will leverage adaptations started by SUSHI, using the RVDFI toolchain as a baseline. SUSHI's LLVM experts will provide guidance to help the mentee establish a foundational compiler backend. This phased approach guarantees a solid hardware deliverable while ensuring a full-stack proof-of-concept remains an achievable stretch goal.</p>

hardware design (systemverilog, rtl)computer architecturedevelopment tools (linux, git, makefiles, bash, etc.)+10
1 active years2026
Explore
Implementation of the RISC-V ISA Extensions for Control-Flow Integrity logo

Implementation of the RISC-V ISA Extensions for Control-Flow Integrity

RISC-V

<p>Control-flow integrity (CFI) is a fundamental security mechanism that prevents attackers from hijacking a program's execution flow. By exploiting memory vulnerabilities, such as stack-smashing or use-after-free bugs, malicious attackers can corrupt pointers or overwrite return addresses, thereby silently redirecting execution to arbitrary malicious code. RISC-V has recently ratified two ISA extensions to enforce CFI at the hardware level through two complementary primitives. The shadow stack maintains a separate, hardware-protected copy of return addresses, preventing a corrupted call stack from redirecting returns to malicious code. Landing pads require that all valid indirect jumps must land at an explicitly marked location with a special instruction, preventing attackers from redirecting execution to unintended locations.</p><p><br></p><p>In collaboration between the Barcelona Supercomputing Center (BSC) and the SUSHI research team (Inria Rennes), this project aims to implement both CFI extensions on Sargantana, an open-source, Linux-capable, RISC-V core. The mentees will begin by studying the RISC-V CFI specification and the Sargantana microarchitecture, and will then produce an architectural plan of the required pipeline modifications. The mentee will then implement the shadow stack mechanism, including hardware enforcement of shadow stack semantics and access-protection logic. This will be followed by landing pad support, which will involve pipeline enhancements to validate indirect branch targets at commit time. Finally, the mentee will use the Sargantana emulation infrastructure to ensure functional correctness of the implemented extensions and to study the hardware overhead they impose.</p>

systemverilogcomputer architecturelinux
1 active years2026
Explore
Knative Functions logo

Knative Functions

Cloud Native Computing Foundation (CNCF)

<p>Knative Functions ships an MCP (Model Context Protocol) server that exposes its toolchain to AI agents. This project builds on that foundation: deepening the MCP server to cover initial environment setup and CI/CD integration, and authoring a companion skill that walks agents through the full lifecycle of a Function. Together these enable end-to-end agentic usage of Serverless Functions; from initial scaffolding through deployment with CI/CD.</p><p><br></p><p>- Expected Outcome:</p><p>&nbsp;- New agentic installer</p><p>&nbsp;- New MCP operations covering prerequisite checks with guidance.</p><p>&nbsp;- A companion skill that composes initialization, CI/CD setup, and deployment into a guided workflow.</p><p>&nbsp;- End-to-end demonstration.</p><p>&nbsp;- User-facing and agent-facing documentation.</p><p><br></p>

gopythonai/ml agents+6
1 active years2026
Explore
Koordinator logo

Koordinator

Cloud Native Computing Foundation (CNCF)

<p>AI agentic workflows (multi-agent collaboration frameworks, automated evaluation systems such as SWE-bench) frequently spawn and tear down large numbers of short-lived sandboxes (gVisor, Wasm, Kata Containers) to execute skills or tools. Current Kubernetes scheduling models are too heavy for these transient workloads, causing high latency, weak isolation, and APIServer pressure. This project will extend Koordinator to provide first-class support for AI agent scenarios by integrating sandbox runtimes with Koordinator QoS classes, implementing equivalence-class scheduling for near-identical sandbox requests, and introducing a dedicated Sandbox Pipeline that handles pre-warming, capacity reservation, and actionable scheduling feedback to enable agent self-healing.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Native integration of agent sandbox runtimes (gVisor/Wasm/Kata) with Koordinator QoS classes (LSR, LS, BE) and resource hardening templates</p><p>&nbsp;- Equivalence-class scheduling logic in the Koordinator scheduler that skips redundant Predicate/Priority calculations for batches of similar sandbox pods</p><p>&nbsp;- A Sandbox Pipeline mechanism with pre-warming, automated environment provisioning, and reservation hooks</p><p>&nbsp;- Annotation/Status-based scheduling diagnostics that surface actionable next-step suggestions to upstream agents</p><p>&nbsp;- End-to-end tests and benchmarks demonstrating throughput and latency improvements for high-concurrency sandbox workloads</p><p><br></p>

gokubernetes scheduler-frameworkdevice plugins+18
1 active years2026
Explore
Kuadrant logo

Kuadrant

Cloud Native Computing Foundation (CNCF)

<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>&nbsp;- 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>&nbsp;- Design document covering A2A routing through ext_proc, federated agent card serving in the broker, session handling implications, and CRD design</p><p>&nbsp;- Federated agent card endpoint in the broker that aggregates upstream A2A agent cards</p><p>&nbsp;- A2A request routing through the Envoy ext_proc path, with appropriate header handling and policy enforcement</p><p>&nbsp;- CRD design (new resource or MCPServerRegistration extension) for registering A2A agents with the gateway controller</p><p>&nbsp;- E2E tests demonstrating A2A agent discovery and task execution through the gateway</p><p><br></p>

gokubernetesnetworking+9
1 active years2026
Explore
LF Energy - Hyphae APIS logo

LF Energy - Hyphae APIS

Linux Foundation

<p>With energy resources and infrastructure increasingly challenged to meet the coming impacts of climate change and natural disasters, Hyphae aims to make the grid more resilient and flexible with microgrids. By providing an Autonomous Power Interchange System (APIS), Hyphae automatically and efficiently distributes locally-produced renewable energy over a DC grid to interconnect with AC Grids. With resilient, physical peer-to-peer microgrid energy trading, even the most remote communities will be able to store and distribute energy autonomously without connecting to large-scale power stations or electrical distribution networks. Sponsored-Term: This is a 10-12 week project that aims to stabilize APIS repositories and integrate the energy trading mechanism with enAccess PayGo Token (https://github.com/EnAccess/OpenPAYGO-python) . We are looking to raise $6000 for registration and travel expenses to OSEAS 2026 (https://www.oseas.org/)</p><p>For the Spring 2026 cohort, we will also look into integrating with GAIFARE from Open Renawable Energy Systems LF Energy program to see what AI can bring to the Hyphae use cases.</p>

javajavascriptmake+14
2 active years2026
Explore
LF Research logo

LF Research

Linux Foundation

LF Research publishes actionable and decision-useful insights into open source software, hardware, standards, and data based on empirical research methodologies. Through leveraging community networks, project databases, surveys, and qualitative findings, and through its commitment to best practices in primary research, Linux Foundation Research is the definitive home for data-driven insights into open source for the benefit of governments, enterprises, and society at large.

survey developmentsurveymonkey programmingcanva+4
2 active years2026
Explore
LFDT - Advanced Threshold Key Management logo

LFDT - Advanced Threshold Key Management

Linux Foundation

<p>In standard cryptography, a single compromised key means total failure. Threshold Cryptography eliminates this risk. Using a Distributed Key Generation (DKG),&nbsp;n&nbsp;participants generate a&nbsp;t-out-of-n&nbsp;key where the full secret is never reconstructed in one place. Operations like signing or decryption happen via interactive protocols like CGGMP24 or FROST.</p><p><br></p><p>In this project, you are invited to build the "lifecycle" tools required for production-ready key management:</p><ul><li>Key Share Repair:&nbsp;t&nbsp;parties restore a lost share for a peer, "healing" the network without exposing the secret.</li><li>Key Refresh:&nbsp;Enables proactive security by rotating shares. This protects from "low and slow" attackers, as shares from different epochs are mathematically incompatible.</li><li>Key Reshare:&nbsp;Dynamically changes the participant set or the threshold&nbsp;t, allowing the security policies to evolve.</li></ul><p><br></p><p>Protocol implementation will follow an academic paper: for instance, Key Refresh protocol can be adapted from&nbsp;<a href="https://eprint.iacr.org/2021/060.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">CGGMP24 paper</a>&nbsp;(see Fig. 7). Development will leverage the Lockness ecosystem, utilizing&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/round-based" rel="noopener noreferrer" target="_blank">round-based</a></code>&nbsp;as MPC framework and&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/generic-ec" rel="noopener noreferrer" target="_blank">generic-ec</a></code>&nbsp;for elliptic-curve arithmetics.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Deep Dive into MPC &amp; Threshold Primitives: Transition from theoretical knowledge of cryptography to implementing complex Multi-Party Computation (MPC) protocols, and gain a first-hand understanding of how&nbsp;t-out-of-n&nbsp;security is maintained mathematically.</li><li>Rust Development in the Lockness Ecosystem: Master high-performance, memory-safe programming by contributing to the Lockness ecosystem, specifically using the&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/generic-ec" rel="noopener noreferrer" target="_blank">generic-ec</a></code>&nbsp;library for efficient and type-safe elliptic curve operations.</li><li>Modern Distributed Programming:&nbsp;Learn to write asynchronous code via the&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/round-based" rel="noopener noreferrer" target="_blank">round-based</a></code>&nbsp;framework to manage complex network interactions.</li><li>From Paper to Production:&nbsp;Develop the ability to translate academic research into reliable, auditable, high-quality code, bridging the gap between "whitepaper math" and "real-world software".</li><li>Production-Grade Workflow:&nbsp;Experience a professional development lifecycle where cryptographic code is subject to rigorous peer reviews and testing to ensure maximum security. Learn the discipline required to build cryptographic libraries where every line of code must be verified for both correctness and security.</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><p>Standalone libraries that implement mentioned protocols</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/56" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/56</a></p>

rustelliptic curvedlt
1 active years2026
Explore
LFDT - Build and release a Java SDK for Paladin logo

LFDT - Build and release a Java SDK for Paladin

Linux Foundation

<p>Paladin is a programmable privacy solution for EVM blockchains. It provides a framework for deploying and working with private tokens and EVM-compatible private smart contracts for private, programmable on-chain logic such as atomic swaps.</p><p><br></p><p>See&nbsp;<a href="https://www.paladinprivacy.org/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://www.paladinprivacy.org/</a>&nbsp;and&nbsp;<a href="https://lfdt-paladin.github.io/paladin/head/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://lfdt-paladin.github.io/paladin/head/</a></p><p><br></p><p>To work with Paladin tokens and private smart contracts applications typically use one of the existing SDKs - currently available for Go and Typescript.</p><p>There are users keen to build Java applications that utilize all of the Paladin privacy features in a performant, language-idiomatic way.</p><p><br></p><h3>Learning Objectives</h3><ol><li>Understand all the basic components and privacy patterns of Paladin</li><li>Understand the Paladin REST APIs and and their inputs/outputs</li><li>Review the existing SDKs to understand what feature-parity of a new SDK would look like</li></ol><h3>Expected Outcome and Deliverables</h3><ul><li>A Java SDK available as a published dependency for Java applications to consume</li><li>Request/reply and web-socket event-driven interfaces</li><li>A repeatable release process integrated with the current release pipeline</li><li>A high degree of test coverage of the new SDK</li></ul><p><br></p><p>Ultimately we are looking for a well designed SDK that feels natural to Java application developers to use, and makes use of current, idiomatic language features.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/64" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/64</a></p>

javaevmdlt
1 active years2026
Explore
LFDT - Continuous Benchmarking for Besu EVM logo

LFDT - Continuous Benchmarking for Besu EVM

Linux Foundation

<p>Besu includes comprehensive EVM benchmarking tooling — including JMH microbenchmarks for 40+ EVM operations, precompile benchmarks via&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool benchmark</code>, and full blockchain-level test execution via&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool block-test</code>. However, these benchmarks are currently only run manually by developers on local machines. There is no automated way to track performance over time, detect regressions introduced by PRs, or visualize trends.</p><p><br></p><p>This project aims to build a continuous benchmarking pipeline for the Besu EVM, for example by integrating existing benchmark tooling into CI. The mentee will discuss a solution with Besu maintainers, design and implement automated (and/or manually triggered) workflows that run EVM benchmarks, collect results, store historical data, and produce reports that give maintainers clear visibility into performance changes.</p><p><br></p><p>An excellent reference for the kind of output we'd like to achieve is the&nbsp;<a href="https://benchmarks.ethrex.xyz/gas-benchmark-eest/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">ethrex gas benchmarks dashboard</a>, which provides comparative benchmark reports with sortable tables, speedup metrics, and historical tracking across runs.</p><p><br></p><p>Besu's existing benchmark tooling includes:</p><ul><li>JMH microbenchmarks&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">ethereum/core/src/jmh/</code>) — 40+ benchmarks covering EVM arithmetic, bitwise, shift, stack, memory, and crypto operations (reported in execution time only)</li><li>Precompile benchmarks&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool benchmark</code>) — benchmarks for AltBN128, EcRecover, ModExp, BLS12, P256Verify, SHA256, RIPEMD-160, and KZG Point Eval with throughput metrics (MGps)</li><li>Block-test execution&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool block-test</code>) — full blockchain reference test execution with timing and pass/fail reporting</li><li>Shell-based benchmark scripts&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">ethereum/evmtool/src/test/benchmarks/</code>) — existing scripts for static operations, loop operations, and mainnet-like contract execution</li></ul><p><br></p><p>The project scope could include:</p><ol><li>CI Workflow Design&nbsp;— Create GitHub Actions workflows (manually triggered in the first instance) that run selected benchmarks on consistent hardware.</li><li>Results Collection and Storage&nbsp;— Design a scheme for storing benchmark results over time (e.g., GitHub Pages, artifact storage, or a lightweight results repo).</li><li>Reporting and Visualization&nbsp;— Find/build a dashboard or report format that shows performance trends, highlights regressions, and allows comparison between runs.</li><li>PR Integration&nbsp;— Optionally, enable benchmark runs on PRs that touch EVM-critical code paths, with summary comments showing performance impact.</li><li>Documentation&nbsp;— Document how to run, extend, and interpret the benchmarks.</li><li>RPC Performance&nbsp;- As a stretch goal could also cover RPC performance, such as eth_call.</li></ol><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/69" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/69</a></p>

javagitblockchain+2
1 active years2026
Explore
LFDT - Exploring Chaincode Support for Hyperledger Fabric-X logo

LFDT - Exploring Chaincode Support for Hyperledger Fabric-X

Hyperledger

<p>Hyperledger Fabric has been available for several years and there are many production networks using Chaincode. Fabric-X has just been released and it introduces changes to the current way of deploying applications. This brings up the question on how to migrate existing applications and chaincodes to this new environment.</p><p>The goal of this mentorship project is to:</p><ul><li>Explore the feasibility to run existing Fabric Chaincode on Fabric-x;</li><li>Design and develop a proof of concept that showcases Go Chaincode for Fabric-X;</li><li>Implement a prototype of the components identified;</li><li>Identify a demo use case (i.e., Fabric Samples, CC-Tools, Fabric Private Chaincode) that comes with go chaincode;</li><li>Produce documentation that explains the architecture and how it can be used as well as potential avenues of development.</li></ul><h3>Learning Objectives</h3><ul><li>Deep dive into Hyperledger Fabric and Fabric-X.</li><li>Experience an active open-source community.</li><li>Mastering open-source workflow.</li><li>Enhance your designing and implementing skills, testing, documentation, and project management.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>Proof of Concept that showcases an alternative on how to migrate classic Fabric go chaincode to Fabric-X.</li><li>Documentation that explains the demo and how to run it.</li><li>Bonus: a technical blog post and meetup talk.</li><li>Having fun.</li></ul><p><br></p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/59" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/59</a></p>

gitgobash+3
1 active years2026
Explore
LFDT - Extending Hiero Enterprise Java with Smart Contract Event and Log APIs logo

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

Linux Foundation

<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>

javahttpgrpc+4
1 active years2026
Explore
LFDT - Fablo logo

LFDT - Fablo

Linux Foundation

<p>Hyperledger Fabric-X introduces a new architecture for Fabric, with decomposed services for ordering, endorsement, validation, and committing, but its current developer workflow is still centered around dedicated deployment scripts and Ansible-based setup.</p><p>Fablo, on the other hand, is widely used to start Hyperledger Fabric networks quickly from a single configuration file for local development, CI, and experimentation.</p><p>This project will explore and implement the best path to support a simple local Fabric-X network through the Fablo experience. We will evaluate architectural options such as a new engine, a separate repo, or an extension/wrapper approach, then build a minimal but practical MVP that can generate configuration, bootstrap the required components, and start/stop a working local Fabric-X network. The goal is to reduce setup friction for contributors and users, and provide a repeatable developer workflow, examples, and documentation that make Fabric-X easier to try, demo, and extend.</p><h3>Learning Objectives</h3><ul><li>Understand the architecture and deployment model of Hyperledger Fabric-X, including how it differs from classic Hyperledger Fabric.</li><li>Learn how to design contributor-facing tooling for distributed systems with evolving architecture.</li><li>Gain experience in open source development across CLI/tooling, configuration generation, testing, and documentation.</li><li>Develop practical skills in Docker-based environments, and debugging multi-component systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>A design proposal describing the recommended integration path between Fablo and Fabric-X (for example: separate repo, pluggable engine, or wrapper-based approach).</li><li>An MVP implementation that can bootstrap a simple local Fabric-X network and manage its lifecycle.</li><li>Example configuration(s) and sample workflow for running Fabric-X through the proposed Fablo-based experience.</li><li>Automated tests and/or validation scripts covering the supported MVP scenario.</li><li>Contributor and user documentation explaining setup, architecture decisions, and next steps.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83</a></p>

linuxblockchaingo+5
1 active years2026
Explore
LFDT - Fabric-x EVM Compatibility logo

LFDT - Fabric-x EVM Compatibility

Linux Foundation

<p>The Fabric / Fabric-X EVM Gateway adds a standard Ethereum JSON-RPC interface and an embedded go-ethereum EVM execution path to a permissioned Fabric(X) network. Client transactions are simulated by EVM Endorsers against a custom&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">StateDB</code>&nbsp;wrapper that builds Fabric-style read–write sets (rwsets) and preserves Fabric endorsement, ordering, and MVCC validation—while remaining fully compatible with Ethereum tools and semantics (e.g.,&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">msg.sender</code>, receipts, logs).</p><p><br></p><p>This mentorship centers on&nbsp;hardening and concurrency: implementing a durable, correct mempool/queue with retry logic that masks MVCC conflicts from Ethereum clients; enforcing ledger-tracked Ethereum nonces decoupled from Fabric txIDs with endorser-side checks; handling client bursts and replacement transactions; ensuring API-visible consistency across processes/restarts and (eventually) across multiple gateway replicas; and validating event/log hygiene so non-committing executions never leak to clients.</p><p><br></p><p>Candidates will work in Go, touch the gateway/endorser boundary, and contribute tests and docs that make the gateway robust under failures (kill/restart), high load, and contention.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/72" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/72</a></p>

gogitdocker+4
1 active years2026
Explore
LFDT - Hiero logo

LFDT - Hiero

Linux Foundation

<p>Open source collaboration platforms rely heavily on email-based identity and platform accounts for contributor attribution.</p><p>While widely adopted and convenient, this model has limitations: commit author metadata can be spoofed, contributor identity is fragmented across projects / ecosystems and hard to verify, and trust relationships are challenging to establish without additional verification on a person-to-person basis.</p><p>Current GitHub contribution workflows face multiple risks, including commit author impersonation and email-based identity spoofing.</p><p>These risks became even more relevant with advancements of Agentic AI capable of identity impersonation and "flooding" open source projects with low-quality or even malicious contributions.</p><p>From a technical perspective, there are many ways to mitigate these risks. However, not all of them are suitable for open source specifically – decentralized and transparent trust along with self-sovereign identity management are crucial factors.</p><p><br></p><p>Compromising on these principles can lead to a less trustworthy relationship between individual contributors and the projects, as well as it can create a higher entry barrier for new contributors.</p><p><br></p><p>We believe that decentralized identity concepts (<a href="https://www.w3.org/TR/did-1.1/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">Decentralized Identifiers (DIDs)</a>&nbsp;and&nbsp;<a href="https://www.w3.org/TR/vc-data-model-2.0/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">Verifiable Credentials (VCs)</a>) can help to mitigate the spoofing and impersonation risks without compromising trust, providing a more secure and trustworthy way to recognize contributors.</p><p><br></p><p>This project proposes the development of a prototype (with long-term development potential) for contributor identity validation in Hiero that will leverage existing tools / applications available in Hiero Identity ecosystem, including the new&nbsp;<a href="https://github.com/hiero-ledger/heka-identity-platform" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">Heka Identity Platform</a>.</p><p><br></p><p>The prototype will be tested in a real-world scenario using one of Hiero open-source repositories (e.g.,&nbsp;<a href="https://github.com/hiero-ledger/identity-collaboration-hub" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">Identity Collaboration Hub</a>, DID SDKs, or Heka Identity Platform repo itself).</p><p><br></p><h3>Expected Outcome and Deliverables</h3><p>The successful completion of this project will result in a working prototype for contributor identity verification that can be used safely across Hiero repositories.</p><p>Expected deliverables include:</p><ul><li>A GitHub App capable of verifying contributor identity using DID and VC / VP</li><li>Implementation of a contributor onboarding workflow based on Heka Identity Platform</li><li>Implementation of pull request verification workflow leveraging contributor DID and Linked VP</li><li>Full integration demo with GitHub pull requests in one of the Hiero repositories</li><li>Documentation and high-level design for future development</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/87" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/87</a></p>

javagosdk+8
1 active years2026
Explore
LFDT - Hiero Github Workflow App logo

LFDT - Hiero Github Workflow App

Linux Foundation

<p>The Hiero ecosystem includes a growing number of diverse contributors, repositories, junior committers/committers/maintainers, pull requests, issues, discussions, and quality requirements.</p><p><br></p><p>To build a diverse ecosystem which generates high-quality code, maintainers need to spend a significant amount of time on repetitive coordination tasks such as checking contributor qualifications, validating pull request quality, un-assigning inactive contributors, closing stale issues, creating issues at different difficulties, and ensuring that repository processes are followed consistently.</p><p><br></p><p>We have demonstrated in some SDK repositories many of these maintainer tasks can be automated using custom GitHub action workflows and templates. However, the current setup is fragmented, difficult to customize and scale, and inconsistent across repositories. Different repositories may require different rules, but maintainers still need support to ensure they are working on the most important tasks, and developers need support to help them progress quickly and qualify to gain more responsibilities.</p><p><br></p><p>This mentorship project aims to design and build an automation framework and application for Hiero end-to-end maintainer workflows. The system should support configurable repository automation features that maintainers can turn on or off, depending on the repository context.</p><p><br></p><p>Example user on-boarding workflows:</p><ul><li>Checking contributors are humans</li><li>Checking whether contributors meet contribution requirements before assigning issues</li><li>Offering automatic issue assignment</li><li>Automatically assigning mentors for new contributors</li><li>Issue templates and documentations</li></ul><p>Example pull request review and quality workflows:</p><ul><li>AI issue planning</li><li>AI initial reviewing</li><li>Automated code quality, DCO, GPG, etc checks based on configurable quality requirements</li><li>Automatic review based on configurable quality requirements</li></ul><p>Example developer progression workflows:</p><ul><li>Automatic issue recommendations after a merged pull request to next available issues</li><li>Checking whether advanced contributors meet requirements to progress to JC/committer/maintainer</li></ul><p>Example issue management workflows:</p><ul><li>Managing stale issues or pull requests</li><li>Requesting help or feedback from specified teams based on labels</li></ul><p><br></p><p>A core requirement of the project is to ensure that this automation is reliable, consistent, secure, and scalable enough to be used across a variety of repositories inside Hiero (and one day optionally across LFDT).</p><p><br></p><p>The project should also define clear boundaries for what the automation is allowed to do, how maintainers configure it, and how users can understand or override automated actions when necessary.</p><p>The result should not just be a prototype for a single repository, but a hardened and reusable solution that can serve multiple Hiero repositories with different policies and maintenance needs. </p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/73" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/73</a></p>

javascriptgitgithub api+1
1 active years2026
Explore
LFDT - Hyperledger Fabric Token SDK Sample logo

LFDT - Hyperledger Fabric Token SDK Sample

Hyperledger

<p>The Hyperledger Fabric Token SDK sample (fabric-samples/token-sdk) is a reference application demonstrating how to issue, transfer, and redeem privacy-preserving tokens on a Hyperledger Fabric(X) network using Zero Knowledge Proofs and the UTXO model.</p><p><br></p><p>The sample was originally created in October 2023 and currently pins to Token SDK v0.3.0 and an older version of the Fabric Smart Client. Since then, both the Token SDK and Fabric Smart Client have evolved significantly. The sample needs to be updated to track the latest library versions, and several features listed as "out of scope" in the original implementation are now feasible and would significantly improve the sample's value as a learning and prototyping resource.</p><p><br></p><p>This project targets contributors who want to gain hands-on experience with privacy-preserving token systems, Zero Knowledge Proofs on Hyperledger Fabric, Go-based distributed application development, and REST API design.</p><p><br></p><h3>Learning Objectives</h3><p>By the end of this mentorship, the mentee will be able to:</p><ol><li>Navigate and contribute to a real-world open source Go project within the Hyperledger / LF Decentralized Trust ecosystem, following standard PR and code review workflows.</li><li>Understand the architecture of the Hyperledger Fabric Token SDK — including the roles of issuer, auditor, and owner — and how they communicate via Fabric Smart Client.</li><li>Manage and upgrade Go module dependencies in a multi-module repository, resolving version conflicts and validating compatibility across fabric-token-sdk and fabric-smart-client.</li><li>Explain how privacy-preserving token transactions work using the UTXO model and Zero Knowledge Proofs (specifically the dlog/zkatdlog proof system), and implement or extend token flows accordingly.</li><li>Design and implement REST API endpoints using OpenAPI / Swagger and oapi-codegen, following the existing patterns in the sample.</li><li>Write end-to-end integration tests for distributed multi-party applications running on a local Fabric(X) network via Docker Compose.</li></ol><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/66" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/66</a></p>

gorest apiblockchain+3
1 active years2026
Explore
LFDT - Hyperledger Fabric to Fabric-X Ledger Migration Tool logo

LFDT - Hyperledger Fabric to Fabric-X Ledger Migration Tool

Hyperledger

<p>Hyperledger Fabric-X is a ground-up re-architecture of Hyperledger Fabric designed for national-scale regulated digital-asset systems, achieving 400 K+ TPS through independently scalable micro-services. For enterprise adoption, existing Fabric deployments must be able to migrate their ledger state to Fabric-X without losing transactional history or state integrity.</p><p><br></p><p>This project defines and implements an end-to-end ledger migration path using Fabric's official peer snapshot mechanism as the source of truth. Two architectural gaps must be bridged: (1) Fabric organizes state by channel, namespace, and collections, whereas Fabric-X uses a only namespaces, and (2) Fabric snapshots contain private-data-collection (PDC) artifacts that have no equivalent in Fabric-X.</p><p><br></p><p>The mentee will design a channel-to-namespace mapping strategy, build an Exporter tool that parses Fabric snapshots and produces a portable genesis-data file, and implement a Bootstrap procedure inside the Fabric-X committer that ingests that file and verifies state integrity post-migration.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/65" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/65</a></p>

gogitblockchain+2
1 active years2026
Explore
LFDT - Hyperledger Identus - Identity Portal logo

LFDT - Hyperledger Identus - Identity Portal

Hyperledger

<p>Hyperledger Identus provides mature backend services (Cloud Agent, Mediator) and Edge Agent SDKs (TypeScript, Kotlin Multiplatform, Swift) for building Self-Sovereign Identity (SSI) solutions.</p><p><br></p><p>This mentorship project will deliver a&nbsp;lightweight, unified agent interface&nbsp;— primarily a web-based reference dashboard — that supports:</p><ul><li>Offline-first / non-custodial mode&nbsp;— powered entirely by the TypeScript Edge Agent SDK running in the browser, with CIP-30 Cardano wallet integration (via MeshSDK) for PRISM DID operations.</li><li>Connected / custodial mode&nbsp;— optional connection to an existing Cloud Agent instance via a configurable API endpoint.</li></ul><p>Core architectural principles</p><ul><li>Offline-first by default&nbsp;— If no&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">CLOUD_AGENT_API_ENDPOINT</code>&nbsp;is provided, the application runs fully in the browser with no backend dependencies.</li><li>Maximal reusability&nbsp;— Core SSI logic is built as pure TypeScript modules / utilities that can be reused in other projects (web, React Native,, custom dApps, etc.).</li><li>Minimal vendor lock-in&nbsp;— No UI component kits (e.g., no shadcn/ui); use plain Tailwind CSS + simple, custom, portable components.</li><li>Stable &amp; compatible stack&nbsp;— Target React 18 (latest stable non-experimental version) to maximize future compatibility with projects.</li><li>Modular structure&nbsp;— Separate concerns: pure SSI logic → service adapters (Edge vs Cloud) → presentation layer.</li></ul><h3>Learning Objectives</h3><ul><li>Deep understanding of SSI concepts: Decentralized Identifiers (DIDs – especially PRISM method), Verifiable Credentials (JWT, SD-JWT, AnonCreds), schemas, revocation, DIDComm messaging, trust frameworks, issuer/holder/verifier roles</li><li>Hands-on experience with the Hyperledger Identus ecosystem: Cloud Agent REST APIs, TypeScript Edge Agent SDK, Mediator coordination, PRISM DID resolution &amp; publishing to Cardano, Verifiable Data Registry</li><li>Building reusable, framework-agnostic TypeScript code for SSI workflows</li><li>Implementing a unified UI system for both the Cloud Agent and the Edge Agent (offline first)</li><li>Practice open-source development workflows, including code review, documentation, community engagement, and incremental delivery</li></ul><p><br></p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/77" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/77</a></p>

typescriptreacttailwind css+4
1 active years2026
Explore
LFDT - Implement DKLs23 (threshold ECDSA) protocol logo

LFDT - Implement DKLs23 (threshold ECDSA) protocol

Linux Foundation

<p>In standard cryptography, a single compromised key means total failure. Threshold Signing Schemes (TSS) mitigate this by distributing "shares" of a key across&nbsp;n&nbsp;participants, requiring a minimum threshold&nbsp;t&nbsp;participants to engage into the protocol to generate a signature. While the Lockness ecosystem already has a CGGMP24, a threshold ECDSA protocol, the&nbsp;<a href="https://eprint.iacr.org/2023/765.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">DKLs23</a>&nbsp;protocol presents different features and performance, and unlocks new use-cases.</p><p><br></p><p>In this project, your goal is to transform a formal description of the protocol from the&nbsp;<a href="https://eprint.iacr.org/2023/765.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">DKLs23 paper</a>&nbsp;into the code utilizing&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://docs.rs/round-based/latest/round_based/" rel="noopener noreferrer" target="_blank">round-based</a></code>, a framework for TSS protocols, and&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://docs.rs/generic-ec/latest/generic_ec/" rel="noopener noreferrer" target="_blank">generic-ec</a></code>, a type-safe library for elliptic-curve arithmetics.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Deep Dive into MPC &amp; Threshold Primitives: Transition from theoretical knowledge of cryptography to implementing complex Multi-Party Computation (MPC) protocols, and gain a first-hand understanding of how&nbsp;t-out-of-n&nbsp;security is maintained mathematically.</li><li>Rust Development in the Lockness Ecosystem: Master high-performance, memory-safe programming by contributing to the Lockness ecosystem, specifically using the&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/generic-ec" rel="noopener noreferrer" target="_blank">generic-ec</a></code>&nbsp;library for efficient and type-safe elliptic curve operations.</li><li>Modern Distributed Programming:&nbsp;Learn to write asynchronous code via the&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/round-based" rel="noopener noreferrer" target="_blank">round-based</a></code>&nbsp;framework to manage complex network interactions.</li><li>From Paper to Production:&nbsp;Develop the ability to translate academic research into reliable, auditable, high-quality code, bridging the gap between "whitepaper math" and "real-world software".</li><li>Production-Grade Workflow:&nbsp;Experience a professional development lifecycle where cryptographic code is subject to rigorous peer reviews and testing to ensure maximum security. Learn the discipline required to build cryptographic libraries where every line of code must be verified for both correctness and security.</li></ul><p><br></p><h3>Expected Outcome and Deliverables</h3><p>A library that implements DKLs23 protocol.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/58" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/58</a></p>

rustcryptographydlt
1 active years2026
Explore
LFDT - Implementation of a ZK-SNARK Token Driver for Hyperledger Fabric using gnark logo

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

Hyperledger

<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>

gohyperledger fabriczkp+1
1 active years2026
Explore
LFDT - Improve usability, maintainability, and contributor experience of Hyperledger Cacti logo

LFDT - Improve usability, maintainability, and contributor experience of Hyperledger Cacti

Hyperledger

<p>This mentorship focuses on improving the usability, maintainability, and contributor experience of Hyperledger Cacti. Following the merger of Hyperledger Cactus and Weaver, the codebase and architecture have grown complex, with fragmented documentation and legacy components that hinder onboarding and long-term sustainability.</p><p><br></p><p>The project targets the ongoing Cacti Cleanup Initiative, aiming to simplify architecture, remove deprecated modules, improve security, and create high-quality documentation. The mentee will audit and restructure developer and user documentation, align docs with the evolving architecture, identify outdated components for removal, and improve onboarding guides and contribution workflows.</p><p><br></p><p>Implementation will follow an iterative process: reviewing GitHub issues and cleanup boards, proposing improvements, implementing updates to documentation and selected code areas, and validating improvements with maintainers. The outcome will be a streamlined, well-documented Cacti framework that lowers entry barriers for contributors and strengthens the project’s long-term sustainability.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Understand cross-chain architectures and pluggable DLT frameworks</li><li>Gain experience contributing to a large open-source project under the LF Decentralized Trust ecosystem</li><li>Learn best practices for technical documentation, developer experience, and onboarding design</li><li>Develop skills in codebase refactoring, modularization, and security-driven cleanup</li><li>Collaborate with an international open-source community using GitHub, CI/CD pipelines, and review workflows</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>A restructured and standardized documentation suite (developer, user, and architecture docs)</li><li>Cleanup contributions removing deprecated or low-value components and simplifying modules</li><li>Improved onboarding guides, tutorials, and contributor documentation</li><li>CI/CD improvements reducing pipeline runtime and complexity (where applicable)</li><li>A final report summarizing changes, impact, and recommendations for future improvements</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/62" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/62</a></p>

typescriptblockchaingit+2
1 active years2026
Explore
LFDT - Improving Hyperledger Solang Through Comparative Analysis with the Soroban Rust SDK logo

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

Hyperledger

<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>

rustsoliditywebassembly+3
1 active years2026
Explore
LFDT - Refactoring and Evolution of the Besu Plugin API logo

LFDT - Refactoring and Evolution of the Besu Plugin API

Linux Foundation

<p>The Besu team has been pushing heavily on extensibility via plugins, as a way to support Layer 2 or private networks, without needing to fork the core Besu codebase, with Linea being a notable success example.</p><p><br></p><p>The Plugin API, now offer a variety of services, form consuming blockchain data for custom needs, modifying the behavior of an Ethereum network to adapt to specific workflows, to streamlining the deprecation of legacy features by re-implementing them as plugins. They are also highly useful for testing and debugging purposes.</p><p><br></p><p>However, Besu Plugin API is fragile and grew in a non-organic way over the years. Because its evolution was mainly driven by specific needs rather than clear design principles, so it grew without a real direction, resulting in poorly organized code. Currently, every time a new functionality needs to be exposed via the Plugin API, it is not clear how to expose the interfaces or where to place them. Consequently, quick trade-offs are sometimes taken to avoid undertaking a large refactoring effort.</p><p><br></p><p>Furthermore, the plugin lifecycle—especially during the startup phase—is not well defined. This ambiguity can result in critical problems, such as plugins attempting to access a service before it is fully initialized. Finally, there is currently no real process around deprecation, versioning and backward compatibility, which makes it difficult to detect and manage braking changes in a coherent way.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain a deep understanding of the Besu architecture, specifically its plugin ecosystem, module organization, and node lifecycle.</li><li>Learn advanced Java software design, focusing on code refactoring, API versioning and deprecation strategies, API documentation best practices, and establishing clean design principles.</li><li>Develop practical experience in open-source software development, including untangling technical debt and proposing structural architectural improvements.</li><li>Collaborate closely with plugin users and core maintainers to better understand their needs and pain points.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>Code Reorganization &amp; Design Principles: Refactor the existing plugin codebase to improve organization and document clear guidelines/patterns on how and where to expose new interfaces in the future.</li><li>Lifecycle Refinement: Analyze and implement a robust, well-defined startup lifecycle for plugins to eliminate race conditions, ensuring services cannot be accessed before they are fully initialized.</li><li>API Versioning System: Design and integrate versioning support into the Plugin API so that maintainers and developers can systematically detect and manage breaking changes</li><li>Documentation: Renew the API documentation and Plugin writing guides.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/82" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/82</a></p>

javaapigit+3
1 active years2026
Explore
LFDT - Research Composable Token Primitives for Post-Trade Clearing, Settlement, Compliance on DLT logo

LFDT - Research Composable Token Primitives for Post-Trade Clearing, Settlement, Compliance on DLT

Linux Foundation

<p>Global post-trade settlement infrastructure remains fragmented across incompatible ledger implementations, jurisdictional compliance regimes, and asset-class-specific token schemas — creating systemic friction at the intersection of programmable finance and institutional market microstructure. This project conducts an open, community-driven research inquiry into the design space for a protocol-agnostic token framework within the LF Decentralized Trust ecosystem, exploring how composable token primitives may serve as a convergence layer across heterogeneous post-trade settlement rails. All research outputs, findings, and prototypes will be contributed openly to the LF Decentralized Trust community under applicable open-source licenses, with no implied endorsement or proprietary claim by any contributing organization.</p><h3>Learning Objectives</h3><p>The mentee will survey existing tokenization frameworks, identify gaps in interoperability and compliance metadata propagation, and develop exploratory prototypes to inform community discussion around open standards for post-trade infrastructure within the LF Decentralized Trust ecosystem.</p><h3>Expected Outcome and Deliverables</h3><ul><li>A Research Report documenting a comparative survey of existing tokenization frameworks, proposed schema considerations, and community recommendations for token base types, behaviors, and metadata — contributed as an open draft for community review.</li><li>An Exploratory Prototype — a series of illustrative smart contract examples (Solidity or Chaincode) demonstrating potential implementation patterns across representative use cases, intended for research and educational purposes only.</li><li>A Community Whitepaper presenting findings, open questions, and suggested directions for post-trade token framework adoption — offered as a contribution to broader community discourse with no prescriptive or regulatory guidance implied.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/88" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/88</a></p>

soliditymoverust+2
1 active years2026
Explore
LFDT - Web3j Libraries Full Lifecycle Development logo

LFDT - Web3j Libraries Full Lifecycle Development

Linux Foundation

<p>The Web3j library is an essential tool for Java and JVM-based developers looking to integrate with the Ethereum blockchain. It provides seamless Ethereum client communication, enabling developers to interact with smart contracts and blockchain networks. However, maintaining and improving Web3j while ensuring seamless adoption of the latest Ethereum Improvement Proposals (EIPs) remains a challenge for maintainers due to the lack of time and contributors.</p><p><br></p><p>This project aims to enhance the core Web3j by improving and continue to keep up to date its component libraries, focusing on reducing existing issues and integrating the missing EIPs. By improving the additional Web3j libraries, we aim to streamline development workflows, enhance testability, and create a more robust framework that simplifies Ethereum development for Java and JVM-based projects. The updates will address known gaps in the libraries, ensuring compatibility with the latest Ethereum standards while improving documentation, developer experience, and maintainability.</p><p><br></p><p>A similar mentorship project took place during the last mentorship program and resulted in significant code contributions, documentation and blog posts.</p><p><br></p><p>The initiative will introduce structural improvements, new features and documentation for better integration, and testing, making Web3j a more sustainable and adaptable web3 development tool project.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain hands-on experience contributing to an open-source blockchain library, improving their understanding of Ethereum integration in JVM applications.</li><li>Develop expertise in Java and its application in blockchain smart contract development.</li><li>Enhance their skills in software libraries architecture, Ethereum blockchain and Solidity Smart Contracts development practices.</li><li>Collaborate with an open-source community, learning best practices for issue tracking, code reviews, and pull request management.</li><li>Develop expertise in complex library release process and code management.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/60" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/60</a></p>

javagradlegithub api+5
1 active years2026
Explore
Lima logo

Lima

Cloud Native Computing Foundation (CNCF)

<p>Lima launches Linux virtual machines with automatic file sharing and port forwarding (similar to WSL2). Currently, Lima supports Linux, macOS, and FreeBSD as guest operating systems. The primary goal of this project is to expand this capability by adding support for Windows guests. Furthermore, the project aims to improve the stability and user experience of running Lima on Windows hosts. This will be achieved by removing dependencies like `cygpath.exe`, researching and developing a native Hyper-V(or a [HCS](<a href="https://learn.microsoft.com/en-us/virtualization/api/hcs/overview" rel="noopener noreferrer" target="_blank">https://learn.microsoft.com/en-us/virtualization/api/hcs/overview</a>) driver to provide optimized, native virtualization on Windows hosts.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Primary:</li><li class="ql-indent-1">The ability to successfully launch and run Windows guest virtual machines using `limactl start template:windows` using the QEMU driver on any host.</li><li class="ql-indent-1">Deliver a seamless installation experience on Windows hosts by automating configurations and eliminating the need for [manual setup notes](<a href="https://github.com/microsoft/winget-pkgs/pull/356038/changes#diff-9c16ba1b4e8cfc88d634b6cc436e0041d2201ac93e1d4fcd78fca09e0667ca3aR29" rel="noopener noreferrer" target="_blank">https://github.com/microsoft/winget-pkgs/pull/356038/changes#diff-9c16ba1b4e8cfc88d634b6cc436e0041d2201ac93e1d4fcd78fca09e0667ca3aR29</a>)</li><li class="ql-indent-1">Complete removal of the `cygpath.exe` dependency.</li><li>&nbsp;Secondary (if time permits):</li><li class="ql-indent-1">Investigate and decide between Hyper-V and HCS for the native driver: HCS is the basis of WSL2 and may be available in Windows 11 Home Edition, while Hyper-V is only available in Pro/Enterprise editions. Research availability and integration feasibility.</li><li class="ql-indent-1">Potentially integrate the chosen driver (Hyper-V or HCS) as an [external VM driver](<a href="https://lima-vm.io/docs/dev/drivers/" rel="noopener noreferrer" target="_blank">https://lima-vm.io/docs/dev/drivers/</a>).</li><li>Tertiary Goals (if time permits): Upgrade the existing WSL2 driver to drop image restrictions and allow users to run multiple instances, as well as exploring a simple graphical interface (`limagui.exe`) to launch virtual machines.</li></ul><p><br></p>

goqemuhyper-v+2
1 active years2026
Explore
Linux kernel Spring Unpaid 2026 logo

Linux kernel Spring Unpaid 2026

Linux Foundation

Linux kernel is the largest open source project with 2+ million lines of code and 10,000 developers across the globe. It is a challenge to understand how the community works, how to get started learning the code base, and take steps to become a contributor. This project will help the applicants help navigating the code base, community, and guide them in choosing the areas of the kernel, finding kernel bugs to focus on, and developing a solution working with the experts in the community. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and get their patches accepted into the kernel.

cshellgnu make+3
1 active years2026
Explore
Linux kernel Summer Unpaid 2026 logo

Linux kernel Summer Unpaid 2026

Linux Foundation

<p><span style="color: rgb(65, 65, 65);">The Linux kernel is the largest open source project with millions of lines of code and 10,000+ developers across the globe. It is a challenge to understand how the community works, how to get started in learning the code base, and take steps to become a contributor. This project will help developers new to kernel development navigate the large code base, diverse community, and guide them in choosing the areas of the kernel to focus on to enhance, fix bugs, and develop solutions working with the experts in the community. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and get their patches accepted into the kernel.</span></p>

cshellgnu make+4
1 active years2026
Explore
Magma Core ( Unpaid 2026) logo

Magma Core ( Unpaid 2026)

Linux Foundation

Magma is an open-source software platform that gives network operators an open, flexible and extendable mobile core network solution. Magma enables better connectivity by: Allowing operators to offer cellular service without vendor lock-in with a modern, open source core network Enabling operators to manage their networks more efficiently with more automation, less downtime, better predictability, and more agility to add new services and applications Enabling federation between existing MNOs and new infrastructure providers for expanding rural infrastructure Allowing operators who are constrained with licensed spectrum to add capacity and reach by using Wi-Fi and CBRS

network5g4g+2
2 active years2026
Explore
Mainframe Modernization Whitepaper (unpaid) logo

Mainframe Modernization Whitepaper (unpaid)

Linux Foundation

<p>Advance thought leadership around what it means to modernize the mainframe. Our mentorship program offers you the chance to research, analyse, and document strategies for modernization of mainframes and the applications workloads that run on top of it. You'll work closely with a mentor and connect with top industry professionals.</p><p><br></p><p>Deliverables: A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>

research skillstechnical writtingmainframes
1 active years2026
Explore
Mainframe Open Education – Educational Content & Advocacy Mentorship (Unpaid-2026) logo

Mainframe Open Education – Educational Content & Advocacy Mentorship (Unpaid-2026)

Linux Foundation

<p>The Mainframe Open Education (MOE) Project seeks a creative and enthusiastic individual to serve as a&nbsp;<strong>Mainframe Education Advocate</strong>. The primary goal of this mentorship is to champion&nbsp;<strong>peer-to-peer education</strong>: taking foundational mainframe concepts and turning them into clear, engaging, and accessible content for the student community.</p><p>The 2026 program emphasizes&nbsp;<strong>Education-as-Communication</strong>. The mentee will act as a relatable voice for the student and early-career community, documenting their own learning journey and translating foundational technical workflows into engaging, introductory-level blog series and interactive modules.</p><p><br></p><p><strong>Deliverables</strong></p><p><strong>"Mainframe 101" Blog Series:</strong>&nbsp;Create a series of 3–4 introductory blogs that break down foundational topics into easy-to-digest, interactive guides.</p><p><strong>Social Advocacy:</strong>&nbsp;Create short-form summaries of educational content to share across student-facing platforms, driving awareness of the Open Mainframe Project.</p><p><strong>Peer Collaboration:</strong>&nbsp;Work alongside the MOE Student User Group to identify the top 5 "points of confusion" for new learners and address them through content.</p><p><strong>Mentorship Journey Blog:</strong>&nbsp;A post reflecting on their experience learning within the OMP/MOE community and tips for other undergraduates looking to get started.</p><p><strong>Industry Engagement:</strong>&nbsp;Develop a session for an industry event, focusing on the importance of student-led technical documentation.</p>

educationcommunicationcommunity
1 active years2026
Explore
Mapping the RISC-V Extensions Landscape logo

Mapping the RISC-V Extensions Landscape

RISC-V

<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>

javascriptreactjson+9
1 active years2026
Explore
Minder 2026 logo

Minder 2026

Linux Foundation

<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>

gopythonshell+1
1 active years2026
Explore
Mirror Serial Console Traffic in SONiC logo

Mirror Serial Console Traffic in SONiC

Linux Foundation

<p><strong>*APPLICATIONS ONLY OPEN TO STUDENTS LOCATED IN CHINA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>SONiC supports serial console management using console switch functions, enabling it to act as a terminal server and control devices through the serial console. Diagnosing issues with the serial console can be challenging because the connection is exclusive, so only the user on that line knows what’s happening. For Ethernet, SONiC users can leverage the Everflow feature to mirror data plane traffic or use tcpdump to monitor control plane traffic. In the context of serial consoles, however, a new feature is needed to mirror serial console traffic, which would greatly assist with diagnosing console problems.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The goal of this project is to create and implement a new SONiC feature that lets users start or stop recording for a specific console line whenever needed.</p><p>Key features include:</p><ul><li>Designing a file format to store the serial console data stream, with configurable time resolution.</li><li>Mirroring incoming (RX) data streams to a local file.</li><li>Mirroring outgoing (TX) data streams to a local file.</li><li>Adding CLI support to start or stop recording for any serial console line.</li><li>Additional desired features are:</li><li>Mirroring the CTS flow control signal to a local file.</li><li>Mirroring the RTS flow control signal to a local file.</li><li>Providing encryption for recordings.</li><li>Implementing gNOI APIs to enable start/stop recording for specific serial console lines.</li><li>The feature will be implemented in Python based on existing serial console infrastructure which allows developer to manipulate serial console data stream.</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>HLD document for console mirroring feature</li><li>Implementation details of console mirroring</li><li>Test plan for console mirroring</li><li>Test cases for console mirroring</li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Familiarity with a common programming language (Python, Java, C, C++, Rust, etc.)</li><li>Basic Linux knowledge</li><li>Basic SONiC knowledge (preferred)</li><li>AI or vibe coding experience (preferred)</li></ul>

pythonjavac+2
1 active years2026
Explore
Multi-asic T1 and T2 PR checker logo

Multi-asic T1 and T2 PR checker

Linux Foundation

<p><strong>*APPLICATIONS ONLY OPEN TO US BASED COLLEGE STUDENTS*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p>&nbsp;</p><p>The current multi-ASIC T1 PR checker and T2 PR checker in SONiC major github repositories have much less test coverages than the T0/T1 PR checkers, because some existing test cases need proper adaptation to work on virtual multi-ASIC T1 and T2 emulators. That has made SONiC images for multi-asic T1 and T2 platforms more prone to regressions. To leverage the benefits of automated CI/CD pipeline, we aim to work on the test cases that are currently failing on multi-ASIC T1 and T2 PR checker so that we can increase the test coverage. We believe this is a good opportunity for beginners to get hands-on experience on SONiC system and contributed to the improvements of SONiC image quality.</p><p>&nbsp;</p><p><strong>Mentorship Objectives</strong></p><p>&nbsp;</p><p>* Help the mentee learn about the basic knowledge of SONiC OS</p><p>* Help the mentee get hands-on experience on SONiC OS code and sonic-mgmt testing system.</p><p>* Help the mentee learn about network emulation and automation</p><p>&nbsp;</p><p><strong>Expected Outcomes and Deliverables</strong></p><p>&nbsp;</p><p>* Increase test coverage of multi-ASIC T1 PR checker and T2 PR checker in sonic-buildimage and sonic-mgmt repos.</p><p>* Improve the performance of existing test cases or the current implementation virtual multi-asic T1 and T2 emulators</p><p>*THIS IS A SUMMER TERM PROGRAM (MAY - AUGUST) 40 HOURS A WEEK</p><p>&nbsp;</p><p><strong>Recommended Qualifications</strong></p><p>&nbsp;</p><p>1. Knowledge about one of the common programming language: python/java/c++/golang</p><p>2. Basic understandings of Linux networking stack</p><p>3. Familiarity of containers</p>

pythonjavac+++1
1 active years2026
Explore
Open Mainframe Project - Modernising Mainframe with Open Source  (Unpaid-2026) logo

Open Mainframe Project - Modernising Mainframe with Open Source (Unpaid-2026)

Linux Foundation

<p><span style="color: rgb(0, 0, 0);">The zopen community is a collaborative initiative dedicated to modernizing the z/OS platform by porting widely used open-source tools and libraries. Our goal is to bridge the skill and technology gap between mainframes and other modern computing environments by making z/OS a first-class open-source platform. As a mentee, you will contribute to this mission by working alongside experienced developers to port and extend open-source software for z/OS.</span></p><p><br></p><p><span style="color: rgb(0, 0, 0);">Although the zopen community has 300+ open source tools ported, Many essential developer tools and libraries are not available on z/OS. A prioritized list of tools that require porting are listed under: </span></p><p><a href="https://github.com/orgs/zopencommunity/discussions/1019" rel="noopener noreferrer" target="_blank">https://github.com/orgs/zopencommunity/discussions/1019</a><a href="https://github.com/zopencommunity/meta/issues/922." rel="noopener noreferrer" target="_blank" style="background-color: rgb(255, 255, 255);">.</a><span style="color: rgb(0, 0, 0);"> They include rpm, LuaJIT (for Noevim), htop and many more.</span></p><p><br></p><p><span style="color: rgb(0, 0, 0);">A successful mentee will:</span></p><p><br></p><p><span style="color: rgb(0, 0, 0);">- Port an open-source tool to z/OS, ensuring it builds successfully.</span></p><p><span style="color: rgb(0, 0, 0);">- Work towards achieving at least 90% unit test pass rate.</span></p><p><span style="color: rgb(0, 0, 0);">- Release the tool for use by the broader zopen community.</span></p><p><span style="color: rgb(0, 0, 0);">- Work with the open source community to upstream z/OS changes</span></p>

cc++java+2
1 active years2026
Explore
OpenCost logo

OpenCost

Cloud Native Computing Foundation (CNCF)

We need enhanced integration tests to prepare OpenCost for graduation and enterprise readiness. This proposed project will deliver a comprehensive suite of integration tests designed to facilitate development and contribution by third parties, while protecting the stability of OpenCost for our tens of thousands of users. These tests will validate both the quality of the data collected by OpenCost, and the correct operation of the APIs. We have recently implemented a pipeline that builds real stacks for these tests to hit - we now need to fill that framework up with great tests. See the testing strategy document @ https://github.com/opencost/opencost/blob/develop/docs/testing/AUTOMATED_TESTING.md for the current state of testing, and the infrastructure that we have put into place to support this mentorship effort. Expected Outcome: 1) A comprehensive integration test suite as defined in the linked ticket. 2) All tests run and pass automatically in pre-existing per-push integration test pipeline. 3) Approach for each integration test is documented 4) Endpoint coverage % and parameter coverage % is calculated 5) Any unfinished or follow on work is documented via issues on OpenCost

reactux designfrontend development+16
2 active years2026
Explore
OpenEverest logo

OpenEverest

Cloud Native Computing Foundation (CNCF)

<p>OpenEverest is an open-source cloud-native database platform that helps developers deploy and manage PostgreSQL, MySQL, MongoDB, and other databases on Kubernetes. Currently, `everestctl` serves primarily as an installation tool for deploying and deleting OpenEverest itself. However, users increasingly need a powerful command-line interface to manage their databases, clusters, and integrations directly from the terminal. This project aims to transform `everestctl` from a basic deployment tool into a comprehensive CLI for managing OpenEverest resources. The mentee will design and implement a modern, user-friendly CLI experience that allows users to provision databases, manage Kubernetes clusters, interact with OpenEverest plugins, and automate database operations — all without leaving their terminal. The project will involve working with Go, Kubernetes APIs, OpenEverest's plugin architecture, and modern CLI frameworks like Cobra.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Core database management commands: `everestctl db list`, `create`, `delete`, `get`, `logs` for PostgreSQL, MySQL, and MongoDB</li><li>Cluster management: `everestctl cluster list`, `register`, `status` for managing Kubernetes clusters</li><li>Plugin integration: `everestctl plugin list`, `install`, `configure` for OpenEverest plugins</li><li>Shell completion scripts (bash, zsh, fish)</li><li>Unit and integration tests with &gt;80% coverage</li><li>Comprehensive documentation with usage examples</li></ul>

reacttypescriptmui+12
1 active years2026
Explore
Platform Driver Development Framework Improvements logo

Platform Driver Development Framework Improvements

Linux Foundation

<p><strong>*APPLICATIONS ONLY OPEN TO COLLEGE STUDENTS BASED IN THE UNITED STATES*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p>&nbsp;</p><p>Platform Driver Development Framework (PDDF) is a common abstraction interface used by system vendors to define peripheral devices like temp sensors, fans, and power supplies, and associate those devices with drivers in SONiC.&nbsp;Improvements can be made for (1) memory savings, (2) performance benefits, and (3) improve visibility of managed devices.&nbsp;</p><p>&nbsp;</p><p><strong>Mentorship Objectives</strong></p><p>&nbsp;</p><p>* Help the mentee learn about the SONiC NOS</p><p>* Help the mentee gain experience in contributing to the open source community.</p><p>* Help the mentee learn about how device drivers are managed in SONiC</p><p>&nbsp;</p><p><strong>Expected Outcomes and Deliverables</strong></p><p>&nbsp;</p><p>* Add “show” commands to better display the PDDF configuration and status information</p><p>* Parallelize PDDF device initialization</p><p>* Monitor PDDF managed device health</p><p>* Enhance PDDF code reuse and extensibility</p><p>* Introduce a unit test framework which injects a mock sysfs for PDDF</p><p>* Introduce a reboot cause framework to PDDF</p><p>* Add enhancements to PDDF framework related to thermal management</p><p><strong>Summer / Fall Term: Expecting 20~ hours of work each week</strong></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p>&nbsp;</p><p>Knowledge of programming languages - C/C++/Python.&nbsp;</p><p>Basic understanding of Linux</p><p>Familiarity with containers (docker)</p><p>(Preferable) Basic understand of device drivers</p><p>(Preferable) interest or experience in AI-based coding</p>

cc++python
1 active years2026
Explore
RISC-V ACT Framework Enablement and M-Mode Firmware Validation on Hardware Board logo

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

RISC-V

<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>

cc++embedded systems+11
1 active years2026
Explore
RISC-V Audiomark logo

RISC-V Audiomark

RISC-V

EEMBC AudioMark is a benchmark which models a sophisticated, real-world audio pipeline that uses a neural net for keyword spotting. It combines digital signal processing and AI tasks in one workload. This benchmark currently does not have dedicated RISC-V support. It is based on CMSIS-NN and CMSIS-DSP libraries, for which several vendor-specific ports to RISC-V by IP suppliers exist. The goal of this mentorship is bootstrap the RISC-V support for AudioMark and the addition of architecture specific optimizations. The architectural extensions which benefit this benchmark are the RISC-V Vector extension, and the currently in-development specification for Packed SIMD (P).

compilerssimulatorsc-programming+2
1 active years2026
Explore
RISC-V Processor Certification logo

RISC-V Processor Certification

RISC-V

The RISC-V Certification Steering Committee is developing certification tests to prove that RISC-V processors conform to the ratified specifications. The goal of this mentorship project is to run the tests on as many open-source RISC-V cores as possible, and improve the usability of the tests, debug any issues found in the tests, and report any real bugs that might be found in the cores. This work will involve: * Identifying multiple open-source cores to test * For each core: - Develop a Unified Database (UDB) file specifying the extensions and parameters supported by the core - Implement trick box macros to trigger interrupts, print characters to a console, and terminate a simulation in a core- specific manner - Create a linker script appropriate to the memory map of the core - Compile the tests with the core-specific trick box and linker scripts - Run the relevant tests on the core * Identify and fix any problems in the tests that make them hard to run on a core * Identify and fix any problems with the flow or documentation * Identify and report any bugs found in the cores The work will start with Phase 0 tests of the RVI20 profile with the RV{32/64}IMACDF extensions in machine mode. As time permits, it will continue to the Phase 1 MC100 microcontroller profile with machine mode, traps, Zicsr, and Zicntr, and then to the Phase 2 RVA23 application processor profile with all privilege modes, vector and hypervisor.

risc-v instruction setgcc toolchainsystemverilog simulation+4
1 active years2026
Explore
RISC-V Vector Coprocessor for ECG Detection on UET-RVMCU logo

RISC-V Vector Coprocessor for ECG Detection on UET-RVMCU

RISC-V

This project aims to develop and verify a custom RISC-V Vector (RVV) v1.0 compliant coprocessor to accelerate an Electrocardiogram (ECG) detection algorithm. Building on our previous work with a CGRA accelerator, this project addresses its key limitations by leveraging the standardized RISC-V Vector extension, which offers superior toolchain support and predictable data-level parallelism. The mentee will focus on two core pillars: 1. Verification and Integration of RVV Modules: Rigorously test and integrate pre-designed hardware modules to build a functional vector coprocessor. 2. Algorithm Development: Implement and optimize vectorized ECG signal processing kernels using RVV intrinsics.

system verilogriscv-isapipelining+1
1 active years2026
Explore
Repository Service for TUF (RSTUF) 2026 logo

Repository Service for TUF (RSTUF) 2026

Linux Foundation

<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>

documentation best practicesuser-focused documentationtest-driven development (tdd)+19
1 active years2026
Explore
Role of AI in mainframe application modernization (unpaid) logo

Role of AI in mainframe application modernization (unpaid)

Linux Foundation

<p>The primary objective of this project is to analyze how artificial intelligence (AI) tools can assist in mainframe application modernization. The mentee will evaluate the strengths and weaknesses of traditional versus AI-assisted modernization approaches. The research will explore how AI enables business rule extraction and addresses specific challenges where manual methods or traditional tooling fall short. Additionally, the project will assess the current technical limitations and discuss a cost-benefit of AI-driven modernization.</p><p><br></p><p>Deliverables:</p><p>A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>

research skillstechnical writtingai+4
1 active years2026
Explore
Role of mainframes in Digital sovereignty and resilience (unpaid) logo

Role of mainframes in Digital sovereignty and resilience (unpaid)

Linux Foundation

<p>The primary objective of this project is to analyze the role of mainframe platforms in achieving digital sovereignty and operational resilience within enterprise architectures. The mentee will evaluate the strengths and weaknesses of on-premise mainframe infrastructure compared to public cloud environments, specifically focusing on data residency, regulatory compliance (such as DORA), and resilience models. The research will explore how mainframes address critical sovereignty challenges, including third-party concentration risk and data access governance, where distributed systems may introduce vulnerabilities. Additionally, the project will assess the technical limitations of mainframe-centric strategies, such as skills dependencies, and provide a strategic analysis of hybrid sovereign architectures.</p><p><br></p><p>Deliverables: A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>

research skillstechnical writtingregulatory compliance+2
1 active years2026
Explore
SBOMit 2026 logo

SBOMit 2026

Linux Foundation

<p><strong>Purpose</strong></p><p>SBOMit is a means to generate accurate SBOMs by using in-toto attestations gathered at build time.&nbsp;This is not just a software project to consume attestations and refines them into SBOMs in a cryptographic manner, but also involves helping stakeholders adopt this technology as an option into existing tooling.</p><p><br></p><p><strong>Goal</strong></p><p>Add support for Aqua Security’s Trivy:&nbsp;We have a fork of Anchore’s Syft which adds support for SBOMit.&nbsp;We’d like a POC for this with Trivy and then the community work needed to try to get this either upstreamed into Trivy, or at least have the community be aware of this fork’s existence.</p><p><br></p><p><strong>Update to Website and Improve Documentation: </strong>The current SBOMit website does not capture any of the work completed since the writing of the original specification and needs to be updated. The documentation of each of the efforts under the SBOMit project (SBOMit, Syft fork, In-toto Network Trace Attestation, and others) will improve the project’s ability to encourage new contributors and collect feedback from end users.</p><p><br></p><p><strong>Desired Outcomes &amp; Deliverables</strong> (1-2 mentees)</p><p><strong>Prototype SBOMit capabilities in Trivy</strong></p><p>This project should result in a working prototype of SBOMit capabilities integrated directly into a fork of the Trivy project. This would include the ability to enrich an SBOM generated by Trivy with data from in-toto attestations.</p><p><br></p><p><em>Deliverables</em></p><p>&nbsp;&nbsp;•&nbsp;&nbsp;Working code to extend SBOMit capabilities into Trivy</p><p>&nbsp;&nbsp;•&nbsp;&nbsp;Test and demo examples of attestations and SBOMs capturing the build process of projects in multiple different programming languages with an ability to highlight the specific information added from the SBOMit approach</p><p>&nbsp;&nbsp;•&nbsp;&nbsp;Documentation or notes from a Trivy community meeting sharing the work back to its project maintainers to gather interest in the ability to upstream the contributions.</p><p><br></p><p><strong>Update to Website and Improve Documentation</strong></p><p>This project should result in an up-to-date and accurate SBOMit website and current documentation in the GitHub repositories of the respective project efforts.</p><p><br></p><p><em>Deliverables</em></p><p>&nbsp;&nbsp;•&nbsp;&nbsp;Updated content for the SBOMit website detailing current work.</p><p>&nbsp;&nbsp;•&nbsp;&nbsp;A “Getting Started” guide for the SBOMit website.</p><p>&nbsp;&nbsp;•&nbsp;&nbsp;Updated documentation in the SBOMit project repos.</p>

documentationsbomsin-toto+3
1 active years2026
Explore
Page 1 of 5
12345

Looking for a program first?

Start with GSoC, European Summer of Code, Outreachy, or LFX — then drill into orgs.

All programs
SONiC OS Profiling logo

SONiC OS Profiling

Linux Foundation

<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>

py-spyperfpidstat
1 active years2026
Explore
SONiC Test Runtime Optimization logo

SONiC Test Runtime Optimization

Linux Foundation

<p>*APPLICATIONS ONLY OPEN TO STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>The sonic-mgmt test framework is a critical component of PR validation and continuous integration. However, over time, several inefficiencies have accumulated:</p><ul><li>Some individual test scripts run longer than 30 minutes, and some individual test cases exceed 10 minutes, PR pipelines retry failed test scripts up to two additional times, amplifying runtime cost.</li><li>Long-running scripts disproportionately consume KVM CPU resources.</li><li>Excessive runtime increases PR turnaround time and reduces CI throughput.</li></ul><p><br></p><p>Currently, there is no formal runtime governance framework, no enforcement threshold, and limited visibility into runtime regressions across scripts, test cases, topology types, and branches.</p><p><br></p><p>As SONiC continues to scale, unmanaged test runtime growth will:</p><ul><li>Increase infrastructure cost</li><li>Slow down PR validation</li><li>Reduce contributor productivity</li><li>Impact overall CI system stability</li></ul><p>This project aims to establish a data-driven runtime governance and optimization framework for sonic-mgmt.</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The mentee(s) will work on designing and implementing a structured runtime optimization initiative that includes:</p><ul><li>Refactor selected high-impact long-running test scripts</li><li>Propose test case optimization strategies:</li><li class="ql-indent-1">Reduce loop/iteration counts</li><li class="ql-indent-1">Reduce coverage where representative sampling is sufficient</li><li class="ql-indent-1">Optimize setup/teardown overhead</li><li class="ql-indent-1">Remove redundant waits</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>By the end of the mentorship program, the following deliverables are expected:</p><ul><li>Refactored high-impact test scripts demonstrating measurable improvement</li><li>A structured runtime dataset and analysis report</li><li>A documented SONiC Test Runtime Best Practices guide</li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><ul><li>Python programming skills</li><li>Familiarity with pytest framework</li><li>Basic understanding of CI/CD systems</li><li>Ability to analyze data (Kusto / SQL / Pandas experience preferred)</li><li>Understanding of networking fundamentals (basic SONiC knowledge preferred)</li></ul>

pythonpytestci/cd+2
1 active years2026
Explore
Shadow Analytics via Redis Replica logo

Shadow Analytics via Redis Replica

Linux Foundation

<p>*APPLICATION ONLY OPEN TO STUDENTS IN INDIA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>SONiC is a database-centric NOS: much of the control-plane and operational state is available in Redis, and telemetry can poll/subscribe to DB data. There are a variety of interesting analytics and telemetry data that can be extracted from this DB, many by leveraging Redis capabilities. However, directly adding heavy analytics (e.g., long-running server-side scripts) to the primary Redis risks impacting normal SONiC applications. Redis Lua scripts execute atomically but block the server for the full runtime of the script. This project proposes a low-risk pattern: create a Redis replica (master → replica) that maintains a synchronized copy of selected SONiC databases, and run the analytics plane on the replica.&nbsp;</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><ul><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Design and prototype a “shadow analytics plane” using Redis replication (master → replica) so normal SONiC apps continue to use the primary Redis instance unchanged. Design and implement cold boot, Warmboot and fast-boot.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Implement use-cases, some examples”</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Incident Forensics (A): Build a flight-recorder capability on the replica that can reconstruct recent sequences of “interesting” changes (timeline) and provide a compact incident summary.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Alert Storm Reduction (B): Build novelty detection and heavy-hitter summarization on the replica to suppress repeated alerts and highlight top recurring signatures.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Provide operational documentation: how to deploy, how to tune retention/limits, and how to validate that primary-path performance is not affected.</span></li></ul><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Strong Linux fundamentals; comfortable working in containerized environments.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Python and/or Go proficiency (for collectors, processors, and CLI tooling).</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Basic understanding of Redis concepts (pub/sub, streams, replication) and willingness to learn SONiC DB schemas.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Interest in reliability engineering / observability / operational tooling.</span></li></ul><p><br></p>

pythonlinuxgo
1 active years2026
Explore
Simplify Platform and Device Management logo

Simplify Platform and Device Management

Linux Foundation

<p>*ONLY OPEN TO COLLEGE STUDENTS LOCATED IN INDIA*</p><p><br></p><p>Problem Statement</p><p><br></p><p>Onboarding new platforms (sonic-buildimage/platform/) and devices (sonic-buildimage/device/) in SONiC is a cumbersome process: changesets are typically large and reviews are tedious. In addition, current commit checks build only a specific set of platforms (for example, Broadcom, Marvell armhf/arm64, Mellanox, VS). When changes impact a platform outside that set (for example, Marvell Teralynx), the changed platform may not be tested, while unrelated platform builds are still executed—wasting CI resources.</p><p>Note: There have been recent changes to select test-cases among DPU, Multi-ASIC, Dual-TOR etc. based on the areas impacted by the code. We want to extend this across platforms.</p><p><br></p><p>This mentorship aims to simplify platform/device onboarding and maintenance by reducing changeset size through modularization and reuse, automating repetitive reviewer checks (such as detecting binary artifacts), enabling selective commit-gating tests based on impacted paths, and creating directory-specific .github/copilot-instructions.md guidance to reduce review cycles.</p><p><br></p><p>Mentorship Objectives</p><p><br></p><p>Investigate mechanisms to reduce platform/device onboarding changeset size (for example, modularizing and reusing common templates such as buffers.json.j2 and qos.json.j2).</p><p><br></p><p>Automate reviewer work by adding checks for issues often found manually (for example, detect binary artifacts introduced in a changeset).</p><p><br></p><p>Enable selective commit-gating tests by mapping changed paths to the minimum relevant builds/tests; avoid running tests for untouched platforms.</p><p><br></p><p>Create directory-specific .github/copilot-instructions.md (starting with platform/ and device/) so Copilot and other AI tools generate changes aligned with SONiC conventions and CI expectations.</p>

pythonlinuxshell
1 active years2026
Explore
Talent Angels @ Learning Tokens logo

Talent Angels @ Learning Tokens

Linux Foundation

<p>Develop a suite of AI Graph Agents that empower humans to navigate the landscape of skills, tasks, and occupations for lifelong learning in the age of AI.</p><p><br></p><p><strong>Why?</strong></p><p>Skills are the currency of talent. In the age of AI, skill demand shifts faster than any individual, educator, or employer can track, making it critical for humans and AI systems alike to know what to learn, how to develop it, and when it becomes relevant.</p><p><br></p><p><strong>How?</strong></p><p>In AI systems, skills encode domain expertise, reusable workflows, and context, providing a powerful abstraction for how work gets done. In the human world, however, skills, tasks, and occupations remain scattered across incompatible taxonomies with no shared semantic framework, widening the gap between human talent development and the rapidly evolving demands of an AI-driven work ecosystem.</p><p><br></p><p>Similar work already exists within the domain of AI tools, such as Anthropic Skills within the Claude platform; however, efforts of this nature for human use, or interfaces and tools to browse through skill databases that empower humans, are less frequent, which is also a motivation for this project.</p><p><br></p><p>By querying these taxonomies through AI Graph Agents that build and traverse knowledge graphs, we crowdsource a living ontology of talent that bridges human skills development and AI-driven work.</p><p><br></p><p><strong>What?</strong></p><p>Talent Angels is a suite of AI Graph Agents that queries and reasons over the following global taxonomies of skills, tasks, and occupations through a natural language chat interface:</p><ol><li>ESCO, with knowledge, skill, and competencies relevant to the European Union labor market, education, and training.</li><li>O*NET, with all occupations by the U.S. Department of Labor.</li><li>SFIA, a global framework for digital skills and competencies.</li><li>BLS, Occupational Outlook Handbook for career guidance.</li><li>Lightcast, a crowd-sourced common skills language.</li></ol><p><br></p><p><strong>We envision three kinds of agents:</strong></p><ol><li>Locator&nbsp;identifies and pinpoints the exact positions of skills, tasks, and occupations within the taxonomies.</li><li>Connector&nbsp;determines and lists the sequence of nodes directly preceding and succeeding each specified location, enabling users to view related tasks or skills.</li><li>Pathfinder&nbsp;traces and maps all possible routes connecting two locations through combinations of Connector paths, enabling users to discover learning journeys between any two skills, tasks, or occupations.</li></ol><h3><br></h3><h3>Learning Objectives</h3><ul><li>Learn to collaborate in an open-source project.</li><li>Learn about an ontology of Talent.</li><li>Learn to apply Knowledge Graphs.</li><li>Learn the foundational concepts of AI agents.</li><li>Learn to build, evaluate, and deploy AI-powered agents in a production open-source environment.</li><li>Understand the relationships between occupations, tasks and skills.</li><li>Contribute standard descriptions of skills, tasks, and occupations.</li><li>Apply Learning Tokens to granular skill acquisition processes.</li></ul><p><br></p><p><span style="color: rgb(0, 0, 0);">Lean more at </span><a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/80" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/80</a></p>

pythonllmsrest apis+14
1 active years2026
Explore
Test Program logo

Test Program

Linux Foundation

<p>created for testing <a href="google.com" rel="noopener noreferrer" target="_blank">here</a>. https://mentorship.lfx.linuxfoundation.org/project/bd50b598-7969-467c-9191-abfc2199112a/edit</p><p><a href="https://mentorship.lfx.linuxfoundation.org/project/bd50b598-7969-467c-9191-abfc2199112a/edit" rel="noopener noreferrer" target="_blank">Here</a></p>

ajax3d
1 active years2026
Explore
Top-N Interface Traffic Visibility Feature in SONiC logo

Top-N Interface Traffic Visibility Feature in SONiC

Linux Foundation

<p>*<strong>APPLICATION ONLY OPEN TO COLLEGE STUDENTS LOCATED IN INDIA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p>&nbsp;</p><p>SONiC currently exposes per-interface traffic counters, but operators lack a simple mechanism to quickly identify which interfaces are carrying the highest traffic at any given time. In large-scale deployments, manually scanning counters is inefficient and error-prone.</p><p>&nbsp;</p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The objective of this project is to design and implement a SONiC feature that displays the top N (default: 5) interfaces carrying the highest traffic. The feature will be exposed via the SONiC CLI and will leverage existing interface counters.</p><p>&nbsp;</p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>A new CLI command will be introduced to calculate and display the top interfaces based on real-time traffic rates. The implementation will read interface counters from SONiC databases, compute traffic deltas over a configurable interval, sort interfaces by total throughput, and present the top results in a user-friendly format. <strong>*SUMMER SEMESTER EXPECTATION OF 40 HOURS OF WORK A WEEK*</strong></p><p><br></p><p><strong>Key Features</strong></p><p><br></p><p>- Display top 5 interfaces by traffic (RX + TX)</p><p>- Configurable sampling interval</p><p>- JSON output option for automation</p><p>- Minimal performance overhead</p><p><br></p><p><strong>Technology Scope</strong></p><p><br></p><p>The implementation will be done in Python and integrated into the sonic-utilities CLI. Interface counters will be read from COUNTERS_DB. Traffic rates will be computed using delta-based calculations between two samples.</p><p><br></p><p><strong>Expected Outcome</strong></p><p>At the end of the project, SONiC users will have a simple and effective tool to quickly identify high-traffic interfaces, improving troubleshooting and capacity planning.</p><p>&nbsp;</p><p><strong>Recommended Qualifications</strong></p><p>&nbsp;</p><p>1. Knowledge about one of the common programming language: python/java/c++/golang</p><p>2. Basic understandings of Linux networking stack</p><p>3. Familiarity of containers</p>

pythonc++java+1
1 active years2026
Explore
Trusted Delegation and Pre-execution Security Enforcement for AI Agents (Unpaid) logo

Trusted Delegation and Pre-execution Security Enforcement for AI Agents (Unpaid)

Linux Foundation

<p>Design and implement a secure, auditable platform that enforces pre-execution authority for delegated actions initiated by humans, AI agents, and services. The platform will provide a single gateway for policy-driven request routing, a secret vault for API keys and credentials, and a delegation graph model to represent and evaluate long/deep delegation chains with real-time revocation and immutable proofs recorded to a ledger. Initial work will implement core components (gateway, policy evaluator, delegation graph, secret vault integration, immutable audit records) and end-to-end flows for common delegation scenarios. Later work will extend policy negotiation between agents, security reasoning modules, and audit reporting that derives intent and policy-improvement recommendations. The goal is a practical mentorship project that teaches secure authority delegation, DLT-backed auditability, and interoperable identity and credential patterns.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Understand and implement delegation models and graph-based authority evaluation.</li><li>Build a policy-driven gateway that enforces pre-execution checks and real-time revocation.</li><li>Integrate secure secret storage and key management for service/API credentials.</li><li>Record tamper-evident audit trails on an immutable ledger and derive actionable audit reports.</li><li>Apply decentralized identity / verifiable-credential concepts to authorize principals (human, agent, service).</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Working prototype of a single gateway enforcing policy-checked executions with revocation support.</li><li>Delegation Graph module with algorithms for evaluation and path resolution.</li><li>Secret Vault integration (API for storing/retrieving encrypted keys) and sample connectors.</li><li>Immutable audit-log storage adapter (ledger integration) and a basic audit-report generator.</li><li>Documentation: architecture diagram, developer guide, onboarding tasks, and end-to-end test scenarios.</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/78" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/78</a></p>

programming experience in python and node with backend and api development.familiarity with ai/agent frameworks and systems where ai interacts with external tools or services.understanding of distributed systems, gateways, and microservice architectures.+6
1 active years2026
Explore
Using Formal Methods for Comprehensive Malformed Packet Handling in BGP Implementations logo

Using Formal Methods for Comprehensive Malformed Packet Handling in BGP Implementations

Linux Foundation

<p><strong>*APPLICATION ONLY ACCEPTING US BASED COLLEGE STUDENTS*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>As an Internet-facing networking protocol, BGP is one of the most critical components of cloud-scale networks. It enables routing information exchanges between a cloud network and the broad Internet, and incorrect behavior could devastate the connectivity of entire regions. Among many vulnerabilities, the proper handling of malformed packets is particularly important due to the propagation mechanisms of BGP. In real production network, a single mis-handling could result in cascading BGP message floodings across entire regions, degrading services or even causing network outages.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>Currently, high-level BGP behaviors are well-defined through various RFCs. However, low-level details, such as the validation and handling of malformed packets, are often under-specified. Current testing relies on ad-hoc fuzzing or manual test cases, which may miss subtle state-machine interactions that require specific input combinations.</p><p><br></p><p>The objective of this mentorship is to apply formal methods to systematically validate the handling of malformed packets by concrete BGP software implementations. Unlike traditional approaches, formal methods use mathematical logic to systematically explore diverse behaviors triggered by different input combinations, providing comprehensive validation coverage.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>A formal specification that describes high-level BGP interactions.</li><li>A set of implementation-agnostic safety invariants derived from the above high-level model. They ensure that invariant-abiding interactions will not cause cascading effects on neighboring BGP devices.</li><li>A reusable framework that applies off-the-shelf formal methods tools to systematically test concrete BGP implementations against the above invariants.</li><li>A benchmark suite of validated malformed packet scenarios with coverage metrics.</li><li><strong>SUMMER / FALL TERM (20~ HOURS OF WORK EACH WEEK)</strong></li></ul><p><br></p><p><br></p><p>Recommended Qualifications</p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of networks and routing</li><li>Good analytical skills</li></ul><p><br></p>

pythoncc+++1
1 active years2026
Explore
Volcano logo

Volcano

Cloud Native Computing Foundation (CNCF)

Volcano has supported a lot of mainstream computing platforms such as Spark and TensorFlow. As [Ray](https://github.com/ray-project/ray) is a new and popular computing platform, Volcano should integrate with it.

typescriptreactnext.js+51
7 active years2026
Explore
Workflow APIs for Zowe Client Java SDK (Unpaid- 2026) logo

Workflow APIs for Zowe Client Java SDK (Unpaid- 2026)

Linux Foundation

<p>Enhance the Zowe Java SDK by adding support for the z/OSMF Workflow REST APIs documented here:</p><p><br></p><p>https://www.ibm.com/docs/en/zos/2.5.0?topic=services-zosmf-workflow</p><p><br></p><p>This continues the evolution of the SDK toward broader coverage of z/OSMF REST APIs and helps move it closer to full z/OSMF API support. It will also enable the Java community to build automation and tooling for z/OS using modern Java frameworks, libraries, and delivery pipelines.</p>

javahttprest api+1
1 active years2026
Explore
Xen Project logo

Xen Project

Linux Foundation

<p><span style="color: rgb(33, 33, 33);">The Xen Project Summer Internship Program, offers aspiring developers a unique opportunity to contribute to the industry-leading, open-source Type-1 hypervisor. Interns work remotely under the guidance of experienced mentors to solve complex challenges in virtualization, cloud computing, and embedded systems. By following an "upstream first" philosophy, the program immerses participants in the Linux Foundation ecosystem, where they contribute to core technologies such as the Xen Hypervisor, Unikraft (unikernels), and Mirage OS.</span></p>

hypervisorembedded automotivehvmi+7
1 active years2026
Explore
etcd logo

etcd

Cloud Native Computing Foundation (CNCF)

This project is the continuation of the [etcd.io website](https://etcd.io) docs improvement work. While the relocation of the primary documentation, SEO, and site look and feel work has already been done, there is still more work to be done to implement the new information architecture that has been proposed. This includes working with the mentors and project maintainers to write new pages, adapt existing ones, and write blog posts.

golangunderstanding of distributed systems (etcd, kube-apiserver) and systems architecturecybersecurity knowledge+12
2 active years2026
Explore
gittuf-2026 logo

gittuf-2026

Linux Foundation

<h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Purpose</span></h2><p><span style="color: rgb(0, 0, 0); background-color: transparent;">gittuf is a security layer for Git repositories, allowing for a security policy to be applied independently of the service the repository may be hosted on (e.g. GitHub, Gitlab, Bitbucket, etc…). The purpose of this project is to improve gittuf in several domains, such as functionality, usability, and ease of access for new users.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Goal</span></h2><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Improve gittuf's UI and UX</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: gittuf is currently driven primarily by a CLI-based workflow. The gittuf TUI is a work-in-progress UX improvement, where users instead interact with gittuf more akin to a traditional desktop program. The TUI is currently basic, and extending its functionality and improving its appearance so that it can be the primary way users interact with gittuf would be ideal.</span></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Enable temporary/time-limited approvals</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: There may be cases when a developer may need to exercise some discretionary authority and approve something in violation of the policy (e.g. a critical security patch at 4am may not be able to be approved by the full team required in policy). Adding approvals that will satisfy the policy for some duration of time (but not infinitely) would serve to improve this aspect of gittuf.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Desired Outcomes &amp; Deliverables (1-2 mentees)</span></h2><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Improve gittuf's UI and UX</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">This project should result in gittuf featuring a polished, first-class TUI, as well as improvements to gittuf's UX in the CLI and API.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Substantial improvements to the gittuf TUI, both functionally and aesthetically.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use the updated TUI.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Appropriate tests and internal improvements needed to support the upgraded TUI.</span></li></ul><p><br></p><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Add functionality to gittuf to enable temporary/time-limited approvals</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">Some changes in a repository may need to violate the policy (e.g. a critical security patch needing to be released at 4am, and only one developer is available to approve changes at the time).</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(0, 0, 0);">A variant of this feature is to allow for changes to be submitted to a repository that must still be reviewed by someone else at a later time. These changes should not be consumed until they are reviewed, but should not necessarily pose a problem for the repository’s policy.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">A new feature that enables temporary/time-limited approvals in gittuf, as&nbsp; described above.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use this new functionality in gittuf.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Sufficient tests to ensure the proper operation of this new feature.</span></li></ul><p><br></p>

documentation best practicesunit testsgo+5
1 active years2026
Explore
kgateway logo

kgateway

Cloud Native Computing Foundation (CNCF)

<p>The goal of this project is to test and document common&nbsp;</p><p>JWT validation scenarios (e.g., JWKS, multiple issuers, and claim-based validation)</p><p>and demonstrate kgateway integration with multiple OAuth identity providers.</p><p><br></p><p>- Expected Outcome:&nbsp;</p><p>&nbsp;- Design a repeatable documentation pattern for identity providers</p><p>&nbsp;- A set of documentation guides for integrating kgateway with popular IdPs</p><p>&nbsp;- A det of documentation guides covering common JWT validation scenarios</p><p>&nbsp;- Working, reproducible configuration examples (YAML manifests) that users can directly apply</p><p><br></p>

strong written communication skillsinterest in learning and exploring new projects!github api+32
2 active years2026
Explore
krkn - Chaos logo

krkn - Chaos

Cloud Native Computing Foundation (CNCF)

The objective of this internship task is to design and implement a feature of the [`[krknctl](https://github.com/krkn-chaos/krknctl)`](https://github.com/krkn-chaos/krknctl) tool that enables users to explore the project’s functionality by submitting queries in **natural language**. The tool will analyze the user’s request and Identify the most relevant **chaos scenario**, if any. - Expected Outcome: - A **deterministic and lightweight solution** for natural language scenario discovery. - Improved robustness to vocabulary, phrasing, and semantic variations in user queries. - A measurable and extensible evaluation framework to support future improvements. - Clear documentation enabling future contributors to iterate on or extend the approach.

pythonkubernetescontainer runtime environments+5
1 active years2026
Explore
krkn-chaos logo

krkn-chaos

Cloud Native Computing Foundation (CNCF)

<p>Krkn-AI's [discover command](https://krkn-chaos.dev/docs/krkn_ai/discover/) connects to a Kubernetes/OpenShift cluster and generates a static configuration file by enumerating cluster components (namespaces, pods, services, PVCs, nodes). While useful, the generated config still requires significant manual work before it can actually be used. Health check URLs are commented-out placeholders, the fitness function defaults to a single hardcoded PromQL query, and scenario selection is static regardless of what exists in the cluster. This issue proposes enhancing discover to produce a dynamic, cluster-aware configuration that is closer to runnable out-of-the-box. By inspecting routes, ingresses, services, and available Prometheus metrics during discovery, we can auto-populate health check URLs, suggest relevant fitness function queries scoped to discovered namespaces, and intelligently enable only the scenarios that apply to the discovered infrastructure.</p><p><br></p><p>Expected Outcome:&nbsp;</p><p>&nbsp;- Auto-discover OpenShift Routes, Kubernetes Ingresses, and Services to populate health check URLs in the generated configuration.</p><p>&nbsp;- Query Prometheus for available metrics to suggest namespace-scoped fitness function queries instead of hardcoded defaults.</p><p>&nbsp;- Intelligently enable chaos scenarios based on discovered cluster components (e.g., PVC, VMI, network interfaces).</p><p><br></p>

pythongithub actionshugo+5
1 active years2026
Explore
mldsa-native and mlkem-native logo

mldsa-native and mlkem-native

Linux Foundation

This mentorship focuses on contributing to mlkem-native and mldsa-native, production-ready implementations of the ML-KEM and ML-DSA post-quantum cryptography standards. The mentee will help improve and extend these projects by working on areas such as testing, tooling, documentation, build systems, CI/CD infrastructure, platform support, or performance optimization. The project offers flexibility to focus on tasks matching the mentee's interests while contributing meaningfully to the post-quantum cryptography ecosystem.

c programmingpython programmingmake and build systems+6
1 active years2026
Explore
rv-sparse logo

rv-sparse

RISC-V

<p><span style="color: rgb(34, 34, 34);">Sparse linear algebra is fundamental to many domains including scientific computing, machine learning, graph analytics, and large-scale simulations. In modern machine learning workloads, especially pruned neural networks, sparsity is intentionally introduced to reduce computation and memory usage. While several specialized hardware accelerators exist for efficiently executing sparse matrix operations in such workloads, these solutions rely on dedicated hardware and are not always available in general-purpose systems.</span></p><p><br></p><p><span style="color: rgb(34, 34, 34);">Within the RISC-V ecosystem, optimized libraries such as OpenBLAS provide highly efficient implementations for dense linear algebra operations. However, similar support for sparse matrix multiplication optimized for the RISC-V Vector Extension remains limited.</span></p><p><br></p><p><span style="color: rgb(34, 34, 34);">This project aims to develop a lightweight C library that implements key sparse linear algebra primitives particularly sparse matrix multiplication using RISC-V vector intrinsics. The project will handle CSR and CSC sparse storage formats, vectorization strategies, and memory-efficient traversal techniques to better exploit data-level parallelism on RVV-enabled processors. The outcome will include a clean API for sparse matmul operations, optimized implementations using vector intrinsics, and well-documented source code. The goal is to provide an accelerator-independent software solution that enables efficient sparse computation on general-purpose RISC-V vector processors.</span></p>

risc-v c languagerisc-v vector assembly
1 active years2026
Explore
urunc logo

urunc

Cloud Native Computing Foundation (CNCF)

<p>In a standard container setup, the container shares the network namespace with</p><p>its host environment, meaning localhost inside the container refers to the same</p><p>loopback interface as the host's network namespace. Many CNI plugins and</p><p>container networking services rely on this assumption. For instance, Docker</p><p>sets up an internal DNS server listening on localhost within each container's</p><p>network namespace and configures `/etc/resolv.conf` accordingly. Similarly,</p><p>service meshes (e.g., Istio, Linkerd) inject sidecar proxies that listen on</p><p>localhost, and certain CNI plugins expose health checks or metrics endpoints on</p><p>the loopback interface.</p><p><br></p><p>&nbsp;In urunc, however, workloads execute inside a sandboxed environment</p><p>with its own isolated network stack. As a result,</p><p>localhost inside the sandbox does not refer to the host's network namespace</p><p>loopback interface but to the sandbox's own. This breaks any service that</p><p>relies on localhost-based communication between the container and host-level</p><p>components.</p><p><br></p><p>This project aims to investigate and implement mechanisms to bridge localhost</p><p>communication between the host network namespace and the sandbox. The mentee</p><p>will survey the landscape of CNI plugins and networking services that rely on</p><p>localhost, categorize the different communication patterns, and design a</p><p>solution that restores compatibility while preserving the</p><p>isolation guarantees that urunc provides.</p><p><br></p><p>- Expected Outcome:</p><p>&nbsp;- A survey and categorization of CNI plugins and networking services that</p><p>&nbsp;&nbsp;rely on localhost communication, documenting the specific patterns and</p><p>&nbsp;&nbsp;assumptions each makes.</p><p>&nbsp;- A design proposal of one or more mechanisms to bridge localhost traffic</p><p>&nbsp;&nbsp;between the host network namespace and the sandbox.</p><p>&nbsp;- Implementation of the proposed solution in urunc, with DNS resolution as</p><p>&nbsp;&nbsp;the primary use case.</p><p>&nbsp;- Evaluation of the new mechanism.</p><p><br></p>

gocontainer toolscontainer runtimes+22
1 active years2026
Explore
ATOM Syntax Highlighting logo

ATOM Syntax Highlighting

Linux Foundation

Update the syntax highlighters adding support for macro statements, highlighting commas and parentheses, and support for variables. Also, add new snippets to test different aspects of the syntax highlighting grammar.

atom
1 active years
Explore
Accelerating RISC-V vector instructions by using a bionic network design logo

Accelerating RISC-V vector instructions by using a bionic network design

RISC-V

Software acceleration utilizing specifically designed hardware components is a widely used technique for speeding up different kinds of kernels found in the targeted applications. An example of such kernels in High-Performance Computing (HPC) are algorithms involving the computation of sparse data structures. Sparse applications are difficult to accelerate due to their memory-bound nature, which means that the data is not accessed contiguously in memory. That implies many scatter and gather accesses to the comparatively slow memory. Consequently, dedicated hardware components capable of accelerating the scatter/gather instructions, are a key to improve the performance of sparse applications. The goal of this project is to achieve an FPGA-based acceleration of the vrgather RISC-V vector instruction (RISC-V ISA vector extension v1.0) using a bitonic network. The bitonic network is originally a sorting network that implements the merge-sort algorithm (add reference here). A number of inputs of the network can end up in any output after traversing it. When this concept is applied to a Vector Register File, the bitonic network can be used not only to sort a set of vector elements, but also to move data internally from one register to any other register. The scope of this project is limited to the execution and acceleration of the gather vector instruction, in which the variability of the vector length needs to be considered.

rtl (system verilog, verilog or vhdl)rtl simulationcomputer architecture+6
1 active years
Explore
Add F-extension support to "Ripes" RISC-V Micro-Architectural Visual Educational Simulator logo

Add F-extension support to "Ripes" RISC-V Micro-Architectural Visual Educational Simulator

RISC-V

The core goal of this mentorship consists in implementing the much requested feature of adding support for the F-extension to Ripes. This involves two major steps: first, constructing inside Ripes source code a working implementation of the extension for correctly simulating the instructions with VSRTL (a Ripes-specific, Hardware-Description-Language-like C++ Domain Specific Language created ad-hoc for Ripes); second, implement the required additional Ripes GUI interface for correctly visualizing meaningful insights into the inner working of cores implementing the F-extension. The mentee should expect to fully complete all complementary tasks to the development process, as writing and running comprehensive tests and updating the documentation to reflect the latest version of the project.

intermediate to advanced in c++ and experience with hardware description languages are the sine-qua-non, while having familiarity with and interest in computer architecture, digital electronics and design is necessary to understand the implementation objectives. keen interest in open source, risc-v, visual micro architectural simulation, next generation web development with webassembly. good organisational skills. education-oriented mindset or experience at any level is a plus. interest into information design and visualisation of data is also a plus.linuxc+++6
1 active years
Explore
Adding Single Precision Floating Point (F) extension in NucleusRV Core logo

Adding Single Precision Floating Point (F) extension in NucleusRV Core

Linux Foundation

"NucleusRV Core: NucleusRV is the RISC-V based Core that currently supports I, M and C extensions. It is used along with the SoC-Now SoC Generator that accepts parameters and generates an entire SoC comprising of a Core with selective extensions and other configuration, devices which are selected via parameters and a Bus Interconnect that is used as the communication medium between the Core and the Devices, which is also selected by means of parameters. Adding the support of Single Precision Floating Point (F) extension in NucleusRV Core would enable RISC-V to reach even more use-cases on the deeply embedded side. This way the SoC-Now Generator’s scope will also expand so that now the parameter to include the F extension in the Core will become available. Henceforth increasing the value of the Generator and the Core standalone itself. The SoC-Now generator furthermore uses two Frameworks Caravan and Jigsaw, for connecting Buses and Devices respectively in any CHISEL Design/IP. Single Precision Floating Point (F): RISC-V ISA contains an extension for single precision floating point instructions, which means that all arithmetic and logic operations can be executed with floating point (single precision) values."

moderate communication skillsstrong problem solvinghdl+9
1 active years
Explore
Adding cSONiC support in sonic community testbed topology logo

Adding cSONiC support in sonic community testbed topology

Linux Foundation

*OPEN TO US BASED STUDENTS ONLY* - Accepting applications until May 23, 2025 Currently, SONiC community testbed use vendor NOS (cEOS) to create community topology. This puts unnecessary dependency for people to setup community testbed. SONiC has cSONiC image for a long time. The project here is to incorporate cSONIC into SONiC community testbed. This will be much easier for people setup community testbed. Internship Objectives: - Setup cSONiC as neighbor devices in sonic community testbed. - Enable warm reboot LACP lag extension for cSONiC neigbhor. - Enable Macsec for cSONiC neighbor. Expected Outcomes and Deliverables: - Complete the development and setup the community testbed with cSONIC as neighbor. - Submit a pull request and upstream the code changes to the SONiC project. Recommended Qualifications: Education: Current undergraduate student. Skills & Interests: - Eager to contribute to the SONiC open-source community. - Have python/ansible experience. - Academic background in Computer Science, Computer Engineering, or a related field.

pythonansible
1 active years
Explore
Aether Mentorship Program logo

Aether Mentorship Program

Linux Foundation

The purpose of the Aether mentorship program is to engage students to incorporate the results of their research in 5G/NextG networks into the Aether open source software base, making it available for others to experiment with and build on. This includes work on scalable Mobile Cores and Software-Defined Radio Access Networks.

familiarity with cluster technology (kubernetes, helm) and devops tooling (ansible, jenkins).in-depth expertise with some facet of 5g/nextg technology (including innovative applications) potentially leading to publishable research results.private 5g+3
1 active years
Explore
All In logo

All In

Linux Foundation

All In is a community dedicated to advancing diversity, equity, and inclusion within open source. All In for Students is a paid, 12-month program for select college students from underrepresented backgrounds. During the program, students will receive professional development training, open source education, a structured 12-week open source project, and ultimately have the opportunity to join one of our corporate partners for a summer internship experience.

documentationgit
1 active years
Explore
Alpha-Omega logo

Alpha-Omega

Linux Foundation

To accelerate the mission of the Omega in Alpha-Omega project, four entry-level individual contributors (IC) are being requested for a Summer internship type program. Two of these individuals will assist with the software development and research on the Omega toolchain, led by Yesenia. While the remaining two will assist with developing automated remediation of security vulnerabilities, and open source security research, led by Jonathan. The overall goal will be to provide a 12-week program for the four ICs during the Summer semester term for undergraduate and graduate students. The targeted students will be newcomers to the open source community, software development, or security researcher assisting to expand knowledge and talent to underrepresented majorities, DEI groups, and increase the diverse talent pool for future employers.

apiazurecompiler+14
1 active years
Explore
Alternate Numerical Notations for RISC-V logo

Alternate Numerical Notations for RISC-V

RISC-V

We plan to have students download and modify processor core code bases to include a number of different numerical notation options. We will try a number of variations to get either multiple functions or a single optimized numerical notations.

fpgaverilogrtl
1 active years
Explore
Antrea logo

Antrea

Cloud Native Computing Foundation (CNCF)

As a Kubernetes (K8s) network plugin (CNI plugin), Antrea provides networking functions for K8s Pods and includes various troubleshooting tools for cluster administrators and application developers to diagnose networking issues. The PacketCapture feature (https://github.com/antrea-io/antrea/blob/main/docs/packetcapture-guide.md) was introduced recently and allows capturing network traffic for specific endpoints using predefined filters similar to those supported by libpcap/tcpdump. Users can initiate a packet capture through a Kubernetes Custom Resource Definition (CRD) or a CLI command. The Antrea control plane then generates and injects the corresponding BPF program, and the captured packets can be exported as a pcap file. Currently, only a limited set of filters is supported. With this project, we aim to introduce additional filters, particularly Layer 4 protocol filters, such as TCP flags for the TCP transport protocol. These new filters will enable Antrea users to target network traffic more precisely. - Expected Outcome: Extend the API definition for the PacketCapture CRD with additional filter fields, and implement the new API functionality by mapping the new fields to the corresponding BPF instructions. The new fields should also be exposed in the corresponding `antctl` CLI commands. The implementation should come with a sufficient amount of tests (both unit tests and e2e tests), ensuring that the new functionality is working as expected.

golangkubernetestcp/ip+14
3 active years
Explore
Argo logo

Argo

Linux Foundation

Open source Kubernetes native workflows, events, CI and CD

gokubernetescloud native
1 active years
Explore
Armada logo

Armada

Cloud Native Computing Foundation (CNCF)

Virtual Kubelet (https://github.com/virtual-kubelet/virtual-kubelet) is a way to bring a Kubernetes front end and allow for your execution environment to be something other than Kubernetes. We want to add a virtual-kubelet provider for Armada so we can allow for a k8 front end integration with Armada. - Expected outcomes: - A provider for virtual-kubelet that allows integration of Armada with Virtual-Kubelet

gosql
1 active years
Explore
Atomic NucleusRV logo

Atomic NucleusRV

Linux Foundation

Modern computing increasingly relies on parallel processing and multi-core systems. For correct execution of programs on multi-core and heterogeneous systems, synchronization support is crucial to avoid race conditions and other hazards. RISC-V provides the A (Atomic) Extension for synchronization in a multi-hart environment. The objective of the project is to add support for the A Extension in NucleusRV, a five-stage pipelined RV32IMFC core written in CHISEL (Constructing Hardware In Scala Embedded Language). The mentees will need to: 1. Integrate the A instructions into NucleusRV’s datapath. 2. Resolve hazards that might arise after the implementation. 3. Verify NucleusRV via RISC-V’s architectural tests. Support for atomic instructions in NucleusRV will open doors for the utilization of NucleusRV in multi-core and heterogeneous systems.

risc-vscalachisel+1
1 active years
Explore
Basic Azure Pipeline with Alpine and KNE logo

Basic Azure Pipeline with Alpine and KNE

Linux Foundation

*OPEN TO US BASED STUDENTS ONLY* - Accepting applications until May 23, 2025 All SONiC builds use Azure Pipelines. This project will integrate Alpine to run tests in the build pipeline. These new tests will improve test coverage and prevent regressions due to changes that break the dataplane that are not caught in today’s pre-submit pipeline. Expected Outcome: 1: Determine how KNE can be brought up efficiently in an Azure pipeline 2: Setup an Azure pipeline that brings up a VM with KNE and Alpine 3: Run data plane tests on Alpine as part of a pipeline 4: Work with SONiC community to enable Alpine tests as part of pre-submit 5: Document how new tests can be added and how to interpret results Relationship to SONiC and Impact on Community: With this project, Alpine can enhance SONiC Azure pipeline testing, accelerating software delivery via fast test iterations. Additional Information: https://youtu.be/55X1_2utiVg

linuxkubernetes
1 active years
Explore
Bringing the "Sliderules" Cheat Sheets to the Web logo

Bringing the "Sliderules" Cheat Sheets to the Web

Linux Foundation

This mentorship builds on the ""Sliderule"" Encoder and Decoder Cheat Sheets project, which is a highly visual and condensed view of the information contained in the RISC-V specification documents for consultation and education purposes. The sliderules are especially designed to facilitate manual encoding and decoding of assembly, placing instructions coherently in the binary address space. This original project was compiled by hand on a Google Sheets document and later exported to PDF: this method has the advantage of producing aesthetically pleasant results, but it is slow to create and expand, error prone, non interactive and version controllable only in a very limited way. The general goal of this mentorship consists in extending the information contained in the slide rule to RV64GC and obtaining a web page that interactively shows subsets of the sliderules to the user thanks to an information selection interface and is able to export PDFs from it. The main goal is to create a tool that serves as an education oriented consultive tool that documents the RISC-V instruction set in a more user-friendly way. The project shall be deployed from a GitHub repository.

htmlcssjavascript+6
1 active years
Explore
Buildpacks logo

Buildpacks

Cloud Native Computing Foundation (CNCF)

As a buildpack user using `pack`, I would like to be able to inspect the final app image and determine where the source of the code is located as well as what version (keeping in consideration SCM systems) was used.

containersjavascriptcss+4
1 active years
Explore
CCC - Certifier Framework logo

CCC - Certifier Framework

Linux Foundation

Description: This project will add new useful sample applications to the Certifier Framework including a secure messaging app and several key management applications. In addition, we plan to support more platforms, including client platforms like RISC-V, ARM, Raspberry Pi based implementations and potentially a "soft" platform like Android (which is not an "official" Confidential Computing platform but a simulated environment useful for interacting with "real" Confidential Computing platforms). Expected Outcome: The forgoing applications (using the certifier framework), some additional "shims" to support other programming environments like Java and additional support for new platforms.

linuxandroidraspberry pi
1 active years
Explore
CCC - Islet logo

CCC - Islet

Linux Foundation

Enhance Islet’s security by identifying vulnerabilities early using fuzz testing. This project integrates Cargo Fuzz tools with Islet’s CI pipeline, focusing on testing RMM interfaces (RMI and RSI) based on ARM’s RMM specification. Expected Outcome: Deliver a set of robust fuzz tests integrated into Islet’s CI, improving security and compliance with ARM standards.

rustfuzz testingconfidential computing+2
1 active years
Explore
CCC - Veraison logo

CCC - Veraison

Linux Foundation

Align Verifiers with the RATS model by defining evidence formats and attestation results, working toward integration with other projects like Keylime. Participants will work on adopting CMW for Evidence and EAT for Attestation Results. Expected Outcome: Deliver standardized evidence formats and adoption paths for open-source Verifiers, facilitating seamless integration with the RATS architecture.

gorats architectureattestation+5
1 active years
Explore
CDP 2-Way Communications logo

CDP 2-Way Communications

Linux Foundation

ClusterDuck Protocol is a mesh communication firmware that utilizes LoRa radios and makes it easy to set up emergency networks. The current implementation only allows for information to flow in one direction. While this works well, the experience is not great for end users who need to know if help is on the way. Therefore we want to add 2-Way communication so that disaster survivors can chat with emergency response teams.

c++arduinoc+2
1 active years
Explore
CICS and Laptop Option for COBOL Programming Course logo

CICS and Laptop Option for COBOL Programming Course

Linux Foundation

Create a version of the OMP COBOL Course that includes new modules to cover CICS COBOL programming basics. Additionally, to enable a version of the course that can be run on a laptop using the free version of Enterprise Developer for IBM Z.

cobol
1 active years
Explore
CNCF logo

CNCF

Linux Foundation

Currently tremor supports composition through composing pipelines together, through function composition and through allowing references to query operator definitions and constants in externalizable modules that can be loaded via a module path. It would be excellent if the modularity in tremor extended fully to the query language so that distinct subgraphs could be modularized and consumed by multiple queries to optimise for reuse of flow oriented logic in tremor. This would require extending module support in the tremor query language to support sub-graph definitions with parameters that can be declared and used as part of a higher level query. Modules in tremor-query in their current state: <https://docs.tremor.rs/tremor-query/modules/> This project idea involves designing the sub-graph module syntax and semantics and implementing changes to the lexer, grammar, optimizers and runtime. It is most suited to candidates who are interested in programming language evolution and design.

gotestingrust
1 active years
Explore
CNCF Landscape logo

CNCF Landscape

Cloud Native Computing Foundation (CNCF)

In an effort to better the user experience, the CNCF Landscape is actively seeking ways to improve and enhance its features. - The aim is for the mentee to carry out a User Research to validate existing user personas, gain a deeper understanding of user needs, and conduct a thorough heuristic evaluation to gain insights into user experiences. Using the results, the mentee will establish a solid foundation to start an iterative process of ideation, prototyping, and testing possible solutions. The ultimate goal is to initiate a continuous cycle of improvement and further development of features that enhance the user experience of the CNCF Landscape. Recommended skills: Design Thinking, UX research methodology. In this stage of the project, we are seeking candidates with a background and/or training in user research. Supporting materials, such as the following recommended deliverables, that demonstrate your understanding and experience in this area are ideal: 1. Proto-Personas 2. Validated Personas with Supporting Findings 3. Brief Explanation of the Difference between Proto-Personas and Validated Personas 4. List of UX Research Techniques for Kickstarting the Discovery of Landscape Users 5. Figma and Visual Design are a plus.

design thinkingux research methodologyfigma+1
1 active years
Explore
CNCF TAG Network logo

CNCF TAG Network

Cloud Native Computing Foundation (CNCF)

Network topologies and graph databases go hand-in-hand. The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph. Deliverables (among other items): - MeshModel capabilities browser - Import/export of MeshModel models and components as OCI images - augmentation of cuelang-based component generator

cuelanggolangoci
1 active years
Explore
COBOL Modernization logo

COBOL Modernization

Linux Foundation

Using tried and true processes and tools, modernize a legacy COBOL application to take advantage of cloud, APIs and micro services. Document the process and results, enabling others to modernize their legacy COBOL applications.

cobol
1 active years
Explore
COBOL Programming Course updates logo

COBOL Programming Course updates

Linux Foundation

The mentee will work on updating the Getting Started chapter with updates from Zowe, add new and updated content to the Advanced chapter, review issues, and work on incorporating those that will add value to the course offering and be part of the release team, releasing the next version of the course

cobol
1 active years
Explore
CORE-V Wally Technology Readiness Level 5 logo

CORE-V Wally Technology Readiness Level 5

Linux Foundation

CORE-V Wally is an open-source configurable RISC-V processor that belongs to the OpenHW Group suite of cores. It is also the guiding example for a textbook on RISC-V System on Chip Design, being written by the developers. Wally can be configured from a simple RV32E embedded core to an RV64GC application processor with caches, branch prediction, virtual memory, floating-point, and an array of peripherals. Wally presently is at Technical Readiness Level 4, passing the riscv-arch-test compatiblity suite and a set of custom directed tests. It boots Linux on an FPGA and in lock-step simulation checking against the ImperasDV reference model. It has about 90% code coverage, and functional coverage is not yet measured. The goal of this project is to bring Wally to Technology Readiness Level 5. This would be an excellent project for a mentee interested in computer architecture, logic verification, and logic design. This will entail: • Reviewing and improving the Wally SystemVerilog code base • Writing tests in RISC-V assembly language and/or C to bring Wally to 100% code coverage • Writing and improving scripts (e.g. in Python) to automate testing • Bringing up the ImperasISACOV functional coverage verification flow • Bringing up risc-dv or another random test generator • Creating coverage groups for architectural and microarchitectural features and developing random and directed test cases to bring functional coverage to 100%

systemverilogrisc-v assembly languagepython+3
1 active years
Explore
CRI-O logo

CRI-O

Cloud Native Computing Foundation (CNCF)

There are several steps to the CRI-O release process that are manual. Lots of work has been done to update this, but there is still pushing a tag, copying release notes and some other small tasks. This project is about such automation. Expected Outcome: - Fully automated release and patch versions of CRI-O

rustcontainersgo
2 active years
Explore
Cache architecture between GOWIN's RISC-V processor IP cores and GOWIN's embedded PSRAM controller I logo

Cache architecture between GOWIN's RISC-V processor IP cores and GOWIN's embedded PSRAM controller I

RISC-V

PSRAM/HyperRAM is a low pin count DDR-type memory that provides data in sequential address bursts. These memories are fairly large and would be great for applications that require more memory. Block SRAM inside GOWIN's FPGA's are dynamically addressable and are better for use with RISC-V MCUs since they can obtain instructions and data at any address within a clock cycle. However, there is limited amount of BSRAM in most semiconductor devices including FPGAs. A cache between the PSRAM controller bus and the RISC-V processor bus can help fetch instructions/data from PSRAM with sequential addressing and store locally in BSRAM. The processor can then dynamically obtain subsequent instructions and data from the BSRAM within a particular address range. GOWIN already has multiple RISC-V IP cores and PSRAM IP cores in it's IP Core Generator tool. This project would be to develop the cache architecture and RTL that sits in between these two IPs and efficiently trades off the efficiency of using BSRAM for instructions/data versus the storage size/cost benefits of using PSRAM memory.

have a solid understanding of how to create systems and use industry software and tools.foundation of engineering skills and knowledge, including how engineering projects progress from the initial brainstorming and planning phase to final completion.must be able to clearly communicate with their teams and colleagues using industry jargon.+4
1 active years
Explore
Cartography logo

Cartography

Cloud Native Computing Foundation (CNCF)

Want to be a cloud hacker? In the cloud, answering the question "who has access to what" is surprisingly complex: we need to know what identities exist, what permission policies and controls apply to them, what resources (storage, compute, networking) exist, what permissions apply to those, and we need to tie those together. Cartography (https://github.com/cartography-cncf/cartography) is an ambitious open source project that aims to do just that. In this project, our goal is to model and map cloud IAM relationships in GCP and Azure so users can answer “who can access what resources” across multi-cloud environments. We previously did this in AWS as seen in “IAM: Whatever You Say I Am”(https://eng.lyft.com/iam-whatever-you-say-iam-febce59d1e3b), and we would love to complete our coverage of this across the major cloud providers. Expected Outcome: 1. Design and implement support for evaluating permission objects in GCP and Azure to draw paths such as (:GCPUser)- [:CAN_READ]->(:GCPBucket) or (:AzureServicePrincipal)- [:CAN_READ]->(:StorageAccount). 2. Bonus: opportunity to author or co-author a blog post or video demo

pythonaws sdk (boto3)graph databases / neo4j (cypher)+9
1 active years
Explore