Explore Projects

<p>Interactive data exploration is an increasingly important component of data science. Interact.jl and Escher.jl are good libraries that have the potential to be extremely powerful for these tasks, but currently Interact only supports IJulia and Escher suffers some stability issues. WebIO.jl looks to be a promising path forward for building web based components that are created by or interface with Julia. Rebuilding Interact.jl on top of WebIO.jl will bring Interact beyond IJulia, to the Atom/Juno IDE and to desktop apps with Electron/Blink.jl. Additionally it should enable Escher.jl to reuse much of Interact, which will likely reduce Escher’s size and complexity significantly, increasing its stability. Furthermore, by removing its dependence on Jupyter and IPywidgets, Interact will gain flexibility to produce more complex UIs which intermix displayed data such as plots, and UI controls. Finally, I plan to add some automated UI testing which hopefully will assist in improving the stability of not just Interact and Escher, but potentially IJulia, Juno, and Blink as well.</p>

Mobile users currently lack native access to P2P protocols like hyper://, limiting the reach of decentralized web technologies. Although desktop browsers like PeerSky support these protocols, mobile platforms remain largely inaccessible without centralized gateways. To address this, this project proposes building PeerSky Mobile Browser, a React Native application for Android using Holepunch's bare-expo template, which provides the Bare runtime necessary for running Hypercore libraries that standard React Native cannot support. The project will implement native hyper:// protocol support with DHT-based peer discovery, basic HTTPS browsing via WebView, Holesail P2P tunneling through QR codes, and mDNS for offline discovery. So the core features will include secure key management using Android KeyStore, mobile-optimized UI with tab management, and comprehensive testing across Android versions. The deliverable will be a functional Android application that brings P2P browsing capabilities to mobile and extends the PeerSky ecosystem.

<p>Visualizing genetic circuits is essential in the field of synthetic biology. These genetic designs often involve complex representation of modular and hierarchical biosystems. The representations are standardized through the Synthetic Biology Open Language (SBOL) in the form of glyphs. To make the visualization of biocircuits more efficient and amenable to automation, my goal is to upgrade DNAplotlib to support highly customizable visualizations of genetic circuits from SBOL version 2 files. I will achieve this by integrating DNAplotlib with the pySBOL2 library to support reading and writing of SBOL2 files. The current DNAplotlib only support SBOL 1.0 documentation, and thus is only capable of manifesting DNA components consisted of DNA sequence and sequence annotation. It cannot represent complex interactions between different subcomponents, and thus has poor connectivity with other genetic platforms. Through my work this summer, DNAplotlib will (1) incorporate non-DNA components / partially complete design sequences (2) document and link to external models such as SBML and CellML (3) visualize hierarchical and modular biosystems (4) save customization into SBOL file.</p>

<p>EASE is a scripting project for eclipse which allows users to execute scripts from local and remote sources. It is a threat to user in executing scripts from unknown sources especially scripts stored on remote server. One way to provide authenticity and integrity is digital signature. I would like to work with EASE Eclipse community to extend project to provide signing and verifying script functionality to users. For providing signing feature, we can use java security API. It provides simple classes and methods to perform wide range of things like signing files using private key of user, export certificates, import certificates, verify signature, generating public and private keys, etc. User will be uploading his script on server, from where remote users can directly access such scripts through code and verify them before execution to know their credibility. I plan to provide several UI enhancements to support script signing efficiently. With successful completion of this project, EASE users will be able to judge nature of script before execution.</p>

<p>Model Bricks project is an effort focused on describing recurring patterns in biological networks. These patterns are described as small VCell models that are retrieved from the VCell database and displayed online. To make Model Bricks recurring patterns more efficient and easily accessible, an entire code base shift from YAML to Vue.js is proposed. Vue.js features an incrementally adaptable architecture that focuses on declarative rendering and component composition. Vue.js component system will enable us to organize VCell APIs appropriately.</p> <p>The main objectives of this project are:</p> <ol> <li>Enhance Modelbricks.org user interface by using modern web design trends.</li> <li>Create a well-organized web architecture that will allow displaying of as many VCell elements as possible.</li> <li>Create VCell APIs for each element to be displayed.</li> <li>Enhance VCell user interface features to enable their display online.</li> <li>Write appropriate documentation.</li> </ol>

Currently, the EoP deck is not browsable or accessible through Cornucopia's API, blocking integration with OWASP Threat Dragon. This project adds a fully browsable Elevation of Privilege (EoP) deck to OWASP Cornucopia and exposes EoP cards through the existing API, enabling Threat Dragon integration. The implementation follows the Companion Edition scaffolding as a reference, which I already implemented in PR #2528 (https://github.com/OWASP/cornucopia/pull/2528). Deliverables include: data scaffolding for all 78 EoP cards across 6 suits, browsable deck UI with full card endpoints, API endpoints for EoP language and CRE mappings, a "Need more info?" link on copi cards linking to their corresponding cornucopia.owasp.org pages, and a maintainability refactor of the card browser — moving suit colors and per-card image data into YAML config files and introducing per-deck layout components, so adding any future deck requires only config and a new component with no changes to existing templates. The EoP game is licensed under CC-BY-3.0.

This LFX Term 3 project will transform the KubeStellar Design System foundations (created in Term 2) into a production-ready implementation using Next.js (Nextra or Mintlify) and deploy it on Oracle Cloud Infrastructure. The project will deliver a unified design language across all KubeStellar interfaces, featuring immersive animations and interactive components that enhance UX while maintaining performance and accessibility. Expected Outcome: 1. Implement the complete KubeStellar Design System as a production-ready component library. 2. Build an interactive documentation site using Nextra or Mintlify. 3. Develop advanced 3D visualizations and micro-interactions using Three.js and animation libraries. 4. Deploy the design system and documentation to Oracle Cloud with enterprise-grade reliability. 5. Establish automated CI/CD pipelines for continuous deployment and semantic versioning. 6. Provide seamless integration paths for all KubeStellar interfaces (web UI, docs, CLI tools). 7. Ensure accessibility compliance while delivering visually engaging experiences.

<p><strong>Objective</strong> : This project will involve building a complete module for Drupal 8 site to make it a zero-knowledge system using front-end JS encryption so that the users can rely on the site when uploading sensitive files, including images on confidential posts, not having to worry about data being stolen in case the server gets compromised.<br> <strong>Project Introduction and why this project is important</strong> : The implementation of a zero knowledge system is very essential for the user as they would want to rely on the CMS that their data is not being stolen and they are not being spied upon. Using client side encryption, sensitive data is already being encrypted before being stored on the server.<br> In a confidential post/article sharing sensitive information, the embedded illustrative images and attached files might contain more detailed information than the plain-text article that only provide an overview to the actual in-depth data in the document. Hence, having only the fields encrypted is of no use if the images and other files related to that secret article are leaked by the attackers, possibly posing a higher threat than leak of regular article field text.</p>

The RISC-V movement has massive potential to unify a fragmented industry behind a single instruction set architecture (ISA). If technology providers 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 numerous projects which directly serve as the base components of the software ecosystem, including assemblers, disassemblers, compilers, linkers, loaders, simulators, emulators. In most of those projects today, the human-readable documentation is consulted, and the necessary implementations are performed manually. Needless to say, these processes are time-consuming, inefficient, and error-prone. A new foundation which can serve as a base for automatically generating large swaths of the processor-dependent ecosystem is available, but is not yet effectively use. The “RISC-V Unified Database” project has transformed the salient content from within the RISC-V specifications into an accessible format, YAML, from which content for downstream projects can easily and automatically be further transformed into the content necessary to their project which is currently produced by manual effort.

Abstract: This project aims to enhance the speech recognition engine used in Automotive Grade Linux by creating a natural language intent engine that can understand and respond to commands. The goal is to develop a voice assistant that can understand voice commands and take necessary action based on them (e.g. turn down the volume, increase AC temperature). -- Implementation Details: The current Vosk Kaldi speech-to-text functionality will be enhanced by integrating the Snips and RASA NLU engine. The NLU engine will help in extracting the context and intent of voice commands. The extracted intent will be used directly or indirectly by a gRPC-based service which will execute it by communicating with the underlying Kuksa Server APIs. -- Deliverables: 1.) Integration and development of Snips and RASA Natural Language Understanding Intent Engines with existing Vosk implementation. 2.) Ability to execute the intent extracted from the NLU engine using a gRPC-based server, GStreamer, and Kuksa. 3.) A flutter-based Linux voice assistant app to communicate with the gRPC-based service.

This project focused on upgrading the existing pgwatch Grafana dashboards to ensure full compatibility with the latest Grafana version 12. While some dashboards had already been partially migrated, many still relied on outdated components and required manual refinement to ensure optimal performance. Grafana v11 had introduced significant changes, including the removal of AngularJS support and updates to panel JSON structures and transformation capabilities. With the release of Grafana v12, further enhancements and updates were made, making it crucial to migrate all dashboards to take full advantage of the new visualization features and capabilities. The primary objective of the project was to update the dashboards, ensuring they were fully functional with Grafana v12, while also improving usability and maintaining high performance. This involved not only updating the visualization elements to align with the new version but also addressing any deprecated components and optimizing the dashboards for a smoother user experience.In addition to the technical upgrades, the project included comprehensive documentation to guide future maintenance and ensure ease of future updates. This approach ensured the longevity and continued efficiency of the dashboards in a rapidly evolving Grafana ecosystem.

<p>My projekt goal is to extend PSYCO by a symbolic search algorithm to generate a termination criteria for the learning phase and to enable PSYCO to check properties on reactive systems.</p> <p>The current JPF-PSYCO extension combines active automata learning and dynamic symbolic execution to generate interfaces of reactive components. Further in the accompanying theoretical work of Giannakopoulou et al.[1] is shown, that this interfaces are k-full, in case they are safe, permissive, and tight for all method sequences of length up to k, k ϵ ℕ. The evaluation part of the current PSYCO implementation shows that the choice of k heavily influences the runtime behavior of PSYCO. Further it is argued, that it is possible to choose k to a relative small value after a manual analysis of the source code. During my project I will implement a symbolic search on the symbolic transition system produced by JDART to generate possible good choices for k in an automated manner. Apart of the choice of k the symbolic search output can also be used to prove invariants on the analyzed components, e.g., the absence of assertion violations.</p>

DBpedia unifies the amount of information on the web in Wikimedia projects and provides access in the form of an Open Knowledge Graph. Started in 2021, a DBpedia GSoC project led to the development of a Dialogflow-based chatbot that enables users to access the DBpedia Knowledge Graph (KG) using Natural Language (NL). This QA system provides accessibility but is still quite static. The goal of this GSoC project is to make the QA chatbot more explainable and accessible to increase credibility, accountability, and trust, which helps the user obtain explanations on how the result was obtained, what resources were used, intermediate processing steps and components’ behaviour. This project would achieve the goal by 1) Work with the current codebase to refine and refactor, followed by deployment and a CI/CD pipeline using Docker and GitHub Actions. 2) Introduce new features to the chatbot by adding scenarios that adds explainability on Qanary pipeline and its components. 3) Evaluation of the DBpedia chatbot by running A/B tests to measure user satisfaction 4) Machine Learning integrations might be used to create recommendations for improved QA pipeline configurations.

I will improve a SMART on FHIR patient-facing app to make it more accessible, user-friendly, and efficient. This includes simplifying menus and buttons, ensuring strong screen-reader support, and optimizing loading times. My plan involves: Research & Analysis Review the current user interface and identify usability issues. Conduct user interviews to pinpoint major pain points (e.g., confusing navigation, slow pages). Redesign & Development Rebuild the interface using React.js with clear, accessible design. Enhance features like keyboard navigation, text sizing, and screen-reader compatibility. User Testing & Feedback Invite patients to test the updated interface. Collect feedback and fix any bugs before final deployment. Documentation & Handoff Provide a developer guide and post the code on GitHub. Ensure future teams can easily maintain and update the app. Key Deliverables A revamped, accessible React.js interface. Improved user workflows and faster load times. A documented codebase on GitHub. A clear style guide and developer documentation.

This project focuses on improving the Ceph Dashboard by completing the migration from Bootstrap to the Carbon Design System and ensuring a consistent user experience across all components. Currently, the dashboard exists in a hybrid state with mixed UI frameworks, leading to inconsistencies, increased maintenance overhead, and a fragmented user experience. The proposed solution involves fully refactoring legacy UI components to Carbon, standardizing the frontend architecture using the lazy-loaded RoutedModule pattern, and replacing modal-based workflows with dedicated routed pages for better scalability and performance. Additionally, the project will address broken unit and end-to-end tests, expand test coverage for critical modules, and ensure long term stability through reliable CI validation. Key deliverables include a fully carbonized and consistent UI, improved application performance through modular routing and lazy loading, and a robust testing suite including unit and e2e tests covering previously untested areas. These improvements will enhance usability for end users, reduce technical debt, and make the codebase more maintainable and contributor-friendly.

I propose to enhance the Mifos Initiative's Kotlin Multiplatform (KMP) Multi-Module Project Generator to streamline cross-platform application development and make it more valuable for developers. My plan is to create a customizable Material Design 3 component layer for a consistent UI across platforms, implement a unified configuration system, and enhance GitHub Actions workflows for comprehensive CI/CD. I'll develop pre-built infrastructure components (networking, database, storage), streamline dependency management with Gradle plugins, improve the sync directories system, add a type-safe API client with Ktorfit, and automate library publishing to Maven Central. With my experience in Kotlin (3+ years) and Kotlin Multiplatform (2+ years), plus my extensive contributions to Mifos projects, I have the technical foundation to implement these enhancements successfully. I've created a detailed 15-week implementation plan with clear deliverables for each stage. These improvements will transform the KMP Project Generator into a more powerful and user-friendly tool, benefiting both the Mifos ecosystem and the broader KMP community by reducing development time and ensuring best practices across platforms.

<p>The aim of the project is to increase the number of active installs in XWiki by providing the end-users with the flexibility to use Cloud Computing or services provided by AWS. There are two types of installations currently present for XWiki - Testing one and Production one. Also, there are two major versions available currently: 12.10.5 - the stable release and 13.2 - the active latest release. Cloud computing has gained significant recognition in the past few years due to the availability of a virtually unlimited number of servers and unlimited power/memory availability within seconds while maintaining a pay-per-use model for billing. As companies and users move to Cloud-based solutions for their server needs, it makes sense that XWiki too should integrate seamlessly with major cloud provider solutions. Currently, Amazon’s AWS has the greatest market share in the Cloud Market, which is greater than the combined market share of Google (GCP) and Microsoft (Azure). Therefore we need to provide AMIs and Cloudformation Templates (in the context of AWS), which end users can consume directly to spin up XWiki within minutes and start testing/working.</p>

<p>Web services became a necessity in today’s web development world. It helps add other dimensions to the power of websites for example: a new website can sell their articles for other developers as APIs, also they can use Joomla! API to build a mobile application for their news and articles to help them reach more audiences. As Joomla is one of the most famous CMSs in the world, with millions of websites that use it, It would be great that Joomla have the capability to provide APIs for websites owners.</p> <p>This project is to provide a REST interface for Joomla 4. As discussed by the mentors, it would be a stand alone web app that integrates with Joomla CMS extensions. This app will be built using Joomla! Framework as it’s a tool developed and managed by Joomla team and also Joomla 4 is coming with it.</p> <p>I’m thinking of the app as two parts, request and response handling. The request will be routed by the app router to reach the corresponding components and retrieve the data related to the user’s request. The response is when the component receives the request from the router, it will run its logic to respond to that request and then serialize the response to follow the REST specifications.</p>

Kolibri's current Windows installer is outdated, difficult to maintain, relies on the unsupported IE11 engine, and lacks parity with the modern kolibri-app used on macOS. This project aims to replace the legacy installer by enhancing the existing Python-based kolibri-app to provide a first-class experience on Windows. The solution involves integrating the Microsoft Edge WebView2 engine, implementing native Windows features such as background operation via a Windows Service (using pywin32) and a system tray icon (wxPython), and creating a new native installer using InnoSetup. The application architecture will separate the UI and server processes for robustness. An automated build pipeline using GitHub Actions will be developed to produce the application bundle (via PyInstaller) and the final installer package, including code signing for releases. Main deliverables include: a functional Kolibri Windows application built from the kolibri-app codebase, a native InnoSetup installer (.exe), system tray functionality for server management, reliable background operation via a Windows service, seamless WebView2 integration, and an automated GitHub Actions build workflow for Windows artifacts.

JuliaBUGS is a modern Julia implementation of the classic Bayesian Inference using Gibbs Sampling — BUGS language for Bayesian modeling, combining BUGS’s intuitive model specification with Julia’s high-performance sampling methods like Hamiltonian Monte Carlo. This project proposes a browser-based graphical model editor for JuliaBUGS, enabling users to visually construct probabilistic graphical models by adding nodes and drawing arrows, instead of writing code. Built using React with TypeScript and React Flow, the web interface will support adding, connecting, grouping, and editing random variables and deterministic nodes via an interactive canvas. Users can specify probability distributions and hyperparameters through intuitive forms. The editor will export model structures to JSON and generate valid JuliaBUGS (or BUGS) code. The GSoC project will focus entirely on delivering a polished, user-friendly frontend with clear usage examples and tutorials. Inspired by tools like DoodleBUGS (for WinBUGS or MultiBUGS), shinystan, and the R Package causact, this editor aims to make model specification more accessible and streamline the Bayesian modeling workflow.

This project addresses critical gaps in Gemini API integration across leading agent frameworks (LangChain, LlamaIndex, CrewAI, Composio), where multimodal capabilities and function calling remain underdeveloped or inconsistent. By implementing standardized components for multimodal processing, function calling, and performance optimization, the project will democratize access to Gemini's advanced capabilities for developers building sophisticated AI agents. The implementation will follow a systematic approach, beginning with a comprehensive framework audit and gap analysis, followed by development of core multimodal support, function calling capabilities, and performance optimization layers. The solution will include a unified adapter layer that standardizes Gemini API access while respecting each framework's architectural patterns. Deliverables include: (1) enhanced framework integrations with full multimodal support, (2) standardized function calling implementations, (3) performance optimization components including token management and caching systems, (4) comprehensive documentation and examples, and (5) a benchmarking suite for performance analysis. This project will establish a new standard for Gemini integration in the agent ecosystem, enabling entirely new classes of multimodal AI applications.

Cacti enables two blockchain or DLT networks to transfer digital assets between each other using different mechanisms and modules, inherited from the older Cactus and Weaver projects. The Node Server acts as a container for business logic to orchestrate (or trigger) transactions across multiple networks toward achieving some desired simultaneous state change in those networks. The Relay acts as a gateway, or an ingress/egress appliance, for a given network to send communication to, and receive communication from, another network. Using the Relay or the Node Server or both, one can effect a digital asset transfer from one network to another, sample protocols for which have already been implemented in Cacti with samples for demonstration. Parallelly, there is an ongoing effort to standardize blockchain/DLT interoperation protocols through consultation and brainstorming among experts within the field under the IETF's aegis. The goal of this project is to implement the more current SATP draft specification in Cacti, in the process augmenting the Cacti Relay to be a gateway that provides a reference or template for any other standardized implementation. Using other Cacti modules and sample apps, secure transfers of digital assets using SATP must also be demonstrated. If time permits, performance measurements may also be conducted to benchmark the protocol, and specifically the Relay.

<p>Mission Support Collaboration(mscolab) is a part of the MSS application which allows real-time collaboration and editing of flight paths of a project. However, there are some key features which are currently missing from mscolab. I propose to work on the following features and improvements to mscolab:</p> <h3>Local Flight Path Editing:</h3> <p>There are many instances where a user might want to test out his/her own changes to the flight path locally without changing the path on the server. Another scenario is that the user has a slow network connection at the flight campaign location which is a common problem. Both these situations require a method for the users to be able to make changes to the flight path locally and then be able to compare and merge it with the flight path on the server later.</p> <h3>Chat Service Improvements:</h3> <p>Improve the communication between users by adding features like - markdown support, ability to send images, searching through messages, ability to delete messages and replying to a specific message.</p> <h3>Admin Dashboard:</h3> <p>Develop an admin dashboard window to allow mscolab project admins to manage users efficiently, giving them options to add/modify/delete user permissions in bulk.</p>