Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

Your premium companion for discovering, matching, and tracking paid open-source mentorship programs and verified starter issues.

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Accessibility Statement

Made with love bySubhranshu Sekhar Dash

© 2026 Contribo. Built for the global open-source community.

PlatformProjects

Explore Projects

Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.

Confused which project to choose or don't know which one you are most suitable to work on?

Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.

Match with Orbit AI
Filters Clear
1243 Projects Found
Sort by

Hyperledger - Improve User Experience from Getting Started to Continuous Engagement 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)

Hyperledger India Chapter started with the https://start-here.hyperledger.org to help new developers look for contribution opportunities. The tool provides an option to see through a list of all "Good First Issues", "Open PRs" and "Releases". The requirement, in this proposal, is to extend or improve the website to include - role-based navigation (eg. Developer, Business User, Contributor, etc) to information. The process will involve adding easy to access links or information for project documentation, community contribution guidelines, guiding (new & experienced) users towards how to start & what tasks require contribution, informing the latest happenings within the community (i.e. figuring out available events and meetups), and Calendar(s). The cherry on top of it would be to have navigations defined for different users and search capability. The task would start with the survey on what somebody looks for within the community, understand what troubles them. The project is aimed at providing an improved user experience.

TBA
Proposal

Develop ORAS Website

Intermediate
•Varies175h (Medium)

Description: [ORAS](https://oras.land/) is a tool for working with OCI artifacts and OCI registries. It allows users to distribute OCI artifacts across OCI Registries. ORAS only has a documentation site so far, the project goal is to develop a new website using Hugo framework based on the Figma layout design. Expected Outcome: Develop a new website using the [Hugo framework](https://gohugo.io/) based on the Figma layout design. It will replace the existing [ORAS documentation website](https://oras.land/) and provide a better user experience with interactive design.

TBA
Proposal

Backstage plugin that adheres to the new plugin system (2024 Term 2)

Intermediate
•Varies175h (Medium)

Backstage has become a popular option for an internal portal that provides information for engineers in different capacities. Creating a backstage plugin for Kubescape will ultimately help users achieve their goal of hardening Kubernetes clusters, by being able to view security posture information on Backstage and without context switching. Expected Outcome: A Kubescape plugin for Backstage in which users will be able to get information about their security posture and highest risk workloads at a glance within the organizational portal.

TBA
Proposal

Work through OpenTelemetry User Research Documentation and Implement Fixes

Intermediate
•Varies175h (Medium)

Implement the fixes suggested in the user research documentation to make this project more consumable for end users.

TBA
Proposal

Contributor Journey Research (2024 Term 1)

Intermediate
•Varies175h (Medium)

Getting new contributors onboarded into a complex project like Knative is a lot of work for both the new contributors and for the maintainers. This is compounded by the fact that many contributors don't stick around after the first few contributions. We would like to perform a research study into why some contributors stay while others leave the community after a bit, and determine where we can improve the contributor experience. Expected Outcome: Create a report based off of user research detailing the current contributor journey within Knative and highlighting areas where that can be improved.

TBA
Proposal

Iterating Enhancement for KubeEdge Dashboard (2024 Term 2)

Intermediate
•Varies175h (Medium)

Based on the previous release of KubeEdge, a version of the dashboard has been implemented. With the iterative updates of the backend API, the current dashboard may have several issues. In this project, we aim to iterate and update the dashboard to ensure its compatibility with the latest version of KubeEdge. Additionally, we want to refactor the dashboard using more mainstream frameworks such as Material and optimize the user experience of the dashboard. Expected Outcome: new release Dashboard which supports new KubeEgde APIs.

TBA
Proposal

Add Kubeflow to Headlamp: ML workflow management UI (2026 Term 1)

Intermediate
•Varies175h (Medium)

Build a Headlamp plugin to surface Kubeflow resources (Pipelines, Katib, PipelineRuns, Notebooks, TFJob/PyTorchJob/TrainJob, Spark) so operators and ML engineers can discover, monitor, and manage ML workloads alongside standard K8s resources. Link to Kubeflow UIs when deeper functionality is needed. - Expected Outcome: - New Kubeflow sidebar with cross-namespace lists for Pipelines (Experiments, Runs), Katib experiments, Notebook servers, Training and Spark jobs. - Detail pages per resource showing metadata, status, metrics, logs and common actions (start Run, open Jupyter, view best hyperparams). - Links/embed to Kubeflow Central Dashboard or Pipelines UI for advanced tasks. - Headlamp Map integration: show relations to Deployments/Pods, Argo workflows, Spark driver/executors. - Metrics via Prometheus or /metrics: basic charts for experiment objectives and pod resource use. - Polished UX: icons, pagination, filtering, error handling. - Outreach: README/User Guide and a demo blog post with screenshots.

TBA
Proposal

Relationships and Solutions Architecture of Cloud Native Deployments (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This project focuses on expanding Meshery Relationships across a wide range of technologies, including Kubernetes and major cloud providers, to better model their interactions and improve user insights. There is a growing need to accurately model these relationships to provide better insights and control over deployments.</p><p><br></p><p>&nbsp;The next phase focuses on Cloud Solution Architecture through workload design by creating and publishing Meshery designs that use the newly developed relationships to represent real-world deployments. These designs will be turned into structured tutorials with hands-on labs using Meshery Playground, offering step-by-step guidance and interactive learning. All content will be reviewed by maintainers and published in Meshery’s official documentation</p><p><br></p><p>Responsibilities:</p><p>&nbsp;- Research and Analyze Technologies: Dive deep into various cloud-native technologies (e.g., different compute services, databases, messaging systems, network services, etc.) to understand their components and how they interconnect.</p><p>&nbsp;- Develop Relationship Definitions: Create and contribute relationship definitions, typically in JSON or YAML format, to the Meshery models.</p><p>&nbsp;- Model Inter-Technology Interactions: Focus particularly on defining relationships between components from different technologies (e.g., how a Kubernetes deployment relates to an AWS RDS instance, or how a Linkerd service interacts with a Prometheus monitoring component).</p><p>&nbsp;- Document New Relationships: Clearly document the newly defined relationships, their purpose, and how they are represented within Meshery designs, contributing to the official Meshery documentation.</p><p>&nbsp;- Create and publish designs that use newly developed relationships.</p><p>&nbsp;- Create and publish hands-on tutorials using Meshery Playground, featuring step-by-step guides and interactive labs that enable learners to apply concepts without the hassle of any configuration.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A multitude of new intra- and inter-service relationships defined across AWS, Azure, and GCP.</p><p>&nbsp;- Creation and publishing of real-world workload designs that represent cloud solution architectures using the newly defined relationships.</p><p>&nbsp;- Tutorials reviewed by various project maintainers and then published in guides/tutorials.</p><p>&nbsp;- Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.</p><p><br></p>

TBA
Proposal

Hyperledger - Deploy Carbon Accounting Network with Bevel Mentorship Project

Intermediate
•Varies175h (Medium)

The Hyperledger Labs blockchain-carbon-accounting project has progressed significantly, and we're looking to move to production deployment of it. The deployment of a Hyperledger Fabric, however, has been a difficult and time consuming process in the past. Working with the maintainers of Hyperledger Bevel, we would like to streamline the deployment processes for both Fabric and Besu networks. Our goal is to allow any organization to join the networks using its own cloud infrastructure. At the end of the project, we are looking for: - Successful deployment of blockchain-carbon-accounting across multiple cloud networks, such as Digital Ocean, AWS, and Azure. - Scripts for further maintenance of the networks. - Detailed tutorials and learning materials which would benefit both blockchain-carbon-accounting developers and the broader Fabric, Besu, and Bevel communities.

TBA
Proposal

Improve IPsec Stability and Usability (2025 Term 3)

Intermediate
•Varies175h (Medium)

Communication encryption is an important functional feature of the Service Mesh to ensure communication security. Kmesh uses IPsec to implement this feature. However, Kmesh lacks the reliability maintenance and ease of use enhancements for Kmesh. Therefore, we should optimize the reliability and ease of use of IPsec in addition to its implementation. Expected Outcome: 1. Reduce IPsec configuration steps according to users' actual usage scenarios. It is best to realize one-click configuration for users. 2. Sorting out Ipsec code and refactoring where it affects stability and performance. 3. UT overlay with enhanced IPSec features

TBA
Proposal

Data Querying for Kai & InstructLab Integration Potential (2024 Term 3)

Intermediate
•Varies175h (Medium)

Kai is a tool designed to leverage AI for application modernization by analyzing code, identifying issues, and suggesting fixes. We aim to enhance Kai by developing a robust data querying mechanism to facilitate fine-tuning processes. This enhancement will lay the groundwork for potential future integration with InstructLab, an open-source AI project enabling community contributions to Large Language Models (LLMs) by adding new skills or knowledge. The primary focus will be on creating mechanisms to query and utilize data effectively, with a stretch goal of integrating static analysis tools and implementing an agent-based workflow. - This project will significantly enhance Kai’s backend, making it more scalable and capable of providing deeper code insights while also contributing to the enrichment of LLMs through InstructLab. It will offer a rich learning experience for participating students, covering backend development, workflow management, and contributing to open-source AI projects. - Expected Outcome: - Successfully develop and implement a data querying mechanism in Kai to facilitate fine-tuning processes. - Demonstrate the enhanced backend with improved data querying capabilities. - Participate actively in community meetings, presenting progress and insights. - Create a detailed blog post documenting the project, its outcomes, and potential future directions, including the possible integration with InstructLab. - (Stretch Goal) Develop a reusable module fo

TBA
Proposal

Series Cardinality API

Intermediate
•Varies175h (Medium)

Description: Prometheus has a TSDB stats API https://prometheus.io/docs/prometheus/latest/querying/api/#tsdb-stats which contains information about series cardinality and the API is supported by Thanos. However, it can only return 10 results per stats, which is not flexible to track the arbitrary metrics. This project aims to design and implement APIs that expose cardinalities. Stretch goal can be to add cardinality explorer page to Thanos UI. Expected Outcome: New Thanos APIs to expose series cardinality.

TBA
Proposal

Refactor the cloudStream to pass-through the request instead of parsing the web pat

Intermediate
•Varies175h (Medium)

Edgestream is used to handle the request from apiserver, then forward the request to edged through tunnel. We will find a way to pass-through the request, through the hijack stuff, instead of parsing the web path manually.

TBA
Proposal

Adapter for AI and LLMs (2026 Term 1)

Intermediate
•Varies175h (Medium)

Meshery is the open-source cloud native manager that empowers platform engineers to design and operate infrastructure. As infrastructure complexity grows, the need for intelligent assistance becomes critical. This project focuses on developing and enhancing a dedicated AI Adapter and AI Connections for Meshery. This adapter serves as the bridge between Meshery’s core orchestration engine and various Large Language Models (LLMs). The goal is to enable "Natural Language to Infrastructure" capabilities, allowing users to describe their architectural intent (e.g., "Deploy a highly available Kubernetes cluster on AWS with Prometheus monitoring") and have Meshery auto-generate the visual topology and configuration manifests. The intern will work on decoupling the AI logic from the core platform, allowing users to "Bring Your Own Model" (BYOM)—supporting both cloud-based providers (OpenAI, Anthropic) and local inference runners (Ollama, LocalAI). Expected Outcome: 1. A fully functional AI Adapter (or Connection) integrated into the Meshery ecosystem. 2. Demonstrable capability for users to swap between at least two different LLM providers (e.g., OpenAI vs. a local Llama 3 model). 3. Implementation of a feature where natural language queries result in a rendered design. 4. Merged pull requests (PRs) including code, tests, and documentation.

TBA
Proposal

Zowe Explorer extension templates Mentorship Project

Intermediate
•Varies175h (Medium)

The sample VS Code extension should satisfy a generic mainframe use case (search, compare, etc ) and be hosted on github.com/zowe. The extension should demonstrate how to call directly to a backend service and extend Zowe Explorer via a new tree or menu options.

TBA
Proposal

Verilator VPI array value accessor Mentorship Project

Intermediate
•Varies175h (Medium)

Verilator, an open-source Verilog emulator, is a well-established and community-supported hardware verification tool. It is widely used in developing and testing RISC-V CPU RTL designs. Rocket, CVA6, BOOM, and most other RISC-V RTL designs in the RISC-V Chipyard toolkit lean on Verilator to emulate their respective designs. A common requirement in hardware verification is the ability to access the value of hardware elements and registers during live emulation. The Verilog Procedural Interface (VPI) is an interface that enables this ability. It is defined under the IEEE 1364 and IEEE 1800 standards. Two of the functions provided by VPI are “vpi_get_value” and “vpi_put_value”, these are the sole function that allows C/C++ code to access Verilog scalars during live emulation. Currently, accessing elements within an array requires the use of iterators and consecutive calls to these functions. This poses a high-performance cost when attempting to validate the contents of large arrays. However, IEEE VPI standard does define “vpi_get_value_array” and “vpi_put_value_array” functions, which allow C/C++ code to access verilog arrys with a single call. These functions are unimplemented in the latest version of Verilator and depending on their implementation, may be used to access arrays with less memory utilization, fewer instructions, and faster emulation time.

TBA
Proposal

LFDT - Continuous Benchmarking for Besu EVM Mentorship Project

Intermediate
•Varies175h (Medium)

<p>Besu includes comprehensive EVM benchmarking tooling — including JMH microbenchmarks for 40+ EVM operations, precompile benchmarks via&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool benchmark</code>, and full blockchain-level test execution via&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool block-test</code>. However, these benchmarks are currently only run manually by developers on local machines. There is no automated way to track performance over time, detect regressions introduced by PRs, or visualize trends.</p><p><br></p><p>This project aims to build a continuous benchmarking pipeline for the Besu EVM, for example by integrating existing benchmark tooling into CI. The mentee will discuss a solution with Besu maintainers, design and implement automated (and/or manually triggered) workflows that run EVM benchmarks, collect results, store historical data, and produce reports that give maintainers clear visibility into performance changes.</p><p><br></p><p>An excellent reference for the kind of output we'd like to achieve is the&nbsp;<a href="https://benchmarks.ethrex.xyz/gas-benchmark-eest/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">ethrex gas benchmarks dashboard</a>, which provides comparative benchmark reports with sortable tables, speedup metrics, and historical tracking across runs.</p><p><br></p><p>Besu's existing benchmark tooling includes:</p><ul><li>JMH microbenchmarks&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">ethereum/core/src/jmh/</code>) — 40+ benchmarks covering EVM arithmetic, bitwise, shift, stack, memory, and crypto operations (reported in execution time only)</li><li>Precompile benchmarks&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool benchmark</code>) — benchmarks for AltBN128, EcRecover, ModExp, BLS12, P256Verify, SHA256, RIPEMD-160, and KZG Point Eval with throughput metrics (MGps)</li><li>Block-test execution&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">evmtool block-test</code>) — full blockchain reference test execution with timing and pass/fail reporting</li><li>Shell-based benchmark scripts&nbsp;(<code style="background-color: rgba(129, 139, 152, 0.12);">ethereum/evmtool/src/test/benchmarks/</code>) — existing scripts for static operations, loop operations, and mainnet-like contract execution</li></ul><p><br></p><p>The project scope could include:</p><ol><li>CI Workflow Design&nbsp;— Create GitHub Actions workflows (manually triggered in the first instance) that run selected benchmarks on consistent hardware.</li><li>Results Collection and Storage&nbsp;— Design a scheme for storing benchmark results over time (e.g., GitHub Pages, artifact storage, or a lightweight results repo).</li><li>Reporting and Visualization&nbsp;— Find/build a dashboard or report format that shows performance trends, highlights regressions, and allows comparison between runs.</li><li>PR Integration&nbsp;— Optionally, enable benchmark runs on PRs that touch EVM-critical code paths, with summary comments showing performance impact.</li><li>Documentation&nbsp;— Document how to run, extend, and interpret the benchmarks.</li><li>RPC Performance&nbsp;- As a stretch goal could also cover RPC performance, such as eth_call.</li></ol><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/69" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/69</a></p>

TBA
Proposal

Pointer Alignment Checking for WASI Host Functions (2025 Term 3)

Intermediate
•Varies175h (Medium)

WasmEdge implemented a series of WASI host functions to support the official WASI APIs. There are some arguments of WASI APIs are in pointer types. According to the WASI document, the pointer values are expected to be aligned to the alignment of their pointee type, otherwise the the function shall trap. In this mentorship, the mentee should check all functions of WASI interface in WasmEdge, and implement the alignment checking of pointer type arguments. Expected Outcome: 1. Add the alignment checking to the pointee type of WASI host functions in WasmEdge (https://github.com/WasmEdge/WasmEdge/blob/master/include/host/wasi/wasifunc.h), according to the alignment requirement in WASI functions (https://github.com/WebAssembly/WASI/blob/main/legacy/preview1/docs.md#modules). 2. Hand-write some basic WASM tests to prove the correctness of the implementation.

TBA
Proposal

Open Mainframe Project - Give Love to the Bugs List Mentorship Project

Intermediate
•Varies175h (Medium)

Feilong RESTful API makes it easy to manage Linux virtual machines on z/VM mainframes. It is at the center of products like IBM's Cloud Infrastructure Center. Feilong's bug list currently consists of 98 bugs in Launchpad and 19 issues in GitHub. The purpose of the mentorship is to review them, move them to GitHub, classify them, experiment and play, and for the easiest ones, even provide fixes, or close them if no longer relevant. The work does not need to be exhaustive; it is envisioned more as a musing with technical issues and as a discovery of the mainframe world. Deliverables: - An updated and consolidated list of issues. - A few bugs directly fixed, if time and difficulty permits.

TBA
Proposal

LFDT - Hiero Github Workflow App Mentorship Project

Intermediate
•Varies175h (Medium)

<p>The Hiero ecosystem includes a growing number of diverse contributors, repositories, junior committers/committers/maintainers, pull requests, issues, discussions, and quality requirements.</p><p><br></p><p>To build a diverse ecosystem which generates high-quality code, maintainers need to spend a significant amount of time on repetitive coordination tasks such as checking contributor qualifications, validating pull request quality, un-assigning inactive contributors, closing stale issues, creating issues at different difficulties, and ensuring that repository processes are followed consistently.</p><p><br></p><p>We have demonstrated in some SDK repositories many of these maintainer tasks can be automated using custom GitHub action workflows and templates. However, the current setup is fragmented, difficult to customize and scale, and inconsistent across repositories. Different repositories may require different rules, but maintainers still need support to ensure they are working on the most important tasks, and developers need support to help them progress quickly and qualify to gain more responsibilities.</p><p><br></p><p>This mentorship project aims to design and build an automation framework and application for Hiero end-to-end maintainer workflows. The system should support configurable repository automation features that maintainers can turn on or off, depending on the repository context.</p><p><br></p><p>Example user on-boarding workflows:</p><ul><li>Checking contributors are humans</li><li>Checking whether contributors meet contribution requirements before assigning issues</li><li>Offering automatic issue assignment</li><li>Automatically assigning mentors for new contributors</li><li>Issue templates and documentations</li></ul><p>Example pull request review and quality workflows:</p><ul><li>AI issue planning</li><li>AI initial reviewing</li><li>Automated code quality, DCO, GPG, etc checks based on configurable quality requirements</li><li>Automatic review based on configurable quality requirements</li></ul><p>Example developer progression workflows:</p><ul><li>Automatic issue recommendations after a merged pull request to next available issues</li><li>Checking whether advanced contributors meet requirements to progress to JC/committer/maintainer</li></ul><p>Example issue management workflows:</p><ul><li>Managing stale issues or pull requests</li><li>Requesting help or feedback from specified teams based on labels</li></ul><p><br></p><p>A core requirement of the project is to ensure that this automation is reliable, consistent, secure, and scalable enough to be used across a variety of repositories inside Hiero (and one day optionally across LFDT).</p><p><br></p><p>The project should also define clear boundaries for what the automation is allowed to do, how maintainers configure it, and how users can understand or override automated actions when necessary.</p><p>The result should not just be a prototype for a single repository, but a hardened and reusable solution that can serve multiple Hiero repositories with different policies and maintenance needs. </p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/73" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/73</a></p>

TBA
Proposal

Enhance Knative Educational Game & web deployment (2026 Term 1)

Intermediate
•Varies175h (Medium)

Knative provides a powerful event-driven platform, but learning its concepts, especially brokers and EDA patterns, can be challenging for beginners. The Knative Educational Game aims to simplify this learning curve through interactive gameplay that visually and conceptually demonstrates Knative components and event-driven patterns. An overview of the project was presented at the KubeCon NA 2024 (https://www.youtube.com/watch?v=TTBKh6F4v-g), and several technical sketches, gameplay patterns, and level designs were created and implemented during the LFX Mentorship of Spring 2025 (https://github.com/knative-extensions/educational-game/blob/). This project serves as the continuation of that work and is divided into two main parts: 1. The first part focuses on expanding and enhancing the game by implementing existing level designs, introducing advanced EDA patterns (like Outbox and DataRef patterns), designing assets as needed, and improving interactivity. 2. The second part focuses on deploying the game to the web, making it easily accessible for learners to try and share. Expected Outcome: 1. A fully implemented and web-deployed Knative Educational Game by completing previously designed levels, and newly added EDA patterns (DataRef and Outbox). 2. Improved learning experience through interactive animations, sounds, and clear visualizations that make Knative Eventing concepts and real-world patterns easier to understand....

TBA
Proposal

Hyperledger Fabric - Add Interactive Examples to Fabric Python SDK Mentorship Project

Intermediate
•Varies175h (Medium)

This project aims to add interactive examples to fabric-python-sdk using jupyter notebook. The intern is expected to first understand the functionalities of fabric sdk (v0.8.1) and add missing functionalities of fabric 2.0 (e.g. wallet storage, etc.) to fabric sdk based on nodejs/golang sdk. Then, write jupyter notebook examples using fabric sdk and demonstrate functionalities of sdk. It provides new developers with better understanding of using fabric sdk.

TBA
Proposal

RISC-V Vector Coprocessor for ECG Detection on UET-RVMCU Mentorship Project

Intermediate
•Varies175h (Medium)

This project aims to develop and verify a custom RISC-V Vector (RVV) v1.0 compliant coprocessor to accelerate an Electrocardiogram (ECG) detection algorithm. Building on our previous work with a CGRA accelerator, this project addresses its key limitations by leveraging the standardized RISC-V Vector extension, which offers superior toolchain support and predictable data-level parallelism. The mentee will focus on two core pillars: 1. Verification and Integration of RVV Modules: Rigorously test and integrate pre-designed hardware modules to build a functional vector coprocessor. 2. Algorithm Development: Implement and optimize vectorized ECG signal processing kernels using RVV intrinsics.

TBA
Proposal

e2e tests and CLI tests to cover sample policies

Intermediate
•Varies175h (Medium)

Description: Kyverno is a Kubernetes native policy engine that secures and automates Kubernetes configurations. This project will create automated test cases for the samples policies which are missing, and automating execution of tests.The enhancement will involve adding more unit/E2E tests.

TBA
Proposal
Showing 937 - 960 of 1243 Projects
3839404142