Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
When the KCL IDE encounters some errors in the KCL code, it can pop up `Quick Fix` prompts to help users quickly fix the errors. Expected Outcome: Added Quick Fix for some error prompts in KCL IDE.
This is a continuation of our past two LFX mentorship projects -- the Rust Coder. https://www.cncf.io/blog/2025/01/10/rustcoder-ai-assisted-rust-learning/ https://github.com/cardea-mcp/RustCoder Users of Rust Coder, which was originally a chatbot and then an MCP server, have told us that they wanted a modern approach like Claude Code. A new focus would also be to port existing Python / C++ projects to Rust, instead of creating Rust projects from scratch. This new proposed LFX mentorship project will 1 Fork or add to the open-source Claude Code project 2 Create new workflows to ask the user to import Python / C++ projects, make plans for how to port, and ask the user for preferred Rust crates 3 Use MCP to add Rust-specific prompts, knowledge base search tools, web-based documentation import tools etc 4 Use open source coding models to evaluate the results. Expected Outcome: 1. A Claude Code add-on or fork that is specialized optimized for "rewriting in Rust".
Description: In KubeVela, we use CUElang to code the definition. We want to support auto generation of multiple languages SDK from CUE, so that users can use KubeVela in their own language. Expected Outcome: Support auto generation of multiple languages SDK from CUE, including Golang, Java, Python, etc. The capabilities should be wrapped in vela cli command.
The proposed integration of Decentralized Identity (DID) with telecom services aims to provide customers with a secure and convenient way to manage their digital identities, while also offering telecom companies an opportunity to become trusted identity brokers. The integration addresses the challenge of maintaining customer engagement by enabling customers to have a single identity that they can use to access services. The integration also presents a significant opportunity for telecom companies to become identity brokers, leveraging their existing customer base and regulatory relationships. As issuers of verified KYC information, telecom companies can support identity verification by offering APIs to third-party service providers. The integration of DID with telecom services has the potential to revolutionize the telecom industry and offers significant benefits to customers and operators alike.
Description: Kubewarden has many policies to validate and mutate Kubernetes resources. Therefore, there are many enhancements to be made on them. However, these improvements are still to be made. Thus, it's necessary to fix the open issues in the policies repositories and implement new policies to add more value to the Kubewarden users. Expected Outcome: Fix as many open issues in the Kubewarden policies as possible and create new policies requested by the community
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 internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter Azure services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
Kubernetes Pods are the unit of execution. Pods's API surface is limited, but yet presenting many challenges for people authoring complex behaviors like proper graceful termination, probes, or advances initialization behaviors. Documentation and testing of those scenarios is limited. The misunderstanding of pod lifecycle and edge casesoften lead to reliability issues in Pods. Lately there were limited efforts to document and test those behaviors. Creating a skaffolding to document and test those behaviors will help temendously the Kubernetes project as well as end users. Expected Outcome: Skaffolding in https://github.com/kubernetes/website/ to add new pod lifecycle behavios descriptions. Tests for those edge cases. And cross linking between tests and documentation.
Support some enhancements to Policy Exceptions. Expected Outcome: 1. Support list of PolicyException namespaces (--exceptionNamespace flag) 2. PolicyExceptions to have a status object and report readiness in printer column 3. Support imageReferences in Policy Exceptions for verify image rules
A documentation serves best when understood and designed based on user needs. Although Hyperledger Bevel current documentation is comprehensive and robust, it still requires improvement and can be much more effective and useful if designed based on user and community needs. The project scopes to structure the existing documentation of Hyperledger Bevel and redesign it from the perspective of user personas and their deployment needs. It would equally benefit product users and developers, and increase usability and adoption. Learning Objectives - Hyperledger Bevel concepts, features and operations - Documentation techniques and best practices - Hyperledger Bevel community, users and use-cases Expected Outcome - Complete redesigned of documentation based on the decided structure and theme
Kmesh now has an e2e testing framework, but it only covers some of the usage scenarios for key features. More test cases need to be covered to ensure the stability of key features. Expected Outcome: 1. e2e Test Cases 2. Documentation maintenance for e2e testing
Envoy Gateway translates Kubernetes-native Gateway API resources into xDS configuration consumed by Envoy Proxy. It also manages the lifecycle of the Envoy Proxy fleet by generating Kubernetes resources such as Deployments and Services. Currently, upgrades to Envoy Gateway (the control plane) result in immediate, in-place updates to the associated Envoy Proxy fleet (the data plane). While this operation is designed to be zero-downtime, some users prefer a staged upgrade process where the control plane is updated first, followed by a progressive rollout of the data plane. This project aims to design and implement support for progressive data plane upgrades, allowing users to decouple the control and data plane upgrade processes. This would provide enhanced control and safer rollout strategies (e.g., canary or blue-green deployments). Expected Outcome: 1. Design a two-step upgrade workflow that separates control plane and data plane updates. 2. Implement configuration or CRD support to control rollout strategy of the Envoy Proxy fleet. 3. Add documentation and example manifests for users to adopt the new workflow.
Harbor Satellite is a lightweight, OCI-compliant registry (currently based on Zot) designed to run on edge devices, such as Raspberry Pi or ARM-based hardware. It acts as a local container registry for edge devices and workloads. The satellite autonomously fetches configuration and state, registers with Ground Control, reports its status, and optionally sends system-level events to connected edge systems. Expected Outcome: 1. Implement an eventing mechanism to notify edge systems about critical state transitions (e.g., "state update ready", "sync complete"). 2. Improve build and release pipelines. 3. Make the satellite functional on ARM-based edge devices (like Raspberry Pi). 4. Add reliable state and health reporting back to Ground Control. 5. Add e2e tests to validate artifact fetching, status reporting, and eventing.
A common pain-point heard from users is improper resource allocations, and if Kyverno policies can help with that. This is an exploratory project to see if Kyverno can work with Kubernetes Vertical Pod Autoscalers (VPA). Expected Outcome: Kyverno policies that work with VPA recommender.
When a KCL package is loaded using KCL IDE, the IDE automatically updates the dependencies of the current KCL package through kpm. Expected Outcome: Add automatic updates for third-party libraries to the IDE.
WasmEdge supports PyTorch, TensorFlow Lite, llama.cpp, and more NN backend. Dealing with the Voice to Text is a big thing that we want to achieve. To make it possible, we would like to integrate whisper.cpp (https://github.com/ggerganov/whisper.cpp), a port of OpenAI's Whisper model in C/C++ as a new WASI-NN (https://github.com/second-state/wasmedge-wasi-nn) backend. Expected Outcome: A new plugin provides a whisper.cpp WASI-NN (https://github.com/second-state/wasmedge-wasi-nn) backend, a test suite for validating the plugin, documents and examples for explaining how to use the plugin.
This project focuses on building the backend functionality necessary for managing clusters in ITS. It will provide API endpoints to support the frontend’s cluster onboarding and management features. Objectives: - Develop backend APIs for ITS cluster management. - Implement validation and security features for onboarding new clusters. - Ensure high performance and scalability for handling multiple clusters. - Optimize API interactions for faster response times. Expected Outcomes: - A fully functional ITS backend with API support. - Secure and efficient cluster onboarding processes. - Scalable architecture for managing large Kubernetes deployments.
On the Cilium homepage (https://cilium.io), we want to document technical outcomes from using Cilium. Think of these technical outcomes as aggregating some of cilium features to achieve a high level technical goal. These are the current ones we have in mind: Zero Trust Networking, Network Automation, Distributed Firewalling, Cost and Carbon Savings, Multi-cloud Connectivity. Expected Outcome: A section of the Cilium website detailing these technical outcomes. This section on the website can include any supporting materials from the Cilium community i.e blogs, videos, talks, illustrations, etc. Recommended Skills: Technical Writing, some basic working knowlegde of Cilium or the willingness to quickly ramp up, Kubernetes, general familiarity with the cloud native ecosystem, basic React.js(the cilium webiste is built with Gatsby). Upstream Issue: cilium/cilium.io#492
The main content of this topic is to refer to the structure of the test part of common programming languages, such as go and rust, to develop a test framework for KCL's package management tool to help developers better write test cases for the project. The main function of the test framework is to provide a mock environment that supports compiling KCL and interacting with simulated environments such as OCI/Git registry. Expected Outcome: - A mock environment is started during testing. This mock environment can complete the test without being affected by the network. - In this mock environment, complete the test of: `kcl run`, `kcl mod add`, `kcl mod pull`, `kcl mod push`.
The HLF-Connector is a project within the Hyperledger Labs community that provides a way to connect to and interact with Hyperledger Fabric Blockchain Networks from external applications using REST APIs & Kafka based Topics. This connector acts as a gateway between Fabric and non-Fabric applications, allowing external applications to securely read and write data to the Fabric blockchain through both synchronous and asynchronous modes of interaction. HLF-Connector provides a convenient and flexible way to integrate Fabric blockchain networks into external applications, allowing developers to build robust and secure decentralized applications that can interact with the Fabric network. Learning Objectives - Understand Hyperledger Fabric conceptually. - Learn enterprise integrations for practical usage of blockchain technology. - Become proficient in micro-service development. - Design API interfaces and work to scale by handling asynchronous interfaces. - Learn open source processes. - Work closely with community experts. Expected Outcome - Design and implement new features in the connector. - Updating the usage documentation.
The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph. Expected Outcome: - YAML-formatted definition of one or more relationships per Kubernetes resource. - Documentation of each relationship - per component. - Development of new types of genealogies - new types of ways in which resources relate to one another and how these relationships might be visualized. - Verification of functional relationships
The goal of this project will be to build a template or sample Interoperation Identity Network (IIN) by minimally augmenting existing decentralized identity registries built on Hyperledger Indy and Aries, adding support for group Decentralized Identifiers (DIDs), and optionally proposing changes or additions to W3C standards for DIDs and Verifiable Credentials (VCs). To demonstrate the working of identity plane protocols, existing Cacti IIN agents for Hyperledger Fabric must be augmented, and IIN Agents for Corda must be built, enabling data sharing and asset transfer across networks built on either Fabric or Corda. Also, a sample trust anchor must be designed and implemented as a service to issue VCs to network members.
Cacti provides a protocol and trigger mechanism for the sharing of ledger data or data derived from smart contracts (called "view", and identified by a "view address") deployed in a network with another network using relays for communication and consensus-driven proof generation and verification in the end networks. Some parts of the protocol are generic and DLT-agnostic but others, specifically protocol drivers or connectors and core ledger operators (typically built as smart contracts) are DLT-specific. Presently, Cacti provides DLT-specific data sharing mechanisms for Hyperldger Fabric and Corda. The goal of this project is to add similar support, i.e., build modules, plugins, and API for permissioned networks built on Hyperledger Besu. As an optional extension, these mechanisms will then be extrapolated to share data to and from public Ethereum. This will involve designing and basic building blocks or capabilities for view proof generation, proof verification, and access control of remote data requests, in the form of smart contracts. Higher up the stack, the Cacti SDK for Besu must then be augmented to enable network apps to trigger data sharing requests and submitting the responses for validation to local smart contracts.
kpm is a package management tool for KCL. kpm needs to refactor the local storage structure of the current dependencies to support storage of packages with the same name from different OCI registes and caching of the remote dependencies. Expected Outcome: The local storage structure has been designed in issue https://github.com/kcl-lang/kpm/issues/384, and the feature in issue need to be implemented.
Description: Design, plan and implement an and UI and backend to be able to visualize per project and/or for the registry vulnerability overview which will allow better security audits and vulenrability mitigation Expected Outcome: Addition to the Web UI which can be used to represent in full for the whole Harbor instance or per project the vulnerability status of the images, which will allow Harbor admin or project admin to get an overview of the existing vulnerabilities on in the images, also to provide capability to export the data via the CVE exporter so it can be consumed in 3rd party tools(not necessary to be complete functionality) Upstream Issues: https://github.com/goharbor/harbor/issues/16680 https://github.com/goharbor/harbor/issues/10496 https://dso.docker.com/explore?search=pkgs