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.
Effective connectivity analyses are a staple of many neurophysiological research projects, providing key insights into the healthy functioning of the brain and pathological alterations with disease. MNE-Connectivity leverages the API of the highly-popular MNE-Python signal processing package to provide tools for computing such connectivity. However, given the complexities associated with studying interactions in the brain, it is critical that the metrics for estimating connectivity are robust, and the estimates themselves statistically significant. Naturally, it is essential that such tools are available in open-source toolboxes, something we will address in this project. First, building on recent work in the MNE-Connectivity toolbox, we will implement further support for advanced multivariate connectivity metrics in the form of a dedicated decoding module. This module will provide flexible tools for the data-driven analysis of connectivity that is critical for robust characterisations of network activity in multi-channel recordings. The only comparable implementations of such methods are in toolboxes for the proprietary language MATLAB, limiting the availability of these tools to the wider research community. Second, we will expand the existing set of statistical features available in MNE-Python to include tools for assessing the statistical significance of estimated connectivity, crucial for distinguishing genuine interactions from background noise. In all cases, new features will be complemented with detailed examples and tutorials in the MNE-Connectivity documentation. Altogether, the project will expand the repertoire and quality of open-source tools available for studying connectivity in the brain, a cornerstone of modern neurophysiological research.
Integrating AI agents with databases today requires custom implementations for each framework—no standard exists for capability discovery, safe query execution, or persistent context across sessions. This project adds agent compatibility to Apache AsterixDB by implementing two emerging standards: the Model Context Protocol (MCP) for structured tool exposure and the Agent-to-Agent (A2A) protocol for multi-agent coordination, along with persistent agentic memory utilizing AsterixDB's native storage. Key deliverables include: McpServlet implementing JSON-RPC 2.0 protocol with tools/list, tools/call, and resources/read methods; ToolRegistry enabling dynamic capability discovery; QueryTool and SchemaTool exposing SQL++ execution and dataset introspection; rate limiting and query safeguards for production safety; AgentMemoryManager providing durable CRUD storage for session context via SQL++ datasets; MemoryServlet REST endpoints for memory operations; and A2A protocol endpoints for multi-agent task delegation (stretch goal). The implementation integrates with existing AsterixDB infrastructure—BasicAuthServlet for authentication, MetadataManager for schema access, and LSM storage for persistence—requiring no breaking changes. By project end, AI agents can discover AsterixDB's capabilities, execute queries like "find customers with orders over $1000," and recall previous interactions across sessions—transforming AsterixDB into an AI-native database that speaks the language of modern agent frameworks.
The Nix build hook mechanism has been marked for removal since 2017, but it still fills an important gap in Nix's distributed build architecture. In particular, it is currently the only interface that can pass a build request together with its full set of input paths atomically. Store-based remote building does not provide this: it splits the process into separate calls, which makes it difficult for builder stores that schedule builds across a cluster, such as "nix-scheduler-hook", to know where inputs need to be copied before the build is assigned. This project proposes a cleaner, more extensible replacement by adding a new virtual "buildDerivation" method to the "Store" base class. This method would bundle the derivation path, derivation, and input paths into a single call, preserving the atomic behavior that cluster schedulers rely on. To ensure compatibility, the new interface would include a default implementation so that existing store backends continue to work unchanged. The project will validate this design through an end-to-end proof of concept by adapting "nix-scheduler-hook" to use the new API. Once the new mechanism is confirmed to support distributed scheduling correctly, the legacy build hook mechanism can be removed from the Nix daemon. Expected deliverables include the new virtual "Store" method and its default implementation, full removal of the build hook mechanism from the Nix daemon, a proof-of-concept "nix-scheduler-hook" adaptation, a passing distributed build test suite, and accompanying API documentation and migration guidance.
As AI assistants adopt humanlike names, conversational tone, and confidence framing, users form impressions of AI competence from interface design alone — independently of actual system capability. This can produce overtrust, underuse, or miscalibrated reliance. Most existing research measures trust through self-report scales, which cannot capture when or how quickly users actually defer to or override an AI recommendation. This project builds a modular, open-source web-based experimentation platform that makes behavioral trust measures tractable for researchers. Built in Next.js, the system supports randomized condition assignment, configurable manipulation of humanlike interface cues (agent name, tone, confidence framing), and a recommendation-acceptance task that produces clear reliance-versus-override outcomes under controlled AI accuracy. Fine-grained event logs — decisions, timestamps, response latency — are exported as clean JSON and CSV datasets, and a reproducible Python notebook reports reliance rate, override rate, and latency by condition. The platform is designed as reusable research infrastructure: cue logic is configuration-driven, task logic is decoupled from condition management, and the event schema is fully documented so future researchers can extend the system with new cues, tasks, and study conditions. Deliverables include a functional experimental prototype, cue manipulation framework, behavioral logging backend, sample dataset, analysis notebook, and complete documentation in a public GitHub repository.
The RISC-V movement has massive potential to unify a fragmented industry behind a single instruction set architecture (ISA). If the participants in the industry can agree to focus their efforts on a single processor architecture, rather than duplicating efforts among incompatible architectures, the entire computing ecosystem benefits. Inefficiency in critical base components of the ecosystem hampers this consolidation. There are separate efforts in documenting the RISC-V ISA, succinctly describing the semantics of the ISA in the RISC-V Sail implementation, and the numerous projects which directly serve as the base components of the software ecosystem, including assemblers, disassemblers, compilers, linkers, loaders, simulators, emulators. In summary, the tasks in this project will include: Improving the RISC-V Sail specification. (Sail language, git/GitHub) Improving the Sail parser’s JSON backend to extract more complete and accurate information. (OCaml, git/GitHub) Improving the RISC-V ISA interactive web site with new functionality and information. (Javascript, React, Carbon, or similar web frameworks, git/GitHub) Survey downstream projects which have dependencies on the RISC-V ISA. (C, C++, RISC-V assembly) Implement transformations of RISC-V ISA representation in JSON into downstream project content. (Python or similar, C, C++, RISC-V assembly) Engage with upstream projects (Sail, RISC-V Sail specification) to submit change proposals and see that they become acceptable.
The Pharo VM is written in Slang, a Smalltalk subset that is transpiled to C by the CCodeGenerator. Currently, the entire VM is generated into a handful of large monolithic C files where code from completely different subsystems the garbage collector, the interpreter, and the JIT compiler are all merged together into a single output stream. This makes the generated code difficult to read, navigate, and maintain, and means that changing a single method triggers recompilation of the entire VM rather than just the relevant module. This project introduces separate compilation to Slang by refactoring CCodeGenerator to route generated C code into multiple files, one per class hierarchy, while correctly tracking and emitting #include dependencies between them. The approach involves extending CCodeGenerator to maintain per-hierarchy output streams, implementing a dependency graph builder to determine which hierarchies reference which others, generating corresponding header files with the necessary forward declarations and prototypes, and updating the CMake build system to automatically discover the new files. The deliverables are: a working dependency graph builder for TMethod objects, a refactored CCodeGenerator supporting multiple output streams, successful extraction of the SpurMemoryManager garbage collector hierarchy into its own standalone C file with correct includes as a proof of concept, header file generation for all separated modules, extension of separate compilation to the Cogit JIT compiler and remaining hierarchies, and an updated CMake build configuration. All existing VM tests will pass throughout, ensuring no regressions in the generated code.
The mediapipe-rs project provides a Rust SDK to support mediapipe AI models. The SDK provides utility functions to pre-process application data (such as images, audio and video) into TFLite / PyTorch formats, and convert the inference results back into application data. In order to accomplish this, the [mediapipe-rs](https://github.com/WasmEdge/mediapipe-rs) project has made extensive use of the [ffmpeg](https://www.ffmpeg.org/) library. It [compiles ffmpeg to Wasm](https://github.com/WasmEdge/mediapipe-rs/blob/main/src/build.rs) and then builds it together with the application binary. However, the issue with this approach is that those Wasm-compiled ffmpeg functions are slow. We believe a better approach is to create a ffmpeg plugin for WasmEdge, and allow Wasm applications to call native ffmpeg functions as host functions. - Expected Outcome: - The deliverables will be - A WasmEdge plugin for ffmpeg that is similar to the [WasmEdge OpenCV-mini plugin](https://github.com/WasmEdge/WasmEdge/tree/master/plugins/wasmedge_opencvmini). That is to re-export ffmpeg functions in C style as plugin functions as covered in the [plugin developer guide](https://wasmedge.org/docs/category/wasmedge-plugin-system). - A Rust SDK for Wasm programs to access ffmpeg functions in the plugin. Similar to the [WasmEdge OpenCV-mini SDK](https://github.com/second-state/opencvmini) - Refactor the mediapipe-rs project to use the ffmpeg plugin
This project aims to develop a versatile mobile application tailored for efficient data management on Firebase databases. Given Firebase's popularity among small to medium-scale projects for its schemaless nature, there is a growing need for a generic mobile editor that enables seamless CRUD operations, independent of the database structure. Our project addresses this need by building a user-friendly and feature-rich mobile application that effectively empowers users to manage Firebase databases. Key Deliverables: CRUD Operations Editor: Functionality for seamless Create, Read, Update, and Delete operations on Firebase databases. Real-time Notifications: Notification system for alerting users to new or edited records, facilitating timely review and modification. User Authentication and Authorization: Secure authentication and authorization mechanisms to control access to the application. Search and Filter Functionality: Advanced search and filter options to locate records based on specific criteria easily. Export and Import Data: Ability to export data in JSON, enhancing data portability. Data Visualization: Data visualization tools to provide visual insights into data transactions and analytics. Firebase Data Audit Logging System: User activity tracking features to monitor and audit interactions with Firebase data. Batch Operations Editor: Support for batch operations to perform CRUD operations on multiple records simultaneously. In Conclusion, our project aims to empower developers with robust tools for managing Firebase databases effectively.
New openSUSE users face a steep learning curve navigating distribution-specific tools like zypper, YaST, Btrfs/Snapper, and systemd. This project builds a locally-running AI onboarding assistant that pairs a Small Language Model (SLM) with a Retrieval-Augmented Generation (RAG) pipeline over official openSUSE documentation. The assistant detects the user's actual system context (desktop environment, pending updates, failed services, filesystem layout) and grounds every answer in real documentation and real system signals. It runs fully offline after setup, respecting user privacy. A working proof of concept already exists with local SLM inference (TinyLlama 1.1B via llama-cpp-python), a ChromaDB-backed RAG pipeline, system context detection, CLI and Web UI interfaces, and a benchmarking framework. Deliverables: (1) production-ready SLM with tiered model support, (2) enhanced RAG pipeline with 4+ documentation sources and tuned retrieval, (3) expanded system context detection covering Btrfs/Snapper, networking, GPU, and locale, (4) jeos-firstboot module for first-boot integration, (5) systemd service with socket activation, (6) RPM packaging via OBS with subpackages for core, docs, and model, (7) security hardening and prompt injection defenses, (8) comprehensive testing across hardware tiers, and (9) blog posts and user documentation.
The OWASP Agent - Module C: The Librarian (OpenCRE) project makes it possible to use continuously changing OWASP guidance inside OpenCRE, while keeping the OpenCRE graph trustworthy. OpenCRE already links stable standards well, but mapping “living” OWASP content at scale is still manual and can introduce mistakes. Module C becomes the decision boundary: it determines when a new section should automatically map to a CRE node, when an existing mapping should be updated, and when the case is uncertain and must go to human review. The Librarian follows an explicit-link-first workflow and uses a semantic fallback that retrieves the top 20 candidate CRE nodes with pgvector, reranks them with a sentence-transformers cross-encoder (ms-marco-MiniLM-L-6-v2), and applies safeguards such as negation handling, update detection, and contradiction checks. Only results scoring above 0.8 are written automatically; the rest are routed to a review queue. Deliverables include a production-ready Module C pipeline integrated with OpenCRE, a golden dataset and reproducible evaluation harness, CI regression gates to prevent quality drift, and operational documentation for calibration and maintenance. If time permits, I will also prototype hybrid retrieval (vector + BM25) for identifier-heavy cases and a lightweight human review dashboard (Module D). By the end of GSoC, OpenCRE will have a measurable, safe mapping layer that enables Project OIE to ingest OWASP knowledge without sacrificing trust.
Most scientific and engineering applications heavily depend on floating point arithmetic. Floating point numbers only approximate the real numbers, which can lead to accumulation of errors and ultimately to unusable results. Current state of the art of floating point arithmetic optimization is done in Rust (egg) or Racket (Herbie). This is not very accessible for the actual target group of scientists & engineers who are used to program in high-level languages such as Python, MATLAB and Julia. Additionally, it requires manual labour (rewriting symbolic expressions, then optimizing them, and finally translating the resulting code back to the original language) due to the necessity of interfaces to interoperate between different systems written in different languages. We propose to take advantage of Julia's homoiconicity and powerful existing symbolic-numeric ecosystem to implement an automatic floating point expression optimizer in Julia, acting on any expression that supports TermInterface.jl, such as Symbolics.jl expressions as well as native Julia code. The project will include a package that implements the floating point expression optimization apporach (OptiFloat.jl). To achieve this Metatheory.jl will be fully integrated with Symbolics.jl, enabling e-graph based optimization of any symbolic expression (not just numerical). Additionally we will finalize the release of Metatheory.jl v3.0, identify existing Julia packages that may suffer from numerical error propagation, and perform a thorough comparison of automatically optimized expressions vs. original vs. external system including the time required to obtain them.
ArviZ is a package for the exploratory analysis of bayesian inference models. The current Python release of ArviZ involves three major modules that also encapsulate its core functionalities- data, plots, and stats. These are planned to be split into packages of their own, like arviz-plots, arviz-base, and arviz-stats. Development work involving the creation of these is being undertaken, with some key refactoring changes especially planned for the arviz-plots based plotting functionality, which is what this project is based on. The current plots that Arviz supports were added incrementally to the package over time, including in past GSoC projects, resulting in some redundancy and complicated to extend code. Plans and brainstorming for refactoring this have been around for a while. Work done so far on ArviZ-Plots has included a new class, PlotCollection, an improved backend interface and backend system, and 4 “batteries-included” plots at least partially adapted for this new backend. For my role in the course of this project, I will be using the PlotCollection class to implement some other plots from old ArviZ and add modular backend functions and visual elements (an intermediate layer for atomic visual elements used across plot types) required for these as appropriate. I will also be working on creating documentation and tests for these new plots added to ArviZ-plots as well as the PlotCollection class used to do these. For users, the refactored changes aim to provide improved visual aesthetics, an abstraction of aesthetics mapping to subplots and a more compact, flexible API overall. For developers, easier writing of new plotting functionality, extensibility and maintainability are the goals.
FinBot CTF is OWASP's premier learning environment for agentic AI security, yet it currently operates solely as an offensive arena. Practitioners can exploit vulnerabilities but lack the capability to implement, test, and score defenses against the OWASP Agentic Top 10. This project closes the blue-team loop by introducing a production-inspired, hook-based security framework. The solution is a four-part architecture: (A) a pluggable Guardrail & Detection Framework with pre-tool, post-output, and pre-action hooks that emit a standardized security event model; (B) a Defense-Enabled Challenge Pack converting 3-5 existing offensive challenges (A2: Excessive Agency, A3: Memory Poisoning, A8: System Prompt Leakage) into paired red/blue tracks with integrated defensive scoring; (C) an MCP-Style Scenario Module featuring benign and malicious JSON-RPC tool servers, with detectors for output poisoning, prompt injection via payload, and unauthorized endpoint redirects; and (D) comprehensive Documentation & CI including Docker Compose, contributor guides, and a GitHub Actions test suite. This work transforms FinBot into a complete AI security training platform. Leveraging my prior contributions to the codebase, I will deliver a low-risk, high-impact implementation that equips defenders to build, test, and validate guardrails against real-world agentic threats, solidifying FinBot's role as the practical counterpart to the OWASP Agentic Top 10.
SMT solvers are widely utilized in computer-guided verification of computer programs and artificial intelligence. With a multitude of theories employed in these solvers, it is beneficial to have access to a diverse range of solvers and to minimize the challenge of learning a new API for each of them. Using the solver’s own API directly makes it difficult to switch to another solver without rewriting extensive parts of the application, as there is no standardized binary API for SMT solvers. Also, since these SMT solvers have varying degrees of capabilities and performance and may not accept the same input, frameworks were created, that offer a unified API to several SMT solvers. JavaSMT has exactly these attributes, a common API for SMT solvers. The framework provides access to a variety of solvers created using Java and other programming languages. Although most solvers share a common set of supported theories and features, their availability of extra theories and performance may differ. Therefore, the inclusion of additional solvers in the framework is advantageous to its users. SMT formulas over the real numbers can encode a wide range of problems in theorem proving and formal verification. Such formulas are very hard to solve when nonlinear functions are involved. For that reason, the SMT solver dReal will be implemented in JavaSMT. The SMT solver dReal is a solver that solves nonlinear formulas over the reals. The solver can handle various nonlinear real functions such as polynomials, trigonometric functions, exponential functions, etc. The goal of the project will be to integrate the SMT solver dReal into the JavaSMT framework and to include it in the existing JavaSMT tests.
RISC-V Performance Modeling SIG is driving the development of Performance Modeling and Simulation Tools for use across RISCV membership to foster collaboration across the community. To that end, the SIG has developed a trace-driven performance model of an example RISC-V superscalar processor using C++ based on the Sparta simulation framework. The performance model, named Olympia, has been adopted by multiple organizations in both industry and academia. We have identified set of features for further development of Olympia: * Add support for execution-driven modeling - https://github.com/riscv-software-src/riscv-perf-model/issues/14 * Model state of art branch predictors along with decoupled frontend using branch-prediction API, with an example being the BOOM processor frontend documented at https://docs.boom-core.org/en/latest/sections/branch-prediction/index.html - https://github.com/riscv-software-src/riscv-perf-model/issues/143 - https://github.com/riscv-software-src/riscv-perf-model/issues/1 * Develop an API for Interconnect model and implement an example Interconnect microarchitecture. - https://github.com/riscv-software-src/riscv-perf-model/issues/60 * Use the API for data/instruction prefetcher and implement an example prefetcher microarchitecture - https://github.com/riscv-software-src/riscv-perf-model/issues/142 * Enhance the existing vector extension implementation Etc.
Currently, national climate and fiscal policy analyses operate in isolated domains. The CLEWS framework models physical constraints across energy, land, and water systems, whereas OG-Core projects macroeconomic and demographic trajectories. Because their output schemas, unit normalizations, and temporal resolutions are fundamentally incompatible, analysts must manually translate data between the two models to understand how physical policies impact long-term fiscal stability. This project establishes the first automated, bidirectional integration between OSeMOSYS and OG-Core within the MUIOGO platform. Building upon the asynchronous execution architecture and API contracts recently established in the repository, the project will construct a multi-step convergence pipeline. This system will orchestrate the execution of CLEWS, perform the necessary schema translations, run the OG-Core macroeconomic model, and iteratively feed the fiscal outputs back into the physical model until a mathematical fixed point is reached. The development is structured across four strictly ordered deliverables: 1. A stabilized, cross-platform MUIOGO runtime environment supported by comprehensive automated testing. 2. A native OG-Core execution module featuring a dedicated scenario manager and a visual results dashboard. 3. A coupled data pipeline designed to strictly normalize and translate critical bridge variables between the two distinct architectures. 4. A final convergence orchestrator capable of managing the iterative loop, complete with configurable stopping criteria and automated divergence detection.
The Gemini Cookbook is a set of sample applications and tutorials illustrating different functionalities of the Gemini APIs. The intent of this proposal is to modernize current tutorials and documentation to assist with the new unified Gemini SDKs for JavaScript/TypeScript and Python. This involves bringing examples from Python into JS/TS, creating new end-to-end tutorials, and modernizing examples for other open source libraries utilizing outdated versions of the Gemini APIs. By giving users new, current learning tools, this project hopes to facilitate adoption of the Gemini APIs. 1. Migrate Existing Python Examples to TypeScript Convert the current Python-based examples in the Gemini Cookbook to idiomatic TypeScript using the latest Gemini SDK. This will ensure cross-language support and make sure the resources are accessible to a wider range of developers. 2. Create End-to-End Tutorials for Real-World Use Cases Design and implement comprehensive, practical tutorials that showcase the capabilities of the Gemini APIs. These tutorials will include projects such as intelligent chatbots, document summarization tools, and image generation from prompts, covering both basic and advanced use cases. New ideas for tutorials can be submitted by the community, and can be sourced from the existing cookbook issues. 3. Modernize Open-Source Libraries Using Gemini APIs Identify and contribute to popular open-source projects that use deprecated versions of the Gemini SDKs. Update the examples and documentation to leverage the features and improvements introduced in the latest unified Gemini SDKs.
<p><a href="https://github.com/0x0f0f0f/Metatheory.jl/" target="_blank">Metatheory.jl</a> is a general purpose metaprogramming and algebraic computation library for the Julia programming language, supporting the novel technique of e-graph term rewriting through equality saturation, first introduced in <a href="https://egraphs-good.github.io/" target="_blank">egg</a>. Our contribution allows performing general purpose symbolic mathematics, manipulation, optimization, synthesis or analysis of syntactically valid Julia expressions and user defined types, with a clean and concise programming interface, both during compilation or execution of programs. We have been currently experimenting with optimizing mathematical code and equational theorem proving strategies. Some of the proposed tasks for this project include:</p> <ul> <li>Experimenting with <a href="https://github.com/JuliaSymbolics/Symbolics.jl" target="_blank">Symbolics.jl</a> integration and optimization for symbolic mathematics.</li> <li>Experiments in optimizing lowered Julia IRs (possibly by statically overlaying methods with <a href="https://github.com/femtomc/Mixtape.jl" target="_blank">Mixtape.jl</a>), allowing users to define concise rewrite systems that directly optimize Julia code.</li> <li>Experimenting in encoding category theory axioms to efficiently model string diagrammatic equational reasoning, and to produce human readable equational proofs. Possibly, integrate this rewrite system with <a href="https://github.com/AlgebraicJulia/Catlab.jl" target="_blank">Catlab.jl</a></li> </ul>
Offline change-point detection is a widely used statistical technique for identifying structural breaks in sequential data, with applications in fields such as signal processing, finance, and bioinformatics. Traditional methods, such as prune exact linear time (Killick et al., 2012) and binary segmentation (Hocking, 2024), are unsupervised, modelling shifts in the underlying data distribution without requiring prior knowledge or labels. While effective, they cannot leverage domain knowledge when it is partially available. Weakly supervised change-point detection methods bridge this gap by incorporating small amounts of coarse, inexact, or noisy labels to guide detection. Unlike unsupervised methods, many of which are efficiently implemented with consistent interfaces in packages such as changepoint (Killick et al., 2024) and rupturesRcpp (Nguyen et al., 2025), implementations of weakly supervised approaches are fragmented across packages, with no standardised tooling or shared interface currently available. This project aims to address this gap by extending the mlr3 ecosystem (Lang et al., 2019), a modular and extensible machine learning framework in R that provides unified interfaces for model training, evaluation, and benchmarking, to support weakly supervised change-point detection. It will also establish common abstractions for tasks, learners, and evaluation protocols tailored to change-point problems within the mlr3 design. The resulting framework will be rigorously tested and benchmarked, benefiting practitioners across various fields, enabling systematic comparison across methods, and providing a foundation for future extensions.
Joplin users accumulate hundreds of notes over time, but existing graph plugins only visualize explicit links (:/noteId) and shared tags, leaving semantically related yet unlinked notes disconnected. This project introduces an AI-powered Joplin plugin that uncovers these hidden relationships using text embeddings as the primary mechanism, with optional LLM-based enrichment for labeling and categorization. The default embedding provider is Transformers.js, enabling fully local, zero-setup inference with no external dependencies, while advanced users can opt into Ollama, Google Gemini, OpenAI, or compatible APIs. The system combines explicit links, tag relationships, and embedding-based semantic similarity into a unified graph, ensuring comprehensive note connectivity. The plugin renders this enriched structure as an interactive graph using Cytoscape.js with the fCoSE layout, where node size reflects centrality, node color represents Louvain-detected communities, and edge styles distinguish relationship types (solid for links, dotted for tags, dashed for semantic connections). It includes features such as click-to-navigate, focus mode, filtering, and export to PNG/SVG/JSON. A SQLite-based cache stores embeddings for incremental updates, ensuring scalability and performance, while optional Pass B LLM enrichment adds human-readable relationship labels and categories. The final deliverable is a production-ready .jpl plugin with secure API key handling, provider abstraction, and a comprehensive test suite including deterministic validation of AI outputs.
Drasi is a Data Change Processing platform that enables developers to detect and react to meaningful data changes using declarative Cypher queries. Drasi excels at complex change detection with unique features like `drasi.trueFor()` (detecting conditions that persist over time) and absence-of-change detection (alerting when expected events don't occur). However, it currently lacks native connectivity to IoT protocols. Drasi Lib provides Drasi's powerful graph-aware decision engine as an embeddable Rust library that can run completely offline on constrained hardware—enabling edge computing scenarios where logic runs directly on sensors and gateways. IoT applications fundamentally need to detect state transitions, but developers typically must write boilerplate code and manage state persistence manually. Drasi's diff-engine handles state management and change computation automatically, emitting events only when meaningful changes occur. MQTT (Message Queuing Telemetry Transport) is the de-facto standard protocol for IoT, used by AWS IoT Core, Azure IoT Hub, and virtually every IoT deployment. Adding MQTT support to Drasi Lib will unlock the entire IoT ecosystem for Drasi users. In this project, the mentee will build a suite of lightweight Rust crates that enable Drasi Lib to communicate with MQTT brokers. They will create connectors to ingest sensor data (MQTT Source), execute local actions (Shell Reaction), and close the control loop (MQTT Reaction).
Problem Statement: The current MyUoM app for Greek universities is a central hub for students and faculty, but it's missing some key features. Right now, it lacks a solid login system, a scalable backend, and real-time updates from official university sources. Plus, there’s no easy way for other universities to customize or integrate the platform to fit their needs. This makes the app less flexible and limits its potential to be a truly unified solution for higher education in Greece. Proposed Solution: I’m proposing MyUni—a unified, open-source platform that fixes these headaches. Built with a modern MERN stack (Next.js, Express.js, MySQL), MyUni will offer a scalable backend, real-time data syncing via APIs, and a flexible CMS for announcements and updates. It’ll support multiple universities with customizable branding and layouts, all wrapped in a user-friendly interface. Using TypeScript, microservices, and tools like Nginx and Redis, I’ll ensure it’s fast, secure, and ready to grow. Deliverables: By the end of GSoC 2025, I’ll deliver: - Web application that provide good user experience(UX) and has good User Interface(UI). - Admin dashboard where myuni admin can able to handle CMS and more. - Student dashboard where student can able to take-care of their profile, notifications of academics, and more. - Backend Architecture which serves as solution to all project requirements. - REST APIs with at least 95% test coverage. - REST APIs with modern design patterns. - Docker container image of entire app.
GIMP is actively migrating its legacy filter system to proper GEGL operations to enable non-destructive editing, and better PSD compatibility. This project contributes to that effort. First, an Inner Glow layer style will be implemented as a native GEGL operation. The implementation will use a distance transform on the layer's alpha channel to generate a per-pixel glow mask, with parameters including spread, size, opacity, intensity, noise, and blend modes empirically validated against Photopea for PSD compatibility. Once complete, it will be mapped to GIMP's PSD importer so that PSD files with inner glow layer styles import correctly. Second, a Bevel layer style will be implemented as a GEGL operation. Bevel is the remaining unimplemented PSD layer style in GIMP, involving multiple bevel styles, separate highlight and shadow blend modes, and depth and blur interactions. The same empirical approach will be used, systematically studying parameter outputs and implementing each feature step by step. Third, the legacy sharpen filter will be ported to a GEGL meta-operation. The existing implementation relies on the legacy GimpDrawable API with manual pixel loops and is limited to 8-bit images. Since the algorithm is a 3×3 convolution, it can be cleanly expressed as a GEGL meta-op, bringing it into the modern pipeline. Deliverables: A PSD-compatible gegl:inner-glow operation mapped to the PSD importer A PSD-compatible gegl:bevel operation mapped to the PSD importer A ported sharpen filter as a GEGL meta-operation
Overall, the proposal is about adding a few missing features in the package, like addition of new models, some metaprogramming, lazy evaluation, testing, documentation and linting. Currently, the package only supports four regression models (Linear, Logistic, Poisson and Negative Binomial regression). There is a huge scope of adding many more models to the package. To start with, we can add the Gamma and Inverse Gaussian regression models, and the ARIMA model for time series. Over time, more models can be added to the package. There is also a scope of adding new macros to the package to make the syntax more clean. An example of this is in the fitmodel function of the package (and is explained via a code snippet in the proposal). From the documentation, it can also be seen that any model has many attributes which are computed when the fit function is called. When working on big data, it is possible that not all the attribute values are needed, so it is currently inefficient to compute every attribute. Instead, one can compute the attributes lazily, i.e as and when they are needed. Rigorous unit testing should be added to the package to ensure code correctness. Also, the package code can use a lot of help with its documentation and code coverage. All of these can be implemented using CI/CD. Finally, in its current state, the package lacks strict code conventions (like variable names, commit message rules etc). These are essential to ensure good quality code and to make the job easier for future contributors. To enforce this, linting can be added to the code along with Git hooks to enforce these conventions. Also, a well defined API should be documented for the models, so that new models can be added at ease.