Explore Projects

<p>Transaction-Level Verilog (TL-Verilog) is an emerging language extension to System Verilog, Has the ability to define flexible reusable components. For this project, will develop a library of compatible components such as FIFOs, queues, arbiters, elastic buffers, etc. that could form the basis of a new era of hardware design,And will demonstrate the ease of composing these components into sophisticated transaction flows and quickly implementing what are currently considered to be complex designs, such as a complete on-chip network!</p>

This project aims to improve CircuitVerse by adding new components that are useful for learning about real hardware, such as shift registers (SISO, SIMO, MISO, MIMO), comparators, and a buzzer (speaker), Priority MUX, etc. It will also introduce support for connecting CircuitVerse with real devices using the Browser’s Web Serial API, allowing users to interact with physical hardware directly through the simulator. These features will help people better understand how digital circuits work—both in theory and in practice. The goal is to make CircuitVerse more powerful and helpful for learning digital circuits and embedded systems.

Bhyve is a modern type 2 hypervisor originally written for FreeBSD. The goal of this project is to enhance the functionality of its debugging server. Several existing features related to single-stepping are tied to Intel-specific VM mechanisms, which severely impairs bhyve's debugging functionality on other platforms. Thus, the first major goal of this project is to rework the single-stepping mechanism to use the RFLAGS.TF VMEXIT mechanism. This will allow bhyve to support debugging guest operating systems on AMD platforms, which would facilitate kernel development for more 64-bit x86 hardware (other than Intel). The second goal is adding support for hardware watchpoints (and optionally hardware breakpoints) using the guest OS's hardware debugging registers. This will improve the kernel development workflow and allow easier and faster fixes for various kernel memory corruption bugs.

While the Open Medical Record System (OpenMRS)'s major objective is to store and retrieve electronic medical records in the developing world, in some areas this objective has been frustrated due to lack of a stable internet connection, tech-illetracy and rampant power outages in most parts of the developing world. A patient's medical history and treatment may be well documented but due to lack of internet, computers and electricity in the next facility, that patient may not be in position to receive the service due to lack of reference document hence breaking continuity of care among health care providers, its is against this background that the print feature was development. so that at any point in time, a patient and the service provider can have a hard copy of whichever document they want. how I plan to solve it; 1. have a list of areas where printing is required and add them to the configurations 2. Add the print button in the selected areas 3. write code for the print function using the react-to-print package 4. write tests

The proposal aims to enhance Eclipse Winery, a web-based environment for modeling OASIS TOSCA topologies, by implementing basic security measures. Currently, Winery focuses on providing a graphical editing environment for modeling application topologies. However, the proposal suggests adding a Language Server Protocol (LSP) provider for OASIS TOSCA YAML files. This would allow Winery to support the latest version of the OASIS TOSCA standard and handle dynamic type additions. The expected outcomes of the project include: 1-Developing an LSP server that supports the latest OASIS TOSCA 2.0 standard. 2-Ensuring that the LSP server is aware of newly introduced types and makes them available in the service template. 3-Enabling the LSP server to handle multiple files. 4-Demonstrating the functionality of the LSP server using compatible IDEs such as Eclipse Theia, Visual Studio Code, or Eclipse IDE. 5-Writing clean and maintainable code, with a preference for using modern Java (version 21 or later). The proposal indicates that the project's size is estimated at 350 hours and rates its difficulty as medium. Overall, the proposal aims to improve the security and functionality of Eclipse Winery by implementing an LSP server for OASIS TOSCA YAML files, thereby providing a more robust and comprehensive modeling environment.

The JSON Schema website currently uses custom UI components, which increases maintenance complexity and slows down updates. This project modernizes the site by integrating a UI library like ShadCN/UI and refactoring components into a modular, consistent system to improve maintainability and user experience. Work includes theming the UI library, updating layout and navigation with dark mode support, and improving Markdown rendering by refactoring StyledMarkdown.tsx into a more flexible and maintainable system. This will support advanced features like tables, tab groups, and a dynamic table of contents, while replacing legacy overrides with modern equivalents. All changes will be supported by clear documentation and implementation guide for future contributors. The project will also resolve all related open issues, including long-standing bugs and enhancement suggestions tied to the adapted components.

PyZombis is a dynamic community course designed to teach Python to Spanish-speaking individuals, inspired by the Brazilian MOOC, Python para Zumbis. Delivered entirely online, PyZombis eliminates the need for users to install Python on their local machines or manage server configurations. However, the current implementation relies on Brython for executing Python within a browser environment, leading to inherent limitations. Certain functionalities, non-native Python modules, and C-built Python modules pose challenges for interactive learning experiences. The proposed solution aims to enhance PyZombis's interactivity and usability by addressing these limitations. The primary focus will be on PyZombis and the RunestoneComponents repositories. Key objectives include: Introducing a PyScript component to facilitate advanced exercises, enhancing interactivity and skill development, Implementing a Tkinter wrapper to enable browser-based execution of exercises, removing dependency on local installations, Enhancing user engagement through the implementation of a new user interface, fostering an immersive learning environmen, Strengthening the educative platform by integrating end-to-end playwright tests, ensuring reliability, and addressing pending issues for continuous improvement, Implementing stretch goals and overhauling documentation to further enrich the learning experience and accessibility. By addressing these objectives, the proposal aims to elevate PyZombis into a comprehensive and interactive learning platform for Python enthusiasts within the Spanish-speaking community.

The current validator of component model inside of WasmEdge only check nested module and ensure VM can run the nested modules without problem, but the validations from component model are mostly skipped. Expected Outcome: 1. One should create a workable (merged into upstream) implementation of validator by working on 2. include/validator/validator_component.h 3. lib/validator/validator_component.cpp 4. The visitor pattern are already setup. Recommended Skills: Since component model proposal separate their validation spec, one should able to find requirements from https://github.com/WebAssembly/component-model/tree/main/design/mvp

Jaeger (https://www.jaegertracing.io/) is an open-source, distributed tracing platform designed to monitor and troubleshoot microservices-based systems. Jaeger-UI is the web UI for Jaeger, built with React (https://react.dev/) . The current version of React used by Jaeger-UI is v18. This project aims to upgrade Jaeger-UI to React v19, in order to stay up to date with the dependencies. Expected Outcome: A working version of Jaeger-UI upgraded to React v19, with all the features and functionality of the current version. This may include a need to upgrade or replace some other dependencies that may not be compatible with the latest React.

<p>Connected components algorithms are used to analyze graph and solve problems (like 2-satisfiability problem). There are three parts of connected components algorithms in the Boost Graph Library (BGL),</p> <ol> <li>Connected components algorithm.</li> <li>Strongly connected components algorithm.</li> <li>Biconnected components algorithm. </li> </ol> <p>I am proposing to add those BGL functionalities to pgRouting during this GSoC period.</p>

A language server is what makes it possible to rich editing like to go to definition or code completions in source code editors. The Solang Solidity Compiler does have a language server, but it is very rudimentary. The aim of this mentorship is to make the language server much more complete, will make developing Solidity code using this language server will be a much greater developer experience. During this mentorship you will learn how language servers work, and you'll need to walk the parsed Solidity abstract syntax tree in various ways to for example find where a variable is defined (Go to definition), or to find all usages of a variable (Find all references), or find the type definition (Go to type definition). This means walking a complex data structure, and understanding how source code is represented as a abstract syntax tree, which is the result of parsing and semantic analysis, the first stage of an compiler.

This project enhanced Gradle Build Server for Android development by implementing composite build support, improving Java Home handling, and providing support for Android Java projects. These enhancements significantly improve the development experience for Android developers using Text Editors/IDEs that utilize the Build Server Protocol (BSP). By bridging the gap between Android Studio and Gradle Build Server, this project contributes to a more productive development workflow. This is a start to let developers benefit from the powerful capabilities of Android Studio within their preferred development environments.

Jaeger UI is built on React. While we are seemingly already on v18.x of React, the upgrade was not done across the board and some other dependencies are still lagging behind, e.g. `"@types/react": "16.8.7"`. It's also blocking upgrades of other dependencies. This project is likely to involve a substantial amount of code contribution, as certain upgrade require fixing the code to use the new APIs, and sometimes we may run into dependencies that are EOL and need to be replaced altogether. - Expected Outcome: Ideal outcome is to have _all_ dependencies upgraded to the latest versions (with the help of @dependabot) and fix all deprecation warnings during the build. But incremental progress towards that goal is also acceptable.

Devfiles are YAML files that define development environment running in the cloud. The main part of a Devfile is the components section and specify the containers required to code, build and test an application. Some components, such as those to code and build the application, need to be deployed as soon as development environment is provisioned. Others instead are supposed to be started later, usually when a command is triggered by the developer to test the applicaiton she is working on (a database for example). The current definition of the latter type of coponents is complicated and not self explanatory. The goal of this project is to add a new component field to specify if the component should be included at startup or not.

Description: [TestGrid](http://testgrid.k8s.io) is the test visualization tool attached to Prow to collate and display historical test results for the k8s and k8s-adjacent Expected Outcome: Create Lit-based view components for TestGrid (summary, index, etc.) that display data from the API. Implement Jasmine and Storybook testing for these components.

Now KubeVela's VelaUX uses two kinds of Database to store metadata: Kubernetes ConfigMap and MongoDB. As more users are expecting using different kinds of database. We proposing to expanding multiple database drivers for the VelaUX API server. - Expected Outcome: The outcome of this project will be expand two more database driver for KubeVela VelaUX API server:

<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>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>

The Kubeflow SDK gives AI practitioners a clean Python interface to submit, monitor, and manage distributed training jobs on Kubernetes via TrainerClient. However, LLM-based developer tools currently have no standardized way to access this runtime context — they cannot see a TrainJob's status, stream its logs, or reason about why a job failed. This project extends the existing MCP server MVP (tracked in kubeflow/community#936) for the Kubeflow Trainer SDK. The goal is to deliver a production-ready MCP server that exposes the full TrainJob lifecycle through well-typed, LLM-accessible tools — enabling AI assistants to actively help developers debug, monitor, and operate their Kubeflow training workloads in real time.

<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>