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

Contribute to etcd Self-Assessment (2026 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)

This project continues the work initiated in the etcd - technical scope of the assessment (https://docs.google.com/document/d/1RTXffyDJ8hLoHl_Mo-frQheRQ-8QIVQJ6mqAw69zcP4/edit?pli=1&tab=t.0#heading=h.o524zy9jn6nn). The goal is to dive deep into etcd's architecture in depth by completing and publishing the self-assessment for SIG-Security review. The project has two key components: (1) collaborating with mentors, project maintainers, and Special Interest Groups (SIGs) to investigate etcd and kube-apiserver internals, particularly the lifecycle of requests and consensus mechanisms, and (2) updating and enhancing the etcd.io website (https://etcd.io/) documentation by creating new pages, refining existing content, and publishing blog posts to ensure the documentation reflects current architecture and best practices. Whether you're a new contributor, already active in the community, or simply curious about etcd, we welcome you to join this project! Expected Outcome: 1. Complete the etcd self-assessment draft currently in progress in this document (https://docs.google.com/document/d/1RTXffyDJ8hLoHl_Mo-frQheRQ-8QIVQJ6mqAw69) and prepare it for review by SIG-Security and etcd maintainers. 2. Publish the finalized self-assessment in the SIG-Security repository (see example format - https://github.com/kubernetes/sig-security/blob/main/sig-security-assessments/cluster-api/self-assessment.md)............

TBA
Proposal

Distributed workflow engine

Intermediate
•Varies175h (Medium)

Integrate a new architectural component into Meshery: a workflow engine. This project involves shifting Meshery off of bitcask and off of sqlite over to postgres using gorm (golang). Interns will familiarize with concepts of orchestration engines, including chaining workflows, and content lifecycle management.

TBA
Proposal

Frontend development inside Lit Component Framework

Intermediate
•Varies175h (Medium)

Description: [TestGrid](http://testgrid.k8s.io) is the test visualization tool attached to Prow to collate and display historical test results for the k8s and k8s-adjacent Expected Outcome: Create Lit-based view components for TestGrid (summary, index, etc.) that display data from the API. Implement Jasmine and Storybook testing for these components.

TBA
Proposal

Expand Microcks Hub Sandbox & Mocking for Key Industry APIs (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. This project aims to enhance the [Microcks Hub](https://hub.microcks.io/) by updating the existing sandbox environment or adding new hub entries to mock key APIs IT industry leaders use. The goal is to make it easier for developers to test and prototype integrations with popular APIs like GitHub, Twilio, Stripe, or Salesforce using Microcks. Expected Outcome: Participants can choose to focus on one or both of the following aspects: 1. Update and Refresh the Existing Sandbox: - Improve the sandbox environment provided by Microcks Hub for existing mock APIs. - Ensure compliance with the latest versions of existing APIs. - Enhance documentation, usability, and deployment mechanisms. 2. Add New Hub Entries for Key Industry APIs: - Develop mock entries for leading APIs like GitHub, Twilio, Stripe, or Salesforce, but we welcome any ideas... - Ensure the mocks cover essential endpoints and realistic request-response pairs. - Provide detailed examples and use cases to support integration testing.

TBA
Proposal

Industrial embodied intelligence benchmarking framework (2025 Term 2)

Intermediate
•Varies175h (Medium)

As industrial manufacturing accelerates its digital transformation through advancements in robotics, adaptive production lines, and smart testing systems, cloud-edge collaboration has emerged as a critical enabler for deploying embodied intelligence in complex operational environments. Contemporary industry requirements for embodied intelligence now extend beyond basic task execution to encompass multimodal perception-decision integration, dynamic environment adaptation, and distributed device orchestration. Existing benchmarking frameworks exhibit limitations in evaluating scenario-specific embodied attributes inherent to industrial settings. This initiative leverages the KubeEdge-Ianvs collaborative AI framework, integrating domain-specific test datasets, simulation environments, and quantitative metrics to establish a certified industrial-grade evaluation infrastructure for embodied intelligence systems. Expected Outcome: 1. Develop an industrial-grade embodied intelligence dataset through systematic classification and reorganization of existing resources across four standardized task categories 2. Design standardized validation suites within KubeEdge-Ianvs 3. Deploy reference baseline algorithms using the developed validation suites to establish performance benchmarks within KubeEdge-Ianvs

TBA
Proposal

Kyverno Kuttl Enhancements

Intermediate
•Varies175h (Medium)

Add new features to the kuttl application used by the Kyverno project to aid in its end-to-end testing process. - Expected Outcome: Kyverno's fork of kuttl has these enhancements allowing more and better test cases to be written.

TBA
Proposal

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

Intermediate
•Varies175h (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
Showing 481 - 504 of 1243 Projects
1920212223