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
13453 Projects Found
Sort by

Finetune LLM models for Rust coding assistance (2024 Term 2)

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)

WasmEdge is a lightweight inference runtime for AI and LLM applications. We want to build specialized and finetuned models for WasmEdge community. The model should be supported by WasmEdge and its applications should benefit the WasmEdge community. In this project, we will build and compare two finetuned model for Rust coding assistance. A code review model. It aims to be a new backend for the PR review bot (https://github.com/flows-network/github-pr-summary/) we currently use in the community. A QA model. It should be able to answer user questions about the Rust language and provide explanations. Our goal is to provide an alternative to our Learn Rust app (https://flows.network/learn-rust). Expected Outcome: Two finetuned models based on Llama3-8b for Rust code review and QA.

TBA
Proposal

Design and implement the KubeEdge Dashboard

Intermediate
•Varies175h (Medium)

Description: Users now can use K8s API or Kubectl to talk to KubeEdge, in this project we will design and implement the KubeEdge dashboard, so users can talk to KubeEdge cluster through UI. Expected Outcome: Create the KubeEdge dashboard, users can view and operate the resource through UI.

TBA
Proposal

Hyperledger - Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel Mentorship Project

Intermediate
•Varies175h (Medium)

yperledger Bevel supports production-worthy deployments for Hyperledger Fabric. And all production systems need to undergo updates which can often be live-updates. This project aims to complete a live upgrade of a Hyperledger Fabric network from version 1.4.x to 2.2.x using Hyperledger bevel and document the steps as well as make any changes needed to automate any steps possible.

TBA
Proposal

Hyperledger - Document, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic Primitives Mentorship Project

Intermediate
•Varies175h (Medium)

Hyperledger AnonCreds includes specifications and implementations of AnonCreds (Anonymous Credentials) Zero-Knowledge Proof (ZKP)-based verifiable credentials. AnonCreds extends the capabilities of “typical” verifiable credentials by including important privacy-preserving features including selective disclosure, ZKP predicates (e.g., proving I’m older than 21 based on my date of birth without sharing my date of birth), and not revealing any correlatable identifiers in presenting credentials. The version 1.0 specification (based on CL-Signatures as initially implemented in Hyperledger Indy) is near completion, and work has begun on the version 2.0 specification that will retain and extend the privacy-preserving features of AnonCreds v1.0, while improving capabilities, performance, extensibility, and security. An implementation based on the Version 2.0 specification will occur in parallel with the development of the specification. - For the Version 1.0 specification, the primary task will be to extract the cryptographic primitives from identified sources, confirm alignment with the Rust implementation of AnonCreds, and include the cryptographic primitives in the specification. This is the last step of the specification to make it ready for submission to a standards development organization (SDO). - The Version 2.0 specification, the task will be similar, but the work will extend he focus as appropriate to implementation of the cryptographic primitives.

TBA
Proposal

Expanding Go Compile-Time Instrumentation and otelc Tooling (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>The [OpenTelemetry Go Compile Instrumentation](https://github.com/open-telemetry/opentelemetry-go-compile-instrumentation) project provides `otelc`, a compile-time auto-instrumentation tool for Go applications. It injects OpenTelemetry instrumentation during the Go build process without requiring manual source-code changes in the target application. As the project moves toward its v1.0 release and continues feature-parity work with mature compile-time instrumentation efforts such as [Orchestrion](https://github.com/DataDog/orchestrion) and [Loongsuite](https://github.com/alibaba/loongsuite-go-agent), the next phase is to broaden real-world library coverage while hardening the tooling and contributor workflow needed to maintain those integrations over time. This mentorship focuses on adding several mentor-approved integrations from the project roadmap and backlog, such as messaging, database/cache, logging, Kubernetes client, or GenAI SDK libraries, while improving `otelc` whenever the integration work exposes gaps in rule authoring, hook implementation, testing, or debugging. The mentee will also document the science behind compile-time instrumentation: how Go symbols and versions are matched, how hooks are injected, how OpenTelemetry semantic conventions are applied, and how compatibility is verified across library releases.</p><p><br></p><p>Expected Outcome:</p><p> - Add `otelc` instrumentation support for 3-4 widely used Go libraries selected with mentors from the project roadmap/backlog, depending on complexity and project priorities.</p><p>&nbsp;- For each new integration, implement instrumentation rules and hook code, define supported version ranges, and follow the relevant OpenTelemetry semantic conventions.</p><p>&nbsp;- Add meaningful unit, integration, and/or end-to-end tests that verify the instrumented application builds and emits the expected telemetry.</p><p>&nbsp;- Improve the instrumentation tooling or contributor workflow as needed during the work, for example rule validation, hook scaffolding, latest-library compatibility checks, integration layout, or debugging output.</p><p>&nbsp;- Write documentation, examples, and demos that explain how to use the new integrations and how future contributors can build similar ones.</p><p><br></p>

TBA
Proposal

Add Argo CD to Headlamp - GitOps Application Management UI (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>[Argo CD](https://github.com/argoproj/argo-cd) is a Kubernetes-native GitOps continuous delivery tool for managing application deployments from Git. This project builds a Headlamp plugin that integrates Argo CD concepts directly into Kubernetes workflows by extending the **Projects view**. The plugin surfaces high-level GitOps signals (applications, sync status, health, revisions) so SREs, operators, and developers can understand deployment state.</p><p><br></p><p><br></p><p>Expected Outcome:</p><p><br></p><p>&nbsp;- Extend **Projects view** to include Argo CD context per project.</p><p>&nbsp;- Show associated Argo CD Applications with:</p><p>&nbsp;- Sync Status (Synced / OutOfSync)</p><p>&nbsp;- Health Status (Healthy / Degraded)</p><p>&nbsp;- Current Revision (Git commit / branch)</p><p>&nbsp;- Surface minimal GitOps context:</p><p>&nbsp;- Source repository + revision</p><p>&nbsp;- Target namespace / cluster</p><p>&nbsp;- Deployment status summary</p><p>&nbsp;- Lightweight UX enhancements:</p><p>&nbsp;- GitOps status indicators (icons / badges)</p><p>&nbsp;- Inline listing of related Applications</p><p>&nbsp;- Links to Application detail pages and Kubernetes resources</p><p>&nbsp;- Follow **Headlamp UX patterns**:</p><p>&nbsp;- Tables, icons, detail layouts</p><p>&nbsp;- Cross-resource navigation (Project → Application → Workloads)</p><p>&nbsp;- README with prerequisites and limitations; blog post demoing usage.</p>

TBA
Proposal

KCL Package Version Management (2024 Term 1)

Intermediate
•Varies175h (Medium)

The KCL package management tool primarily handles the management of third-party KCL packages for the KCL project, which includes tasks such as uploading and downloading these packages. When adding third-party packages to the KCL project, it is important to adhere to version management strategies. This involves carefully selecting and downloading the appropriate version of a package, especially when different versions of the same package are available. Expected Outcome: Add version management to the KCL package management tool.

TBA
Proposal

Progressive Delivery for Native DaemonSet (2025 Term 3)

Intermediate
•Varies175h (Medium)

OpenKruise Rollout already support the progressive delivery of OpenKruise advance DaemonSet, however switching workload is not an option for many users. The goal is to utilize the OnDelete updateStrategy of native kubernetes workload, and trigger the pod upgrade by deleting desired number of pods per Rollout specification. Expected Outcome: 1. Implentation of progressive delivery for native kubernetes daemonset, and only basic multi-batch release is required. 2. Unit and integration test 3. Documentation for the function usage and typical use cases in the OpenKruise website

TBA
Proposal

LF Networking - 2023 OpenDaylight Website Refresh Mentorship Project

Intermediate
•Varies175h (Medium)

This internship will provide the opportunity to learn open source community standards, values, and processes by joining and contributing to the OpenDaylight community. The intern will interact with community members across many corporations large and small. Application of modern UX analysis, design, and website implementation technologies will provide ample opportunity to grow the applicant's skill set. The applicant will also learn some basic marketing principles in working with the LFN marketing team on this project.

TBA
Proposal

UX Research: How users expect to use OTLP Resource Attributes in Prometheus (2025

Intermediate
•Varies175h (Medium)

In the last year Prometheus has tackled and solved many UX problems that OTel users had when sending OTLP data to Prometheus. One challenge that remains unsolved is how do users expect to use OTLP Resource Attributes in Prometheus. This project is about conducting a UX research that explores the main problems users are facing today with the current state of Resource Attributes and Prometheus and coming up with ideas how to solve them. Expected Outcome: 1. Preliminary artifacts (e.g., research plan) shared as project progresses. 2. Research report, summarizing the findings. 3. A spoken presentation including research method and results. a. Stretch goal: apply to present the project at KubeCon.

TBA
Proposal

Design Configurator

Intermediate
•Varies175h (Medium)

Integrate a new user experience into Meshery: a cloud native design configurator. This project involves presentation of Kuberenetes core resources and any custom resource (CRD) as a configurable component in a React-based user interface in which users design (in great detail) and deploy their cloud native infrastructure. Interns will familiarize with concepts of content lifecycle management.

TBA
Proposal

Update the Microcks Hub frontend and make it deployable on-premises (2025 Term 1)

Intermediate
•Varies175h (Medium)

Microcks (https://microcks.io/) is a cloud native, open source tool under CNCF for API and microservices mocking and testing. Microcks Hub (https://hub.microcks.io) is a community-driven hub that aggregates standards or product-related API mocks and test suites. Microcks hub was created a long time ago with a technology stack we should refresh (Angular 8 at the moment). Expected Outcome: - refresh UI aligned with ongoing work and decisions taken for the main Microcks UI, see: https://github.com/orgs/microcks/discussions/1458 - It was initially designed to be deployable only in a single public instance, but there are requests to make it deployable on-premises. - We're looking for contributions on this part, such as helping develop Docker Compose files, Kubernetes Helm Charts, or whatever makes sense. - The code base is hosted on https://github.com/microcks/hub.microcks.io

TBA
Proposal

OCI references support

Intermediate
•Varies175h (Medium)

Description: Use OCI References in image verification Expected Outcome: PR sent to kyverno/kyverno implementing support for OCI references in verifyImages rules

TBA
Proposal

Implementing Upgrade Agent Support in Litmus 3.x (2024 Term 2)

Intermediate
•Varies175h (Medium)

Integrating an upgrade agent into Litmus 3.x streamlines Chaoscenter upgrades, eliminating the need for fresh installations. This feature ensures seamless transitions between versions, especially useful when facing significant changes. Expected Outcome: 1. Seamless Upgrades: Integration of the Upgrade Agent ensures smooth transitions during Chaoscenter upgrades, removing the necessity for fresh installations. 2. Simplified Process: Users can upgrade from one version to another without the hassle of reinstallation, saving time and effort.

TBA
Proposal

End-to-end example of a multiplayer game using NATS in Unity

Intermediate
•Varies175h (Medium)

Description: This project consists of developing an example Unity setup of a multiplayer game using the latest version of the NATS Server. Expected Outcome: A well documented repository under the `nats-io` GitHub organization that contains the artifacts and sample code of the setup using the .NET NATS Client (https://github.com/nats-io/nats.net)

TBA
Proposal

Kubernetes working group for CSI driver

Intermediate
•Varies175h (Medium)

Container Storage Interface (CSI) is a standard for exposing storage systems to containerized workloads on Kubernetes. The idea is to enhance a few CSI features(e.g. NFS, SMB) and also add e2e, sanity tests to cover those features, e.g. inline volume support, Windows support etc.

TBA
Proposal

Official Website Docs Enhancement

Intermediate
•Varies175h (Medium)

Official website docs has not been updated for a long time including technology docs, talks, best practice and so on, which bothers users and developers a lot.

TBA
Proposal

Add support for hedged requests (2024 Term 3)

Intermediate
•Varies175h (Medium)

The long-tail requests sometimes are inevitable between the Thanos Store Gateway and an external cache. Lowering the timeouts between the store-gateway and the cache service isn't a greater way to address this problem. Using a HTTP client to issue hedged requests to object storage and other parts of Thanos' stack could help reduce tail latency by a lot. Expected Outcome: By the end of the term, the mentee will have a deeper knowledge of Thanos and have improved our HTTP request tail latencies considerably!

TBA
Proposal

Implement a Binding Policy Backend to Support UI Frontend (2025 Term 1)

Intermediate
•Varies175h (Medium)

This project focuses on implementing the backend API for managing Binding Policies. The API should support creating, reading, updating, and deleting policies while ensuring robust validation and performance. Objectives - Develop backend API endpoints for Binding Policy management. - Ensure proper validation and enforcement of Kubernetes standards. - Optimize backend performance for handling multiple policy requests. - Implement logging and error handling for better debugging. Expected Outcomes - A secure and scalable backend API for Binding Policies. - Full CRUD functionality accessible from the UI. - Improved validation and performance optimizations.

TBA
Proposal

Fix bugs found by fuzzer (2024 Term 3)

Intermediate
•Varies175h (Medium)

WasmEdge received several bug reports, which Fuzzer found. We would like to ask mentees to investigate and determine whether the issue is real, figure out solutions, or mark it as a `won't-fix` issue if it's invalid. To apply for this mentorship, you should also submit a proposal as part of the application materials. Please check the upstream issue for the detailed target list and the proposal template. Expected Outcome: At least fix/determine 60% of the mentioned issues.

TBA
Proposal

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

Intermediate
•Varies175h (Medium)

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.

TBA
Proposal

Enhancement of litmusctl: Adding E2E Tests, CRUD Probes Commands (2024 Term 1)

Intermediate
•Varies175h (Medium)

The project (https://github.com/litmuschaos/litmusctl) aims to improve litmusctl by introducing end-to-end (E2E) tests for better release testing and adding CRUD commands for probes, addressing user needs. Additionally, it seeks to enhance user accessibility by making litmusctl available on Brew and Chocolatey package managers. Expected Outcome: The enhancement of litmusctl will include comprehensive E2E testing for improved reliability, the addition of CRUD commands for probes to expand functionality, and availability on Brew and Chocolatey for greater accessibility and user convenience.

TBA
Proposal

CLI v2 - VS Code Integration and Local Dev Loop Enhancement (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>The Microcks CLI (microcks-cli, written in Go) is a key part of Microcks' CI/CD story - it lets developers trigger contract tests and import artifacts from the command line and in GitHub Actions. This project goes into the developer experience layer. Today, developers must navigate to the Microcks web UI in a browser to see test results, check mock status, and diagnose import errors. There is no IDE integration, no offline validation mode, and no way to get mock results inline with the code being tested. This project builds three focused improvements that bring Microcks into the editor and the local dev loop: a VS Code extension, a local dry-run mode powered by Testcontainers, and an updated GitHub Actions output format that annotates PRs with per-operation pass/fail results.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A VS Code extension (microcks-vscode) published to the VS Code Marketplace that connects to a running Microcks instance and shows: loaded services, mock operation status, recent test run results, and importer job logs - all inline in the editor sidebar (Like postman, thunder client)</p><p>&nbsp;- A microcks test --dry-run flag in the CLI that uses Testcontainers (the Microcks uber image) to spin up an ephemeral local Microcks instance, import the specified artifact, run the contract test, report results, and tear down - with no external Microcks server required</p><p>&nbsp;- A demo video and documentation page on microcks.io showing the full local-to-CI workflow</p><p><br></p>

TBA
Proposal

UX Research & IA for Ecosystem Explorer (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>The [Ecosystem Explorer](<a href="https://explorer.opentelemetry.io" rel="noopener noreferrer" target="_blank">https://explorer.opentelemetry.io</a>) helps users discover and get detailed documentation around various OpenTelemetry components. As the project expands to more ecosystems (Python, JavaScript, GenAI), information density will increase significantly, requiring patterns and approaches tailored to more than just the initial Java Agent use case. This mentorship involves conducting UX research to understand how users actually want to consume and use this information, covering: how users currently find information about components or instrumentation (LLMs, GitHub, docs, vendor sites, trial and error); what questions they are trying to answer (what telemetry will I get, how do I configure it, what changed between versions); what personas exist (app developers instrumenting code, platform engineers running collectors, SREs debugging production); how similar tools present dense technical information (npm registry, crates.io, Go pkg site, Docker Hub); and how LLMs are being used in this area and what the experience has been with them. The research will inform how we structure information, what features to prioritize, and how to present complex telemetry data in an accessible way.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>User Interviews Report: Summarized findings from 3-5 user interviews covering different user types and key tasks</li><li>Competitive Analysis Report: Findings from reviewing 2-3 similar tools (e.g., package registries, API documentation sites) on how they present component information</li><li>Information Architecture Recommendations: Proposed structure for presenting a specific type of component data (e.g., "instrumentation" or "collector components")</li><li>Wireframes/mockups (stretch goal): Visual concepts for key user flows</li></ul>

TBA
Proposal
Showing 12697 - 12720 of 13453 Projects
528529530531532