Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

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

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

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

Made with love bySubhranshu Sekhar Dash

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

PlatformProjects

Explore Projects

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

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

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

Match with Orbit AI
Filters Clear
1243 Projects Found
Sort by

Create high fidelity audio and animations to Educational Game (2025 Term 1)

Intermediate
•Varies

Ready to Apply?

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

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

The Knative community is developing an educational game to teach concepts about event driven architectures and how to build them with Knative. A good overview of the project was presented at KubeCon NA 2024 (https://youtu.be/TTBKh6F4v-g?si=MRmx6a2YJsl7y0Q-). We are currently looking to tale our initial prototype and turn it into a full game. In this project, you will help achieve this by creating both visual and audio assets, giving the game a polished look. - Expected Outcome: Identify which assets should be created, create audio assets, create visual assets, add assets Godot.

TBA
Proposal

Linux Kernel trace events in pstore Mentorship Project

Intermediate
•Varies175h (Medium)

Pstore is a subsystem in the Linux kernel that is used to store kernel logs which can retrieved after a machine warm-reboots. Currently, during ftrace tracing, ftrace events in the kernel are lost when a machine hard-locks up. There is a need for writing these events into the pstore so that after a lock up, the trace events that led to the crash can be retrieved from the Pstore after a warm reboot. This has to be done in a scalable way so that tracing a live system does not impact performance of the system – ftrace is extremely fast. Initial patches posted to write and retrieve events to/from pstore are not scalable due to locking and other issues. Introducing a scalable approach will open up more possibilities for crash analysis. Prototype work for reference: https://linaroconnectsandiego.sched.com/event/Sue7/event-tracing-and-pstore-with-a-pinch-of-dynamic-debug

TBA
Proposal

Support AOT mode in proxy-wasm

Intermediate
•Varies175h (Medium)

WasmEdge is a WebAssembly runtime that supports both interpreter and ahead-of-time modes. For proxy-wasm support, WasmEdge only provides the interpreter mode currently. Such as the other runtimes, WasmEdge should be able to support the AOT mode for better performance. In this mentorship, the mentees will help the WasmEdge project to complete the AOT mode in proxy-wasm proposal and write the docs for examples of running with proxy-wasm. - Expected Outcome: - Modify the Bazel file to include the LLVM dependency. - Modify the code to support running WASM in AOT mode. - Add the documentation of proxy-wasm in the WasmEdge docs repo.

TBA
Proposal

Enforcing XFS quotas on OpenEBS hostpath Local PV

Intermediate
•Varies175h (Medium)

OpenEBS Local PV hostpath is the most simple to use Local PV option available for Kubernetes today. Many of the applications use XFS filesystem to create Local PVs. This project is to implement XFS project quota on the OpenEBS Local PV subdirectory to restrict pods from exceeding the Quota assigned to them via the PVC request.

TBA
Proposal

OSPO Playbook Mentorship Project

Intermediate
•Varies175h (Medium)

A summarization of various resources and building a documentation playbook detailing the specifics and resources needed for running Open Programs offices within a University.

TBA
Proposal

Allow a WDS to work with more than one ITS (2025 Term 3)

Intermediate
•Varies175h (Medium)

Currently a Workload Description Space (WDS) has Binding objects that refer to inventory objects in exactly one Inventory and Transport Space (ITS). This mentorship project would generalize that, allowing references to inventory objects in multiple ITSes. Bear in mind scalability concerns. Expected Outcome: generalized API and implementation as described.

TBA
Proposal

Hyperledger Collaborative Learning - An Optimized BFT on Fabric - Unpaid Mentorship Project

Intermediate
•Varies175h (Medium)

The current existing implementation of Hyperledger Fabric with Raft consensus has many shortcomings such as transaction censorship and no mechanism to safeguard the network if a malicious leader gets elected. The network also has limitations on scalability which restrict the type of use cases that can be built such as real-time applications that use IoT devices. This impedes blockchain adoption and limits the type of applications and use cases that can be built on Fabric. The goal of this project is to build BiniBFT, a Byzantine Fault Tolerance consensus library for Hyperledger Fabric which provides end-to-end security, high throughput with low latency and high scalability so that Fabric can be applicable for distributed and decentralized day-to-day applications. Learning Objectives - Building and Integrating a BFT library with Hyperledger Fabric. - Understanding how BFT consensus protocols work and optimizing algorithms for better performance. - Developing an understanding of how DLT networks like Hyperledger Fabric work. - Exploring the different ways in which BFT protocols can improve the performance and security of Fabric networks.

TBA
Proposal

Hyperledger Collaborative Learning - Fabric Token SDK Lab Support for Hyperledger Caliper B - Unpaid Mentorship Project

Intermediate
•Varies175h (Medium)

The Fabric Token SDK allows developers to create token-based distributed applications on Hyperledger Fabric. While the Fabric Token SDK offers many features (i.e., configurable privacy, p2p transaction orchestration, atomic swaps, and audits,...), performance is yet another important aspect. The Hyperledger Caliper project is a blockchain performance benchmark framework, which allows the evaluation of blockchain solutions. How about using Caliper to benchmark token-based applications built on top of the Fabric Token SDK? The goal of this project is the design and the implementation of a Caliper plugin to evaluate applications using the Fabric Token SDK. This includes the creation of appropriate documentation and performance evaluation of sample applications. The project requires a solid understanding of theory and practice of software development using Golang and Node.JS, distributed systems, and performance benchmarking. During the project you will get hands-on experience with the deployment of Fabric networks, the transaction lifecycle, the Fabric Token SDK, and Hyperledger Caliper.

TBA
Proposal

Add status infos in Kubernetes CRDs

Intermediate
•Varies175h (Medium)

Description: Kuma is a modern Envoy-based service mesh that can run on every cloud, in a single or multi-zone capacity, across both Kubernetes and VMs. It is currently a CNCF Sandbox project. While Kuma currently exposes information about status in its api Kubernetes users usualy expect these to be also present in the Status fields of their resources. This project aims in adding status to all Kuma CRD and to improve our controllers to set these as cluster state changes.

TBA
Proposal

CORE-V Wally Technology Readiness Level 5 Mentorship Project

Intermediate
•Varies175h (Medium)

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%

TBA
Proposal

Mirror Serial Console Traffic in SONiC Mentorship Project

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Ensuring Behavioral Equivalence in SONiC’s RIB/FIB Architecture

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Build a virtual-kubelet provider for Armada

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Add BTF and BPF CO-RE Support to KubeArmor

Intermediate
•Varies175h (Medium)

Currently KubeArmor depends on kernel headers to use various kernel structures. This creates difficulty in having portability. Linux Kernel versions with BTF (BPF Type Format) information available allows us to write portable BPF CO-RE (or Compile Once - Run Everywhere) applications that can run on multiple kernel versions and configurations without any modification or runtime compilation on the target machine. But there is a restriction that CO-RE requires to have the BTF information of the target kernel, which is provided by the kernel itself when it's compiled with CONFIG_DEBUG_INFO_BTF=y. This option was introduced in Linux 5.2. For kernels < 5.2 we can use BTFGen to ship BTF information with KubeArmor code or use pahole to generate BTF information from the vmlinux image (with DWARF information) at runtime. The project aims to make KubeArmor truly portable across all kernel versions by reducing host environment dependencies.

TBA
Proposal

SONiC Test Runtime Optimization Mentorship Project

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

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

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

ZOROW - BYO z/OSMF Workflow Mentorship Project

Intermediate
•Varies175h (Medium)

Develop z/OSMF workflow for some common tasks such as copying one dataset to other. Learn various capabilities provided by z/OSMF workflow. Contribute the z/OSMF workflows to the ZOROW community.

TBA
Proposal

Switch Cortex Ruler to query Query Frontend

Intermediate
•Varies175h (Medium)

Description: Cortex Ruler queries ingester directly for rule evaluation. This is okay but if Cortex Ruler could query Query Frontend instead for rule evaluation, it can benefit from more features in the Query Frontend like vertical sharding. This also simplifies the Cortex ruler to not embed a querier and uses less resources. For this project, we would like to switch Cortex Ruler to query Query Frontend. You are expected to work with a microservice architecture and write unit tests and end to end tests to make sure the feature works correctly. Expected Outcome: Cortex Ruler talks to Query Frontend for rules evaluation.

TBA
Proposal

SONiC OS Profiling Mentorship Project

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

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

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Hyperledger Collaborative Learning - Privacy-preserving data sharing for SLAs on Fabric - Unpaid Mentorship Project

Intermediate
•Varies175h (Medium)

Current project targets privacy preservation developing modular tools for data sharing while envisioning the deployment of the necessary future blockchain and smart contract processes in Service Level Agreements (SLAs) evaluation. Service Level Agreements (SLAs) define the way that service and infrastructure providers are making available products to their clientele, for example, the dedicated agreements for Public Cloud Infrastructure As A Service. An SLA is an accurately defined contract involving the specified service level objectives (SLOs) and contractual guarantees that are promised to be delivered to clients by the providers of the service or infrastructure. Particularly, monitoring of SLAs determines whether a provider meets an SLA's contractual terms or otherwise breaches of the agreement unfold. SLA breaches lead to definite violations of the terms, namely SLA Violations, as described in the contract. Ultimately, contractual definitions and parameter values computations vary across different provider setups, e.g. Telecom, 5G, Edge, and Cloud. The main objective of the project is to develop privacy preservation through trusted execution environments, zero-knowledge proofs, or ring signatures for the corresponding transactional operations of SLAs assessment under a modular data sharing scheme on Hyperledger Fabric. The applicable deployment and engagement with such architectural elements of privacy leads the current project to preserve and secure data protection.

TBA
Proposal

Improve developer experience and documentation (Unpaid)

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Pick out reasonable victim pods for rescheduling plugin

Intermediate
•Varies175h (Medium)

Currently, rescheduling is a little rough to evict victim pods without difference. It should distinguish pods with more consideration such as pod priority, namespace and so on. Your task is to take a full consideration about all the scenarios, provide a design documentation, implement your idea and give a full test.

TBA
Proposal

Rework the frontend UI of Vitess’ benchmarking tools

Intermediate
•Varies175h (Medium)

Vitess uses a couple of tools to benchmark its codebase and to make sure that new code doesn’t introduce performance regressions. These tools are: arewefastyet and the VReplication Benchmarking Framework. We currently have an old frontend UI that serves arewefastyet. However, this UI is slow, not optimized and not easily extensible. It uses the built-in Golang template system to serve pages. We would like to create a common frontend UI that will be used by both benchmarking tools and that will replace the current arewefastyet’s UI. The mentee will have the responsibility of creating the UI using (most likely) React/Vite on Vercel. The frontend component will connect to our already-existing backend components: a MySQL database and arewefastyet’s REST API. - Expected Outcome: The expected outcome is to have a working frontend UI that integrates well with our different backends (databases and benchmarking tools’ APIs).

TBA
Proposal
Showing 1153 - 1176 of 1243 Projects
4748495051