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 proposed GSoC project aims at integrating support for the Faust audio programming language into HISE, an extensive framework for the creation of sample-based virtual musical instruments. There are multiple ways to accomplish the integration, ahead-of-time compilation and just-in-time compilation, each with their specific benefits and shortcomings. The most straight-forward method involves ahead-of-time compilation of the Faust code into a dynamic library which the HISE instrument can interface with. This works well for finished products which will be exported and compiled once, but run many times. During prototyping, however, build time is essential and relinking the complete instrument would be excessive. In that case machine code will be generated just-in-time (JIT) from the Faust source code whenever it is modified without recompiling or linking the rest of the instrument. Faust already provides the necessary mechanisms for just-in-time compilation via LLVM, which will be tied to suitable data structures inside HISE. Lastly HISE also provides an integrated development environment (IDE) with a syntax-highlighting text editor to the instrument developer. Programming the instruments in Faust should be an on-par experience to the developer when comparing to other supported languages, e.g., SNEX and JavaScript. Therefore the existing development environment will be extended to support the Faust language, while allowing the developer to still use their editors and tools outside of HISE.
The RISC-V Mentorship Program enables one or more 12-week internship-style projects per session, funded by RISC-V, to match mentors/project leaders together with mentees/interns . Mentees are guided through a series of milestones by one or more project mentors, with whom the mentees meet on a weekly basis. Convolution is the core operation of deep learning models and computer vision applications. MLIR supports various convolution operations. Our project is to vectorize them for the RISC-V backend. There are several methods to implement convolution vectorization, such as optimizing nested loops, implementing vectorization algorithm, converting to GEMM, etc. This project needs to choose a vectorization method and implement a conversion pass for the convolution operations. As for the vector semantic support, MLIR has the “Vector” dialect for the general vector abstraction, and it also allows the backend-specific vector dialect, such as the “x86vector” dialect, “arm_neon” dialect, and “arm_neon” dialect. Like these dialects, the project also needs to propose an “RVV” dialect and work with existing dialects and tools. Deliverables: - An MLIR “RVV” Dialect. (Operations in the dialect can support the convolution vectorization) - A conversion pass to vectorize convolution operations in “Linalg” dialect with “RVV” dialect enabled. - A conversion pass to lower the operations in “RVV” dialect to “LLVM IR” dialect. - Unit tests for “RVV” dialect and conversion passes.
VCell-AI is an AI-powered platform for discovering, analyzing, and exploring biological models from the VCell database. While the platform already provides a functional chatbot interface, it requires additional capabilities to support real-world usage — including authentication, usage control, and broader integration with scientific data sources. This project aims to extend the system across these dimensions. Auth0 authentication will be integrated using the existing VCell Auth0 tenant, allowing existing VCell users to log in seamlessly. On top of this, a per-user token tracking and enforcement system will be introduced, along with an admin dashboard for managing limits. The prompt handling layer will be refactored into a centralized registry to improve consistency and reduce fragmentation. Local LLM support will be exposed as a user-facing feature. The system will also be expanded with PubMed search, complementing the already implemented BioModels DB integration. To improve usability, BNGL-based molecular visualization will be integrated. Support for SBML data will be completed, and BioPAX pathway data will be introduced as an additional source for biological knowledge. Prior to the coding period, 8 pull requests have already been raised covering API standardization, local LLM bug fixes, and BNGL visualization integration as a proof of concept, demonstrating familiarity with the codebase and commitment to the project.
This project addresses the absence of HTTP streaming support in the Rage framework, where responses are currently fully buffered before being sent to the client. This limitation prevents real-time use cases such as incremental LLM outputs, live data feeds, and large streaming responses. Even when applications generate data in chunks, the Iodine server collects all output into a buffer and sends it only after completion, making true streaming impossible. To solve this, the project introduces native HTTP streaming using chunked transfer encoding across both Iodine (C layer) and Rage (Ruby layer). A new streaming path will be added to Iodine to support incremental writes with a robust backpressure mechanism, ensuring the event loop remains non-blocking. On the Rage side, a developer-friendly API (render stream:) will be implemented using enumerators and fibers, allowing applications to stream data declaratively while seamlessly handling pause/resume behaviour under backpressure. The deliverables include implementing the http_stream transport, a Rack-compatible streaming writer with lifecycle and backpressure management, and the Rage streaming API. The project will also provide integration tests, edge-case handling (e.g., disconnects, high load), and updated documentation. This enables real-time streaming in Rage while preserving compatibility and supporting future extensions like HTTP/2.
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.
OpenClaw is an open-source autonomous AI agent framework that allows users to run powerful local AI agents capable of executing complex tasks, using tools, and maintaining long-term memory. However, it currently lacks native integration with Rocket.Chat, a widely used open-source team collaboration platform. This project aims to bridge this gap by building a complete bidirectional integration between OpenClaw and Rocket.Chat. Users will be able to interact with OpenClaw agents directly within Rocket.Chat channels and direct messages, enabling seamless automation, task execution, and proactive responses inside their familiar workspace. I plan to develop a robust Rocket.Chat adapter/plugin that includes bot user creation, REST API integration, incoming and outgoing webhook support, secure authentication, and reliable message handling. Key Deliverables: Production ready OpenClaw plugin for Rocket.Chat Full support for direct messages and public/private channels Smooth sending and receiving of messages with OpenClaw agents Proper configuration support in openclaw.json Comprehensive documentation and setup guide Upon completion, Rocket.Chat users will be able to harness the power of autonomous AI agents for tasks like security audits, reminders, code assistance, and custom workflows directly from within Rocket.Chat.
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>
<p><a href="https://docs.opencv.org/3.4/df/d0a/tutorial_js_intro.html" target="_blank">OpenCV.js</a> is a JavaScript binding for selected subset of OpenCV functions for the web platform. It allows emerging web applications with multimedia processing to benefit from the wide variety of vision functions available in OpenCV. OpenCV.js leverages Emscripten to compile OpenCV functions into asm.js or WebAssembly targets, and provides a JavaScript APIs for web application to access them.</p> <p>However, now the performance of OpenCV.js still have a big gap with Native, and it can't support real-time tasks very well, such as <a href="https://docs.opencv.org/3.4/df/d6c/tutorial_js_face_detection_camera.html" target="_blank">face detection</a> and <a href="https://docs.opencv.org/4.0.0/d5/d86/tutorial_dnn_javascript.html" target="_blank">face recognition</a>. The biggest reason is that the current version of OpenCV.js runs with single thread and no SIMD, which greatly wastes the parallel computing power of the CPU.</p> <p>But at this time, WebAssembly can reduce the performance gap between Web and Native. WASM now support multi-threading with Web Worker and shareArrayBuffer, and is going on supporting new v128 value types used for SIMD, which can both improve the parallel computing capability on Web.</p> <p>Therefore, the main goal of this project is to speedup OpenCV.js by multi-threading and SIMD.</p>
Executive Summary: Create a Comprehensive FHIR facade Layer For OpenELIS Global. The Challenge: The Synchronization Gap The current architecture utilizes a HAPI FHIR JPA "Sidecar" which functions as a secondary, disconnected data store. This results in: Data Latency: Clinical data is trapped in a "sync queue," delaying real-time care coordination. State Drift: Risks of "Split-Brain" where the LIS database and FHIR store disagree on patient records. Resource Waste: Redundant storage of the same data in two different PostgreSQL schemas, increasing infrastructure costs by ~40%. The Solution: Real-Time Native Facade I propose a Native FHIR Facade embedded directly within the OpenELIS Spring context. This transforms OpenELIS into a FHIR-native server without the need for a secondary database. Core Innovations: HAPI Plain Server Integration: Swapping the heavy JPA engine for a lightweight RESTful controller. Live Resource Mapping: A FhirTransformService that maps OpenELIS Domain Objects (Java 21 Records) to FHIR Resources on-the-fly. Atomic Transactions: FHIR writes (POST/PUT) share the same @Transactional context as the LIS, ensuring 100% data integrity. Technical Implementation Stack Language: Java 21 (leveraging Pattern Matching for cleaner transformation logic). Engine: HAPI FHIR (Plain Server Library). Mapping: Manual POJO transformation or MapStruct for high-performance throughput. Validation: Native HAPI FhirValidator to ensure compliance with regional Implementation Guides (IGs).
“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.
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.
The project consists of replacing the I/O Layer of pgagroal, today highly dependent on the libev library, for a pgagroal's own implementation. The so called I/O Layer is an event loop abstracted by libev. The motivation behind this project is the fact that libev is no longer being maintained. Therefore pgagroal needs an efficient (i.e. maintainable, reliable, fast, lightweight, secure, and scalable) implementation of an event loop that can be maintained by the pgagroal community. Currently, pgagroal depends on libev to (a) watch for incoming read/write requests from its connections in a non-blocking fashion; (b) launch timer events; and (c) watch signals. In Linux, these functionalities may be optimally achieved by using io_uring (introduced in Linux kernel 5.1). io_uring is a communication channel between a system's application and the kernel by providing an interface to receive notifications when I/O is possible on file descriptors. io_uring is accessible to system applications through liburing, which is a library that contains helpers for the setup of io_uring. A successful Linux implementation of an efficient event loop for pgagroal necessarily utilizes io_uring -- as well as other Linux I/O interfaces (e.g. stdio) -- for efficient I/O. In FreeBSD, these functionalities may be optimally achieved by using kqueue (introduced in FreeBSD 4.1). kqueue is an event notification interface that allows monitoring of multiple file descriptors. Like io_uring in Linux, kqueue enables non-blocking I/O operations, but it is specifically designed to fit into the FreeBSD kernel's event-driven architecture. The objective of this proposal is to provide a plan to achieve such efficient implementations in both Linux and FreeBSD, which shall be, at the end of this program, at least as efficient as libev, but fully maintained and controlled by the pgagroal community.
Symbolic integration is one of the central capabilities of any advanced calculator system e.g. Mathematica. SymPy currently provides several integration strategies including heuristic methods, algorithmic approaches such as the Risch algorithm, and a rule-based integrator implemented in sympy.integrals.manualintegrate. The manualintegrate module performs integration by recursively applying pattern-based rules similar to how integrals are solved manually. While this approach produces readable step-by-step results and supports a wide range of expressions, its current rule coverage is limited and many integrals involving special functions or structured products are not recognized. The goal of this project is to extend the rule-based integration system in manualintegrate, focusing on improving support for special functions, structured products, and rule prioritization. The project will expand the set of integration rules, improve heuristics for rule selection, and ensure better compatibility with SymPy's symbolic simplification system. The approach is to first analyze the gaps between manualintegrate and more comprehensive rule-based systems such as RUBI in order to identify missing classes of integrals and structural weaknesses. Based on this analysis, the project will design SymPy-compatible rule representations using its existing pattern-matching framework, ensuring consistency with the current architecture. New rules will then be implemented incrementally, with each addition accompanied by rigorous testing and validation to guarantee correctness and stability. Throughout this process, particular attention will be given to preserving and extending SymPy’s step-by-step explanation capability, ensuring that all newly supported integrals remain interpretable and aligned with human-style symbolic reasoning. The end goal is to make SymPy’s integrator more complete, explainable, and closer to human-style symbolic reasoning, while maintaining correctness.
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.
This project aims to complete the development of an Apple Metal port for gprMax, building upon the initial work in PR #457. gprMax is an open-source electromagnetic wave propagation simulator using the Finite-Difference Time-Domain (FDTD) method, and this port will enable efficient execution on Apple Silicon hardware. The implementation involves translating CUDA/OpenCL FDTD kernels to Metal Shading Language (MSL), creating Python bindings to manage Metal devices and memory, and integrating Metal as a first-class backend option alongside CPU and CUDA/OpenCL. Key components include: Finalizing Metal device detection and selection Completing MSL kernels for field updates, PML boundaries, sources, and outputs Implementing Python interfaces for Metal device management and memory operations Integrating Metal execution into the main solver loop Creating a comprehensive testing framework to validate numerical accuracy Optimizing performance through profiling and tuning Documenting the Metal backend for users and developers The project will follow a structured development approach, starting with reviewing existing code in PR #457, implementing remaining kernels, building integration tests, and finally optimizing performance. This systematic progression ensures a stable, validated, and efficient Metal implementation. The primary challenge lies in achieving competitive performance compared to existing implementations, requiring a deep understanding of Apple's GPU architecture and careful optimization. Upon completion, the Metal port will enhance gprMax's capabilities on Apple hardware, potentially offering superior performance to CPU implementations. This will benefit researchers, students, and professionals in electromagnetics, particularly those using Apple devices, and demonstrate Metal's viability for scientific computing applications.
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.
<p>Markdown provides a great ability to format messages and write structured documents using plain text format.</p> <p>Zulip uses two different markdown processors: for the backend, it is <a href="https://github.com/Python-Markdown/markdown" target="_blank">Python-Markdown</a> and for the frontend, it is <a href="https://github.com/markedjs/marked" target="_blank">marked.js</a>.</p> <p>While the backend markdown processor is highly extensible but the current frontend markdown processor doesn’t allow the same. Moreover, it is not upgradeable because of the Zulip customisations.</p> <p>The goals of this project are:</p> <ol> <li>Refactor the frontend-markdown processor with CommonMark parser.</li> <li>Make the same extensible for Zulip’s custom features like @-mentions.</li> </ol> <p>I’ll take the reference from <a href="https://github.com/commonmark/commonmark.js" target="_blank">commonmark.js</a> to write the CommonMark parser for our frontend-markdown processor. And to make it extensible, I'll use the upstream <a href="https://github.com/markedjs/marked" target="_blank">marked.js</a>.</p> <p>In parallel to this, I’ll focus on works in the markdown area. Integrating them with the Zulip will help to increase the overall users’ experience. The list of them are:</p> <ol> <li><a href="https://github.com/zulip/zulip/issues/17971" target="_blank">Add support for link shortener</a></li> <li><a href="https://github.com/zulip/zulip/issues/2401" target="_blank">Re-enable backslash escape inline pattern</a></li> <li><a href="https://github.com/zulip/zulip/issues/2183" target="_blank">Add support for online mentions</a></li> <li><a href="https://github.com/zulip/zulip/issues/13746" target="_blank">Add support for importing avatar from GitHub on account creation</a></li> </ol>
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>Kuadrant's MCP Gateway uses an Envoy external processor (ext_proc) to parse MCP JSON-RPC requests, extract metadata, rewrite request bodies, and route tool calls to backend MCP servers. This works but adds latency via a gRPC hop per request and requires maintaining custom MCP protocol parsing logic. Envoy has been rapidly adding native MCP support, as of v1.38, the Envoy MCP filter can parse MCP messages, populate dynamic metadata for downstream RBAC/ext_authz filters, handle session management, support SSE and Streamable HTTP transport, and aggregate multiple backend MCP servers. A previous investigation rejected the Envoy MCP filter due to missing body modification support, limited method coverage, and no aggregation, but the filter has since evolved considerably. This project will perform a fresh evaluation, produce a design document mapping each ext_proc responsibility to native Envoy capabilities, identify gaps (particularly around request body rewriting for tool prefix stripping and dynamic metadata consumption by Authorino), build a proof-of-concept demonstrating the native filter approach, and propose an incremental migration path. The mentee will work closely with mentors on the design, validate assumptions through prototyping with standalone Envoy, and engage with both the Kuadrant and Envoy communities.</p><p><br></p><p>Expected Outcome:</p><p> - Design document covering capability mapping of each ext_proc responsibility to Envoy MCP filter features, body modification strategy, dynamic metadata vs header trade-offs for Authorino integration, federation/aggregation comparison, session management analysis, and Istio version dependency chain</p><p> - Proof-of-concept demonstrating Envoy MCP filter parsing requests and populating metadata, downstream authorization consuming that metadata, and tool routing to multiple backends</p><p> - Clear identification of what still requires custom code after migration</p><p> - Proposed target architecture and incremental migration plan</p><p> - E2E tests validating the prototype against existing test scenarios</p><p> - Documentation of Istio version requirements and feature gates needed</p><p><br></p>
<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>