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.
<p>The main aim of this project is to come up with distributed and resilient version of Amber, which can help it in achieving the real vision of 404/broken-link free internet. The project can be divided into two different parts which involves IPFS integration, and distributed Amber design and implementation.</p> <h4>IPFS Integration</h4> <p>IPFS is the new P2P hypermedia protocol made to achieve “The permanent web” by Protocol Labs. It can be seen as a single BitTorrent swarm, exchanging objects within one Git repository. It will be added into Amber’s backend options using official <a href="https://github.com/cloutier/php-ipfs-api" target="_blank">PHP IPFS API</a> implementation.</p> <h4>Distributed Amber</h4> <p>This section of project deals with distributed version of Amber which enable Amber nodes to communicate and share cached contents with each other (P2P cache sharing). The proposed design can be briefly divided as:</p> <ul> <li><p><strong>Central Server</strong> based on <a href="https://github.com/mementoweb/timegate" target="_blank">memento timegate</a>, which will allow users to query peers and facilitate P2P cache sharing.</p> </li> <li><p><strong>Amber nodes</strong> with added APIs for cache sharing.</p> </li> <li><p><strong>Security Measurements</strong> to prevent misuse of the system by using <strong>Public-key cryptography</strong> and <strong>Reputation based cache resolving</strong>.</p> </li> </ul> <p>Technologies: Python, PHP, Networking concepts, Basic cryptography</p>
At the CMS detector, jet images are stored at reduced resolution, discarding ~75% of total deposited energy. Standard super-resolution fails here because it optimises for visual similarity, not physical validity — a model without energy constraints converges to a response of 0.52, recovering only half the missing energy. As part of the ML4Sci/CMS test task, I developed a complete physics-aware conditional GAN pipeline (github.com/rajveer43/cms-superres-reconstruction) that maps 3×64×64 LR jet images to 3×125×125 HR reconstructions using a residual CNN generator, PatchGAN discriminator with spectral normalisation, and a three-component hybrid loss (LSGAN + L1 + energy response). The best configuration achieves raw-space L1 of 0.00698 vs 0.00846 for bicubic (17.5% improvement), PSNR 14.32 vs 14.13 dB, and energy response 1.0098 — within 1% of simulation ground truth. This GSoC project extends that validated baseline by implementing and benchmarking SwinIR-style transformer SR adapted for η-φ calorimeter coordinates, and a conditional DDPM/flow-matching diffusion variant as a stretch goal. Every architecture is evaluated on the same physics-constrained suite: energy response must remain within [0.99, 1.01] or the model is rejected regardless of pixel quality. Deliverables: reproducible GAN baseline with full metric suite, trained transformer SR model with benchmark comparison table, mid-project GAN vs transformer report, final benchmark across all architectures, technical report, and organized codebase for CMS collaboration use.
Print Dialogs are one of the most used features for many people, and it is important that they stay up to date with the current print technologies (like CUPS) and be able to quickly adopt any new such upcoming technology (XYZ Cloud Printing Service). The print technology developers should also be able to fix any bugs as soon as they are found. However, since most Print Dialogs are provided natively by the GUI toolkits (and in some cases applications like LibreOffice and Chrome), this is often not the case. This is because the GUI toolkits themselves are large projects with long release cycles, and they have a lot of other similarly important things to work on. As of current, most GUI toolkits like GTK and QT connect their Print Dialogs directly with the print technologies like CUPS which creates problems for both. Any changes made by the print technologies, be it a bug fix or a new feature release often takes a long time to show up in the print dialogs upstream due to the reason mentioned before. Similarly, the print technologies need to constantly maintain backwards compatibility since they can’t release breaking changes if the Print Dialogs have not yet implemented them. Besides this, there is also a disconnect between the two sides due to the slow-release cycles. The Common Print Dialog Backends (CPDB) introduced in 2017 by Till Kamppeter aims to de-couple the GUI from the print technologies. Instead of directly connecting to each print technologies separately, the GUI projects only must adopt CPDB support once, and then OpenPrinting (or any upcoming cloud printing projects) takes care of the CPD Backend for the print technologies to be up to date with any changes. This way print technologies can react quickly and not be bound by the big GUI toolkits’ inertia. This project will attempt to get CPDB into print dialogs upstream for GTK, Qt and Chrome.
<p>Karmada is a multi-cluster orchestration system, but AI coding agents still lack a Karmada-specific skill set. Without a dedicated skill repository, agents often need to search scattered documentation, infer policy structure from incomplete context, and may produce incorrect `PropagationPolicy`, `OverridePolicy`, or troubleshooting guidance. This project aims to build the Karmada skill set for AI coding agents. The design follows mature multi-skill repository patterns, with a shared knowledge base, focused workflow skills, and deterministic helpers for schema-sensitive tasks.</p><p><br></p><p>Expected Outcome:</p><ul><li>A shared knowledge base for policy APIs, policy patterns, troubleshooting cases, component guides, and reusable examples.</li><li>Initial skills:</li><li class="ql-indent-1">karmada-knowledge</li><li class="ql-indent-1">karmada-create-policy </li><li class="ql-indent-1">karmada-audit-policy</li><li class="ql-indent-1">karmada-explain-placement</li><li class="ql-indent-1">karmada-debug-propagation</li><li class="ql-indent-1">karmada-search</li><li class="ql-indent-1">karmada-controller-manager</li><li>Deterministic helper scripts, fixtures, and example scenarios for policy generation, policy review, placement explanation, propagation debugging, and multi-country cluster management.</li><li>Contributor documentation for adding new skills, examples, and knowledge files under hack/agent-skills/.</li></ul>
<p>The Apache open-source-project <a href="https://brooklyn.apache.org/" target="_blank">Brooklyn</a> is a multi- cloud application management platform. Brooklyn can manage the provisioning and deployment of cloud applications, can monitor applications’ health and metrics, and handle the dependencies between components. It enables cross-computing features through a unified API built over <a href="https://jclouds.apache.org/" target="_blank">jClouds</a> to manage IaaS services offered by various providers. The tool offers a REST API and a GUI that enables a single-click deployment of applications across multiple machines, locations and clouds.</p> <p>As it was aforementioned, Brooklyn provides an API for the management of IaaS cloud services and ssh resources for a great number of providers and establishes a lifecycle for the management of services and applications. This project propose to extend this API with facilities for the management of PaaS offerings such as <a href="https://cloud.google.com/appengine/docs" target="_blank">Google App Engine</a>, <a href="http://aws.amazon.com/" target="_blank">AWS services</a>, <a href="https://www.heroku.com/" target="_blank">Heroku</a>, <a href="https://www.cloudfoundry.org/" target="_blank">CloudFoundry</a> (such as <a href="https://run.pivotal.io/" target="_blank">Pivotal</a> or <a href="https://console.ng.bluemix.net/" target="_blank">Bluemix</a>) , <a href="https://www.openshift.com/" target="_blank">Openshift</a>, etc., providing an homogeneous access to IaaS and PaaS services. Moreover, it opens up some interesting proposal such as adding new technologies support, e.g., Python, PHP and adding new management policies in order to take advantage of PaaS features.</p>
Overview This project aims to create a tool for Apache PMCs that will automate analysis of contributor activity in any given Apache repository. Project Goal The project goal is to make it easy for PMCs to manage their communities. We will try to achieve this by developing a tool that automatically finds and tracks first (or 3rd, or 10th) pull requests in a specified repository on Github that belongs to a specific community. The idea is that the PMC can take this data and send “Thank you” notes or emails to new people that joined the community and made their first contribution. If these automatic reports show that there are contributors with consistent commits to the project, PMC can send them encouragement emails to keep up the good work and become committers, etc. Project Description The tool will be based on using Github API to retrieve a list of all pull requests in the specified repository. Users will be able to set search parameters such as repository name and filters by pull request status. Users can use this tool to: Track pull requests in their own repositories Track issues opened in their own repositories Track the activity of individual contributors to encourage them to improve The tool will provide a user-friendly interface for searching and filtering valuable community information, such as pull requests, issues, questions in StackOverflow and others. Users will also be able to configure notifications to receive alerts about new pull requests. Technical Details The tool will be developed in Python and will use the Github API directly to fetch data (another possibility is using the PyGithub library to interact with Github API, however this may not be necessary). For the user interface, we can use the Flask or Django framework. The tool will be deployed on a web server and will be accessible through a browser.
The primary goal of this project is to refactor Akonadi’s agents and resources by decoupling their configuration dialogs from their underlying logic. This change will allow us to remove the inclusion of heavy QtWidgets header files, which currently lead to unnecessary memory usage. Reducing this overhead is essential for making the Merkuro suite fully usable on mobile devices, where resource constraints are critical. At present, many components load their GUI elements by default, unnecessarily increasing the memory footprint and hindering performance on resource-constrained platforms. By refactoring these configuration dialogs into separate, dynamically loaded plugins, the agents and resources can run leaner and more efficiently (it would save around 15-20 Mib of RAM per agent/resource) while still providing full-featured configuration interfaces when needed by host applications. Project Deliverables ● Refactor as many as reasonably possible of the selected Akonadi agents and resources within the GSoC timeframe. The goal is not necessarily to port all agents, but to make meaningful progress and establish a repeatable pattern for others to follow, ensuring the project is successful even if not every target is completed. ● Eliminate embedded QtWidgets dependencies—such as replacing QApplication with QCoreApplication—in their primary functionality. ● Identify and replace additional usages of QtWidgets beyond the configuration dialogs—such as QMessageBox instances used to show error messages. ● Modify build configurations (CMake files) to strip out unnecessary UI files and reduce dependencies, thereby lowering memory usage. ● Create dedicated configuration plugins that encapsulate the GUI functionality previously embedded within agents and resources. ● Test and document all changes to verify that memory usage is indeed reduced and that the new plugin-based configuration system functions correctly across both desktop and mobile environments.
I will build an accessible AI support agent for Zendalona product.. This project addresses a critical gap in accessibility support by creating a conversational interface that seamlessly accepts both voice and text input, allowing users to interact naturally with Zendalona's product ecosystem. The technical architecture employs an Agentic Retrieval-Augmented Generation (RAG) approach using LlamaIndex. This system will methodically index all Zendalona product information, documentation, and support materials in a vector database (ChromaDB or FAISS). When users submit queries, the system retrieves contextually relevant information and passes it to a large language model alongside the query, enabling precise, helpful responses based on accurate product knowledge. The implementation follows a three-tier approach: First, a comprehensive data ingestion pipeline that processes, cleans, and vectorizes Zendalona's product information. Second, a robust Python backend built with FastAPI that handles query processing, context retrieval, and response generation through integration with STT/TTS services and LLM APIs. Third, a fully accessible React-based multimodal chat interface featuring high-contrast text, complete keyboard navigation, ARIA attributes, and seamless screen reader compatibility, particularly with Orca. Key deliverables include a modular, containerized system with separate frontend and backend Docker containers orchestrated via Docker Compose, comprehensive API documentation, extensive accessibility testing results, and detailed user guides. The solution prioritizes WCAG 2.2 compliance, minimal latency, data privacy, and security throughout the architecture. The final product will provide visually impaired users with an intuitive, conversational way to access product support that works effectively with their existing assistive technologies.
ARM64 is becoming increasingly common with the rise of Apple Silicon and cloud instances like AWS Graviton, but Kubeflow still doesn’t run consistently on ARM-based systems. Right now, different components behave differently — some work partially, some require manual fixes, and others don’t work at all. This makes it difficult to use Kubeflow reliably outside of traditional x86 environments . The goal of this project is to make ARM64 a properly supported architecture across the Kubeflow ecosystem. Instead of partial or experimental support, the idea is to make sure Kubeflow works the same way on ARM as it does on AMD64. To achieve this, I plan to start by auditing the container images used in Kubeflow and identifying gaps in ARM64 support. Based on that, I will enable multi-architecture builds using Docker Buildx and integrate them into existing CI/CD pipelines so that ARM64 images are built and published automatically. I will also update manifests to remove architecture-specific references and ensure they work across both architectures without requiring changes. A major part of the work will be validation. I will deploy Kubeflow on ARM-based environments (OCI Ampere) and run end-to-end tests to catch issues that only appear at runtime. Any failures related to dependencies, builds, or configuration will be debugged and fixed incrementally. By the end of the project, Kubeflow should be able to run end-to-end on ARM systems without manual workarounds. The final output will include working multi-architecture builds, improved CI/CD pipelines, updated manifests, and a clear “golden setup” guide for running Kubeflow on ARM. Overall, this project is about making Kubeflow more consistent and usable across modern infrastructure, especially as ARM adoption continues to grow.
It’s Urgent Project is a notification app, with the twist that allows the user trying to reach out decide how urgent it is (i.e. if they want to disrupt or not). It is not a messaging app or a phone app. Intuition behind the project: Have you ever had to get in touch with someone at all costs even if that meant disrupting whatever they were doing? Of course they can make you a priority contact that always rings, but then you would be disrupting every time. So that doesn't work. Deliverables: User Authentication and Management: Account creation, sign-in, and sign-out functionality. Adding other users who are currently on the app. SMS invite functionality for user referrals & Account deletion option. Notification System: Implement the Notification system with Do-Not-Disturb Mode & other checks along with Challenge mechanism. User Interface (UI) Implementation: Intuitive UI design adhering to material design guidelines. Consistent design elements and smooth navigation between app sections. Good Documentation: Technical articles explaining the app's functionality and implementation details. Updated README with project details, setup guide, and contribution guidelines. Testing (Unit, Widget & Integration): Comprehensive testing for different scenarios to ensure app reliability. Unit tests for individual components, widget tests for UI elements, and integration tests for overall functionality. Timeline & Plan of Action: Phase 0 (May 1 - 26): Community Bonding Period, UI Design, Repository Setup. Phase 1 (May 27 - Jun 16): User Authentication Implementation. Phase 2 (Jun 17 - Jul 7): Notification System Development. Midterm Evaluation (Jul 8 - 14): Mid Evaluation. Phase 3 (Jul 15 - Aug 4): UI Enhancement, Testing, and Documentation. Phase 4 (Aug 5 - 25): Refactoring, Final Testing, and Evaluation.
Benchmarking sampler implementations for Bayesian inference is hard — the algorithms are inherently stochastic, and often produce only Monte Carlo samples of some distribution of interest. As a result, Bayesian inference lags other areas of machine learning in the availability of common benchmarks. To help solve this, the Stan team put together posteriordb, described as: "a set of posteriors, i.e. Bayesian statistical models and data sets, reference implementations in probabilistic programming languages, and reference posterior inferences." (posteriordb Github readme). This proposal would add Turing implementations for most of these models, facilitating easier sampler benchmarking in Turing. This database would also serve as a set of examples of Turing best practices. The project will result in a database of 120+ varied Bayesian models written in Turing, representing translations of a database of corresponding Stan models. Regarding deliverables, the proposal pdf contains a detailed and complete schedule, directly blocking out time for 130+ of the posteriors, with some additional stretch goals included. As a summary, (1) Initial weeks are spent getting familiar with Turing best practices while building out 50+ of the simplest models (mostly, variants of Bayesian regression). (2) Weeks leading up to the midterm assessment are blocked off for GLMMs and Bayesian ODEs. (3) Weeks following the midterm assessment are dedicated to two types of discrete models — first, models with a discrete structure amenable to simply summing out the discrete components (e.g. mixture models). Second, I'll implement HMMs, which require some specific algorithms to match the Stan posteriors. (4) Chip away at remaining models that don't neatly fit into a specific category, for example, neural networks, splines, and gaussian processes. If a week ends with models incomplete, I'll move on to the next week, ensuring a varied selection of models make it into the database.
This project addresses a key challenge in High Energy Physics: efficient and accurate end-to-end reconstruction of particle properties from detector data. In the CMS experiment at the Large Hadron Collider, particle collision events can be represented as high-resolution, multi-channel images. The goal is to simultaneously classify particle types and regress their invariant mass directly from these images. A major limitation of existing Vision Transformer (ViT) approaches is the quadratic computational complexity of softmax attention, which makes them inefficient for large-scale detector data. While linear attention mechanisms reduce this complexity, they often struggle to capture rich global interactions and multi-channel dependencies required for physics tasks. To address this, this project proposes the development of linear-attention-based Vision Transformers tailored for CMS E2E tasks, with a strong focus on extending the DepthViT architecture. The approach consists of three key components: Efficient Representation Learning A linear attention ViT with Masked Autoencoder (MAE) pretraining will be used to learn strong representations from large-scale unlabeled CMS data, improving downstream performance and convergence. Architecture Adaptation (DepthViT Extension) The DepthViT architecture will be adapted for supervised classification and regression by: Introducing dual-task heads for classification and mass regression Preserving depth-channel and rank structure in later layers to avoid information collapse Integrating Hierarchical Attention Permutable (HAP) blocks to enable efficient cross-window and cross-channel information flow while maintaining linear complexity Systematic Benchmarking The proposed models will be rigorously compared against standard and efficient transformer baselines (ViT, Swin, L²ViT, XCiT) using: Physics metrics (accuracy, MAE, R²) Efficiency metrics (FLOPs, memory, throughput)
The recent efforts of the `scala-wasm` project have made it possible for Scala to use the WebAssembly Component Model binary format as a compilation target. Although, the implementation has not yet been finished, it is already possible for developers to run Scala code on Wasm runtimes. In order for the Scala language to succeed in the Wasm ecosystem, core libraries which rely on platform APIs must be ported to the Wasm/WASI platform. The goal of this project is to prototype porting the core parts of the Cats Effect and FS2 libraries to the Wasm/WASI platform. The CE runtime prototype will be single-threaded and based around `wasi:io/poll`. The end result is expected to be similar to the (now-replaced) single-threaded LLVM runtime which used a `libuv`-style event-loop. The FS2 porting effort is going to focus on `fs2-core` and the `network` and `file` APIs from `fs2-io`. As a part of this project, a standalone reimplementation of java.nio.file API will be developed as a separate library. Planned Deliverables: 1. A working prototype of Cats Effect's single-threaded runtime compiling and running on Wasm/WASI free of glue JavaScript code. This prototype will serve as a basis for an upstream implementation. 2. Prototype port of the core FS2 module and the fs2.io.file and io.network APIs. 3. A standalone library reimplementation of JDK file APIs for WASI. Initial scope of the implementation will be adjusted to the needs of the fs2.io.file port. 4 An extensive documentation of the project. 5. A report regarding implementation details and findings discovered over the course of the project which will help with further porting efforts of Scala compilers and other platform-dependent libraries. 6. Wasm test environment and CI created for this project can upstreamed to sbt-typelevel so that it can be used in other projects.
Kale compiles a single Jupyter notebook into a Kubeflow Pipeline by parsing cell tags, detecting data dependencies with PyFlakes, and generating KFP DSL. But real ML work rarely fits in one notebook ,teams split preprocessing, training, and evaluation across separate notebooks, and today there's no way to compose them through Kale without dropping down to the KFP SDK manually. This project extends Kale with multi-notebook composition and a visual pipeline editor. Each notebook declares typed inputs and outputs (KFP artifacts like Dataset, Model, Metrics or parameter types). A new workflow compiler processes multiple notebooks and compiles them into a single Kubeflow Pipeline, with each notebook becoming a KFP sub-pipeline that preserves its internal steps. A visual editor built as a JupyterLab DocumentWidget handles assembly ,drag notebooks onto a canvas, connect typed ports, compile and run. Deliverables: #1.Notebook interface declaration system (backend + frontend) — explicit typed inputs/outputs per notebook, integrated into existing NotebookConfig and the Kale sidebar UI #2. Workflow data model and .kale-workflow file format with DAG validation (cycle detection, type checking, reference resolution) #3. Workflow compiler that processes each notebook through the existing NotebookProcessor → Compiler pipeline, wraps output as sub-pipelines, and generates a top-level KFP pipeline wiring them together through artifacts #4. CLI support: kale --workflow path/to/workflow.json #5. Visual DAG editor in JupyterLab using React Flow — drag-and-drop from file browser, typed port connections, properties panel, compile/run actions via Kale's existing RPC layer #6. End-to-end tests on a real KFP cluster, user documentation, and example workflows
EcoGrid Intelligence: AI-Driven Climate Resilience Analysis for Global Energy Infrastructure on Liquid Galaxy is an AI-driven geospatial analysis system designed to proactively identify global energy infrastructure at risk of operational failure due to severe climate events such as heatwaves, droughts, and wind anomalies. It addresses the problem of critical infrastructure and meteorological data being siloed, which prevents stakeholders from achieving a unified, spatial understanding of risk. The solution dynamically fuses live climate anomalies with global energy infrastructure maps to create an interactive analytical canvas on the Liquid Galaxy platform. The EcoGrid Intelligence system follows a layered architecture: Data Sources and Risk Assessment: Climate Data: Streams live and forecasted climate anomalies, including temperature deviations, precipitation extremes, and wind intensity, from the Open-Meteo API. Infrastructure Data: Geospatial coordinates, generation type (hydro, nuclear, solar), and operational capacity are sourced from the Global Power Plant Database. Risk Model: A deterministic model computes a Climate Vulnerability Score (CVS) by evaluating localized anomaly intensity against the plant type's operational sensitivities. AI Orchestration: Google’s Gemini models act as the system’s brain to autonomously determine region-relevant climate anomalies, trigger API calls, interpret the resulting CVS metrics, and structure the output for spatial rendering. Visualization: The results are converted into Keyhole Markup Language (KML), generating elements like Placemark, LookAt, and FlyTo for native, synchronized rendering and camera guidance on the Liquid Galaxy multi-screen rig. Outputs: Primary displays render immersive climate anomaly heatmaps and color-coded nodes indicating vulnerability levels, while secondary screens display dynamically generated HTML content and AI-driven insights.
The proposal outlines a project to migrate the management of omegaUp's public courses to GitHub, enabling open-source contributions and improving collaboration, version control, and deployment consistency. Currently, omegaUp's public courses are managed manually, which can be time-consuming and lacks community involvement. By using GitHub, contributors can submit pull requests (PRs) to update course content, which will be automatically validated and deployed using GitHub Actions and omegaUp's API. Key components of the project include: 1. Course Migration: All public courses will be uploaded to a GitHub repository, structured by course and content type (lectures, problems, etc.). 2. CI/CD Workflow: A GitHub Actions pipeline will validate and deploy updates when a PR is merged. This pipeline will automatically check for any changes in problems and deploy only the modified content. 3. API Integration: The system will use omegaUp’s API to upload content after successful review and approval of changes. 4. Community Collaboration: Contributors can suggest improvements via PRs, with a review process ensuring quality control before deployment. 5. Automated Testing: The CI/CD pipeline will run validation scripts to check metadata, problem structure, and other course details before deployment. 6. Security: A review and approval mechanism will prevent unauthorized or malicious content from being deployed. The project aims to enhance omegaUp’s educational content by leveraging GitHub’s collaboration model, ensuring faster updates, better quality control, and reduced manual workload for omegaUp staff. A proof of concept has been set up in a sample GitHub repository, where contributors can simulate the entire workflow by submitting PRs and seeing automatic deployments on omegaUp. This approach is expected to streamline course management, making it scalable and more responsive to community-driven improvements.
<p>This project is divided into two parts, namely, building a <code>matcher.js</code> library and revamping Public Lab's <a href="https://github.com/publiclab/Leaflet.DistortableImage" target="_blank"><code>Leaflet.DistortableImage</code></a> repository, a helper module for <a href="https://github.com/publiclab/mapknitter" target="_blank"><code>Mapknitter</code></a>.</p> <p>The <code>matcher.js</code> library essentially consists of the following components.</p> <ul> <li><a href="https://github.com/publiclab/matcher-core" target="_blank"><code>matcher-core</code></a>: This module employs the <code>ORB(Oriented FAST and Rotated BRIEF)</code> algorithm to automate pattern detection using the well-known <code>FAST(Features from Accelerated Segment Test)</code> keypoint detector and the <code>BRIEF(Binary Robust Independent Elementary Features)</code> descriptor technologies, which provide appreciable performance boosts on low computational costs.</li> <li><a href="https://github.com/publiclab/matcher-cli" target="_blank"><code>matcher-cli</code></a>: A Node-based CLI utility to headlessly test custom <code>matcher-core</code> configurations, for different purposes such as testing, demonstration, debugging issues, etc, <code>matcher-cli</code> enables headless support for all of these tasks, and can easily integrate (and automate) with your choice of CI.</li> </ul> <p>This project also incorporates Public Lab's <a href="https://github.com/publiclab/Leaflet.DistortableImage" target="_blank"><code>Leaflet.DistortableImage</code></a> library overhaul for the better half of its duration. For more information, checkout <a href="https://github.com/rexagod/Leaflet.DistortableImage/commits/rexa-soc-ldi" target="_blank">this branch</a> of my fork of the same repository.</p>
<p>Hyperledger Fabric has been available for several years and there are many production networks using Chaincode. Fabric-X has just been released and it introduces changes to the current way of deploying applications. This brings up the question on how to migrate existing applications and chaincodes to this new environment.</p><p>The goal of this mentorship project is to:</p><ul><li>Explore the feasibility to run existing Fabric Chaincode on Fabric-x;</li><li>Design and develop a proof of concept that showcases Go Chaincode for Fabric-X;</li><li>Implement a prototype of the components identified;</li><li>Identify a demo use case (i.e., Fabric Samples, CC-Tools, Fabric Private Chaincode) that comes with go chaincode;</li><li>Produce documentation that explains the architecture and how it can be used as well as potential avenues of development.</li></ul><h3>Learning Objectives</h3><ul><li>Deep dive into Hyperledger Fabric and Fabric-X.</li><li>Experience an active open-source community.</li><li>Mastering open-source workflow.</li><li>Enhance your designing and implementing skills, testing, documentation, and project management.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>Proof of Concept that showcases an alternative on how to migrate classic Fabric go chaincode to Fabric-X.</li><li>Documentation that explains the demo and how to run it.</li><li>Bonus: a technical blog post and meetup talk.</li><li>Having fun.</li></ul><p><br></p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/59" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/59</a></p>
<p>Paladin is a programmable privacy solution for EVM blockchains. It provides a framework for deploying and working with private tokens and EVM-compatible private smart contracts for private, programmable on-chain logic such as atomic swaps.</p><p><br></p><p>See <a href="https://www.paladinprivacy.org/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://www.paladinprivacy.org/</a> and <a href="https://lfdt-paladin.github.io/paladin/head/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://lfdt-paladin.github.io/paladin/head/</a></p><p><br></p><p>To work with Paladin tokens and private smart contracts applications typically use one of the existing SDKs - currently available for Go and Typescript.</p><p>There are users keen to build Java applications that utilize all of the Paladin privacy features in a performant, language-idiomatic way.</p><p><br></p><h3>Learning Objectives</h3><ol><li>Understand all the basic components and privacy patterns of Paladin</li><li>Understand the Paladin REST APIs and and their inputs/outputs</li><li>Review the existing SDKs to understand what feature-parity of a new SDK would look like</li></ol><h3>Expected Outcome and Deliverables</h3><ul><li>A Java SDK available as a published dependency for Java applications to consume</li><li>Request/reply and web-socket event-driven interfaces</li><li>A repeatable release process integrated with the current release pipeline</li><li>A high degree of test coverage of the new SDK</li></ul><p><br></p><p>Ultimately we are looking for a well designed SDK that feels natural to Java application developers to use, and makes use of current, idiomatic language features.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/64" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/64</a></p>
<p>The Web3j library is an essential tool for Java and JVM-based developers looking to integrate with the Ethereum blockchain. It provides seamless Ethereum client communication, enabling developers to interact with smart contracts and blockchain networks. However, maintaining and improving Web3j while ensuring seamless adoption of the latest Ethereum Improvement Proposals (EIPs) remains a challenge for maintainers due to the lack of time and contributors.</p><p><br></p><p>This project aims to enhance the core Web3j by improving and continue to keep up to date its component libraries, focusing on reducing existing issues and integrating the missing EIPs. By improving the additional Web3j libraries, we aim to streamline development workflows, enhance testability, and create a more robust framework that simplifies Ethereum development for Java and JVM-based projects. The updates will address known gaps in the libraries, ensuring compatibility with the latest Ethereum standards while improving documentation, developer experience, and maintainability.</p><p><br></p><p>A similar mentorship project took place during the last mentorship program and resulted in significant code contributions, documentation and blog posts.</p><p><br></p><p>The initiative will introduce structural improvements, new features and documentation for better integration, and testing, making Web3j a more sustainable and adaptable web3 development tool project.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain hands-on experience contributing to an open-source blockchain library, improving their understanding of Ethereum integration in JVM applications.</li><li>Develop expertise in Java and its application in blockchain smart contract development.</li><li>Enhance their skills in software libraries architecture, Ethereum blockchain and Solidity Smart Contracts development practices.</li><li>Collaborate with an open-source community, learning best practices for issue tracking, code reviews, and pull request management.</li><li>Develop expertise in complex library release process and code management.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/60" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/60</a></p>
<p>Design and implement a secure, auditable platform that enforces pre-execution authority for delegated actions initiated by humans, AI agents, and services. The platform will provide a single gateway for policy-driven request routing, a secret vault for API keys and credentials, and a delegation graph model to represent and evaluate long/deep delegation chains with real-time revocation and immutable proofs recorded to a ledger. Initial work will implement core components (gateway, policy evaluator, delegation graph, secret vault integration, immutable audit records) and end-to-end flows for common delegation scenarios. Later work will extend policy negotiation between agents, security reasoning modules, and audit reporting that derives intent and policy-improvement recommendations. The goal is a practical mentorship project that teaches secure authority delegation, DLT-backed auditability, and interoperable identity and credential patterns.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Understand and implement delegation models and graph-based authority evaluation.</li><li>Build a policy-driven gateway that enforces pre-execution checks and real-time revocation.</li><li>Integrate secure secret storage and key management for service/API credentials.</li><li>Record tamper-evident audit trails on an immutable ledger and derive actionable audit reports.</li><li>Apply decentralized identity / verifiable-credential concepts to authorize principals (human, agent, service).</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Working prototype of a single gateway enforcing policy-checked executions with revocation support.</li><li>Delegation Graph module with algorithms for evaluation and path resolution.</li><li>Secret Vault integration (API for storing/retrieving encrypted keys) and sample connectors.</li><li>Immutable audit-log storage adapter (ledger integration) and a basic audit-report generator.</li><li>Documentation: architecture diagram, developer guide, onboarding tasks, and end-to-end test scenarios.</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/78" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/78</a></p>
<p>*THIS APPLICATION IS ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link State (BGP-LS) is a northbound information exchange protocol extension. It allows external clients to subscribe to and collect link-state data (topology, traffic engineering metrics, segment routing SIDs, etc.). Originally designed as an export mechanism, BGP-LS is being increasingly used as a critical feed-back component in the operation and management of cloud network infrastructures. For example, TE controllers may rely on such information to respond to real-time connectivity and traffic status. Thus, the accuracy and reliability of BGP-LS is of foundational importance.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The objective of this mentorship is to develop systematic tests and validations for the BGP-LS implementation. More specifically, it needs to address complexities at various levels to achieve high coverage of the implementation. For example, at the high level, the stateful nature of the protocol extension itself, as well as the dynamic, disaggregated changes in a router's internal states, require thorough exploration of the handling of diverse interaction scenarios and even inconsistent states. At the low level, data processing utilities, such as the parsing of internal routing data formats, also requires systematic testing to validate the handling of both normal and abnormal data. </p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>A set of formal models describing both the expected high-level interactions and low-level processing logics of BGP-LS.</p><p>Benchmarks containing diverse interaction sequences and input data, providing comprehensive behavior and code coverage.</p><p>Testing infrastructures to execute, evaluate, and refine these tests.</p><p><strong>*Program Term: Summer - Fall (May - November) 20 hours of work each week*</strong></p><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and C/C++</li><li>Basic knowledge of IP networking and routing</li><li>Basic understanding of distributed systems and concurrency</li><li>Ability to navigate and understand complex codebases</li></ul>
<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>Software refactoring and restructuring is common in the open-source development of SONiC. Existing code structure may limit the adoption of new usage scenarios or protocol features, necessitating its refactoring into a better logical structure. For example, the ongoing RIB/FIB project intends to separate the RIB and FIB maintenance code in Zebra and move the latter down to SONiC’s fpmsyncd component. Since fpmsyncd resides in SONiC code space, it allows FIB to construct SONiC specific forwarding chain, and handle route convergence based on SONiC’s requirements.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>A central requirement in such refactoring is to ensure that behavior changes are exactly as expected. In the RIB/FIB example, it requires that normal executions must be equivalent before and after the refactor. The objective of this mentorship is to devise a systematic approach to validate behavioral equivalence during SONiC refactoring. More specifically, it involves applying formal methods to mathematically describe the intended behavior, compare two distinct setups, and generate comprehensive tests to ensure the consistency before and after the refactor. This will serve as an exemplar of the formal-methods-based correctness paradigm in production code development.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Abstract formal models describing expected behavior of the relevant RIB/FIB operations.</li><li>Testing infrastructure that supports parametrized testing of individual modules and execution sequences across modules.</li><li>A test generation framework and the resulting high-coverage benchmark to validate the correctness of the RIB/FIB implementation.</li><li>*<strong>Program Term: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of network forwarding and routing</li><li>Comfort with hands-on systems work under technical guidance, including system setups, trouble shooting, etc.</li><li>Strong communication skills</li></ul>
<p><strong>*APPLICATION ONLY ACCEPTING US BASED COLLEGE STUDENTS*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>As an Internet-facing networking protocol, BGP is one of the most critical components of cloud-scale networks. It enables routing information exchanges between a cloud network and the broad Internet, and incorrect behavior could devastate the connectivity of entire regions. Among many vulnerabilities, the proper handling of malformed packets is particularly important due to the propagation mechanisms of BGP. In real production network, a single mis-handling could result in cascading BGP message floodings across entire regions, degrading services or even causing network outages.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>Currently, high-level BGP behaviors are well-defined through various RFCs. However, low-level details, such as the validation and handling of malformed packets, are often under-specified. Current testing relies on ad-hoc fuzzing or manual test cases, which may miss subtle state-machine interactions that require specific input combinations.</p><p><br></p><p>The objective of this mentorship is to apply formal methods to systematically validate the handling of malformed packets by concrete BGP software implementations. Unlike traditional approaches, formal methods use mathematical logic to systematically explore diverse behaviors triggered by different input combinations, providing comprehensive validation coverage.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>A formal specification that describes high-level BGP interactions.</li><li>A set of implementation-agnostic safety invariants derived from the above high-level model. They ensure that invariant-abiding interactions will not cause cascading effects on neighboring BGP devices.</li><li>A reusable framework that applies off-the-shelf formal methods tools to systematically test concrete BGP implementations against the above invariants.</li><li>A benchmark suite of validated malformed packet scenarios with coverage metrics.</li><li><strong>SUMMER / FALL TERM (20~ HOURS OF WORK EACH WEEK)</strong></li></ul><p><br></p><p><br></p><p>Recommended Qualifications</p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of networks and routing</li><li>Good analytical skills</li></ul><p><br></p>