Explore Projects

Description: The Linkerd control plane includes controllers that are written in Rust. Enable users to dynamically profile the running application can aid significantly in debugging and diagnostics. Expected Outcome: In an upcoming release of Linkerd the policy controller would expose endpoints (leveraging [pprof](https://github.com/tikv/pprof-rs/blob/master/README.md) or another tool) for profiling controller resource consumption.

<p>The project aims to provide a compiler extension and runtime for a new "paramserv" built-in function. In the context of large-scale machine learning, it will bring more performance when training a model with a data-parallel and model-parallel parameter server. SystemML already supports the data-parallel and task-parallel operator. Hence, we can focus on designing the parameter server primitive and implementing the parameter update strategies.</p>

<p>In PEcAn, there are data processing pipelines that prepare data as model drivers, as well as constraints. Flux tower networks are one of the most important sources that collect such data. The aim of this project is to add the Integrated Carbon Observation System(ICOS) data stream to PEcAn. This would provide a wide variety of input data for running the ecosystem models, as well as constraining them in the European environment. Additionally, this project aims to add a GEDI LIDAR data stream to the remote data module.</p>

<p>Knative can autoscale applications but currently, it doesn’t support GraphQL servers with subscriptions. GraphQL subscriptions currently use WebSockets. The server maintains a pool of connected clients. If more servers are added, how does a server get notified about mutations made on other servers. Simply scaling your GraphQL server is not enough. This project aims to use Kafka, Debezium and Offix to extend subscription support to Knative and Add Offline Capabilities.</p>

Window functions in MariaDB are currently always materialized into temporary tables before producing any results, even for simple cases, like ranking with a limit. This prevents index usage, enforces unnecessary sorting, and introduces avoidable I/O overhead. For hybrid search queries that combine vector and full-text search using Reciprocal Rank Fusion (RRF), this limitation forces both result sets to be fully computed before any top results can be returned, significantly impacting performance. This project introduces a streaming execution path for window functions, allowing eligible queries to produce rows incrementally without materialization. Building on this, a dedicated execution node for RRF will merge vector and full-text search streams and return top results early, avoiding full computation of either source and significantly improving hybrid search efficiency.

<p>Software Carpentry has been teaching researchers in science, engineering, medicine, and related disciplines the computing skills they need to get more done in less time and with less pain. Several workshops are held in which students are required to setup their system by installing necessary packages.</p> <p>Currently software carpentry provides the <a href="https://github.com/wking/swc-setup-installation-test" target="_blank">installation-test scripts</a> so that, students can check whether they've successfully installed all software required during the workshop. But the results generated by the scripts are not collected anywhere.</p> <p>In this project a server is to be written for storing results of installation-testing scripts, and also enhancing the testing scripts by adding an option for users to collect results and send them to the server. It will help in figuring out what all problems students usually face in installations ,and also the packages which need to be deprecated in future.</p>

Maglev is OneBusAway's next-generation, high-performance Go REST API server designed to replace the legacy Java architecture. To achieve full production readiness for real-world transit agency deployments, this project focuses on four core deliverables. First, it ensures strict 1:1 API parity through automated, field-by-field output validation against the legacy server integrated directly into CI. Second, it executes a complete Go rewrite of the GTFS merge and transformer modules, creating native CLIs that enable runtime multi-feed loading directly into Maglev. Third, the project integrates the GTFS-Flex specification to support demand-responsive paratransit services, and finally, it expands the existing GTFS-RT pipeline to handle real-time structural trip modifications. Together, these enhancements will transform Maglev from a fixed-route Western transit tool into a globally deployable platform capable of serving diverse transit ecosystems across South Asia, Africa, and Latin America.

Develop new features in MSS UI and mscolab server. My proposal includes - show the development of flightpath versions. Currently, a user can only show an older revision when that revision is pushed as top revision. We want to be able to use this in the asynchronously work mode. - show more than one flightpath on a view We have campaigns with more than one aircraft. Sometimes for example they should do in different altitudes the same pattern. Therefore we need an option to add another flightpath on a view. Also it should be possible to toggle the active state, so that it is possible to alter data. On toggling a flightpath the data table gets updated. - the server can use categories to filter existing flight paths. After some defined time a flightpath should be moved to inactive state to have the UI showing only current flightpaths. There should be an option for the creator to reactivate an inactive flightpath and also inactivate one. - invite link to operations Besides that one creator can add others to an operation, we want an option to get invited. by clicking on an invite link. For a creator, we want that different links for different roles can be created and inactivation of links should be possible.

<p>Lightweight Sites is a project at CERN that enables the quick setup of new sites on the grid. Often, a lot of time is spent in setting up new sites with significant inputs from teams at CERN and at the organization operating the site. Lightweight Sites abstracts away and consolidates resources to aid the setup. To achieve this, a Lightweight Sites Specification document has been created that will allow the software configuration of the entire site through a central module. This would be the Level 1 configuration. In addition, other Lightweight Sites Components would be created according to specifications. One such component includes the repositories for containers of different compute elements (CE), batch systems, worker nodes (WN), etc. These containers are also configured and comprise the Level 2 configurations. In the past, YAIM, an in-house configuration tool has been used for Level 2 configurations. In this project, in addition to setting up Level 1 configuration, popular configuration tools like Ansible and Puppet would be used for Level 2 configuration, replacing YAIM. This migration would contribute to the project by making it easier to configure new Lightweight Sites.</p>

I would like to volunteer to develop SSH Client/Server support for NuttX. I believe this is a highly valuable feature, as it would enable remote access to NuttX-based hardware in the field for maintenance and operational purposes. With SSH support, we could remotely interact with devices, trigger I/Os, manage peripherals, and perform diagnostics in a way that is conceptually similar to what we already do on Linux-based systems. Also, this is a great opportunity for me to develop my skills. The implementation would be based on Dropbear, a lightweight and complete SSH stack with a small footprint, which makes it well-suited for embedded environments. There is already a reference port available that I plan to use as a development guide: https://github.com/david-cermak/dropbear The project would be structured in the following phases: Initial study phase to assess requirements and dependencies, including evaluation of cryptographic library integration and system constraints. Review of existing ports for other platforms (for example, ESP-IDF) to understand architectural decisions and integration patterns. Porting of the required SSH client and server functionalities to NuttX. Testing, validation, performance assessment, and resolution of identified issues. Mentors: Alan C. Assis, acassis@gmail.com

This project aims to address the inconsistency and redundancy found across customer-facing mobile applications built on the Mifos and Fineract platforms. Many of these apps share common screens and workflows, but their UI components are often rebuilt from scratch, leading to fragmented design, longer development times, and poor maintainability. To solve this, I propose to develop a unified, reusable UI component library using Jetpack Compose Multiplatform, ensuring compatibility across mobile, web, and desktop platforms. These components will be derived from shared workflows and designed according to updated design standards and guidelines developed in collaboration with our design lead. We will break down existing flows into base-level elements and reconstruct them into modular, scalable UI components. The deliverables will include: A set of core, reusable UI components built with Compose Multiplatform, shared design system with updated design principles and standards, Git-based repository to house the UI components and associated documentation, Sample screens and workflows implemented in a reference fintech app and documentation outlining how to integrate and update apps using the shared UI library.

We would like OpenCost to more effectively integrate with AI agents. To do this, we need to implement a Model Context Protocol (MCP) server to surface the information from the OpenCost API. This is a great opportunity to learn about MCP servers, and help us build an interface for AI agents to obtain reliable cost/usage information so that they can accomplish their business goals. Expected Outcome: We would like an MCP server integrated into OpenCost. This MCP server should support queries on allocations, assets, and cloud costs. The MCP server should support the full range of allocations, assets, and cloud cost query parameters. A demo video should be recorded showing an interaction with the MCP server, and used to obtain costing information in a conversational setting. In addition, integration tests must be created in the OpenCost Integration Tests repo that test all interactions with the MCP server.

<p>Sugarizer School Portal (SSP) is a Kubernetes based portal which provides on-demand Sugarizer Server Deployments. The proposed features include:</p> <ul> <li>A Sugarizer and Sugarizer Server Helm package (Sugarizer-Server Chart).</li> <li>Automated cluster database backup and restore facility.</li> <li>A Setup script to bring the Kubernetes stack up.</li> <li>A web interface for the Kubernetes infrastructure called Sugarizer School Portal Server (SSP Server), that could deploy on-demand Sugarizer-Server instances.<ul> <li>Role-based authentication with optional email verification based signup.</li> <li>Clients can request deployments from the web interface and admin to approve the deployment.</li> <li>The web interface allows creating/managing Sugarizer Server instances on the cluster.</li> <li>Automatically exposes the Sugarizer Server Instances onto a sub-domain to be used by the clients.</li> <li>The infrastructure uses MongoDB Replicaset as the database inside the cluster.</li> <li>Optionally dispatches Slack and Email notifications when the status of the deployment changes.</li> <li>Allow account creation in Sugarizer Server deployment directly from SSP Server.</li> <li>Displays SSP analytics on the dashboard.</li> <li>A Helm package for the SSP Server (SSP Chart).</li> <li>Deployment health checks.</li> </ul> </li> </ul>

This project aims to significantly enhance Mesa-Frames by building efficient and scalable data collection tools for large-scale agent-based simulations. The core focus is on developing a flexible framework that allows researchers to analyze simulation data with greater precision and lower overhead. One of the main components, the Stats Collection, will enable users to define exactly which statistics they want to track—such as mean, max, or count—helping reduce both memory usage and computation time. Another key feature is the Event Driven Collection, which records data only when predefined conditions are met. This ensures researchers capture meaningful insights while avoiding unnecessary logging and storage. To support even larger simulations, the project will also include integration with external storage systems like PostgreSQL and S3, allowing collected data to be streamed directly to disk or the cloud. In addition to these core improvements, the project will focus on performance optimization through lazy execution with Polars and better vectorization. Clear, modular documentation and a focus on usability will ensure Mesa-Frames remains an accessible and powerful tool.

Adding support for streaming and cloud storage is one of the major themes of improvement for MDAnalysis 3.0. Achieving this goal will improve the accessibility and reusability of data generated by simulations by allowing analysis of trajectories on computers with only modest disk and memory sizes. Early prototypes of the Zarrtraj reader and writer show promise as performant and flexible solutions to the MDAnalysis streaming goal. However, after receiving community feedback, we've realized that adding streaming capabilities for an existing format will lead to more sustainable code and make it easier to drive tool adoption. The goal of this project is to make the existing H5MD trajectory format cloud-streamable into MDAnalysis by using Kerchunk to reformat HDF5 metadata and Zarr to handle IO with different storage backends. With this overarching goal in mind, major milestones will include: 1. Building a trajectory reader that can read from AWS S3, Google Cloud Buckets, and Azure Blob storage and data lakes. 2. Benchmarking streaming performance in iteration and basic analysis as compared to locally-stored H5MD trajectories. 3. Achieving an overall repository test coverage of >80%. 4. Documenting the process of uploading and streaming an H5MD trajectory for users. 5. Building and distributing the package via Conda Forge.

Vitess is a distributed database system built on MySQL. Flags are widely used in Vitess for configuring components. As part of a major Vitess flag restructure, support for dynamic flag configuration was introduced. However, several Vitess components have not yet fully adopted this feature. This project involves modifying these components to fully integrate dynamic flags and performing additional flag-related refactors where necessary. Expected Outcome: Improved flag support across all Vitess components, ensuring consistent and flexible configuration management.

<p>I have decided to select the project, camel-minio - Component to store/load files from blob store(<a href="https://issues.apache.org/jira/browse/CAMEL-13934" target="_blank">https://issues.apache.org/jira/browse/CAMEL-13934</a>)</p> <p>Camel simplifies service integrations with an easy-to-use DSL to create routes that clearly identify the integration intentions and endpoints. Camel's out-of-the-box integration components are modeled after the Enterprise Integration Patterns cataloged in Gregor Hohpe and Bobby Wolf's book (<a href="http://www.eaipatterns.com" target="_blank">http://www.eaipatterns.com</a>). Camel allows you to integrate with quite a few protocols and systems out of the box using Camel components. Each component is highly flexible and can be easily configured using Camel's consistent URI syntax. In this project I`m going to add one more component to the camel components collection hopefully it will be a popular and widely used component.</p>

<p>This proposal is aimed to enhance the functionalities and overall server side of Susi.</p>

The Sugar Shell is the core desktop environment of Sugar and is responsible for activity launching, the Journal, the Frame, and system integration through DBus. The current Sugar Shell is built on GTK3, and several core components still depend on deprecated GTK3 APIs, which must be migrated to GTK4. This project focuses on the GTK4 migration of the Sugar Shell. The work includes replacing deprecated GTK3 APIs, migrating container and layout APIs to GTK4 equivalents, updating event handling using GTK4 event controllers, migrating styling to GTK CSS, and updating display and geometry handling using modern GTK4 display APIs. The migration will be done incrementally, component by component, starting with core components such as the Frame, Home View, Activity Launcher, Journal, Clipboard, and Control Panel. Each component will be migrated, tested in a running Sugar session, and submitted as small patches to ensure that the Sugar Shell remains stable and usable throughout the migration process. By the end of the project, the Sugar Shell will run on GTK4, core components will be migrated to GTK4 APIs, deprecated GTK3 APIs will be removed from migrated components, and migration documentation will be provided to support the remaining GTK4 transition work in the Sugar project.

<p>This proposal consists of the development of a compliance test suite for Reference API servers with validation and checks for URLs, status codes, correct response, checksum (to be used as the identifier) etc. This test suite to be used as a reference to facilitate Test Driven Development of Reference Servers. A Python client library along with an interactive command line interface tool to access Reference Server Data will be developed using TDD techniques. Finally, a complete system test suite comprising of various functional and system tests of client-server architecture will be used to test end to end compatibility of every Reference Server with every client.</p>

<p>Currently the open event frontend is implemented in Ember.Js. The plan is to shift the UI to React page by page.</p>

<p>Peer-to-peer protocols allow for powerful utilization of network infrastructure without the cost of a system of servers. P2PSP strives to deliver high quality streaming from a central source by taking advantage of mutual data sharing among peers tuned in to the same stream. NAT (network address translation) routers and some security-motivated features found in them create problems for effective communication in a p2p protocol. This project aims to solve the problem of communication among two or more peers found behind the same NAT router (in other words the same private router)</p>

<p>WSO2 Identity and Access Management Server is open source popular identity and access management server throughout the world plus WSO2 Identity Server efficiently undertakes the complex task of identity management across enterprise applications, services, and APIs. For this project IS version 5.4 is used. Currently, WSO2 identity server is consisting of SOAP services and in near future, there will be REST API's which support for all functionalities and which is more effective. In current environment most It support for different user stores like LDAP, JDBC, and MySQL as primary and secondary user stores. with the having facility of creating a new user store the primary data which are saving to primary user store can be separated to different user stores as one for user details and other one is for user attribute (claims) details which can be accessed by providing user credentials and secrete.</p>