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.
Problem: Embedded Linux systems, particularly for In-Vehicle Infotainment (IVI), lack a user-friendly, secure application store that matches the seamless experience of mobile platforms. Existing solutions often fall short in providing curated app access, robust security, and support for diverse app types, limiting their adoption in production-ready environments. Solution: The Flatpak App Store addresses this by delivering a modern application store for embedded Linux. Built with Flutter for an intuitive UI, it leverages Flatpak for secure, sandboxed app distribution and integrates advanced features like MutualTLS, DRM playback, and Android app support via crosvm. A 22-week implementation plan ensures a scalable, production-ready solution, with cloud APIs for app management and user reviews, tailored to IVI use cases. Deliverables: A fully functional Flatpak App Store application with browsing, installation, and review capabilities. Secure architecture featuring MutualTLS, sandboxing, and secret storage. Support for Flutter, Native Linux, and Android apps, with DRM playback integration. Packaged Flatpak app and repository setup for deployment. Comprehensive documentation and test suite for IVI production readiness. This project will empower embedded Linux users with a reliable, mobile-like app store experience, enhancing IVI system functionality and security.
As a Kubernetes (K8s) network plugin (CNI plugin), Antrea provides networking functions for K8s Pods and includes various troubleshooting tools for cluster administrators and application developers to diagnose networking issues. The PacketCapture feature (https://github.com/antrea-io/antrea/blob/main/docs/packetcapture-guide.md) was introduced recently (Antrea v2.2) and allows capturing network traffic for specific endpoints using predefined filters similar to those supported by libpcap/tcpdump. Users can initiate a packet capture through a Kubernetes Custom Resource Definition (CRD) or a CLI command. The Antrea control plane then generates and injects the corresponding BPF program, and the captured packets can be exported as a pcap file. In the last iteration of the LFX mentorship program, we added support for L4 filters (TCP flags, ICMP type & code) to the PacketCapture API, to enable Antrea users to target network traffic more precisely. We would like to keep improving the PacketCapture feature with 1) IPv6 support, 2) more flexibility when providing the source and destination, 3) the ability to specify the capture point for traffic (source or destination Pod). Expected Outcome: Extend the API definition for the PacketCapture CRD, and implement the new API functionality by generating the correct BPF instructions. The antctl CLI command for PacketCapture should be updated as needed to accomodate for the API changes.
The current GGUF reader in OpenVINO GenAI manually reconstructs model architectures by parsing metadata and building the OpenVINO model layer by layer — requiring explicit C++ implementations for every supported model topology. This project implements GGUFReaderV2, a new GGUF reader that uses dynamic graph translation instead. It leverages llama.cpp APIs to produce a GGML computation graph (ggml_cgraph), passes it through the existing GgmlOvDecoder and ov::frontend::ggml::FrontEnd infrastructure to produce an ov::Model, and integrates the result into OpenVINO GenAI's read_model() pipeline. A working prototype has already been validated with TinyLlama.gguf — successfully capturing 5,141 OpenVINO operations and executing them through the translation pipeline. Key architectural challenges around tensor naming, capture state safety, and test design have been identified and documented. Deliverables: 1. Functional GGUFReaderV2 class with correct RAII resource management and passing math equivalence tests 2. Stable GGML to OpenVINO graph translation with collision-free node mapping 3. Full integration into GenAI's read_model() API with dynamic shape support 4. Regression test suite validating accuracy across quantization formats (Q4_K, Q6_K, Q8_0) and architectures (TinyLlama, Phi-3, Llama-3, Qwen2.5) 5. Comprehensive documentation and developer guide for extending GGML operator support
Problem: While Large Language Models (LLMs) like ChatGPT can generate R code, they often lack precision when answering questions about third-party R packages or contributing to the R language itself. This can limit their usefulness for R users, particularly for new contributors seeking to understand the R core or engage in package development. Furthermore, many of these AI tools are proprietary or resource-intensive, excluding users with limited hardware or funding. Solution: ChatR proposes a specialized R chatbot that is lightweight, locally runnable (even without a GPU), and customized to provide reliable support on R packages, documentation, and contribution practices. The project will use Retrieval-Augmented Generation (RAG), prompt engineering, and a lightweight open-source LLM (via Ollama and llama3.2:3b-instruct) to deliver targeted responses. It will be delivered as an R package with both CLI and Shiny UI interfaces. Deliverables: An R package wrapping the chatbot and customizable prompts Local model integration using Ollama and ellmer RAG-based indexing of documentation (e.g., CRAN, Writing R Extensions) A Shiny widget interface for interactive usage in RStudio Documentation, test suite, and demo applications This project will significantly support learners, developers, and contributors by democratizing access to reliable AI-based R support and onboarding tools.
Option 1: General Junior DevRel Mentorship This mentorship is designed for a junior Developer Relations or community-focused contributor who wants hands-on experience supporting a fast-growing open source project in the cloud native ecosystem. The mentee will work closely with the Kyverno maintainers and community to improve the overall developer and end-user experience through better documentation, tutorials, example content, and community-facing resources. The mentee will contribute upstream to Kyverno by helping create clear getting-started guides, improving existing documentation, supporting educational content such as blogs or walkthroughs, and assisting with community enablement initiatives. The mentorship focuses on foundational DevRel skills including technical communication, open source contribution workflows, user empathy, and translating complex technical concepts into approachable learning materials, while building a visible portfolio of real-world open source contributions. Option 2: Concise Version of the CEL-Focused Mentorship (1–2 Paragraphs) This mentorship offers a junior DevRel contributor the opportunity to work directly with the Kyverno community to support the adoption of Kyverno’s new CEL-based policy capabilities. The mentee will help create and refine documentation, tutorials, and example content that make it easier for new users to get started with CEL policies and for existing users to migrate from traditional policy types to CEL policie
This proposal aims at developing AI-generated choreography for duets. It outlines a novel approach leveraging both Transformer and Graph Neural Networks to analyze and generate dance movements, focusing on creating authentic dance material that reflect the intricate dynamics between dancers. The project will use Transformer and/or GNN to process motion capture data. The comprehensive solution plan involves: · Understanding key relationships between parts of the body of each dancer through a dedicated Spatial/Temporal Joint Relation Module · Utilizing self-attention and cross-attention mechanisms to learn spatial-temporal relationships of dancers' movements · Enhancing the overall coherence of the generated choreography by implementing regression loss and style similarity loss · Create a dataset of point-cloud data corresponding to extracted motion capture poses from videos of dance duets · Utilize Transformer and/or GNN models with encoder-decoder structure and various attention mechanisms to generate the movements of Dancer #2 conditioned on the inputs of Dancer #1 and/or invent new, physically-plausible duet phrases · Implement a Spatial/Temporal Joint Relation Module to learn key relationships between parts of the body of each dancer that are integral to the dynamics of the duet · If time permits: incorporate Music Embedding Module to enrich the model with multi-modal inputs · Collaborate with the original dancers to use the model outputs to inspire new performance material
<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS LOCATED IN CHINA*</strong></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Problem Statement</strong></p><p><br></p><p><span style="color: rgb(0, 0, 0); background-color: transparent;">IS-IS (Intermediate System to Intermediate System) is a link-state routing protocol used as an Interior Gateway Protocol (IGP) in TCP/IP networks. It is widely used in large enterprise networks, ISP backbone networks, and data center networks. It calculates the shortest path using the SPF algorithm, supports a hierarchical structure (Level-1/Level-2), and is known for its high scalability, reliability, and fast convergence.</span></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Mentorship Objectives</strong></p><p><br></p><p><span style="color: rgb(0, 0, 0); background-color: transparent;">ISIS, as a widely used IGP protocol, is already supported in FRR, the routing suite used by Sonic. However, Sonic does not yet support directly enabling and using ISIS protocol functionalities. We need to build the initialization, startup, configuration deployment of isisd in Sonic, and implement the ISIS functionality CLI in Sonic. </span></p>
“Implementing a Code Action in Visual Studio Code to show the expansion of a Swift Macro in a peeked editor”. Swift Macros allow the generation of source code at compile time. While this provides concise code and avoids repetition of common paradigms, understanding the source code can become harder if it is unknown what the macro expands to. Visual Studio Code using the Swift Extension currently has limited ability to show the code generated by a macro by invoking a code action that replaces the macro by its generated code inside the current source file. The project’s goal is to implement a code action to show the macro-generated code without modifying the current source file. This includes the implementation of a request in sourcekit-lsp to compute the contents of the macro expansion and support in the Visual Studio Swift Extension to display that content. As a stretch goal, Visual Studio Code should also offer semantic functionality like jump-to-definition inside the macro expansion and allow the expansion of nested macros. *Deliverables*: 1. An Expand Macro Code Action in VS Code that shows the generated contents of a swift macro in a peeked editor 2. Support for Semantic Functionality such as jump-to-defintion, hover, syntax highlighting in the peeked editor 3. Allow expanding macros generated from macro in the peeked editor i.e. Nested Macro Expansion 4. Add a standard request support for other LSP-based editors giving them ability to expand macros upto the first level.
When I first tried exploring open-source organizations on GitHub, I kept running into the same problem. GitHub shows great details for each repository, but almost nothing that helps you understand an organization as a whole. I had to open repo after repo just to figure out which projects were active, which languages were common, and who was actually contributing. It felt slow, manual, and frustrating. That experience led me to build OrgExplorer. OrgExplorer is a fully client-side web app that turns raw data from the GitHub REST API into clear, organization-level insights. There’s no backend, no login, and no setup. You simply enter one or more organization names and, within seconds, you can see language distribution, repository health, contributor coverage, governance risks, and activity trends. Everything is cached locally so the app feels fast and doesn’t waste API requests. Behind the scenes, OrgExplorer merges repositories and contributors from multiple organizations into a single data model. From that, it highlights practical signals like bus factor risk, cross-repo contributor coverage, dead issues, zombie pull requests, and how activity changes over time. By the end of GSoC, OrgExplorer will support multi-organization analysis, an interactive contributor–repository network graph, repository health classification, governance audits, activity trend charts, exportable reports, deep-linked views, and offline support as a Progressive Web App. Smart caching ensures it stays within GitHub’s rate limits, with optional token support for larger explorations.
PROBLEM: Flatpaks and Snap applications run in isolation from rest of the system, therefore they do not have access to the system resources (such as directories, buses and devices) that other applications take for granted. They access these permissions through Portals (in Flatpak's case) and Interfaces (in Snap's case). Discover is KDE's application for installing software. Presently, Discover can show what permissions are necessary by Snaps and Flatpaks, but lacks a mechanism to change Flatpak's permissions. Flatpaks can access buses, but it is unclear what these buses do, to users. Snaps do offer a mechanism for changing these permissions within Discover's interface (through a popup), but this has 2 problems: first, the permissions will not be understandable to most users; second, the method of displaying these permissions is inconsistent with how it is done for Flatpaks. The project's goal is to implement a mechanism to alter these permissions and their extents in a system settings module for each application, and show Snap permissions in a more informative, easier-to-digest way on Discover's interface, like for Flatpaks. PLAN TO IMPLEMENT: The project is broken into 2 stages: the first is implementation of the feature that allows tweaking of Flatpak's application. This should be done by the end of Week 7. The second is the feature to display Snaps permissions more informatively on Discover's interface, like it is done for Flatpaks. This stage will take up the remainder of the weeks. DELIVERABLES: 1. mechanism to alter Flatpak permissions through a System Settings module for each application 2. mechanism to alter Snaps' permissions through a System Settings module, for each application 3. displaying Snap permissions with additional information such as brief descriptions and icons in their application pages 4. implementation of an "internal dictionary" to explain what access level to each bus on the system implies to the user
Utilizing cloud FPGAs prove to be very expensive and minor coding bugs could consume precious compute cycles and incur hefty bills. This proves using FPGAs on AWS F1, virtually ineffective for students, enthusiasts and early researchers. Additionally, 1st CLaaS, already has a streaming interface in place, not all hardware accelerators would require continuous streaming of data. The addition of support for Memory Mapped Interfaces like AXI4, AXI4 Lite, Wishbone and custom interfaces similar to RoCC, Core-V eXtension interface etc., would enable a wider ecosystem of hardware accelerators to support 1st CLaaS integration without any RTL Level modifications. Besides these, supporting 1st CLaaS on Local FPGAs/Remote FPGAs contrary to AWS F1 would prove useful to enthusiasts, researchers, professors and students having FPGA on-premise or remotely accessible. 1st CLaaS for PYNQ leverages the PYNQ (Python Productivity for Zynq) Framework, which consists of a Jupyter Server running in a Linux Operating system on the ARM Processor in the Zynq SoC. Addressing the current limitations of 1st CLaaS, the proposed framework that not only brings 1st CLaaS to PYNQ FPGAs, but also vendor agnostically automates TL-Verilog/Verilog/SystemVerilog based Hardware accelerator design from RTL to bitstream and deployment eliminating the need to interact with a wide range of vendor specific tools. The framework would provide a complete FPGA based hardware design flow within the browser/terminal right from designing in makerchip-app and IP-Block design-Bitstream generation to deployment on FPGA in a single command.
KerasNLP is a library for building NLP building blocks such as model layers, metrics, tokenizers, text processing/augmentation techniques, etc. I have contributed a few of these modules myself, and would like to contribute more such modules during GSoC. Firstly, I would like to contribute NLP-specific metrics. Here, I plan to implement metrics which are not present in Keras, and which are generally used for NLP tasks. Most of these metrics will be implemented as live training metrics, i.e., they can be input to `model.compile` and computed during training. Hence, the implementation should be "in graph mode". The metrics I wish to implement are: BLEU Score, Word Error Rate [WER], Character Error Rate [CER], CHRF, CHRF++ and BLEURT. Secondly, I wish to add functions for decoding strategies. Text Generation is an important problem in NLP. It encompasses tasks like summarisation, machine translation, story generation, etc. During inference, we need to sequentially decode the output of the encoder-decoder model. This is where these utility functions will help users. I plan to implement popular decoding strategies like Random Sampling, Greedy Sampling, Beam Search, top-k Sampling and top-p (nucleus) Sampling. I also want to add model encoder layers. KerasNLP does not aim to build complete models; it aims to build "building blocks" from which models can be built. Keeping this in mind, some encoder layers which I aim to implement are (these encoder layers can then be stacked up to form the complete model): Reformer and ConvBERT (or gMLP) encoder blocks. Text augmentation means perturbing the samples in the original dataset to increase the size of the training set. This is where native text augmentation layers can be immensely useful. Backtranslation and Contextual Word Augmentation are methods which I will implement. The above modules are explained in details in the proposal document.
Current manual evaluation methods for LLM-based AI applications are unsustainable and resource-intensive. While using LLMs as judges offers a promising alternative, evaluation frameworks provide structured tools that harness LLMs for automated assessments, offering metrics, benchmarks, and scalable testing methodologies that overcome manual evaluation limitations. Gemini's integration with evaluation platforms lacks comprehensive documentation compared to providers like OpenAI and Anthropic. Analysis of ten major frameworks reveals scattered integration, decentralized documentation, and limited implementation guidance for Gemini, creating barriers for developers and researchers. I propose a three-pronged approach to improve Gemini support across evaluation frameworks. First, adding native Gemini support to select frameworks (DeepEval and TruLens) that already offer direct integrations for other providers. Second, enhancing both abstraction-layer and framework-specific documentation, covering API key management, model configuration, and multimodal capabilities. Third, creating framework-specific guides in Python and TypeScript that demonstrate effective combination of library features with Gemini APIs. For code deliverables, I will develop native Gemini integration for DeepEval and TruLens frameworks, with pull requests submitted to respective GitHub repositories. Documentation deliverables include enhanced guidance for abstraction layers (LiteLLM, LangChain, LlamaIndex) focused on Gemini configuration, and framework-specific documentation covering API management, configuration options, multimodal integration, and evaluation best practices. Tutorial deliverables will include comprehensive guides for all ten analyzed frameworks, with Python implementations for all frameworks and TypeScript for supported ones, step-by-step configuration instructions, advanced usage examples highlighting Gemini's multimodal capabilities, and error handling techniques.
Currently, SW360’s integration with FOSSology is limited to only basic functionalities using outdated endpoints namely, triggering scans and checking scan status. This results in inefficient workflows, redundant uploads, lack of flexibility in scanning configurations, and restricted report formats. It also misses opportunities for reuse of scan data and lacks user-level attribution and secure token handling. This project and proposal aims to refactor and extend SW360's FOSSology integration by utilizing the modern RESTful API (OpenAPI v2 spec) offered by FOSSology. It will enable advanced functionalities such as: 1. Direct Source Uploads via POST /uploads 2. Checksum-Based Search and Reuse using /filesearch 3. Selectable Scanning Agents (e.g., Nomos, Monk, Reuser) 4. Multi-Format Report Generation (SPDX, CycloneDX, etc.) 5. User-Specific Token Support for secure and auditable API interactions These enhancements will be implemented through a modular, secure, and scalable API integration layer in SW360, with robust error handling, polling mechanisms, and extensibility for future API versions. Deliverables: 1. REST API Refactoring of SW360's FOSSology connector using modern v2 endpoints. 2. Efficient File Upload System with token-based authentication and job initiation. 3. Checksum Reuse Logic to avoid duplicate scans and utilize FOSSology’s “Reuser” agent. 4. Configurable Scanning Agent Support exposed via backend APIs. 5. Support for Diverse Report Formats, download mechanisms, and metadata linking. 6. Secure Token Management for both server-wide and user-specific workflows. 7. Robust Error Handling, retry logic, audit logging, and performance tuning. 8. Comprehensive Testing, documentation, and CI/CD pipeline integration.
Casbin-dashboard is the official web UI (admin portal) for Casbin models and policies. Casdoor is a centralized authentication / Single-Sign-On (SSO) platform. Problem: 1. A more friendly policy management UI is needed for Casbin-dashboard. And it should be able to handle 10,000+ more rules. 2. Test management page needs to be developed for Casbin-dashboard. A test page to make example requests to Casbin and get responses, like Postman. 3. Authentication and authorization for the Casbin-dashboard itself. Of course authorization will be implemented in Casbin. 4. Casdoor needs to sign up with email without verification by configuring the application edit page. 5. Casdoor needs to support configurable captcha in user flows. It can support different implementations. Solution: 1. We can use more powerful and high-quality UI libraries such as Ant Design to build more friendly web UI. And in order to handle 10,000+ more rules, we can use paging display and virtual list in frontend, and we can use paging query and database index in backend. 2. We can build a test management page, so that we can create and edit our unit test case through the web page. 3. We can build an authorization management page to realize the authorization of the dashboard. We can use Casbin models to control the presentation of every element on the page and control each request of the RESTful API. 4. We can add a rule to control whether the email verification is required.5. We can integrate the different services from cloud captcha providers like gCaptcha, hCaptcha. To save a lot of work, we just only need to integrate the wrapper code. Deliverables: 1. Allow to sign up with Email without verification for Casdoor. - June 7; 2. Support configurable captcha for Casdoor. - June 28; 3. A more friendly policy management UI for Casbin-dashboard. - July 11; 4. Test management page for Casbin-dashboard. - July 23; 5. Authentication and authorization for the Casbin-dashboard itself. - Aug 11;
<p>Fablo is a tool mostly used for local development and in CI. It starts a Hyperledger Fabric network from a single configuration file, and supports various features that makes the development easier (REST API, network snapshots, advanced topology configuration, hooks, etc). It supports Hyperledger Fabric in versions 2.x and 3.x. Last year we were able to ensure feature parity between versions.</p><p><br></p><p>The target user of Fablo is the developer who works with the local Hyperledger Fabric network to either experiment with various topologies or work on contracts. The goal of this internship is to improve the overall developer experience by:</p><p><br></p><ul><li>Ensuring we have up to date and more approachable documentation, kept up to date with the help of AI CI workflows.</li><li>Improving Fablo distribution by supporting npm package along with existing Docker image distribution.</li><li>Resolving friction that is related to random errors, or slow responsiveness of the network setup.</li></ul><p><br></p><p>While a significant part of the proposal is improving the documentation Fablo, the most focus is on automating the process of keeping documentation up to date. This is why the primary focus of this proposal is coding.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Designing and implementing GitHub Actions workflows</li><li>Using AI agent workflows in real use cases</li><li>Creating concise and approachable documentation</li><li>Debugging and resolving complex issues</li><li>Experience with Hyperledger Fabric network topology, setup and configuration</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>GitHub Pages with documentation</li><li>GitHub Actions using AI workflows to keep the documentation up to date</li><li>Agent skill file for Fablo</li><li>An additional channel of distributing Fablo (npm)</li><li>PRs with fixes towards reducing developer friction</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/84" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/84</a>.</p>
<h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Purpose</span></h2><p><span style="color: rgb(0, 0, 0); background-color: transparent;">gittuf is a security layer for Git repositories, allowing for a security policy to be applied independently of the service the repository may be hosted on (e.g. GitHub, Gitlab, Bitbucket, etc…). The purpose of this project is to improve gittuf in several domains, such as functionality, usability, and ease of access for new users.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Goal</span></h2><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Improve gittuf's UI and UX</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: gittuf is currently driven primarily by a CLI-based workflow. The gittuf TUI is a work-in-progress UX improvement, where users instead interact with gittuf more akin to a traditional desktop program. The TUI is currently basic, and extending its functionality and improving its appearance so that it can be the primary way users interact with gittuf would be ideal.</span></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Enable temporary/time-limited approvals</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: There may be cases when a developer may need to exercise some discretionary authority and approve something in violation of the policy (e.g. a critical security patch at 4am may not be able to be approved by the full team required in policy). Adding approvals that will satisfy the policy for some duration of time (but not infinitely) would serve to improve this aspect of gittuf.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Desired Outcomes & Deliverables (1-2 mentees)</span></h2><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Improve gittuf's UI and UX</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">This project should result in gittuf featuring a polished, first-class TUI, as well as improvements to gittuf's UX in the CLI and API.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Substantial improvements to the gittuf TUI, both functionally and aesthetically.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use the updated TUI.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Appropriate tests and internal improvements needed to support the upgraded TUI.</span></li></ul><p><br></p><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Add functionality to gittuf to enable temporary/time-limited approvals</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">Some changes in a repository may need to violate the policy (e.g. a critical security patch needing to be released at 4am, and only one developer is available to approve changes at the time).</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(0, 0, 0);">A variant of this feature is to allow for changes to be submitted to a repository that must still be reviewed by someone else at a later time. These changes should not be consumed until they are reviewed, but should not necessarily pose a problem for the repository’s policy.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">A new feature that enables temporary/time-limited approvals in gittuf, as described above.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use this new functionality in gittuf.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Sufficient tests to ensure the proper operation of this new feature.</span></li></ul><p><br></p>
In order to have a better support of other AI/HPC platforms and GPU, it is necessary to enhance the integration with third-party operators and GPU support.
Adding support for calculating and analysing spectra from atomic databases to RADIS and building a user-friendly Common API with ExoJAX for interacting with supported databases.
<p>The current HPX Parallel Algorithms do no support vectorization. This project aims at providing vectorization support to Parallel Algorithms with OpenMP as backend.</p>
<p>Haiku has great support for its own file system, but is completely missing support for some other filesystems. UFS2 is one of them. In this project I will implement UFS2 in haiku.</p>
Enhancements for Kyverno Policy Exceptions including support for images and conditions. - Expected Outcome: A future version of Kyverno has enhanced support for its Policy Exception resource.
Update the syntax highlighters adding support for macro statements, highlighting commas and parentheses, and support for variables. Also, add new snippets to test different aspects of the syntax highlighting grammar.