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

Hyperledger - Identity Mixer Support for Fabric Gateway SDK for Java and Client API for Java 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)

Idemix is a cryptographic protocol suite, which provides strong authentication as well as privacy-preserving features such as anonymity, the ability to transact without revealing the identity of the transactor, and unlinkability, the ability of a single identity to send multiple transactions without revealing that the transactions were sent by the same identity. More details here - https://hyperledger-fabric.readthedocs.io/en/release-2.2/idemix.html Current JavaSDK doesn't support to store Idemix credentials in Hyperledger Fabric Wallet. Objective of this mentorship program to support wallet to store idimix identities. - Ability to store Idemix Identity in a Wallet by using Fabric Gateway SDK for Java - Ability to store Idemix Identity in a Wallet by using Fabric Gateway Client API for Java - Ability to use the Stored Idemix Identity from a Wallet to fire transaction to the Hyperledger Fabric Network in both Fabric Gateway SDK for Java and Fabric Gateway Client API for Java - Write Unit Tests and Add Examples in fabric-samples Repository

TBA
Proposal

Enhance Karmada testing coverage

Intermediate
•Varies175h (Medium)

Description: Karmada would like to improve the UT coverage of the code to better maintain the quality of the code and reduce the introduction of defects. Expected Outcome: Increase the UT coverage rate to 65% (currently, the UT coverage rate is [43%](https://app.codecov.io/gh/karmada-io/karmada) ), increase the code coverage rate by about 20%.

TBA
Proposal

Hyperledger - Cacti - Polkadot connector Mentorship Project

Intermediate
•Varies175h (Medium)

Creation of polkadot connector plugin, alongside its cactus-polkadot-all-in-one docker image (hosting a sample polkadot ledger for testing purposes) and the test-tooling package for the AIO Learning Objectives - Hyperledger Cacti codebase - Hyperledger Cacti connector design - Understanding of various interoperability solutions, design and usage of cactus api server - Expected Outcome - Creation of polkadot connector - Creation of polkadot all in one docker image - Creation of polkadot test tooling classes - Documentation, architecture reference diagrams for the polkadot connector

TBA
Proposal

Cue support and validation for the Cortex config

Intermediate
•Varies175h (Medium)

- Description: [Cortex](https://github.com/cortexproject/cortex) is a cloud-native Prometheus compatible monitoring system. It is made up of a set of microservices that can be composed into an architecture that fits multiple use cases. However, this level of flexibility can lead to complexity in the configuration file. One way to handle this complexity is first-class validation support for the config. This is where [Cue](https://cuelang.org/) comes in. Cue provides data validation as a language feature and has solid support for Go. We think enabling Cortex to be configured using Cue and creating a Cue specification for the Cortex configuration file and other file types specific to Cortex would be a good step forward in improving the usability of the project.

TBA
Proposal

Add complete parsing support for Spatial MySQL functions III

Intermediate
•Varies175h (Medium)

Description: Vitess is a database clustering system for horizontal scaling of MySQL. One of the key goals of Vitess is to emulate MySQL behavior even while running multiple MySQL instances so that ORMs and frameworks work seamlessly. Vitess has its own in-built SQL-parser which it uses to understand the query and represent as structs for further processing. As of now, a lot of spatial MySQL functions are not parsed correctly and result in syntax errors. The task of the mentee would be to add parsing support for such functions and features which can be found at https://dev.mysql.com/doc/refman/8.0/en/spatial-analysis-functions.html

TBA
Proposal

Transform Policy YAML Editors into Interactive Form Views (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>The Kuadrant Console Plugin provides a web interface for managing API gateway policies in OpenShift, but currently relies heavily on YAML editing for most policy types. While DNSPolicy and TLSPolicy already have user-friendly form-based interfaces with dual Form/YAML views, validation, and guided workflows, the remaining core policies (RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC) still require users to manually write YAML. This creates a steep learning curve and error-prone configuration experience. This project aims to bring RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC policies to feature parity with the existing DNS and TLS form implementations. Form designs will be provided by the Kuadrant team. The mentee will implement these designs as PatternFly-based form interfaces following the established patterns from the DNS and TLS policy forms. These forms will allow users to configure policies through validated form fields while maintaining the flexibility to switch to YAML view for advanced use cases. The forms must support both creation and editing of policies, include proper field validation, handle complex nested structures (such as rate limit configurations and authentication rules), and synchronize seamlessly between form and YAML representations using the same patterns already proven in the DNS and TLS implementations.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Form-based creation and editing interfaces for RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC policies implemented using the same patterns, components, and structure as the existing DNSPolicy and TLSPolicy forms</p><p>&nbsp;- Dual view toggle (Form View / YAML View) with bidirectional synchronization using js-yaml for all five policy types</p><p>&nbsp;- Field validation following the established validation pattern covering required fields, numeric constraints, conditional dependencies, and Kubernetes resource naming conventions</p><p>&nbsp;- PatternFly component integration matching existing forms: expandable sections for complex nested configurations, validated text inputs, dropdowns for enum fields, and reuse of gateway selection components</p><p>&nbsp;- Policy-specific form fields for: rate limit units and counters (RateLimitPolicy), token-based rate limiting (TokenRateLimitPolicy), authentication strategies and credentials (AuthPolicy), plan tiers and quotas (Plan), and OIDC provider configurations (OIDC)</p><p>&nbsp;- Error handling using the existing error modal and inline validation message patterns</p><p>&nbsp;- Internationalization support for all form labels and validation messages using i18next following the existing localization structure</p><p>&nbsp;- Both create (`/~new`) and edit (`/:name/edit`) routes for each policy type matching the DNS/TLS routing pattern</p><p>&nbsp;- Unit and component tests covering form validation, YAML synchronization, and error states following the established testing patterns</p><p><br></p>

TBA
Proposal

UX UI improvement

Intermediate
•Varies175h (Medium)

In an effort to better the user experience, the CNCF Landscape is actively seeking ways to improve and enhance its features. - The aim is for the mentee to carry out a User Research to validate existing user personas, gain a deeper understanding of user needs, and conduct a thorough heuristic evaluation to gain insights into user experiences. Using the results, the mentee will establish a solid foundation to start an iterative process of ideation, prototyping, and testing possible solutions. The ultimate goal is to initiate a continuous cycle of improvement and further development of features that enhance the user experience of the CNCF Landscape. Recommended skills: Design Thinking, UX research methodology. In this stage of the project, we are seeking candidates with a background and/or training in user research. Supporting materials, such as the following recommended deliverables, that demonstrate your understanding and experience in this area are ideal: 1. Proto-Personas 2. Validated Personas with Supporting Findings 3. Brief Explanation of the Difference between Proto-Personas and Validated Personas 4. List of UX Research Techniques for Kickstarting the Discovery of Landscape Users 5. Figma and Visual Design are a plus.

TBA
Proposal

Convert Kubernetes Best Practices Policies to CEL (2024 Term 1)

Intermediate
•Varies175h (Medium)

Kubernetes Best Practices policies are written using Kyverno patterns and JMESPath, which means they cannot be executed as ValidatingAdmissionPolicy resources in the API server. This project aims to convert Kubernetes Best Practices policies, and other validating policies, to CEL wherever possible. Expected Outcome: Convert Kyverno policies for Kubernetes best practices to CEL.

TBA
Proposal

Adaptive Load Control with Nighthawk (2024 Term 1)

Intermediate
•Varies175h (Medium)

The adaptive load controller operates by iteratively running optimization routines to ascertain the maximum load a system can sustain. Typically, this maximum load is determined by the system's capacity to handle requests per second (rps). The metrics, such as CPU usage and latency, collected from the system under test (SUT) serve as constraints to assess whether the SUT can sustain the imposed load. However, it lacks comprehensive lifecycle management functionalities. This hinders its adoption and limits its potential for continuous performance monitoring and optimization. Expected outcome: Implement mechanisms to trigger alerts and notifications based on performance thresholds or significant changes in key metrics. Integrate Nighthawk testing with existing CI/CD pipelines for automated performance validation and optimization as part of the development and deployment process.

TBA
Proposal

Enhancement for Kruise-Game Dashboard (2024 Term 2)

Intermediate
•Varies175h (Medium)

The OpenKruiseGame Dashboard is presently in its basic form, and we aim to significantly expand its functionality going forward. We plan to introduce features such as the ability to filter game servers and perform batch updates on them. Expected Outcome: new release Dashboard which supports searching, querying, updating objects in batch.

TBA
Proposal

Add Metal3 to Headlamp - Bare Metal Management UI (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>[Metal3](https://metal3.io/) is a Kubernetes-native project for managing bare metal hosts using Kubernetes APIs and operators. This project builds a Headlamp plugin that adds a Metal3 section to Headlamp, surfacing Metal3 CRDs so operators can view and manage bare metal hosts, provisioning states, and infrastructure resources from the Headlamp UI. The plugin follows Headlamp UX patterns with list and detail views, links between related resources, and optional metrics embedding.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Plugin exposes key Metal3 CRDs: BareMetalHost, Provisioning, HardwareData, and related resources.</p><p>&nbsp;- List views, with summary columns (name, namespace, status, provisioning state, power state, hardware profile).</p><p>&nbsp;- Detail pages, showing config, status conditions, hardware data, sub-resources (BMC info, NICs, disks), and basic actions (power on/off, reprovision).</p><p>&nbsp;- Relational navigation, cluster → hosts; host → provisioning state and hardware data.</p><p>&nbsp;- Consistent Headlamp UX, icons, tables, detail layouts, Map view enhancements.</p><p>&nbsp;- Structured config display (collapsible sections/YAML toggle), humanized statuses, validated forms for mutating actions.</p><p>&nbsp;- README with prerequisites and limitations; blog post demoing usage.</p><p><br></p>

TBA
Proposal

Hyperledger Indy Read Replica Implementation Mentorship Project

Intermediate
•Varies175h (Medium)

While Hyperledger Indy has proven to be incredibly robust and more than sufficiently scalable to this point in its evolution and application, we think it would be useful to enable further scalability by adding the concept of Indy Read Replicas to the project. An Indy read replica is a copy of the ledger transactions from one or more Indy ledgers that can be used by clients that trust the replica. For this project, we will start from one of two existing, open source Indy "ledger browser" implementations that collect transactions from the ledger and maintain them in a database. A REST API will be added that provides replica clients with an HTTP version of the existing ledger API. Once a functioning Indy read replica implementation has been developed and tested, we will look at what optimizations can be accomplished to further lower the load on the ledger. For example, a new replica has to retrieve all of the transactions on the ledger, and, in the open source ledger browsers does so by do a read for all transactions starting at 1. Is there a good approach to getting a "trusted" batch of transactions to eliminate that startup load? To find transactions added to the ledger, the read replicas poll the ledger "anything new added?" Can that load be reduced by enabling a transaction "pub/sub" API that notifies read replicas of new transactions, perhaps even pushing them to the replicas. Lots of interesting design and implementation questions!

TBA
Proposal

Label-driven install/uninstall of YurtHub on edge nodes (2026 Term 1)

Intermediate
•Varies175h (Medium)

Currently, in OpenYurt, the core component YurtHub—which acts as a transparent proxy between edge node system components (e.g., kubelet, CNI, CoreDNS, kube-proxy) and the Kubernetes API server—is deployed as a systemd service on each edge node. The installation is performed exclusively via the community-provided tool YurtAdm during node joining. This approach imposes a significant limitation: users must use YurtAdm to onboard nodes, making it impossible to install YurtHub on existing Kubernetes nodes that were not initially provisioned with YurtAdm. To improve flexibility and user experience, the community aims to support a label-driven, declarative installation mechanism: 1. When a specific label (e.g., openyurt.io/is-edge-worker=true) is added to a node, YurtHub should be automatically installed and started on that node. 2. Conversely, when the label is removed, YurtHub should be gracefully uninstalled and its resources cleaned up. This enhancement will enable seamless integration of OpenYurt into existing Kubernetes clusters without requiring re-onboarding of nodes. Expected Outcome: 1. Design and implement a controller/operator that watches for node labels and triggers YurtHub lifecycle operations. 2. Develop an installation/uninstallation mechanism that: a. Installs YurtHub as a systemd service. b. Ensures idempotency and handles failures gracefully. c. Cleans up all YurtHub-related files, configurations, and services

TBA
Proposal

Open Service Mesh Mentorship Project

Intermediate
•Varies175h (Medium)

Open Service Mesh (OSM) is a lightweight, extensible, cloud native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments.

TBA
Proposal

Prototype A2A protocol support in the agentic gateway (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Kuadrant's MCP Gateway is an Envoy-based gateway for Model Context Protocol (MCP) servers that provides routing, policy enforcement, and tool federation. As the agentic ecosystem grows, we're looking to extend the gateway's capabilities beyond MCP to support other agentic protocols. The A2A (Agent-to-Agent) protocol is an emerging standard for inter-agent communication with capabilities like long-running tasks, streaming, and agent discovery via agent cards. This project will investigate how A2A support can be added to the gateway alongside MCP, then build a proof-of-concept demonstrating federated agent discovery and A2A request routing through the gateway. The mentee will work closely with mentors throughout — collaborating on the design doc, pairing on implementation decisions, and spiking on specific pieces as needed to validate assumptions early. They will also engage with the broader Kuadrant community through PR reviews, design discussions, and community calls.</p><p>- Expected Outcome:</p><p>&nbsp;- Analysis of the A2A protocol with a gap assessment comparing A2A and MCP traffic patterns (request/response vs long-running tasks, push notifications, multi-modal artifacts)</p><p>&nbsp;- Design document covering A2A routing through ext_proc, federated agent card serving in the broker, session handling implications, and CRD design</p><p>&nbsp;- Federated agent card endpoint in the broker that aggregates upstream A2A agent cards</p><p>&nbsp;- A2A request routing through the Envoy ext_proc path, with appropriate header handling and policy enforcement</p><p>&nbsp;- CRD design (new resource or MCPServerRegistration extension) for registering A2A agents with the gateway controller</p><p>&nbsp;- E2E tests demonstrating A2A agent discovery and task execution through the gateway</p><p><br></p>

TBA
Proposal

Secure Verifiable Credential Registries (VCR) for GitHub & GitLab

Intermediate
•Varies175h (Medium)

As conceptualized and standardized by the W3C, the Verifiable Credentials protocol is one of the three pillars of Self-Sovereign Identity, together with the Decentralized Identifiers protocol (DIDs) and Distributed Ledger Technology (or Blockchain). The project aims to design and build a verifiable credential registry (VCR) on GitHub repository, namely GitHub-based Verifiable Credential Registry (GVCR), by leveraging existing GitHub APIs, and other open-source tools provided by other Hyperledger projects, such as Aries, Indy, and Ursa. The basic architecture is already built. For more details about the conceptional design and workflows, please refer to the GitHub repository GitHub-VCR.

TBA
Proposal

SQL schema management plugin (2025 Term 2)

Intermediate
•Varies175h (Medium)

With the latest advancements in PipeCD, the plugin architecture for piped has been successfully established (ref: PipeCD plugin-arch blog) (https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/), opening the door for community-driven plugin development. While GitOps traditionally focuses on managing workload states, what about database states? Tools like sqldef (https://github.com/sqldef/sqldef) can be incredibly helpful, especially when adopting a GitOps approach. Expected Outcome: 1. SQL plugin for PipeCD 2. Possible update plugin SDK while develop the SQL 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

Solutions architecture for cloud-native deployments (2025 Term 3)

Intermediate
•Varies175h (Medium)

Learning paths with hands-on labs are a crucial resource for DevOps engineers and cloud-native practitioners. The Meshery Playground provides a live cluster environment, making it an ideal platform for learning every kind of cloud and cloud native technology. Meshery Docs is in need of comprehensive tutorials and scenarios covering common infrastructure management use cases. Mission is to create and publish a series of hands-on tutorials using Meshery Playground. Each tutorial will include step-by-step guides, live demonstrations, and interactive labs using the Playground allowing learners to apply their knowledge directly without the hassle of any configuration.These tutorials will be reviewed by various project maintainers and then published in guides/tutorials. Expected Outcome: - 10+ new solution architectures (designs) published in Meshery Catalog - Each design is ideally adjoined with an interactive tutorial (using Meshery Playground), guiding users through infrastructure. - Tutorials should vary in complexity, catering to beginners and advanced learners.

TBA
Proposal

Auto Generate KubeEdge API Document (2024 Term 1)

Intermediate
•Varies175h (Medium)

KubeEdge has introduced several custom APIs, but currently, there is no corresponding API documentation available. We would like to implement automated generation of API documentation and display it on the website documentation to assist users in quickly understanding the APIs and help developers reduce maintenance costs. Expected Outcome: A tool for automatically generating API documentation.

TBA
Proposal

A Rust library crate for mediapipe models for WasmEdge NN

Intermediate
•Varies175h (Medium)

Description: WasmEdge would like to build a Rust library crate that enables easy integration of Mediapipe models in WasmEdge applications. Each Mediapipe model has [a description page](https://google.github.io/mediapipe/solutions/face_detection.html) that describes its input and output tensors. The [models](https://google.github.io/mediapipe/solutions/models.html) are available in Tensorflow Lite format, which is supported by the WasmEdge Tensorflow Lite plugin. Expected Outcome: We need at least one set of library functions for each model in Mediapipe. Each library function takes in a media object and returns the inference result.

TBA
Proposal

Progressive ConfigMap inplace reloading (2026 Term 1)

Intermediate
•Varies175h (Medium)

Native kubernetes configmap can reload dynamically but lack progressive rollout capability. OpenKruise community had comes up with the [design of new workload](https://github.com/openkruise/kruise/pull/1948) for configmap rolling update, and the [initial implementation](https://github.com/openkruise/kruise/pull/2149) has been running in one end user environment. However the current implementation is not generic enough and had many limitations. The goal is to complete the implementation in a more generic way and to support many configuration reloading strategies. - Expected Outcome: 1. The code for dynamic configmap rollout controller (ConfigMapSet) 2. Unit and integration tests 3. Documentation for the usage of ConfigMapSet

TBA
Proposal

Dashboards for application behavior and KubeArmor state (2024 Term 1)

Intermediate
•Varies175h (Medium)

For showing an application's behaviour, we'd like to have a Kibana/Grafana dashboard. We have existing integrations for visualizing alerts with Elastic/Loki and we can use them for creating these. We want to leverage the above for creating a plugin which will allow users to see an application's behavior based on visibility logs sent by KubeArmor. Expected Outcome: A kubernetes dashboard setup that also has the app behaviours described.

TBA
Proposal

CI/CD Integration, SDK Development & Chaos-CI-Lib Revamp (2025 Term 1)

Intermediate
•Varies175h (Medium)

This task aims to improve the CI/CD experience for LitmusChaos by developing a dedicated SDK that integrates seamlessly with existing CI libraries. The revamped Chaos CI Library will align with Litmus 3.x, eliminating outdated installation steps and enabling direct invocation of prebuilt chaos experiments. Additionally, CI action templates will be refined to optimize tunables, ensuring a smoother and more efficient workflow for users leveraging GitHub and GitLab pipelines. - Expected Outcome: - Seamless CI/CD integration with a new Chaos CI SDK - A modernized Chaos-CI-Lib compatible with Litmus 3.x - Optimized CI action templates for GitHub and GitLab pipelines

TBA
Proposal

Chaos scenario rollback feature (2025 Term 2)

Intermediate
•Varies175h (Medium)

We intend to refactor the current Scenario Plugin API and add a new feature in the plugin abstract class to restore all the changes performed by krkn in the cluster in case run method encounters some kind of exception before ending the execution and or if the run failed for external infrastructure failures. Expected Outcome: The cluster status should be rolled back to the original condition before the scenario execution.

TBA
Proposal
Showing 12961 - 12984 of 13453 Projects
539540541542543