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.
The Volcano community introduced JobFlow to address inter-job dependencies. Through the concepts of JobTemplate and JobFlow, users can declare and orchestrate multiple Volcano jobs, leveraging control flow primitives such as sequential, parallel, conditional, branching, and looping execution. JobFlow aims to facilitate the migration of AI, BigData, and HPC workloads to the cloud-native environment. The current JobFlow functionality requires further enhancements to meet more complex real-world scenarios. Ref: https://github.com/volcano-sh/volcano/tree/master/docs/design/jobflow. Expected Outcome: 1. Support modifying parameters of a JobTemplate when referenced in a JobFlow, for example, changing container image versions, adjusting resource limits, etc. 2. Implement a configurable retry mechanism for failed jobs within a JobFlow, for example, supporting exponential backoff retry policies, setting maximum retry attempts, etc. 3. Introduce richer control flow statements such as if, switch, and for statements, for example, conditional branching based on the status of upstream tasks, iterative execution of specific task sets, etc.
Integrate Kubernetes Pod Security with Kyverno for finer grained controls.
Description: Connectors are tremors interface to the outside world, they allow us to integrate with third-party systems. Currently, tremor only has a limited set of connectors for databases, we support s3 and google cloud storage for object stores, and have a k/v connector that offers a simple integrated key-value store. While this is a good starting point interfacing with more databases will make tremor easier to use for our end users. The primary target will be integrating with Yandex Clickhouse.
Kyverno is a Kubernetes native policy manager that also can be used in a CI/CD pipeline. This project will extend the Kyverno command line tool to support mutate and generate rules and add more E2E/Unit Tests and offer test reports based on the results.
This project aims to design and build a suite of automated scale tests for kgateway that would run as part of our builds and releases process. These tests will help us understand how kgateway behaves under a large number of Kubernetes gateway resources and kgateway extensions, and load tests to ensure it performs reliably as usage scales. You'll gain hands-on experience with performance testing, infrastructure automation, and Kubernetes-based systems. Expected Outcome: 1. Design and a scale testing suite 2. Build a scale test suite for kgateway 3. Analyze test results to identify bottlenecks or failure points 4. Write developer-facing documentation 5. Explore Oracle Developer cloud and determine if it is suitable for kgateway’s scale tests.
The Hyperledger Foundation is looking for a Developer Marketing mentee to support marketing efforts tied to our developer ecosystem. This mentee will work alongside the Hyperledger Foundation Marketing Manager in support of social media marketing, developer events and Hyperledger Global Forum our annual global conference in September and conduct research on which marketing activities can be leveraged to grow developer engagement. Responsibilities will include conducting market analysis, monitoring social platforms, and preparing promotional materials - Collaborate with the team to perform market analysis and research on the latest trends around developer engagement and marketing - Contribute to the content calendar with social media postings on a weekly basis - Monitor analytics with the rest of the team to identify viable ideas, trends, and growth patterns
With WASI-NN plugins, WasmEdge is well-suited for running AI applications. However, AI applications are more than just the model. The application must pre-process data (such as images, audio and video) into TFLite / PyTorch formats, and convert the inference results back into application data in post-processing. Here are some examples: * The [mediapipe-rs](https://github.com/WasmEdge/mediapipe-rs) project provides a Rust SDK to build applications for the mediapipe AI models. * The [llama2.c](https://github.com/karpathy/llama2.c) application is [compiled to Wasm and runs in WasmEdge](https://medium.com/@michaelyuan_88928/running-llama2-c-in-wasmedge-15291795c470) to generate text using the [llama2](https://ai.meta.com/llama/) models. In this project, we would like to build a Rust SDK to support applications on the [YOLO models](https://pjreddie.com/darknet/yolo/). - Expected Outcome: - A Rust SDK that implements the pre-processing and post-processing functions required for the YOLO models. Those functions are implemented in OpenCV and Python in the official YOLO release. - Both image and video inputs should be supported. - Examples and documentation should be provided. - Recommended Skills: - OpenCV - Rust - Tensorflow / Pytorch - WebAssembly
Implement a basic coprocessor plugin runtime on top of Wasmer.
<p>Lima launches Linux virtual machines with automatic file sharing and port forwarding (similar to WSL2). Currently, Lima supports Linux, macOS, and FreeBSD as guest operating systems. The primary goal of this project is to expand this capability by adding support for Windows guests. Furthermore, the project aims to improve the stability and user experience of running Lima on Windows hosts. This will be achieved by removing dependencies like `cygpath.exe`, researching and developing a native Hyper-V(or a [HCS](<a href="https://learn.microsoft.com/en-us/virtualization/api/hcs/overview" rel="noopener noreferrer" target="_blank">https://learn.microsoft.com/en-us/virtualization/api/hcs/overview</a>) driver to provide optimized, native virtualization on Windows hosts.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Primary:</li><li class="ql-indent-1">The ability to successfully launch and run Windows guest virtual machines using `limactl start template:windows` using the QEMU driver on any host.</li><li class="ql-indent-1">Deliver a seamless installation experience on Windows hosts by automating configurations and eliminating the need for [manual setup notes](<a href="https://github.com/microsoft/winget-pkgs/pull/356038/changes#diff-9c16ba1b4e8cfc88d634b6cc436e0041d2201ac93e1d4fcd78fca09e0667ca3aR29" rel="noopener noreferrer" target="_blank">https://github.com/microsoft/winget-pkgs/pull/356038/changes#diff-9c16ba1b4e8cfc88d634b6cc436e0041d2201ac93e1d4fcd78fca09e0667ca3aR29</a>)</li><li class="ql-indent-1">Complete removal of the `cygpath.exe` dependency.</li><li> Secondary (if time permits):</li><li class="ql-indent-1">Investigate and decide between Hyper-V and HCS for the native driver: HCS is the basis of WSL2 and may be available in Windows 11 Home Edition, while Hyper-V is only available in Pro/Enterprise editions. Research availability and integration feasibility.</li><li class="ql-indent-1">Potentially integrate the chosen driver (Hyper-V or HCS) as an [external VM driver](<a href="https://lima-vm.io/docs/dev/drivers/" rel="noopener noreferrer" target="_blank">https://lima-vm.io/docs/dev/drivers/</a>).</li><li>Tertiary Goals (if time permits): Upgrade the existing WSL2 driver to drop image restrictions and allow users to run multiple instances, as well as exploring a simple graphical interface (`limagui.exe`) to launch virtual machines.</li></ul><p><br></p>
Umbra has been developed in the past 2 years thanks to successful internship projects, its final target is the development of a platform for emulating blockchain projects and conducting academic research. This year the goal of the internship project is to unleash the full potential of Umbra, therefore running large scale tests added to chaos engineering mechanisms. The intern is going to work on mechanism that enable chaos engineering in Umbra, execute large scale tests in cloud providers (thousands of nodes), and present measurement reports of blockchain and infrastructure metrics. The goal is to enhance Umbra to a stable release, prove its full potential, and produce material to be reproducible by different academic institutions teach and perform research with the developed Umbra experiments. Expected Outcome Enhance Umbra source code, enable a stable experimentation environment for Umbra in cloud environments with large topologies (e.g., thousands of nodes), generate chaos engineering mechanisms in Umbra, capture the events in dashboards, and generate comprehensive reports detailing an Umbra experiment.
Harbor is a widely adopted container registry, and its initial CLI has been developed by LFX mentees. The goal is to extend this CLI by implementing additional functionalities and workflows that are currently only available in the Web UI. The CLI should be useful for Harbor administrators and users, especially to manage workflows within CI/CD pipelines. We seek a Golang-experienced mentee to enhance the CLI independently. Expected Outcome: 1. Extend the Harbor CLI to include essential commands not yet implemented. 2. Add new features to improve Harbor management via the CLI for Harbor Administration, enabling robust workflows in CI/CD environments. 3. Review and test all implemented commands to ensure they work as expected.
With the introduction of Fabric v2.x, a more decentralized way of chaincode management is implemented. There are several improvements over the previous lifecycle and it requires several changes on the sdk. This project aims to support decentralized governance for smart contracts in fabric python sdk and add features such as private data sharing/verifying and external chaincode launcher. The projects will provide a user-friendly and easy-to-use tool for fabric developers and operators. Learning Objectives 1) Contributing and collaborating in an open-source project 2) Advanced understanding for DLT(distributed ledger technology) 3) Understand the basic workflow of fabric 4) Being able to implement features for SDK 5) Writing good documentations Expected Outcome 1) update on the chaincode lifecycle management --Multiple organizations must agree to the parameters of a chaincode --Deliberate chaincode upgrade process --Simpler endorsement policy and private data collection updates --Inspectable chaincode packages --Start multiple chaincodes on a channel using one package --Chaincode packages do not need to be identical across channel members 2) add private data sharing & verifying features 3) (optional) add features for writing smart contracts in python
Prometheus remote write allows users to send their metrics to other time series databases. Though the Prombench tool has existed for a number of years, it has never been extended to support performance testing of Remote Write in a realistic production like environment. With the upcomming Remote Write 2.0 changes to both the underlying implementation as well as the wire format, the need for benchmarking of remote write beyond static Go bechmark tests has increased. Expected Outcome: Build additional (or extends existing) tooling, similar to Prombench’s load-generator and avalanche, to support scenarios under which remote write should be performance tested. For example; allowing gradual increases/decreases in # of active series, sudden spikes in active series, various amounts of latency in the server receiving the remote write data, etc. Time permitted, extend Prombench's test suite to include a set of Remote Write tests that can be run via a new command.
The emergence of blockchain interoperability is reducing the risk of investing in blockchain by avoiding vendor lock-in, leveraging interoperation with off-chain systems, and providing a truly open ecosystem, enabling a network of blockchains. In particular, in the technical report we wrote, we designed a survey aimed to understand the socio-technical challenges that blockchain interoperability poses, with the goal of offering a unique opportunity to link the underlying technology with human experience and values. We discovered that end-users are particularly concerned with visualizing and analyzing cross-chain cost and throughput, with some indication that measuring energetic expenditure in the cross-chain setting would also be valuable. Following that survey, we implemented a simple PoC that obtains transaction receipts from different blockchains and aggregates them in a unified repository. This project aims to build on top of what was done and create a cross-chain model (taking into account what end-users what to analyze from such model) automatically from input cross-chain transactions. This project will take a cross-chain use case, create a model and allow end-users to extract relevant metrics, promoting a better understatement of the business logic running on blockchain infrastructures, and of interoperability.
We need to develop integration and verification of third-party CNI/CSI for the edge applications.
WasmEdge is a cross-platform and lightweight runtime for AI models. It can run a variety of GenAI models, such as LLM (https://llamaedge.com/docs/user-guide/llm/get-started-with-llamaedge/), whisper (voice to text)(https://llamaedge.com/docs/user-guide/speech-to-text/quick-start-whisper/) , and GPT-SoVITS (text to voice) (https://llamaedge.com/docs/user-guide/text-to-speech/gpt-sovits/) on your own computers. By combining those 3 models together, developers in the WasmEdge community has created “video translation” applications that can translate video and audio content into another language. One such application is VideoLangua.com In this mentorship, we would like to build a Japanese translator agent that are specifically tailored to CNCF technical content. Expected Outcome: 1. Use whisper to extract a time-stamped English transcript from a sample of CNCF videos. Develop whisper prompt that are suitable for CNCF technical content. 2. Evaluate and select LLMs that are good at English to Japanese translation. 3. Develop LLM prompts that are suitable for CNCF technical content. 4. Train Japanese TTS actor models for GPT-SoVITS using PyTorch. 5. Create dictionaries for how to pronounce CNCF technical words in Japanese. 6. Evaluate the synthesized Japanese voice.
The project looks at how to facilitate the process of Telecom roaming agreements drafting and negotiation. The project looks at first constructing a library of drafting articles with a set of variables that will be extracted from the available templates and previous roaming agreements using Natural Language Processing process NLP. The second part will be towards translating the drafting and negotiation process as a chaincode on Blockchain to digitalize the process and provide a maintainable and actionable copy of the agreement. The project focus on how to be able to digitalize the legal process and make it automated through smart contracts to be more efficient and less error prone. The expected outcome of this project, would include: 1. Building a drafting library and an NPL model that will include a digital version of the most relevant and important articles in a the GSMA AA.12, AA.13 and AA-14 roaming agreement templates. 2. Developing a chaincode that will map all steps of the drafting and negotiation business processes for roaming agreements. 3. Building a PoC for UI to handle the agreement construction 4. Writing a solution document summarizing the implementation details
Description: [LitmusChaos](https://litmuschaos.io) is an open-source Chaos Engineering platform that enables teams to identify weaknesses & potential outages in infrastructures by inducing chaos tests in a controlled way. This project aims to improve the code quality of the golang components of litmus chaos and refactor the codebase for adding the unit test cases. Expected Outcome: This will help the project to improve code quality, enhance the unit test suite, and identification of weaknesses
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Gateway API resources are used to dynamically provision and configure the managed Envoy Proxies. Currently the implementation only supports Kubernetes clusters with IPv4 enabled, and not IPv6 Expected Outcome: The managed Envoy Proxy fleet can - Accept connections/listen on an interface that has an IPv6 address assigned to it - Can route to IPv6 pod endpoints/addresses
Enhancing observability across key components, including chaos-runner, chaos-operator, and litmus-go. By adding distributed tracing(span, span attributes, and error tracking) and exporting logs to the Open Telemetry Collector. - Expected Outcome: - Enhanced observability with OpenTelemetry in key LitmusChaos components - Detailed span instrumentation for improved tracing and error tracking - Logs seamlessly exported to OpenTelemetry Collector
"The evolution of KVM (Kernel-based Virtual Machine) unit tests from a virtualization testing framework to one that also encompasses bare metal testing allows us to build a comprehensive unit test framework for Supervisor Binary Interface(SBI) in RISC-V. The need for a standalone, comprehensive unit test framework for SBI has become increasingly evident. Validation of the SBI specification has traditionally been intertwined with feature implementations across OpenSBI, KVM, and the Linux kernel. By establishing a dedicated unit test framework, we aim to streamline the identification and rectification of bugs early in the development cycle, thereby ensuring a robust and reliable specification for RISC-V's growing ecosystem. The RISC-V support along with a few SBI extensions got merged[1] recently, which enabled basic SBI extensions and SMP/EFI support in kvm-unit-tests for RISC-V. Expanding the coverage of both existing and forthcoming SBI extensions is critical to accelerating the development and adoption of the SBI specification. Besides generally improving kvm-unit-tests, tests for the following SBI extensions may be added: SBI PMU support Bare Metal testing using OpenSBI firmware Virtualization testing with KVM SBI Steal time extension support Virtualization testing with KVM SBI Debug Trigger extension Bare Metal testing using OpenSBI firmware Virtualization testing with KVM Any other extensions (SUSP, MPXY ?) CoVE related tests (time permitting)
The Litmus Helm Agent, one of the microservice in Litmus, requires modernization for compatibility with Litmus 3.x API changes. Simultaneously, migrating Litmus Chaos container images to Red Hat's Universal Base Image (UBI) enhances security and compatibility. This project aims to revitalize the Helm Agent and streamline image management, ensuring seamless integration and robust deployment in containerized environments. Expected Outcome: 1. Seamless Integration: The Litmus Helm Agent will seamlessly support Litmus 3.x API changes, ensuring compatibility and uninterrupted functionality within the ecosystem. 2. Enhanced Security: Migrating Litmus Chaos container images to Red Hat's Universal Base Image (UBI) will bolster security and compatibility, optimizing deployment in diverse containerized environments.
In order to pass sandbox-specific configuration, such as the guest type, monitor type, rootfs information and others, `urunc` relies on a set of [custom OCI annotations](https://urunc.io/package/#annotations). However, these annotations are missing from the container's configuration in non-Kubernetes-deployments. To work around this issue, a `urunc.json` file containing the same information is currently injected into the container’s root filesystem. This works aims to investigate the OCI image build and runtime flow to understand where and why these custom annotations are dropped or ignored in non-Kubernetes setups. - Expected Outcome: - A clear summary of the investigation, including where and why the custom annotations are lost. - A proposed solution enabling `urunc` to correctly consume its custom OCI annotations. - Alternatively, the design and implementation of a cleaner mechanism than injecting a file into the container’s root filesystem.
Weaver, a Hyperledger labs project, is a DLT interoperation framework that supports data sharing, asset exchange and asset transfer between blockchain networks built on independent DLTs while preserving core blockchain tenets of decentralization of the participating blockchains and without relying on trusted mediating individuals or networks. True interoperability of tokens among different networks, whether they are built on permissoned or open blockchain technology, requires standards around tokens so that they can be exchanged or transferred across network boundaries independent of the underlying DLT implementation. The Enterprise Ethereum Alliance (EEA) has made significant strides in this direction by drafting ERC (Ethereum Request for Comments) standards for managing different types of assets. The widely used ERC-20 standard helps manage fungible token types, whereas ERC-721 and ERC-1155 standards help manage non-fungible token (NFT) types and multi-token types respectively. The scope of the project covers interoperation support for these three prominent ERC token types across Hyperledger Fabric, Corda and Hyperledger Besu networks. Weaver currently supports interoperation between ERC-20 token types for Hyperledger Besu networks. The goal of this project is to add support for ERC-721 and ERC-1155 standards for interoperation among Hyperledger Besu networks, and extend support for ERC-20, ERC-721 and ERC-1155 token types to interoperate across all three DLT platforms.