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

Hyperledger - aries-vcx next-gen mobile wrapper Mentorship Project

Intermediate
•Varies

Ready to Apply?

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

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

Implement rust wrapper around aries-vcx to enable consuming the library in mobile setting using modern FFI approach using uniffi library. Additionally implement aries mediator client to unlock full mobile support. Learning Objectives - Learn about self sovereign identity and Aries protocols - Learn Rust language - Learn basics of Kotlin language, basics of Android development - Learn Github Actions and CI process in general - Learn about FFI (Foreign Function Interface) by using uniffi library Expected Outcome - uniffi_aries_vcx rust crate which generate mobile bindings for aries-vcx library - implement mediator client with aries message pick-up protocol support - simple android demo application which can be run in simulator - CI job to build Kotlin and iOS bindings, CI job to test the wrapper

TBA
Proposal

Fixes and performance improvements

Intermediate
•Varies175h (Medium)

The eXpress Data Path (XDP) feature in the kernel enabled high performance programmable packet processing using BPF. This is achieved by way of the XDP hook for attaching BPF programs to a very early stage of packet processing in the network drivers. This allows very high packet processing performance, and XDP programs have access to the full packet data and can filter or steer packets using kernel helpers and different return codes. The XDP_REDIRECT return code is the most flexible of the return codes and is used to direct packets to other places in the system, including other network interfaces, other CPUs, or straight to userspace. While the redirect feature is conceptually simple from the BPF user's point of view, the implementation of it in the kernel uses various tricks to improve performance as packets traverse the different parts of the kernel. This project aims to improve various outstanding issues of the XDP redirect facility. The exact tasks taken on will be up to the mentee's particular interests and skill set, and can include implementing missing pieces of functionality, performance analysis and improvements as well as adding kernel selftests. We have a list of issues to tackle which includes things like: - Implementing missing redirect features for Generic XDP - Improving performance through bulking of operations on redirect - Adding selftests for redirect map types - Improving the usability of BPF samples using redirect

TBA
Proposal

Cloud-Edge Speculative Decoding for LLM via KubeEdge-Ianvs (2024 Term 3)

Intermediate
•Varies175h (Medium)

The autoregressive decoding mode of LLM determines that LLM can only be decoded serially, which limits its inference speed. Speculative decoding technique can be used to decode LLM in parallel with the help of draft model, so as to improve the inference speed of LLM without loss of accuracy. However, the speculative decoding technology of LLM does not consider the application in the cloud-edge distributed environment. This project aims to implement cloud-edge collaborative speculative decoding based on KubeEdge-Ianvs, an open source cloud-edge collaborative distributed machine learning platform, so as to further improve the LLM inference speed in cloud-edge environment. Expected Outcome: - Implement an example of cloud-edge collaborative speculative decoding based on KubeEdge-Ianvs platform. - (Optional) Propose a more efficient cloud-edge collaborative speculative decoding algorithm.

TBA
Proposal

Enhancements in Chaoscenter: GitOps Support for Azure Git, Group.. (2024 Term 2)

Intermediate
•Varies175h (Medium)

In this project, we aim to implement GitOps support specifically for Azure Git within Chaoscenter. Additionally, we will enhance the Infrastructure Selection Modal by introducing the capability to group chaos infrastructure based on environments, ensuring better organization and management. Expected Outcome: 1. Seamless integration with Azure Git for GitOps workflows. 2. Introduction of environment-based grouping in the Infrastructure Selection Modal. 3. Improved chaos infrastructure management and user experience in Chaoscenter.

TBA
Proposal

Falco Adapter

Intermediate
•Varies175h (Medium)

This project will develop an adapter to run Falco in any Kubernetes cluster and periodically generate or update a [Policy Report custom resource](https://github.com/kubernetes-sigs/wg-policy-prototypes/blob/master/policy-report/README.md). The candidate will learn about Kubernetes controllers and various security topics.

TBA
Proposal

CI and Release process improvements

Intermediate
•Varies175h (Medium)

Description: Tremor has a lot of headroom when it comes to improving the CI and the build process. Those improvements will make the day-to-day life of contributors better and gives end-users more frequent and up-to-date builds allowing them to be used in a more cloud-native fashion. The goal is to make the general developer and user experience around contributing and releasing better. This project is well suited for someone interested in the DevOps/SRE world but offer stretch goals to reach into other topics.

TBA
Proposal

Implement Jepsen test for TiKV

Intermediate
•Varies175h (Medium)

Build an integration test framework with Jepsen for TiKV, using the TiKV Rust client.

TBA
Proposal

Hyperledger - Demonstrate Interoperability using Hyperledger Bevel and Cactus Mentorship Project

Intermediate
•Varies175h (Medium)

Hyperledger Cactus support ledger Interoperability but use a local deployment for testing; Hyperledger Bevel supports production-worthy deployments. This project aims to support Cactus deployment using Bevel to demonstrate production-like usage of Hyperledger Cactus. The steps will be following: 1. Deploy a Hyperledger Fabric network using Bevel on a Managed Kubernetes cluster 2. Deploy a GoQuorum network using Bevel on a Managed Kubernetes cluster (can be the same cluster for simplicity). 3. Make changes in Hyperledger Bevel code to deploy the Cactus connectors in both the above networks. 4. Run Cactus test cases.

TBA
Proposal

Create a Tokio-like async runtime in WasmEdge

Intermediate
•Varies175h (Medium)

One of the most important features of WasmEdge is its support for non-blocking network sockets. However, the current WasmEdge API for async networking is still cumbersome. Rust developers would prefer to use a Tokio-like async / await API for such tasks. But Tokio is multi-threaded and cannot run correctly in standard single-threaded WebAssembly. Yet, it is possible to provide a single-threaded Tokio runtime. Our goal is to create a WebAssembly compatible Tokio scheduler.

TBA
Proposal

Support Namespace-scoped Queue in Volcano (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Volcano's `Queue` is a cluster-scoped resource, which means only cluster admins can create or update it. This is a barrier for multi-tenant scenarios, where tenants usually only own their own namespaces and want to leverage Volcano's queue capabilities (resource sharing, capability/guarantee/deserved, hierarchy, etc.) for their own workloads without requesting changes from a cluster admin. This project adds a namespace-scoped `NamespaceQueue` to Volcano. A `NamespaceQueue` is derived from a cluster-scoped `Queue` and behaves consistently with it, so tenants can create and use queues within their own namespace and associate `PodGroup`/`Job` with a `NamespaceQueue` exactly as they would with a cluster `Queue`. The existing cluster `Queue` semantics and APIs remain unchanged for users who do not opt in.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>A namespace-scoped `NamespaceQueue` CRD derived from cluster-scoped `Queue`, with consistent semantics for fields such as `capability`, `guarantee`, `deserved`, and hierarchy.</li><li>Tenants can create and manage `NamespaceQueue` within their own namespace without cluster-admin permission.</li><li>`PodGroup`/`Job` can reference a `NamespaceQueue` and be scheduled with the same behavior as referencing a cluster `Queue`.</li><li>Resource accounting, status, and events for `NamespaceQueue` work end-to-end through Volcano's existing queue management path.</li><li>Compatibility with the existing cluster `Queue` and the `scheduling.volcano.sh/queue-name` annotation, with a clear migration story for existing users.</li><li>E2E tests covering core `NamespaceQueue` flows, including negative cases.</li><li>User-facing documentation on the Volcano website and the repository.</li></ul><p><br></p>

TBA
Proposal

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

Intermediate
•Varies175h (Medium)

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.

TBA
Proposal

Enhanced Block Viewer UI

Intermediate
•Varies175h (Medium)

The Thanos BlockViewer UI has proven to be an essential part of the debuggability story for the Thanos project. It allows administrators to see the exact state of data in Object Storage in a provider-agnostic way. This project is about extending this UI with richer features, context, and actions to improve observability and increase control.

TBA
Proposal

Create a ffmpeg plugin

Intermediate
•Varies175h (Medium)

The mediapipe-rs project provides a Rust SDK to support mediapipe AI models. The SDK provides utility functions to pre-process application data (such as images, audio and video) into TFLite / PyTorch formats, and convert the inference results back into application data. In order to accomplish this, the [mediapipe-rs](https://github.com/WasmEdge/mediapipe-rs) project has made extensive use of the [ffmpeg](https://www.ffmpeg.org/) library. It [compiles ffmpeg to Wasm](https://github.com/WasmEdge/mediapipe-rs/blob/main/src/build.rs) and then builds it together with the application binary. However, the issue with this approach is that those Wasm-compiled ffmpeg functions are slow. We believe a better approach is to create a ffmpeg plugin for WasmEdge, and allow Wasm applications to call native ffmpeg functions as host functions. - Expected Outcome: - The deliverables will be - A WasmEdge plugin for ffmpeg that is similar to the [WasmEdge OpenCV-mini plugin](https://github.com/WasmEdge/WasmEdge/tree/master/plugins/wasmedge_opencvmini). That is to re-export ffmpeg functions in C style as plugin functions as covered in the [plugin developer guide](https://wasmedge.org/docs/category/wasmedge-plugin-system). - A Rust SDK for Wasm programs to access ffmpeg functions in the plugin. Similar to the [WasmEdge OpenCV-mini SDK](https://github.com/second-state/opencvmini) - Refactor the mediapipe-rs project to use the ffmpeg plugin

TBA
Proposal

Hardware Abstraction Layer Transitional Library for Software to Hardware Posits For RISC-V Mentorship Project

Intermediate
•Varies175h (Medium)

This project aims to ease the transition and implementation of Posits, an alternative numerical representation, for RISC-V systems. By creating a robust hardware abstraction layer (HAL), developers need not know if the target RISC-V platform has a hardware Posits implementation or requires a software implementation. This new POSIX-compliant C++ library (with ports planned eventually) will help make available the option to transition between IEEE Float / Doubles to Posits and should make the machine-specific selection and configuration seamless. The lack of such a HAL is a roadblock in Posit adoption and Posits represent a serious opportunity for free and open source silicon (FOSSi) systems. Initial focus will be directed toward HPC support, where numerical computation efficiency may be best observed. Additionally, we will be conducting benchmarking studies to evaluate the performance of the HAL, identifying bottlenecks, and iterating on the design based on empirical data. The testing framework will also be part of the mentee's deliverables.

TBA
Proposal

Develop content for Notary documentation and blogs

Intermediate
•Varies175h (Medium)

Develop content for Notary documentation and write blog posts to educate users about the Notary use cases. Write user guides, contributing guides, and developer guides for every new Notary release and keep those content up-to-date. - Expected Outcome: - Write user guides with end-to-end scenarios based on given doc structure and requirement - Write contributing guides and developer guides, ensure new developers can easily build and start contributing to Notary subprojects - Write blog posts to educate users to use Notation with cloud-native ecosystem tools

TBA
Proposal

Integrating Kmesh into Headlamp UI (2026 Term 2)

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Improve the WasmEdge-based Rust coding assistant for inference-time scaling (2025 T

Intermediate
•Varies175h (Medium)

In a previous LFX mentorship project (https://github.com/WasmEdge/WasmEdge/issues/3495), we have created an LLM-based coding assistant grounded in Rust programming language skills (https://huggingface.co/datasets/gaianet/learn-rust). We aim to further improve the Rust coding assistant by incorporating inference-time compute that utilizes the Rust compiler for feedback. One of the greatest advantages of Rust is its powerful and strict compiler, and the detailed error message generated by the compiler. The Rust compiler could give valuable feedbacks to code generating LLMs to improve the code quality. Expected Outcome: 1. Run a Qwen Coder 2.5 LLM locally (https://github.com/GaiaNet-AI/node-configs/tree/main/qwen-2.5-coder-7b-instruct) or access it via an API. 2. Create an LLM system prompt that describes the structure and key elements of a cargo project. It will guide the LLM to generate multiple files (artifacts) for a complete project. 3. Create a Python program to send user requests to the LLM and parse the generated result into locally cached files. 4. Use a local Rust compiler to build the generated project. Sends the error messages back to the LLM to re-generate. 5. Iterate until there is no more errors. 6. Build a web API for the Python program that takes OpenAI compatible requests and return OpenAI compatible results.

TBA
Proposal

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

Intermediate
•Varies175h (Medium)

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

TBA
Proposal

Implement Dynamic IPAM for the Slice Overlay Network (2025 Term 3)

Intermediate
•Varies175h (Medium)

In the current KubeSlice design, IP address management (IPAM) for slice overlay networks is static and inefficient. A predefined CIDR block (e.g., 10.1.0.0/16) is divided into a fixed number of subnets regardless of how many clusters participate in the slice, leading to significant IP space wastage. This project aims to implement a dynamic IPAM system that allocates IP subnets to clusters on demand and reclaims unused ranges when clusters leave the slice. It will ensure efficient address utilization, synchronization across clusters, and integration with the KubeSlice control plane. Expected Outcome: 1. A dynamic IPAM allocator integrated with the KubeSlice controller or sidecar component. 2. Support for on-demand IP allocation and subnet reclamation when clusters join or leave a slice. 3. Conflict resolution and state synchronization across clusters using CRDs or distributed storage. 4. Documentation on how the system works, configuration options, and edge case behaviour.

TBA
Proposal

Kthena Router Benchmark (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Kthena Router is the LLM routing component in the Volcano/Kthena project, responsible for forwarding inference requests to in-cluster and (soon) third-party model backends. As Kthena gradually matures, the community needs a reproducible benchmark to understand the router's performance characteristics (throughput, latency, tail latency, resource usage) under realistic LLM traffic patterns, and to detect regressions across releases. This project asks the mentee to design and implement a benchmark framework for Kthena Router, produce a complete report. Where the benchmark surfaces clear bottlenecks or inefficiencies, the mentee will also work with maintainers to land code-level optimizations upstream.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A reusable benchmark framework for Kthena Router (load generator, scenario configs, metrics collection, result aggregation), runnable locally and in CI.</p><p>&nbsp;- A defined set of test scenarios covering typical LLM routing patterns (varying QPS, prompt/response sizes, concurrency, number of backends, routing strategies).</p><p>&nbsp;- End-to-end test procedure documented as a runbook (cluster setup, mock/real backends, how to run, how to interpret results).</p><p>&nbsp;- A benchmark report with metrics (throughput, TPOT, TTFT, GPU/CPU/memory) and analysis of bottlenecks.</p><p>&nbsp;- Upstream PR(s) implementing optimizations for any clear hotspots identified, with before/after numbers.</p><p><br></p>

TBA
Proposal

Hyperledger - Cactus and Hedera Hashgraph integration Mentorship Project

Intermediate
•Varies175h (Medium)

Hyperledger Cactus is a blockchain decentralised integration tool designed to allow users to securely integrate different blockchains started by companies Fujitsu and Accenture. Cactus has pluggable architecture which makes easy to integrate various blockchain by creating plugin, currently plugins for Fabric, Besu, Quorum are implemented. Cactus allows to transfer not only assets but also data between multiple blockchains. Hedera Hashgraph is a DLT built on top of an asynchronous BFT algorithm, providing smart contract, token, and consensus services to end users. The flexibility - Document ready-to-use integration of Hedera and Cactu, - Document example of integration using Hedera's Testnet and Hedera's Previewnet - Document example of integration between another blockchain and Hedera using Cactus

TBA
Proposal

Community building and social media growth (2026 Term 1)

Intermediate
•Varies175h (Medium)

The release of PipeCD v1 introduced a plugin-based architecture that enables deployments on any platform. This is a significant evolution in the project's capabilities, but community awareness and adoption haven't kept pace with the technical progress. This project focuses on growing PipeCD's community through consistent content creation across developer platforms, producing technical content around the v1 release, improving documentation for users and contributors, and engaging with the community through demos and discussions. The mentee will work closely with maintainers to translate PipeCD's technical strengths into accessible content that drives adoption and contributions. - Expected Outcome: Established social media presence for PipeCD across key developer platforms, along with technical content covering v1 features, plugin development, and real-world deployment patterns. Demo content including video walkthroughs and livestreams that make the project easier to adopt. Improved contributor documentation and onboarding materials, with active community engagement through GitHub Discussions and other channels. At least one CNCF talk or meetup presentation delivered.

TBA
Proposal

Upgrade Storage Backends to V2 Storage API (2025 Term 1)

Intermediate
•Varies175h (Medium)

Jaeger is an open-source, distributed tracing platform designed to monitor and troubleshoot microservices-based systems. A critical component of Jaeger is its storage backends, where traces captured by Jaeger are stored. With the release of Jaeger v2 last year we introduced a new, more efficient Storage API v2. However, the existing backend implementations in Jaeger are still using v1 API that is only wrapped in the v2 adapter, which prevents them from benefiting from the new capabilities such as batch writes and result streaming. The objective of this project is to upgrade some (or all) backend implementations to use the Storage API v2 natively. Please refer to the upstream issue for more details. Expected Outcome: 1) Upgrade memory and Elasticsearch backends to use the Storage API v2 natively. 2) Bonus: upgrade Cassandra and Badger backends to use the Storage API v2 natively.

TBA
Proposal

Move2Kube: Compile Move2Kube to WASM/WASI and run it in the browser

Intermediate
•Varies175h (Medium)

Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. It has inbuilt support for creating IaC artifacts for replatforming to Kubernetes/OpenShift. We want to compile targetting WASM/WASI and run the resulting WASM module in the browser. This will help up showcase Move2Kube for demos and allow users to quickly try out Move2Kube without having to install it or any of its dependencies. - Expected Outcome: - Run Move2Kube CLI in the browser using WebAssembly.

TBA
Proposal
Showing 433 - 456 of 1243 Projects
1718192021