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.
Improve CI/CD workflow for automated Feilong package builds
<p>Hyperledger Fabric-X is a ground-up re-architecture of Hyperledger Fabric designed for national-scale regulated digital-asset systems, achieving 400 K+ TPS through independently scalable micro-services. For enterprise adoption, existing Fabric deployments must be able to migrate their ledger state to Fabric-X without losing transactional history or state integrity.</p><p><br></p><p>This project defines and implements an end-to-end ledger migration path using Fabric's official peer snapshot mechanism as the source of truth. Two architectural gaps must be bridged: (1) Fabric organizes state by channel, namespace, and collections, whereas Fabric-X uses a only namespaces, and (2) Fabric snapshots contain private-data-collection (PDC) artifacts that have no equivalent in Fabric-X.</p><p><br></p><p>The mentee will design a channel-to-namespace mapping strategy, build an Exporter tool that parses Fabric snapshots and produces a portable genesis-data file, and implement a Bootstrap procedure inside the Fabric-X committer that ingests that file and verifies state integrity post-migration.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/65" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/65</a></p>
ZOWE ZEBRA provides a rich set of zOS performance data. The program will create a performance methodology used by a customer for analyzing RMF MON III data. The methodology will include: - Understanding available RMF MON III data metrics using an IBM provided Data Dictionary. - Translating the RMF MON III data metrics into ZOWE ZEBRA variables which are then ingested into a Prometheus database. - Learning Grafana and how to build time series visualizations in dashboards using Prometheus as a Data Source. - Introduce a performance methodology for analyzing RMF MON III data for bottlenecks and anomalies. This would require learning existing IBM zOS performance methodologies and building the concepts into Grafana dashboards for analytics and correlation. Data analysis will include performance and configuration data. - Using the performance methodology and data visualization provided by Grafana dashboards, design AI/ML algorithms to automatically detect performance bottlenecks and anomalies. Output would include recommended remedies. Mainframe Performance is a difficult and time consuming process. This program would introduce a performance methodology that can be easily customized by a customer and used to provide deep dive zOS performance analytics.
The program aims to leverage agents built using publicly available large language models (LLMs) and personalize them with Retrieval-Augmented Generation (RAG). This approach creates various levels of agentic roles to transform mainframe workloads and modernize them at every phase, from discovery and design to transformation, testing, and deployment. Problems to be addressed in the project: - Unavailability of application documentation. - Lack of comprehensive view of all tasks to be included in the transformation plan. - Multiple iterations of Code conversions. - Technical and resources dependencies. - Unavailability of Application support for the transformation. Deliverables: - Working Agents which will build a program plan at each of the modernization phase for all workstreams. - Agents performing Code transformation with minimal effort from migration team. - Agents performing application analysis with less dependency from application teams.
The RISC-V Certification Steering Committee is developing certification tests to prove that RISC-V processors conform to the ratified specifications. The goal of this mentorship project is to run the tests on as many open-source RISC-V cores as possible, and improve the usability of the tests, debug any issues found in the tests, and report any real bugs that might be found in the cores. This work will involve: * Identifying multiple open-source cores to test * For each core: - Develop a Unified Database (UDB) file specifying the extensions and parameters supported by the core - Implement trick box macros to trigger interrupts, print characters to a console, and terminate a simulation in a core- specific manner - Create a linker script appropriate to the memory map of the core - Compile the tests with the core-specific trick box and linker scripts - Run the relevant tests on the core * Identify and fix any problems in the tests that make them hard to run on a core * Identify and fix any problems with the flow or documentation * Identify and report any bugs found in the cores The work will start with Phase 0 tests of the RVI20 profile with the RV{32/64}IMACDF extensions in machine mode. As time permits, it will continue to the Phase 1 MC100 microcontroller profile with machine mode, traps, Zicsr, and Zicntr, and then to the Phase 2 RVA23 application processor profile with all privilege modes, vector and hypervisor.
With sandboxed packaging, Linux distributions appear which do not use classic RPM or DEB packages any more, like the all-Snap Ubuntu Core. As a result CUPS will not work with classic PPD/filter-based printer drivers any more but requires all drivers being provided as Printer Applications. The student's task is to add this functionality to the Printer Application framework and create an easy way for users to install proprietary printer drivers into that chroot-equipped Printer Application. IPP Fax out is a feature which is currently missing in Linux unlike Print and Scan. The student's task here is to make this functionality easily accessible for users of common desktop Linux distributions. Like printers, faxes should automatically appear on the system and get available in print dialogs and if one prints to a fax, fax-specific options should also appear in the print dialog and the user should be able to pick phone numbers also from contacts.
WasmEdge supports PyTorch, TensorFlow Lite, llama.cpp, and more NN backend. Burn.rs (https://github.com/tracel-ai/burn) is a new deep learning framework built using Rust. The portability, flexibility, and compute efficiency are important to Wasm. That's why we would love to have `burn.rs` as a new WASI-NN (https://github.com/second-state/wasmedge-wasi-nn) backend. Expected Outcome: A new plugin provides a burn.rs 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.
Users can use KubeVela to do application delivery and management. In this project, we hope to integrate KubeVela with developing time. So developers can have a consitent experience between local development and production deploy. There're multiple developing tools such as Tilt or Nocalhost, both of them can integrate with KubeVela by supporting KubeVela Application YAML.
The overall project plan is divided into three phases while the mentee is properly guided by their mentor in each phase. 1. In the first phase, the development of the Fabric chaincodes for the SLA operations and their integration points occurs in the context of an entire decentralized architecture. 2. In the second phase, building on the required interactions with on- and off-chain data is addressed with details as understood and designed on the previous phase. 3. Finally, the holistic approach is developed in the third phase, where permissioned ecosystem is formed end-to-end and its related documentation is produced.
Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. It has inbuilt support for creating IaC artifacts for replatforming to Kubernetes/OpenShift. Currently, in the CLI we can use the -c flag to point to the folder containing customizations and in UI we could upload a zip file containing the customizatoins. It would be better to consume customizations when specified as a git repo path. The use case can also be extended to take source code input taken directory from a remote git repository. Expected Outcome: Move2Kube should be able to consume git repo path as input.
ISAC & CTG are essential components of the RISC-V Architectural Testing(AT) ecosystem. CTG generates tests for AT using the coverpoints as stimulus to ensure that complete coverage can be achieved with minimal testing. ISAC measures the coverage of the tests and reports on the quality of the test suite. This mentorship involves adding multiple features to both these tools to improve the quality of the architectural test suite. For further information on the tasks to be done during your internship refer here - https://gist.github.com/pawks/e2dec6d67224a9f68bf96fc909398c45 As part of the selection process, all candidates are required to successfully complete the coding challenge described here before August 3rd : https://gist.github.com/pawks/98863e5eca71c8b80b18e060cb4d9558
Implementations of Hyperledger technologies span multiple industries, including finance, supply chain, trade, health, media, telecom and more. The beauty of our open source technology community is that anyone can use and build upon it for their specific needs and use cases. There are hundreds of implementations and capturing them in an easy to find and useful manner is a key enabling tool. Helping our community and the public to better understand use cases is a key part of helping advance the impact of distributed ledger technology. It validates ideas others have, provides avenues for reaching out and sharing lessons learned, and is a key part of building the Hyperledger community. In addition, we would also like to track academic papers and courses related to Hyperledger projects in order to develop an understanding of the academic landscape. In gathering and organizing the above information, the mentee will leverage their broad view of Hyperledger use cases as well as understanding of the overall blockchain space to identify potential opportunities for growth in uses or applications of Hyperledger technology. This can include use cases where our community isn’t as present, where we can explore doing further outreach and education. In addition, the mentee will make recommendations and potentially also work on developing ways for the use case and academic information to be leveraged for educational and ecosystem-building content and activities.
Improve the compatbility of Vitess' evaluation engine against MySQL by adding support for more built-in SQL functions. Detailed description: The evaluation engine in Vitess is one of the most critical parts of our query serving infrastructure. This engine is capable of evaluating arbitrary SQL expressions directly inside Vitess' process, without reaching out to a live MySQL instance, and this allows us to plan and execute complex user queries (e.g. queries that contain WHERE and similar filter clauses) between Vitess shards much more efficiently. If you're interested in this GSoC project, your task for the summer will involve continuing the work on this evaluation engine by implementing support for as many built-in SQL functions as possible, using the behavior of MySQL as a reference. Expected outcomes: We expect the Evaluation Engine in Vitess to be close to 100% compatible with MySQL after all the leftover SQL built-ins have been implemented.
Add an ability allowing a user to tell Kyverno to log in JSON format rather than klog.
<p>About the project</p><p>OPI (Open Programmable Infrastructure), a Linux Foundation project, defines vendor-neutral</p><p>standards and tooling for DPUs / IPUs. This internship produces a reference blueprint for</p><p>running VM networking through OVS that is fully hardware-offloaded to a DPU - first under</p><p>vanilla KVM on RHEL, then under OpenShift Virtualization. NVIDIA BlueField-3 (BF3) is the</p><p>reference platform because it ships a complete, mature stack (OVS-DOCA, vDPA, and DPF).</p><p>The blueprint then generalizes to a second DPU / IPU vendor (Intel IPU or Marvell Octeon).</p><p>What you&#39;ll work on</p><p>The work runs as two tracks. Track 1 (BF3) is the proven reference; Track 2 ports it to a second</p><p>vendor and surfaces the gaps that need upstream work.</p><p>Track 1 - BF3 reference</p><p>• KVM on RHEL with OVS fully offloaded to BF3 in DPU mode via OVS-DOCA. KVM / libvirt</p><p>guests attach over vDPA so the guest runs stock virtio-net while the datapath is</p><p>accelerated in hardware. Validate offload is actually in hardware, baseline performance,</p><p>and exercise live migration. This is the reference blueprint.</p><p>• OpenShift Virtualization on BF3 via NVIDIA DPF, with accelerated OVN-Kubernetes</p><p>(OVS-DOCA) offloaded to the DPU and KubeVirt VMs riding the offloaded fabric.</p><p>Track 2 - second vendor (Intel IPU or Marvell Octeon)</p><p>• KVM on RHEL with OVS offload and vDPA using the vendor&#39;s stack (Marvell: in-kernel</p><p>octeon_ep vDPA driver and Octeon SDK; Intel: IPDK / P4 and IDPF). Document the deltas</p><p>from the BF3 reference.</p><p>• OpenShift Virtualization on the second vendor via the OPI / Red Hat DPU Operator.</p><p>Identify and contribute the work needed to reach full primary-datapath OVS offload and</p><p>KubeVirt enablement, since the operator today centers on network-function offload and</p><p>service function chaining rather than the full offloaded OVN datapath that DPF provides on</p><p>BF3.</p><p><br></p><p>Required</p><p>• Linux, Red Hat family (RHEL 9 / 10): systemd, networking stack, kernel modules, and</p><p>hands-on troubleshooting</p><p>• KVM / libvirt / QEMU: VM lifecycle, virtio / vhost, and vDPA (vhost-vdpa) concepts</p><p>• OVS: bridges, flows, OpenFlow, datapath internals, and hardware-offload concepts</p><p>(switchdev / eswitch mode, VF / SF representors)</p><p>• Kubernetes: core concepts, CRDs, operators, and CNI / pod networking - enough to grow</p><p>into OpenShift Virtualization and OVN-Kubernetes</p><p>• Networking fundamentals: L2 / L3, VLAN, VXLAN / Geneve, SR-IOV (PF / VF / SF), and</p><p>throughput / pps testing</p><p><br></p><p>2</p><p><br></p><p>Preferred (a plus)</p><p>• OVS-DOCA and the DOCA SDK / DPF (DOCA Platform Framework) on BlueField</p><p>• vDPA hands-on: mlx5_vdpa, octeon_ep, vhost-vdpa, libvirt vDPA, and vdpa netlink /</p><p>iproute2</p><p>• OVN / OVN-Kubernetes; OpenShift / OpenShift Virtualization (CNV / KubeVirt)</p><p>• OPI DPU Operator, and vendor offload stacks: Intel IPDK / P4 / IDPF, Marvell Octeon</p><p>SDK</p><p>• Go (operator development), Python, and Bash</p><p>• Prior open source contribution (public Git workflow, mailing lists / Slack); familiarity with</p><p>OPI</p><p><br></p><p><br></p>
<p>Data-Flow Integrity (DFI) offers robust protection against memory corruption by ensuring that runtime data flow matches a program's static data-flow graph. However, software DFI suffers from prohibitive overhead. Recent hardware solutions attempt to mitigate this by using decoupled coprocessors (e.g., RvDfi) or alternative architectures, but a tightly coupled approach that extends the ISA directly within the pipeline offers a compelling opportunity to optimize performance and area.</p><p><br></p><p>In a collaboration between the SUSHI research team (Inria Rennes) and the Barcelona Supercomputing Center (BSC), this mentorship implements tightly-coupled DFI in the open-source RISC-V Sargantana core. To ensure a realistic scope, the project is structured in two phases. Phase 1 focuses on hardware: the mentee will collaborate with a student at SUSHI who developed preliminary RTL modifications for the CVA-6 core. This accelerates porting and optimization of these ISA extensions for Sargantana.</p><p><br></p><p>Once the hardware is stable, Phase 2 explores the software stack. To keep the project tractable, the goal is an initial, proof-of-concept toolchain integration. The mentee will leverage adaptations started by SUSHI, using the RVDFI toolchain as a baseline. SUSHI's LLVM experts will provide guidance to help the mentee establish a foundational compiler backend. This phased approach guarantees a solid hardware deliverable while ensuring a full-stack proof-of-concept remains an achievable stretch goal.</p>
The convergence of blockchain and 5G security presents an opportunity to redefine authentication mechanisms within the core network. Traditional OAuth 2.0 authorization mechanisms in 5G rely on centralized components such as the Network Repository Function (NRF) to verify NF identities and issue access tokens. This introduces risks, including single points of failure, insider threats, and identity spoofing. This research explores a decentralized trust model for NF authentication using blockchain-based OAuth 2.0 authorization. The study will analyze the feasibility of leveraging blockchain smart contracts for secure, verifiable access token issuance, ensuring immutable NF identity records and distributed validation. By integrating blockchain with an open-source 5G core, the project aims to enhance security, mitigate attack vectors, and reduce dependency on centralized trust anchors. Expected Outcome and Deliverables - Design and prototype of a blockchain-integrated OAuth 2.0 authorization mechanism for NF authentication. - Implementation and testing of the system using an open-source 5G core solution. - Performance benchmarking against traditional NRF-based authorization models. - Security evaluation covering resilience to identity spoofing, insider attacks, and token misuse. - Documentation and research insights into blockchain-driven 5G security enhancements.
WasmEdge is a lightweight and cross-platform runtime for LLM applications. It allows developers to create LLM apps on a Mac or Windows dev machine, compile them to Wasm, and deploy them on Nvidia machines without any changes to the binary app. It achieves application portability across CPUs and GPUs by supporting a W3C standard API called WASI-NN (https://github.com/second-state/wasmedge-wasi-nn), which abstracts GPU-related AI functions as high-level APIs. At this stage, however, only inference functions are supported. In this project, we aim to support fine-tuning features in WasmEdge. It will improve the developer experience for WasmEdge-enabled LLM tools. To achieve this, we plan to extend the current WASI-NN spec by adding a set of extra APIs, and then implement them by delegating to corresponding functions in llama.cpp embedded in the WasmEdge GGML plugin. Expected Outcome: 1. Use llama2-7b as the base LLM for fine-tuning; the final implementation should handle it correctly. 2. Extend the WASI-NN (https://github.com/second-state/wasmedge-wasi-nn) spec if needed to support the fine-tuning feature. 3. Implement the fine-tuning functions inside WASI-NN ggml plugin. They will call the corresponding functions in llama.cpp, as the inference functions do. 4. Implement the LoRA-related functions inside the WASI-NN ggml plugin to load the pre-trained LoRA and verify the fine-tuned model. 5. Documentation, examples, tutorials, and demonstration are required.
The Knative community is developing an educational game to teach concepts about event driven architectures and how to build them with Knative. A good overview of the project was presented at KubeCon NA 2024 (https://youtu.be/TTBKh6F4v-g?si=MRmx6a2YJsl7y0Q-). We are currently looking to tale our initial prototype and turn it into a full game. In this project, you will help achieve this by creating both visual and audio assets, giving the game a polished look. - Expected Outcome: Identify which assets should be created, create audio assets, create visual assets, add assets Godot.
Pstore is a subsystem in the Linux kernel that is used to store kernel logs which can retrieved after a machine warm-reboots. Currently, during ftrace tracing, ftrace events in the kernel are lost when a machine hard-locks up. There is a need for writing these events into the pstore so that after a lock up, the trace events that led to the crash can be retrieved from the Pstore after a warm reboot. This has to be done in a scalable way so that tracing a live system does not impact performance of the system – ftrace is extremely fast. Initial patches posted to write and retrieve events to/from pstore are not scalable due to locking and other issues. Introducing a scalable approach will open up more possibilities for crash analysis. Prototype work for reference: https://linaroconnectsandiego.sched.com/event/Sue7/event-tracing-and-pstore-with-a-pinch-of-dynamic-debug
WasmEdge is a WebAssembly runtime that supports both interpreter and ahead-of-time modes. For proxy-wasm support, WasmEdge only provides the interpreter mode currently. Such as the other runtimes, WasmEdge should be able to support the AOT mode for better performance. In this mentorship, the mentees will help the WasmEdge project to complete the AOT mode in proxy-wasm proposal and write the docs for examples of running with proxy-wasm. - Expected Outcome: - Modify the Bazel file to include the LLVM dependency. - Modify the code to support running WASM in AOT mode. - Add the documentation of proxy-wasm in the WasmEdge docs repo.
OpenEBS Local PV hostpath is the most simple to use Local PV option available for Kubernetes today. Many of the applications use XFS filesystem to create Local PVs. This project is to implement XFS project quota on the OpenEBS Local PV subdirectory to restrict pods from exceeding the Quota assigned to them via the PVC request.
A summarization of various resources and building a documentation playbook detailing the specifics and resources needed for running Open Programs offices within a University.
Currently a Workload Description Space (WDS) has Binding objects that refer to inventory objects in exactly one Inventory and Transport Space (ITS). This mentorship project would generalize that, allowing references to inventory objects in multiple ITSes. Bear in mind scalability concerns. Expected Outcome: generalized API and implementation as described.