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.
A really common use case we have been seeing is about enabling an IoT scenario with MQTT based devices and using an Apache Kafka cluster as the events and storage platform running on Kubernetes via Strimzi. In order to do that, there is the need to map the MQTT protocol to the custom Apache Kafka one and bridge from one to the other. This project idea is about designing such a mapping and developing a pure [Netty](https://github.com/netty/netty/tree/4.1/codec-mqtt/src/main/java/io/netty/handler/codec/mqtt) based MQTT server component (not a full MQTT broker) able to accept MQTT client connections and handling the corresponding communication based on the [MQTT 3.1.1 specification](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html). Finally, developing the Kafka producer part to get messages from MQTT clients and sending them to an Apache Kafka cluster. - Expected outcome: POC source code for an MQTT to Apache Kafka bridge
<p>The <strong>Open Event</strong> Project offers event managers a platform to organize all kinds of events including concerts, conferences, summits and regular meetups. The various components support organizers in all stages from event planning to publishing, marketing and ticket sales. Automated web and mobile apps help attendees to get information easily.</p> <p>There are two major divisions of this project:</p> <ol> <li>Implementation of numerous features on the <strong>Open Event Server</strong> in order to make it feature complete. Some of the features that we aimed for were integration of <em>payment system</em>, <em>tickets</em>, <em>taxes</em>, <em>promo codes</em> etc. </li> <li>Integration of missing endpoints and related features on the <strong>Open Event Frontend</strong> and <strong>Open Event Orga</strong> app. Some of the features that we aimed for in the <em>frontend</em> were the implementation of <em>promo codes</em>, <em>notifications</em> while <em>tracks</em> and <em>speakers</em> endpoints were targeted for the orga app.</li> </ol>
<p>HTTP Load balancer is a software application capable of distributing HTTP traffic to backend servers according to the specified scheduling policy.</p> <p>WSO2 Gateway is a high performance, lightweight, low-latency messaging gateway based on standard gateway pattern. Its Netty based non-blocking IO and Disruptor (ringbuffer) architecture makes it the fastest open-source gateway available. Benchmarks shows that the performance of gateway is very high when compared to other solutions and is close to the direct netty based backend (without any intermediate gateway).</p> <p>The following features will be implemented:</p> <ul> <li>Support for different Load Balancing Algorithms</li> <li>Full Compliance with HTTP specification</li> <li>Support for SSL </li> <li>Session Persistence</li> <li>Health Checking and Redirection</li> </ul> <p>This Load Balancer will a pluggable component. It will be able to achieve even load distribution through highly efficient, lightweight and low latency messaging. Thus, the performance will also be able to compete with existing load balancers.</p>
<p>Jupyter project provides a way to perform scientific/mathematical computations with several different programming languages using the same user interface. It achieves that by distributing the processing between a front-end (Jupyter clients, like the web based Jupyter Notebook) and a back-end (Jupyter kernels, written in Python, R, Java, etc.), that communicate among themselves with standardized format messages, transmitted through ZeroMQ connection.</p> <p>Besides the ability to switch across different kernels from the same common interface, another advantage of this approach is the possibility to run the two software components on different machines, e.g., offloading the heavier backend processing to a remote server while sending commands and visualizing data from a mobile device running the frontend.</p> <p>For Scilab, there is currently a kernel that uses a compatibility layer with file access data exchange and numpy calls to communicate with clients through the Python reference implementation.</p> <p>This Google Summer of Code proposal aims to adapt or rewrite the current suboptimal solution, to make it a truly native kernel, linking ZeroMQ messages directly to Scilab API.</p>
This project aims to improve how Asyncapi objects are visualized in AsyncAPI by introducing a new preview feature. By combining Markdown and MermaidJS Class Diagrams, and flowcharts, users can seamlessly integrate with AsyncAPI schema and Avro (.avsc) files, creating dynamic and interactive representations of object structures. The project focuses on building clear class diagrams, and flowcharts with MermaidJS, connecting entities with channels, schemas, and operations, and providing additional info for a visually intuitive understanding of message payloads in AsyncAPI. I have planned to take the following action points to accomplish this goal: 1. Set up the project by installing all necessary dependencies and organizing the structure. 2. Develop a new Preview Panel resembling the HTML rendering panel in asyncapi-react standalone. 3. Integrate a components folder to facilitate markdown generation for all asyncapi objects, including mermaid diagrams. 4. Implement mermaid support for diagrams and utilize EJS as a template. 5. Introduce a tool for converting HTML to Markdown, such as turndown, to enable export functionality. Additionally, I plan to incorporate flowcharts, Class Diagrams, and display relationships among AsyncAPI specifications objects. A fully-fledged Preview Panel of Markdown for VS-Code will become the outcome of this project.
Changepoint detection is widely used in modern data streams, but current regression based changepoint methods are limited in flexibility. Existing approaches typically assume that when a changepoint occurs, it affects all regression variables at the same time. This makes it difficult to model realistic scenarios where some components remain fixed while others change. This project aims to develop an open source R package implementing recent work on generalised changepoint regression, where users can specify both fixed and changing regression covariates. The approach builds on existing research level code, which will be refactored into a generic framework function capable of handling a range of regression models, including time series settings. The project will deliver a fully functioning R package with user-facing functions and supporting tools such as summary, print and plotting methods, designed to be consistent with existing changepoint packages. It will also include extensive testing, simulation functions for generating data, and clear documentation, with the goal of producing a CRAN ready package. Should time allow adding mixed effects or non-parametric regression models would be included. Overall, this project will provide a flexible and practical tool that addresses a gap in current changepoint methodology and will be useful for applied users.
My interest in AsyncAPI was sparked by my admiration for the technical ingenuity behind Netflix's ability to provide flawless video streaming services globally. As a Master's student studying Data Science and Computer Science at the University of Pennsylvania, I am eager to explore the intricacies of event-driven architectures further, particularly by deepening my contributions to the AsyncAPI community. My ambition is to transition from a role of simply contributing code to assuming the responsibilities of a project maintainer for the AsyncAPI Generator, a key instrument for facilitating documentation and code generation based on the AsyncAPI specification. This commitment aims to not just contribute technically but also to foster community engagement and ensure the longevity of the project. In this new role as a maintainer, I plan to review and improve documentation, handle incoming requests, engage in community discourse, assist new contributors, and spearhead the implementation of innovative features, complete with testing. Additionally, I will document my path to becoming a maintainer, the challenges faced, and the insights gained, culminating in a roadmap for future maintainers. This endeavor is not only a testament to my commitment to enhancing the AsyncAPI project but also an opportunity to contribute to the sustainability and enrichment of the broader open-source community. Leveraging my technical skills, demonstrated in a recent project that achieved a 20% performance increase using React.js and Redux, and my proactive participation in AsyncAPI discussions and enhancements, I am prepared to undertake this significant shift.
<p>The main goal of this year's GSoC was to develop <a href="https://github.com/fossasia/badgeyay" target="_blank"><strong>Badgeyay</strong></a> into a complete Service with services ranging from simple to complex functionalities which include :</p> <ul> <li>Modularizing the API and follow the best standards.</li> <li>Improving the Rest API and Resolving the known bugs.</li> <li>Improving current UI of Badgeyay and changing it along with GSoC Period by Using Ember JS and Semantic UI.</li> <li>Improving the Badge Layout and provide more features to the user. </li> <li>Implementing User Authentication and Integrating database management system into Badgeyay. </li> <li>Implementing a Badge Management System.</li> <li>Implementing Admin Panel.</li> </ul> <p>Tech Stack:</p> <p>The whole front end is shifted to Flask template to MVC frontend framework Ember JS. Everything in the frontend is divided into components and chaining of actions and models have been implemented. Semantic UI is used for styling purposes.</p> <p>The whole API is redesigned to follow JSON API specification using the marshmallow to make it compatible with data coming from Frontend. Firebase is also used to support admin and authentication functionalities from the backend flask server.</p>
Background: Current flows from RISC-V Sail specification to downstream implementations have manual steps which are time-consuming and can introduce errors.A lack of familiarity with Sail and OCaml presents a barrier to adoption of Sail as the basis for automated downstream implementations: emulators, simulators, compilers, assemblers, disassemblers, instruction stream tools, documentation, etc. Proposal: - Create an accessible Sail backend. - Extract salient information. - Transform it into an accessible database (JSON). - Survey projects dependent on RISC-V ISA for how that dependency is realized. - Utilize JSON to directly and automatically generate downstream source that is currently generated by hand. - Create a React-based interactive RISC-V ISA reference by directly importing the JSON database. Benefits: The backend can serve as a model for creation of additional Sail backends. The JSON database itself may be sufficient for many downstream uses. Creating downstream source shows feasibility, and a process for a fully-automated downstream flow. Additional collaboration with the effort to transform Sail into documentation is warranted. Much of the effort to transform Sail into JSON is complete, but there is still significant effort ahead: - enhanced parsing - enhancing the RISC-V Sail specification itself with more required content Much of the effort in creating an interactive web site is complete, but there is work to support the incorporation, display, and filtering.
<p>Fineract version 1.0 was based on the client server architecture. Now Mifos is moving one step forward and is going to releasing Gen 3/Fineract Version 2.0 which is based upon the cloud-native architecture for digital financial services.</p> <p>Fineract 2.0 evolved from the Fineract 1.0. Now Fineract 2.0 backend API structure is totally changed with great enhancement and is massively scalable and easily adaptable.</p> <p>I will design an android application on top of fineract 2.0 that will add many exciting features. MVP architecture with Dagger 2, Rxjava, Retrofit 2 etc. Code Quality plugins Findbugs, PMD, CheckStyle. User Login with Multiple account (Using Basic Auth and OAuth2). User Profile with Edit option. Client List. New client onboarding (including additional user-defined data). Viewing of client details. Loan and savings origination - opening, approving, and disbursing applications Dashboard screen with advance search. Synchronizing client data so field officers can collect repayments, view data, and onboard new clients while offline and synchronize when the return with a connection. Unit testing and Instrumentation Testing. Documentation etc.</p>
This project aims to create a tool that automatically generates Python typing stubs for the Device Under Test (DUT) in cocotb-based hardware verification testbenches. By leveraging cocotb’s existing introspection capabilities, the tool will produce .pyi stub files describing the DUT’s interface – its hierarchy of modules and signals – in a statically typed fashion. These stubs will enable IDE features like auto-completion via VS Code’s Pylance and allow static type checkers such as mypy to catch errors in testbench code, significantly improving the hardware verification development experience. The generated stubs will mirror the HDL design’s structure (with considerations for hierarchical vs. flat representations) and provide a structured abstraction of the DUT interface that can even be used for mocking or unit-testing components of the testbench. Initially, the stub generator will rely on runtime cocotb introspection only, but it will be designed with extensibility in mind, so that future enhancements (e.g., integrating a SystemVerilog language server like slang for richer type info) can be incorporated. Over a 175-hour Google Summer of Code timeline, the project will deliver a working stub-generation utility, along with documentation, tests, and integration into the cocotb ecosystem, providing a concrete benefit to the open-source hardware verification community.
<p>Opportunistic IPsec is an attempt to encrypt the internet at large. The idea is to build VPN tunnels directly to all internet hosts irrespective of the communication used. An initial proof of concept was created that leverages LetsEncrypt certificates for use with IKE and IPsec. The goal of this project is to turn this proof of concept into production quality code that makes it trivial to enrol and deploy on any server and any client.</p> <p>The project has the following objectives:</p> <ul> <li>Automate Client, Server configuration and the enrollment and updating of LetsEncrypt certificates for use with libreswan.</li> <li>Implement a DNS/DNSSEC based method for advertising Opportunistic IPsec support using LetsEncrypt for servers.</li> <li>Design a non-DNS based method for publishing support of LetsEncrypt based Opportunistic IPsec for servers.</li> <li>Enhance libreswan to allow a secure fallback to the existing NULL Authentication method.</li> <li>Ensure the working of two behind the same NAT. Along with ensuring the working of two clients behind NAT, with one not using IPsec.</li> <li>Support the recovery from server OR client reboot/crashes. Along with ensuring no lockouts happen.</li> </ul>
<p>Aim of the project is to improve and enhance <strong>Open Event Android</strong> project by adding more features, improving performance and fixing bugs.</p> <ul> <li>Add support for new API (<strong>JSONAPI</strong>) of Open Event API Server</li> <li>Add <strong>User Authentication</strong> in the App along with adding an option in the generator to add authentication in the App.</li> <li>Add <strong>User profile</strong> feature using which user can update name and avatar</li> <li>Improve <strong>Map</strong> by adding markers for all the microlocations</li> <li>Improve <strong>searching/filtering performance</strong> all over the App</li> <li>Add feature to <strong>cache thumbnails and images</strong> to load it when device is offline</li> <li>Add <strong>TextDrawable</strong> to show as placeholder for speaker image while image is downloading</li> <li>Enhance UI by adding <strong>Sticky Headers</strong> for grouping through out the App</li> <li>Improve UI by adding <strong>number of sessions label</strong> for track</li> <li>Improve code base to <strong>support older devices(pre-lollipop)</strong> with API level < 21</li> <li>Refactor code base to <strong>improve performance</strong> and to reuse code using Utility methods</li> <li>Fix other <strong>critical bugs</strong> and issues</li> </ul>
Deploying a honeypot is only half the battle; the real value lies in the intelligence we can extract from it. Currently, standard honeypot deployments leave valuable attacker logs isolated on individual virtual machines. If an instance is terminated, that threat data is gone forever, making it impossible to correlate global attack patterns or build a cohesive defensive strategy. This proposal shifts the C2SI Honeynet from a collection of isolated servers into a centralized, serverless Threat Intelligence Platform. Using Terraform and Ansible, I will build a modular framework to deploy secure, Dockerized sensor nodes across multiple cloud providers (AWS and GCP). Instead of logging locally, these edge nodes will use Fluent Bit to stream attacker telemetry in real-time to a centralized AWS S3 data lake. From there, an event-driven Python Lambda function will automatically enrich attacker IPs with global threat scores and geolocation data, making the raw attacks instantly queryable for researchers via Amazon Athena. I am not starting this project from scratch. To prove this architecture is viable and cost-effective, I have already engineered the core serverless pipeline, secured the remote Terraform state with DynamoDB locking, and built the hardened GCP modules in my preliminary Pull Requests (PR #8, #13, #14, #15, #35). Over the 350-hour GSoC period, my goal is to scale this proven foundation into a production-ready system that allows C2SI security teams to deploy a global honeynet and hunt threats with a single command.
OpenTRIM is a C++/Qt Monte Carlo ion transport simulator for radiation damage research. Every parameter study today requires four manual steps: edit config.json, invoke the CLI, load HDF5 output, and plot by hand. No Python interface exists. No live view inside the target. This project delivers both. Feature A - Python Bindings: A pybind11 module wrapping libopentrim so researchers drive simulations directly from Python: result = opentrim.run(config_dict). Tally data is exposed as zero-copy NumPy arrays via ArrayNDd buffer protocol. result.to_xarray() returns a labeled Dataset with element names and nm coordinates for publication-ready depth profiles in one line. result.core exposes mccore internals - ion counts, per-tally SEM, and run merging. GSoC 2025 user_tally binning is bridged to Python. Seven benchmark configurations verify physics parity with the CLI. Feature B - Real-Time 3D Visualization: A QOpenGLWidget tab rendering live ion tracks as GL_LINES during simulation. A two-buffer pipeline handles 30M events/second without stalling. Cascade genealogy is color-coded from ion.recoil_id(): beam ions blue, PKAs orange, sub-cascade recoils red. A SEM convergence overlay tells researchers when to stop. Camera state serializes to JSON; --render produces headless PNG with no display server. Both features are isolated - bindings/ and source/gui/trackview.* - delivered across 14 pull requests in 350 hours.
The Ziff–Gulari–Barshad (ZGB) model describes how CO and O₂ molecules adsorb and react on a metal surface represented as a square lattice. CO occupies a single site, while O₂ dissociates into two oxygen atoms placed on adjacent sites. When a CO and an O atom meet, they form CO₂, which leaves the surface and frees up space. As the CO partial pressure (yCO) changes, the surface transitions from oxygen-poisoned (no CO₂ production) to reactive (CO₂ formation) and eventually to CO-poisoned. Apothesis is a kinetic Monte Carlo simulator that models these surface reactions with high precision. Building on the ZGB model and the Apothesis simulator, PyApothesis provides a clean, Python-first workflow for running, analyzing, and sharing Kinetic Monte Carlo experiments. From a single script you can change simulation parameters (temperature, pressure, lattice size, seed), define custom adsorption/reaction/desorption processes, and run reproducible simulations — then immediately visualize results with publication-ready plots. PyApothesis includes time-series coverage plots, stacked-area composition views, process-rate and event-count analyses, spatial coverage maps and profiles, and real-time playback of the lattice (color-coded by species) to inspect microscopic behavior as it unfolds. It automatically produces a comprehensive analysis report (plots, logs, and statistical summaries) so users don’t have to dig through raw files, and it exposes hooks to incorporate lightweight ML models for surrogate predictions, parameter scans, or pattern detection directly from Python. Altogether, PyApothesis turns complex surface-kinetics simulations into an interactive, interpretable, and reproducible toolkit ideal for both researchers and students.
<p>Soletta has its own implementation of the lightweight machine to machine (LWM2M) protocol. The LWM2M protocol is used to remotely control IoT devices, these include: Firmware updates, status reporting and etc. Although Soletta already implements the LMWM2M Server and the LWM2M Client, Soletta's implementation is lacking some main features, namely: an LWM2M Bootstrap Server, Message Encryption and Data Access Control.</p> <p>The idea is to:</p> <ul> <li>Add support to LWM2M Bootstrap Server on Soletta, as specified by OMA, enhancing IoT developers' choices on how to bootstrap their machine-to-machine devices.</li> <li>Add support to CoAP Message Encryption inside Soletta's implementation of LWM2M, giving IoT developers' an increase sense of security when using LWM2M through Soletta.</li> <li>Add support to Data Access Control, allowing a LWM2M Client to support one or more LWM2M Servers, by determining which server is authorized to perform which operation. The LWM2M specification specifies Access Control Objects to handle authorization, and they will be implemented from scratch.</li> <li>Deliverables include API Code, Internal Code Changes, Unit Tests, Doxygen Documentation and Sample Applications.</li> </ul>
Problem Statement In interactive tabletop environments, Game Masters (GMs) face significant cognitive load when managing audio assets during live narration. Manually searching for and triggering specific dramatic recordings often disrupts the immersive flow of the session. There is a need for an automated system that can understand narrative intent and retrieve assets without interrupting the storytelling process.Proposed Solution I plan to bridge the gap between raw audio data and narrative utility by developing an automated pipeline for the TableTalk ecosystem. Leveraging my background in Computer Science and Economics and experience in agentic AI frameworks, I will implement:Narrative Tone Classification: Using a machine learning framework to categorize voice recordings into distinct narrative states (e.g., Urgent, Calm, Fearful).Hybrid Semantic Retrieval: Creating a retrieval engine that combines structured filtering with semantic ranking to allow GMs to use natural-language queries.Real-Time Trigger Logic: Implementing stream-based keyword spotting to map a storyteller's live performance to environmental atmospheric effects like lighting and soundscapes.DeliverablesQuantized Inference Engine: A lightweight model optimized for on-device mobile execution to ensure low-latency narrative classification.Search & Retrieval Module: A high-fidelity interface for natural-language audio discovery.Atmospheric Bridge: A software component that translates identified narrative tones or keywords into external hardware triggers.Technical Documentation: A complete guide and implementation roadmap for integrating these modules into the TableTalk mobile application.This project combines technical machine learning rigor with a deep appreciation for narrative immersion, informed by my previous work in multi-genre game development and algorithmic optimization
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.
Modern machine learning workflows in High Energy Physics increasingly rely on large-scale datasets, where the data-loading stage can become a primary bottleneck for performance and scalability, particularly due to the lack of visibility into the I/O behavior of data-loading pipelines. While model performance is extensively studied, data ingestion remains comparatively under-characterized and often limits scalability due to inefficient access patterns, filesystem contention, and poor interaction between data formats and loading strategies. This project addresses this gap by developing a reproducible benchmarking and analysis framework for characterizing data-loading performance in ML pipelines. The system will integrate the Darshan I/O characterization tool to capture system-level access patterns and combine them with application-level metrics such as throughput and runtime. It will support multiple data formats and compare different loading approaches, including the native PyTorch DataLoader and a ROOT-based loader. The methodology consists of controlled experiments that vary data formats, loader configurations, and execution parameters. Results will be processed through an analysis layer to identify recurring patterns and bottlenecks, and a diagnostic component will detect inefficiencies and provide actionable recommendations. The main deliverables of the project are: - A modular CLI-based benchmarking system for dataset generation and ingestion, configurable experiment execution, and structured result collection. It will enable reproducible experiments across data formats (NumPy .npz, HDF5, CSV, ROOT RNTuple), loader implementations, and execution configurations. - Integration of Darshan for automated I/O profiling and trace collection - A curated set of benchmark experiments covering representative combinations of data formats, loader implementations, and configuration parameters - Documentation and a final report summarizing findings and best practices
I propose to augment the current project by implementing pending pipeline features which will drastically improve the security and capability of the base application. Specifically I propose implementing secure RSA encryption to the messaging service, implement secure file sharing with audio and video support and enable user discovery on a WiFi network using UIDs RSA encryption I propose using the rsa_encrypt library in dart to secure the chat service being created between two clients on the same peer network. When two clients are connected on the same peer network, a connection is created using FPTP protocol. This project proposes to use rsa_encrypt to create a security layer over the FPTP layer. Hence the chat service is secure from other possible listeners on the peer network. Secure file sharing I propose to extend the messaging service with file sharing capabilities. We transcribe the file stored in the client’s local storage into raw metadata and securely stream the bytes to the connected client using the RSA encryption layer. The client checks for the file type using MIMETypes and decodes the bytes into the intended file. This implementation is expected to use the dart:convert library for encoding and decoding. The challenge which I aim to surpass is encoding the raw bytes through the RSA layer to ensure that unauthorized listeners cannot access the raw bytes. File Viewing I propose to implement in app file previews for supported file types using open-file-x and also enable in app viewing for image and video file types. User Discovery on a Local Network The challenge here would be for the application to persist UIDs which can be advertised over the WiFi network. Flutter does not have the capability to access users connected to a WiFi network unless the application is the router. Hence I propose to use mDNS to allow the devices to broadcast their presence on the same network without needing a central server.
<p>Kuadrant's MCP Gateway is an Envoy-based gateway for Model Context Protocol (MCP) servers that provides routing, policy enforcement, and tool federation. As the agentic ecosystem grows, we're looking to extend the gateway's capabilities beyond MCP to support other agentic protocols. The A2A (Agent-to-Agent) protocol is an emerging standard for inter-agent communication with capabilities like long-running tasks, streaming, and agent discovery via agent cards. This project will investigate how A2A support can be added to the gateway alongside MCP, then build a proof-of-concept demonstrating federated agent discovery and A2A request routing through the gateway. The mentee will work closely with mentors throughout — collaborating on the design doc, pairing on implementation decisions, and spiking on specific pieces as needed to validate assumptions early. They will also engage with the broader Kuadrant community through PR reviews, design discussions, and community calls.</p><p>- Expected Outcome:</p><p> - Analysis of the A2A protocol with a gap assessment comparing A2A and MCP traffic patterns (request/response vs long-running tasks, push notifications, multi-modal artifacts)</p><p> - Design document covering A2A routing through ext_proc, federated agent card serving in the broker, session handling implications, and CRD design</p><p> - Federated agent card endpoint in the broker that aggregates upstream A2A agent cards</p><p> - A2A request routing through the Envoy ext_proc path, with appropriate header handling and policy enforcement</p><p> - CRD design (new resource or MCPServerRegistration extension) for registering A2A agents with the gateway controller</p><p> - E2E tests demonstrating A2A agent discovery and task execution through the gateway</p><p><br></p>
<p>In a standard container setup, the container shares the network namespace with</p><p>its host environment, meaning localhost inside the container refers to the same</p><p>loopback interface as the host's network namespace. Many CNI plugins and</p><p>container networking services rely on this assumption. For instance, Docker</p><p>sets up an internal DNS server listening on localhost within each container's</p><p>network namespace and configures `/etc/resolv.conf` accordingly. Similarly,</p><p>service meshes (e.g., Istio, Linkerd) inject sidecar proxies that listen on</p><p>localhost, and certain CNI plugins expose health checks or metrics endpoints on</p><p>the loopback interface.</p><p><br></p><p> In urunc, however, workloads execute inside a sandboxed environment</p><p>with its own isolated network stack. As a result,</p><p>localhost inside the sandbox does not refer to the host's network namespace</p><p>loopback interface but to the sandbox's own. This breaks any service that</p><p>relies on localhost-based communication between the container and host-level</p><p>components.</p><p><br></p><p>This project aims to investigate and implement mechanisms to bridge localhost</p><p>communication between the host network namespace and the sandbox. The mentee</p><p>will survey the landscape of CNI plugins and networking services that rely on</p><p>localhost, categorize the different communication patterns, and design a</p><p>solution that restores compatibility while preserving the</p><p>isolation guarantees that urunc provides.</p><p><br></p><p>- Expected Outcome:</p><p> - A survey and categorization of CNI plugins and networking services that</p><p> rely on localhost communication, documenting the specific patterns and</p><p> assumptions each makes.</p><p> - A design proposal of one or more mechanisms to bridge localhost traffic</p><p> between the host network namespace and the sandbox.</p><p> - Implementation of the proposed solution in urunc, with DNS resolution as</p><p> the primary use case.</p><p> - Evaluation of the new mechanism.</p><p><br></p>
The GNOME organization has numerous websites to accommodate all its operations. Every website albeit serving different purposes falls under the GNOME umbrella. Consistency and homogeneity in the design of all present and future GNOME websites are imperative. The goal of this project is to develop and publish a unified CSS framework/library/toolkit incorporating the revised Human Interface and Visual Identity Guidelines that would allow developers to update existing GNOME websites or create new ones with a congruent visual identity. Evaluation, mockups, code-complete implementation, testing, and documentation of the individual elements such as labels, links, and images as well as composite components such as headers, footers and pagination will be performed. The project ensures creating a consistent framework with an exhaustive three-step workflow: 1. Inventory/Evaluation Phase: Variations in individual elements and composite components from each website are recorded to ensure all alternates are captured. 2. Iterative Design Phase: Mockups are created for each evaluated component considering all the possible variations encountered during evaluation. The mockups will be subsequently iterated upon after review and deliberation with the Design Team and other project stakeholders. 3. Implementation and Testing Phase: The final approved mockup will be implemented in TailwindCSS. The element/component will be documented and tested. Once the implementation is approved and all tests pass the element/component will be incorporated into the framework.