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

Developing Guidelines for OTel Survey Analysis and Communication (2025 Term 3)

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)

Various special interest groups (a.k.a. SIGs) in the OpenTelemetry project run surveys to understand the experience of the end-users better. To run surveys efficiently, SIG End-user provides guidelines and assistance to people running surveys. In the past, SIG End-user focused on providing guidelines around survey design. Now we would like to move forward and cover survey data analysis and communication findings. Expected Outcome: The mentee in this project will describe a step-by-step survey data analysis process and tools that OTel contributors without deep data analytics knowledge can leverage to analyze their survey data – from cleaning and coding of data, through descriptive statistics, cross-tabulation, to visualization. In addition, the mentee will come up with suggestions on how to improve existing and/or propose new ways to communicate survey findings from surveys to the OpenTelemetry community. [Bonus] The mentee might also execute one survey to test out the guidelines.

TBA
Proposal

OpenTofu deployment plugin (2025 Term 2)

Intermediate
•Varies175h (Medium)

In the latest evolution of PipeCD, the plugin architecture for piped has been established (ref: PipeCD plugin-arch blog)(https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/) , paving the way for community-developed plugins. Previously, PipeCD already supported deploying applications using Terraform, with the Terraform plugin being developed by the maintainer team to ensure continued support for existing users. Meanwhile, OpenTofu has emerged within the Cloud Native landscape as a drop-in alternative to Terraform. To align with this development, we aim to extend PipeCD’s support to enable the deployment of OpenTofu applications, just as we have done for Terraform. Expected Outcome: 1. OpenTofu plugin for PipeCD 2. Possible update plugin SDK while develop the OpenTofu plugin 3. Possible update docs how to develop PipeCD plugin 4. Blog about how to develop a PipeCD plugin on https://pipecd.dev/blog/

TBA
Proposal

VS Code Debugger Plugin for Hyperledger Fabric Chaincode

Intermediate
•Varies175h (Medium)

A VS code extension and toolbox to debugging a chaincode. The extension once installed can be used by developers of chaincode to run and debug from their IDE, to understand how their chaincode behaves. The current process of installing the chaincode, adding the logs, running it through a test network for operational efficiency is not ideal for a faster development cycle. There is also a dependency on number of tools and commands that a developer would need to be aware of before developing the chaincode. The scope of this project is to utilize one of the existing deployment means for the chaincode, then provide a debugger from the VS code through a plugin. Expected Outcome and Deliverables - Develop a plugin that can be installed and run on any developer machine. - Ideally, one should be able to develop on any operating system, be it a Mac, Windows, or any of the Linux variant. - Debug the chaincode as the developers are used to writing their code, as opposed to learning administrative aspects. At times reproducing a production scenario is all it takes to fix an issue, and it may get complicated with patch fixes. - Option to initialize the state database so that the debugging can be effective. - This is a futuristic goal to achieve with the project. - Primary goal is for the chaincode to be deployment ready at the end of the development cycle. The deliverable is the working VS code plugin.

TBA
Proposal

Technical Content Creation CNCF Challenges (2024 Term 2)

Intermediate
•Varies175h (Medium)

On a periodic basis, the CNCF would like to present a public challenge to those that are interested in participating (e.g. “Challenge: Distributed Tracing with Jaeger”). Your mission in this internship is technical content creation of said challenges through use of markdown, Meshery, and any number of other CNCF projects. Challenges will be created using the Meshery Playground and potentially published in the proposed CNCF Hub. They will be similar too, but slightly different from these [example tutorials](https://docs.meshery.io/guides/tutorials/). Understand that your challenges will be promoted through CNCF channels, reviewed by various project maintainers, and that each challenger (participant) will receive a certain number of points, depending upon whether or not they successfully complete the challenges that you create and in what timeframe they complete those challenges (the faster, the more points). Your challenges will need to vary in level of difficulty. Expected Outcomes: - 10+ new challenges published in CNCF Hub (and Meshery Catalog and Artifact Hub). - Challenges can contain more than one objective. Points are earned for each objective completed. - Bonus: Extend one or more of Meshery’s Learning Paths.

TBA
Proposal

Refactor the ORAS documentation structure and write new user guides

Intermediate
•Varies175h (Medium)

Refactor the ORAS documentation structure and write new user guides based on the latest version of ORAS. The detailed ORAS documentation structure and content should be refactored according to the proposal in the [upstream issue](https://github.com/oras-project/oras-www/issues/65). - Expected Outcome: Deliver a developer-friendly documentation structure for ORAS and write new user guides according to the proposed documentation structure. Publish all content at https://oras.land/

TBA
Proposal

Expand integration with Artifact Hub (2024 Term 1)

Intermediate
•Varies175h (Medium)

While Meshery has made significant strides, its integration with Artifact Hub requires expansion and enhancement to maximize users experience. The goal is expand integration between Meshery and Artifact Hub which starts with making Meshery designs as a new Artifact Hub kind. Expected Outcome: Definition and implementation of Meshery patterns as a distinct category within Artifact Hub. Design features to showcase Meshery's unique design patterns, enhancing visibility and accessibility. Collaborate with select publishers to integrate Meshery snapshots into Artifact Hub entries. Enhance user experience by providing visual representations of Meshery-related artifacts.

TBA
Proposal

Vertical Block Sharding

Intermediate
•Varies175h (Medium)

Current Thanos topology is generally horizontally scalable. However, the use cases and approaches of deploying Thanos shifted through time. While initially, Thanos was enabling ingestion through sidecars, now it’s not uncommon to see Thanos receiver usage. This means that the invariant of definite size TSDB block is no longer true. With offline deduplication and arbitrary Receive tenants data can be ingested into huge, often hundreds GB size TSDB blocks. This makes it harder to scale compaction and query operation on top of such blocks. The idea of this work is to vertically split larger blocks into smaller ones with the common scaling technique called sharding. As a mentee, we will guide you to make progress towards this goal by teaming up with experienced developers to deliver transparent automation for vertical block sharding! We are looking forward to working with you! During this mentorship, you will learn a lot about programming in Go, distributed Systems, TimeSeries Database, Prometheus, Thanos!

TBA
Proposal

Implement flushing of conntrack entries in Netavark (2025 Term 3)

Intermediate
•Varies175h (Medium)

This project will involve implementing conntrack entry clearing into Netavark, Podman's network management tool. Stale conntrack entries can cause network traffic to be dropped if a UDP port is rebound while a container is running. Netavark is written in Rust, but the Rust netlink bindings (located here - https://github.com/rust-netlink/netlink-packet-netfilter) presently do not include support for Conntrack. As such, the first step of the project will be to expand these bindings to cover Conntrack. Netavark can then make use of the bindings to flush Conntrack entries on network change, and tests implemented to verify this functionality. Expected Outcome: 1. Rust bindings for Conntrack implemented in the rust-netlink (https://github.com/rust-netlink/netlink-packet-netfilter) library 2. Netavark modified to use these bindings to drop Conntrack entries at appropriate times 3. Tests in Netavark repository to verify this functionality

TBA
Proposal

Definition of MeshMark (extended)

Intermediate
•Varies175h (Medium)

Description: Create MeshMark provides a universal performance index to gauge your mesh’s efficiency against deployments in other organizations’ environments. MeshMark functions as a service mesh performance index (a scale) to provide people the ability to weigh the value of their service mesh versus the overhead of their service mesh and assess whether they are getting out of the mesh what they are “paying” for in it. Work with maintainers from Layer5, Intel, Red Hat, and HashiCorp on researching cloud native infrastructure performance. Internship involves: machine learning, adaptive algorithms, running and analyzing performance statistics.

TBA
Proposal

Build a Go library and CLI for interacting with OpenBuildService

Intermediate
•Varies175h (Medium)

Kubernetes is set to start using [OpenBuildService](http://openbuildservice.org) as a platform for building, publishing, and hosting Kubernetes system (Debian and RPM) packages. The current integration with the OpenBuildService platform assumes a lot of manual tasks and depending on `osc` command-line tool written in Python. At SIG Release, we're striving to automate as many tasks as possible. We want to build a library and CLI written in Go for interacting with the OpenBuildService APIs and platform that can be integrated with our existing [release tooling (`krel`)](http://github.com/kubernetes/release). - Expected Outcome: Library and CLI tool for interacting with OpenBuildService platform via their publicly available APIs. Both library and CLI tool should be properly tested via unit, integration, and end-to-end tests, and properly documented.

TBA
Proposal

Implement fan-out query observability in Thanos

Intermediate
•Varies175h (Medium)

In the previous mentorship sessions we added the foundation required for query observability in Thanos's new [promql-engine](https://github.com/thanos-io/promql-engine) and hooked it up in the UI. We now have the foundation to record telemetry from our query engine as well such as time consumed per operator. This project aims to expand on this and add more metadata to the query execution, both on the promql-engine operator tree level and Thanos Query `Select()` calls for fan-out query observability. Once we have this metadata, we would like to visualize it in the Query UI. - Expected Outcome: The end goal is to have a query execution tree decorated with the metadata, collected during execution (ideally even visualized in the Thanos UI). This will help users to understand the performance implications of their PromQL queries and the bottlenecks in their Thanos Query setups. https://github.com/thanos-io/thanos/issues/6517 https://github.com/thanos-community/promql-engine/issues/106

TBA
Proposal

Develop MCP Server for Agentic AI interaction with OpenCost (2025 Term 3)

Intermediate
•Varies175h (Medium)

We would like OpenCost to more effectively integrate with AI agents. To do this, we need to implement a Model Context Protocol (MCP) server to surface the information from the OpenCost API. This is a great opportunity to learn about MCP servers, and help us build an interface for AI agents to obtain reliable cost/usage information so that they can accomplish their business goals. Expected Outcome: We would like an MCP server integrated into OpenCost. This MCP server should support queries on allocations, assets, and cloud costs. The MCP server should support the full range of allocations, assets, and cloud cost query parameters. A demo video should be recorded showing an interaction with the MCP server, and used to obtain costing information in a conversational setting. In addition, integration tests must be created in the OpenCost Integration Tests repo that test all interactions with the MCP server.

TBA
Proposal

Support Hyperledger Fabric 3 in Fablo

Intermediate
•Varies175h (Medium)

Fablo is a tool mostly used for local development and in CI. Is 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). Currently it supports Hyperledger Fabric in versions since 1.3 to 2.5. With the new upcoming release of Hyperledger Fabric (version 3): - We want Fablo to support Hyperledger Fabric v3, along with BFT consensus - We want to drop support for Hyperledger Fabric v1.3 and v1.4. - Optionally, we want to approach support for Fablo on ARM architecture (Apple M; running ARM Docker images for Fabric). Mentee will work with Bash scripts that are used for calling Fabric, TypeScript code for validation and normalization of config, and template engine to generate parametrized configs. Also mentee will be responsible for creating automated tests (both TS unit tests and e2e tests in Bash), covering implemented features, and updating Fablo documentation.

TBA
Proposal

Jaeger-V2 Service Performance Monitoring (2024 Term 2)

Intermediate
•Varies175h (Medium)

Jaeger is a distributed tracing platform. Jaeger V2 is a major new version where we rebase all Jaeger backend components (agent, collector, ingester, and query) on top of the OpenTelemetry Collector. Jaeger-v1 implements a functionality known as SPM, but it requires a separately running OpenTelemetry Collector to produce metrics out of spans using SpanMetrics Connector. Since Jaeger-v2 is built on top of OTEL Collector, we can run SpanMetrics Connector directly in the Jaeger binary and simplify the setup for the users. Expected Outcome: Achieve parity in SPM of jaeger-v2 compared to jaeger-v1. Implement integration tests. Update documentation accordingly. Extra credit: implement metrics reader directly on top of Elasticsearch/Opensearch and bypass the need for Prometheus.

TBA
Proposal

Models Support for OCI Registries (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Meshery Models are declarative representations of infrastructure, applications, and their relationships - the canonical artifacts through which Meshery understands and manages cloud native systems. Today, Meshery lacks a standardized, portable distribution mechanism for these models. OCI registries (Docker Hub, AWS ECR, GitHub GHCR, and others) have emerged as the universal artifact store for the cloud native ecosystem, and [ORAS](https://oras.land) (OCI Registry As Storage) provides the Go-native tooling to push and pull arbitrary artifacts to any OCI-compliant registry. This internship implements end-to-end OCI registry support for Meshery Models - from new Connection and Credential types for major registries, to ORAS-powered push/pull logic in the Meshery server, to a redesigned Registry page in the Meshery UI that gives users full visibility and control over their model artifacts across registries.</p><p><br></p><p>Recommended Skills: Golang, REST API development, React. Familiarity with OCI image specifications, container registries, or ORAS is a plus. Experience with Meshery or other CNCF projects is welcomed but not required.</p><p><br></p><p>Responsibilities:</p><p>&nbsp;- Design and implement Connection and Credential types for Docker Hub, AWS ECR, GitHub GHCR, and additional OCI-compliant registries within Meshery's existing connection framework.</p><p>&nbsp;- Implement Golang server-side logic using the ORAS SDK to push and pull Meshery Models (and their component schemas, relationships, and policies) to and from any OCI-compliant registry.</p><p>&nbsp;- Define the OCI artifact media types, manifest structure, and layer conventions used to package Meshery Models for registry storage.</p><p>&nbsp;- Enhance or rewrite the Registry page in Meshery UI to surface connected registries, browsable model artifacts, push/pull controls, and credential management.</p><p>&nbsp;- Write integration tests covering push, pull, and round-trip fidelity of Meshery Models across at least two registry backends.</p><p>&nbsp;- Document the new registry integration, artifact format, and UI workflows in Meshery's official documentation.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Meshery users can connect to Docker Hub, AWS ECR, GHCR, and other OCI registries using managed credentials and push or pull Meshery Models directly from the Meshery UI and `mesheryctl`.</p><p>&nbsp;- A well-defined OCI artifact convention for Meshery Models, documented and suitable for adoption by the broader Meshery ecosystem.</p><p>&nbsp;- A redesigned Registry UI page providing a unified, registry-agnostic interface for model artifact management.</p><p><br></p>

TBA
Proposal

Update Builder implementation to 0.1 Builder Spec

Intermediate
•Varies175h (Medium)

In Cloud Native Buildpacks, [Builders](https://buildpacks.io/docs/concepts/components/builder/) are distributed OCI images that act as the complete context for the building of an application. They came into existance by necessity and have risen to be an essential concept that now needs a specification. As part of this project, you will help us make the necessary changes to [pack](https://github.com/buildpacks/pack) to adhere to the specification as well as _finalize_ the specification itself. This will have to be done with consideration to existing implementations in effort to prevent unintentionally breaking anyone's existing workflow.

TBA
Proposal

Advanced Kubescape plugin features for VSCode (2024 Term 2)

Intermediate
•Varies175h (Medium)

Kubescape has a VSCode plugin to facilitate applying configuration fixes that harden Kubernetes infrastrcutture without creating a burden of context switching on engineers tasked with security scanning and implementing their results. Expected Outcome: Inetgrating container image scanning capabilities in the Kubescape VSCode plugin and implementing Kubescape's ability to apply fixes for configuration issues to YAML files or Helm charts directly within their development environment.

TBA
Proposal

Improve Test Coverage for Istio Ambient Mesh (2024 Term 1)

Intermediate
•Varies175h (Medium)

Ambient mesh is now one of the biggest features in Istio, but it is in its early stage. We are in the process of improving the test coverage for Ambient Mesh in order to move it to Beta. Ztunnel works as shared data plane within a node, it subscribes to `Workload` and `Authorization` resources, both need to be well tested. Expected Outcome: - Enhanced UnitTest coverage for `Workload` and `Authorization` Delta xDS/Stow interface. - Enhanced integration tests for ztunnel Authorization Policy Upstream Issues: - https://github.com/orgs/istio/projects/9 - https://github.com/istio/ztunnel/issues/251

TBA
Proposal

Building gadgets with Rust (2025 Term 1)

Intermediate
•Varies175h (Medium)

Inspektor Gadget is an eBPF tool and systems inspection framework for Kubernetes, containers and Linux hosts. A Gadget is an OCI image that includes one or more eBPF programs, metadata YAML file, and optionally, WASM modules for post processing. Today, Inspektor Gadget provides tooling to build gadgets from source code written in C (for the eBPF module) and Go (for the WASM module). This project is about adding support from building gadgets from Rust both for eBPF programs and for WASM modules. Expected Outcome: users can write their gadgets in Rust.

TBA
Proposal

Hyperledger - Optimising pipelines using Github Actions for Caliper and Caliper-Benchmarks Mentorship Project

Intermediate
•Varies175h (Medium)

Performance benchmarking distributed systems (such as DLTs) is a challenging task, comprising of multiple aspects, such as scalable workload generation, representative workload definitions, and comprehensive data analysis. Hyperledger Caliper is a general-purpose benchmarking tool with the goal of mitigating the aforementioned aspects of performance benchmarking. Hyperledger Caliper-benchmarks provides a set of example benchmarks for use with Hyperledger Caliper. In order to be able to assist maintainers/contributors to Caliper and Caliper-Benchmarks, a build system is utilised to run tests to verify a PR doesn't break anything plus it provides a continual deploy mechanism to publish Hyperledger Caliper artifacts to DockerHub and NPM so end users can have access to the Caliper tool. These build systems use different build pipeline implementations. The goal of this project is to optimise how Caliper and Caliper-Benchmarks verify PRs and publish artifacts using Github Actions and to improve how testing is done to ensure that the artifacts to be published actually work as expected.

TBA
Proposal

Prometheus exporter for image vulnerabilities

Intermediate
•Varies175h (Medium)

Kubescape has a component that runs in-cluster which performs image scanning on all the container images deployed to a cluster. This function is largely used to send the data to an external service. In this projet, you will develop a Prometheus exporter for the image vulnerability information produced by Kubescape. This will allow users to access the data from within the cluster, as well as use it for alerting. - Expected Outcome: Access to cluster vulnerability data through Prometheus. For example, you should have the ability to alert on number or percentage of "Critical" level vulnerabilities in containers running in the cluster.

TBA
Proposal

Hyperledger - One-stop-shop Hyperledger Fabric performance analysis with Hyperledger Caliper Mentorship Project

Intermediate
•Varies175h (Medium)

Performance evaluation of DLTs is a complex process stemming from the inherent complexity of distributed systems. One way to mitigate such complexity is the separation of concerns: use task-oriented solutions for different aspects of the process: - The System Under Test (SUT) is deployed in a representative operating environment. - A dedicated, purpose-specific load generator tool submits representative requests to the SUT. - The SUT is closely monitored during the load generation process, and the measured data is typically stored for post-mortem analysis. - A detailed analysis is performed on the measured data using dedicated data analysis techniques. A summarizing report is the typical final output of the process, containing insights about the SUT. Hyperledger Caliper provides capabilities to integrate lightweight components that can retrieve aggregated results from external components and incorporate them into the generated report. The goal of the project is to provide a single entry/exit point to the performance analysis (once the SUT and its monitoring are configured) by: Providing an open, well-designed, and thoroughly documented side-car service for the detailed performance analysis of distributed Fabric transaction traces. And integrating it into the Caliper load generation and response measurement process as part of the final report. The project will heavily build on the PSWG's Performance Sandbox, aiming to "standardize" its flow and methodologies independently

TBA
Proposal

Adding OpenTelemetry Support

Intermediate
•Varies175h (Medium)

Description: To integrate KubeArmor with OpenTelemetry, an adapter needs to be created. OpenTelemetry is a standard for telemetry data, including distributed tracing, metrics, and logs, and has an SDK and a collector component that can run on Kubernetes. Applications can directly expose OpenTelemetry data through in-app instrumentation using the OpenTelemetry SDK. The collector can then gather data from multiple applications in a cluster and send it to various backends for storage and visualization, such as Jaeger. Expected Outcome: The mentee's task is to develop an OpenTelemetry adapter for KubeArmor that can receive logs, alerts, and telemetry from the kubearmor-relay-service and convert it into the OpenTelemetry format. They are also expected to create documentation and usage guides that describe how to set up and use the adapter, as well as demonstrate the integration with a backend that supports OpenTelemetry.

TBA
Proposal

KubeArmor Telemetry Monitoring and Dashboards

Intermediate
•Varies175h (Medium)

Description: KubeArmor generates a large amount of data through logs and alerts, but interpreting this data can be difficult. To make it easier to understand, it is necessary to parse the telemetry, create meaningful metrics, enable data filtering, and create visualizations such as graphs to display on a dashboard. Expected Outcome: Create a telemetry dashboard, write setup documentation and usage guide.

TBA
Proposal
Showing 12601 - 12624 of 13453 Projects
524525526527528