Explore Projects

AsyncAPI is an open-source initiative that seeks to improve the current state of Event-Driven Architecture (EDA). It has a set of tools for documentation, code and model generation, event management, etc. which helps to easily build and maintain EDA. The AsyncAPI Website is the primary source of information for users and developers. Currently, the website lacks visual consistency, repeated elements lack consistency in design, and duplicate styling is used for similar visual styles. This makes the codebase and design non-modular. Existing UI patterns are undocumented which results in miscommunication and re-inventing the wheel instead of building new features. The goal of this project is to develop a comprehensive UI Kit that can enhance the existing design, and streamline the development process to simplify the creation and management of cohesive elements in the website. This website UI Kit will help in preventing the process of rebuilding similar components.

<h3>Production ready and fully optimized CarbonFootprint app with additional features for Android and iOS</h3> <p>CarbonFootprint app is almost ready to be deployed in App store and currently it is in beta testing phase in Play store but there are much scope of optimization to make the workflow of the application smoother and to provide a better user experience. My main goal for this summer is to build the final production ready app for both Android and iOS and deploy them using Fastlane. iOS counterpart of the project needs to be updated with the Android part. Optimization of the app by reducing third party modules, checking memory leakage and improving testing feature for the app is one of my main goal. I would focus on improving the performance of the application by making code changes and using react hooks in our project. Additionally, I would implement new features like Password strength checker, Crashlytics and Email verification.</p>

A lot of work has been done to parallelize the Rust compiler frontend, with notable success in code generation and some post-HIR lowering stages. Other critical components, such as lexical parsing and macro expansion, are still implemented serially. Macro expansion is fundamental in Rust, enabling code generation at compile-time based on patterns and user-defined rules in the source code itself. However, due to dependencies between macros and the strict ordering of name resolution, its inherently sequential nature poses a significant challenge for parallelization. Currently, macro expansion and import resolution are tightly coupled and executed sequentially, making parallel execution difficult. This project aims to develop a parallel and order-independent algorithm for these two processes, improving compiler performance while maintaining correctness. Addressing the dependencies and execution order constraints could significantly reduce compilation time and enhance the compiler's overall compilation speed.

<p>With the introduction of the Web Audio API and music frameworks such as Flocking, it's possible to make music and develop custom instruments entirely using Web technologies.</p> <p>A variety of user interface component libraries, such as Nexus UI, jQuery Kontrol, Interface.js and G200K's Polymer controls, have been developed to assist in the creation of musical interfaces. However, the majority of them aren't very "web-like." Many are based on Canvas or bitmap images, and aren't compatible with responsive design techniques, can't be easily re-styled or customized using tools like CSS, and aren't accessible via the keyboard or with assistive technologies such as a screenreader.</p> <p>This project will involve the creation of a small collection of high-quality, responsive, SVG or DOM-based musical user interface controls such as knobs, sliders, x/y pads, button matrices, envelope editors, waveform viewers.</p>

<p>Intermine is a powerful data warehousing, integration and analysis tool used to store and share genomics data. However, setting up an instance of Intermine is a time consuming and error prone process. It also requires technical knowledge and some familiarity with Java, Postgres and shell scripts. These issues create a barrier for entry and friction in the adoption of intermine by the bioinformatics community. To solve these problems, Intermine team is planning to create a cloud platform that offers managed Intermine instances. This will remove the technical burden from the user and greatly simplify the creation of intermine instances. Also, the work done on Intermine cloud can easily be translated to simplify the creation of Intermines locally. This project forms a part of the Intermine cloud project. It includes packaging of intermine and it’s components in docker containers, cloud infrastructure setup, orchestration of containers, authentication, and authorization on the cloud.</p>

The Genomic Data Commons(GDC) is a free open source system that distributes harmonized cancer genomic data to researchers internationally. Currently, the documentation website provides extra background information and user guides on how to use the GDC. The website content is produced with markdown and is built with a site generator that is becoming outdated. The project is in 2 Tiers: 1. Aimed at Building a site generator or using existing open-source software that can be used to build the website with markdown and doing proper documentation for the generator. The new documentation website is expected to look exactly the same as it does currently. 2. Design new functional parts of the documentation website to improve usability. DELIVERABLES 1. A static site generator that converts markdown to HTML. 2. Proper documentation of the generator. 3. New Functional parts on the documentation website to ease usability. 4. Proper tests for the above-mentioned components.

One pertinent use case of the gcc-python plugin was to provide the infrastructure for cpychecker, a static analysis tool designed for CPython extension modules. The primary objective of cpychecker was to assist programmers in identifying common coding errors in their extensions, which, in turn, could lead to difficult-to-find bugs in their systems. However, the gcc-python-plugin has suffered from bitrot over the years, and as a result, cpychecker ceased functioning several GCC releases ago. The goal of this project is to port the functionalities of cpychecker to a -fanalyzer plugin, offering programmers a reliable tool for conducting static analysis of CPython extension modules once again in a more maintainable manner. The project will be divided into several logical components, such as reference count checking, format string checking, error handling checking, and verification of PyMethodDef tables. Accomplishing this task will involve building a -fanalyzer plugin and extending certain areas of the existing analyzer.

<p>This project is about preparing a dashboard that can show an admin the visual assets of the digital library for each artifact but also add, edit, delete, images using our archival images serve as a source of better quality images to prepare their web counterpart. Access to images should also be managed there (some images are not public).</p> <ul> <li>Develop a dashboard and a series of workflows so admins can manage the digital library (dl)</li> <li>Populate the tables with information from the current dl</li> <li>Keep the system flexible so we can create an extension for crowdsourcing of images in the future</li> <li>Assist in setting up an automated grab of archival and raw images from the VM, to the archival server. These images will have been uploaded through the images manager or the minio interface.</li> <li>Set up a granular access to images at the image level (instead of at the artifact level)</li> </ul>

<p>Services Kit is the backbone of many Internet-based applications on Haiku such as Weather, HaikuDepot, WebPositive and more... This makes the kit one of the more important components in the system, as the majority of the user experience on Haiku is dependent on this kit.</p> <p>However, Services Kit is not without any issues. It's <a href="https://dev.haiku-os.org/ticket/10748" target="_blank">slow by design</a>, doesn't support HTTP/1.1 (which also contributes to the slowness), and may <a href="https://dev.haiku-os.org/ticket/13235" target="_blank">randomly crash on you</a>. All of which don't translate to a decent user experience.</p> <p>My project this GSoC is to dig into Services Kit, iron out annoying bugs, getting rid of the bottlenecks, adding some more features, like FTP support and give it some better documentation so that people outside of the project can make good use of the kit.</p>

<h3>High-performance P4 software switch using netmap</h3> <p>Software switches are a key component of any cloud infrastructure, and even proposal focused on hardware targets, such as P4 (<a href="http://p4.org" target="_blank">http://p4.org</a>), cannot ignore software implementations and their performance.</p> <p>Historically, software packet processors have been limited in performance by network I/O, but this is no more true with high speed frameworks such as netmap and DPDK.</p> <p>In this project I would like to implement a modified version of the reference p4 switch on FreeBSD, which uses netmap for faster packet I/O: the goal would be reaching the 1 Mpps order-of-magnitude speed (current reference implementation is limited to 150 Kpps for a simple l2 switch with 2 hosts).</p> <p>This would enable P4 to be used in fast networking experimens as well as real environments.</p>

<h3>Abstract</h3> <p>Tracing support with annotation-based traces is a promising approach to allow developers to get a view into the performance behavior of Ceph components. Past efforts have used the blkin library to instrument some parts of Ceph's codebase, and some plugins have been created to allow these traces to be visualized in Twitter's Zipkin platform.</p> <p>This project would add value to the Ceph community by extending the tracing capabilities and integrating the Zipkin visualizations in Ceph's continuous integration processes, allowing developers to quickly get performance information after changes or after testing particular scenarios.</p> <p>The objectives would be achieved by performing the following tasks:</p> <ol> <li>Have a well documented and modern implementation of an infrastructure that can generate and visualize tracepoints in Zipkin from Ceph. </li> <li>Integrate the infrastructure into CBT and Teuthology as well as anywhere else the Ceph Community is interested in having it.</li> </ol>

Multigrid methods shape the method of choice when a self containing family of triangulations of a FEM discretization is at hand to achieve an optimal order solver. Optimal order meaning linear complexity in the number of DOFs, which is the same for the assembly of the associated linear system of equations, making this a completely astonishing and non-trivial result of the theory of multigrid methods. But also in applications this outperforms classical, algebraic based, solver routines when it comes to large scale simulations. Although, the flexibility of modern AMG implementations to not require any such structure of meshes, multirgrid methods remain of great interest not only in academia. So an implementation in the dolfinx framework should allow for versatile extensions and applications. To achieve this, multiple components of data structure associated with mesh, geoemtry and topology require close analysis and a fundamentally new feature, the necessary prolongation and restriction operators, need to be implemented. This process is split into multiple isolated, but chronologically dependent phases.

<p>Riak KV is an open source database with a strong focus on low latency, reliability and fault tolerance. Like any well tested computer system, batteries of tests are run to make sure that the database behaves correctly in typical but also adverse conditions such as network partitions, or even the deployment and upgrade process of nodes running different versions in the same cluster. To this end, one of the resources used by the Riak team is <a href="https://github.com/basho/riak_test" target="_blank">riak_test</a>. Its main function is to provide a test running framework that overlaps significantly with Common Test, but it also contains cluster management and code intercept functionalities. We propose to break up this repository into its discrete components, making important contributions to the Erlang community and adapting the test runner framework into Common Test suites, vastly increasing the reporting ability of current Riak tests.</p>

Currently, Talawa has three major software components which are talawa, talawa-api and talawa-admin. Among these, talawa-admin is a web-based portal and talawa is a mobile application whereas talawa-api provides access to user data and features. We also have talawa-docs, which is a website that contains most of the documentation and can be found at “https://palisadoesfoundation.github.io/talawa-docs/”. Currently, the documentation website is being powered by numerous Markdown files which are being rendered into a static website with the help of Docusaurus. The challenge is to find and implement a way to generate documentation (in the form of static HTML files) from comments within the files, which can then be hosted on the site used for documentation. This will enable the documentation to grow organically with the codebase. We target to automate the creation of our documentation using the content of our code repositories on our existing documentation website. This will give Palisadoes the flexibility to maintain its Markdown documentation and its website more efficiently.

GUI: In this part, we aim to build a new GUI for HNN, using the HNN core functions and open source practices, in the form of an ipywidget. Mimicking the current functionality and tutorials in the existing GUI, it will allow users to interactively set the experiment settings and get visualization results presented on the fly. Unlike the traditional HNN GUI, all these functionalities could be used within JupyterLab, making it convenient and friendly to those who prefer to use HNN on servers. This part will also benefit users that need to frequently adjust simulation settings and get real-time results but have little programming experience. CSD: Currently HNN-core provides APIs to record local field potentials from simulations while an API to turn these signals into source density signals is missing. In this part we will implement a series of mainstream algorithms to calculate the CSD and a visualization API that calls them in the backend to visualize the CSD.

<p>PostgreSQL is a famous database management system, widely used by DBAs and with an open source license. There is a large community dedicated to developing and bug-fixing, intensely working through mailing lists.</p> <p>The Performance Farm is an useful way to test Postgres' functionalities while adjustments are being made, to analyse the efficacy of every change on different operating systems. To further support the community effort, this project has been extended building a database and a website on top of it, to make results easier to browse and display.</p> <p>To make this possible, a web application relying on Python has been built to interface server and client. The code provides a benchmark to collect test results, plus an API where they get stored and accessed from the website. The Performance Farm helps developers to understand the performance of different versions of the system, and users to check the functioning of their database, being helpful in terms of usability and accessibility of collected data.</p>

<p>SUSI is an Artificial Intelligence system which apart from having its own Android, iOS, web and IoT clients also offers an extended support for different bot platforms to get integrated. My aim is</p> <ol> <li>To contribute to the server (<a href="https://github.com/fossasia/susi_server" target="_blank">https://github.com/fossasia/susi_server</a>) side implementation of this project by implementing new servlets required and enhancing the existing ones.</li> <li>Implementing a client where users can manage all SUSI accounts (<a href="https://github.com/fossasia/accounts.susi.ai" target="_blank">https://github.com/fossasia/accounts.susi.ai</a>) related issues. Signup, login, change password, reset password, verify account, manage settings across different clients etc. </li> <li>Admin section for SUSI.AI</li> </ol>

The KServe Models Web App is a crucial front-end interface for managing ML models deployed through KServe, a core component of Kubeflow. However, the application has become outdated, with deprecated dependencies and technical debt. This project aims to modernize and enhance the app by upgrading its tech stack, resolving open issues, and implementing a robust CI/CD pipeline with GitHub Actions. Key improvements include regression testing with Cypress, model editing capabilities, and synchronization with KServe 0.14+. Additionally, the project explores migrating the app from kserve/kserve-models-web to kubeflow/kserve-model-ui for better integration. The deliverables include a stabilized, modernized codebase, improved user experience for ML engineers, and streamlined contributor documentation. This effort will reduce operational overhead, enhance usability, and support Kubeflow’s mission of making ML workflows simpler and more scalable.

<p>Traditional rendering is based on the idea that light can be decomposed into three basic components: red, green and blue (RGB). In some areas this is a vast oversimplification of the physical reality; light exists on a continuous spectrum of wavelengths. Spectral rendering achieves better accuracy by taking that into account. The major drawback is that it cannot use widely available color data for surfaces such as photographs. The process of gathering usable spectral data is significantly more time- and resource-intensive.</p> <p>Spectral upsampling is the process of extrapolating spectral information from RGB color data. This is possible because, in practice, spectral reflectivities, which describe how a surface interacts with incident light on a wavelength-by-wavelength basis, tend to fit relatively simple patterns. The goal would be to add support for several newly published algorithms to Colour, a color science library for Python. With the rising popularity of spectral rendering, the library would greatly benefit from the work.</p>

Community-driven Drupal sites currently rely on reactive, manual moderation for spam and toxic content, which is exhausting and difficult to scale. This project introduces a proactive, real-time defense system by building a fully integrated AI Content Moderation module. The solution utilizes a decoupled ContentModerator service that intercepts form submissions on the client side using debounced JavaScript, providing users with instant, WCAG-compliant inline warnings before toxic data ever hits the database. On the backend, it employs a highly performant hybrid approach, checking local administrative keyword lists before securely querying external NLP models (such as Hugging Face) via Drupal's core HTTP client. Deliverables include a production-ready module featuring an intuitive Admin UI for AI provider and threshold configuration, bulletproof server-side validation fallbacks, and comprehensive site builder documentation.

This ongoing “Sailing Downstream” project strives to transform the salient content from within the RISC-V Sail specification into a more accessible format, JSON, that downstream projects can easily and automatically transform into the content necessary to their project which is currently produced by manual effort. Project efforts and components span: - Adding to the RISC-V Sail specification information necessary for the various downstream projects. - Improving the RISC-V Sail specification so that the salient information can be easily identified and extracted. - Enhancing an existing Sail “JSON backend” to extract salient information completely and accurately and produce that information in a usable JSON format. As the end goal is to enable automatic adoption of changes, enhancements, and new content of the RISC-V ISA into downstream projects, efforts can be made to provide example implementations of such transformations to inform engagement with select downstream projects for adopting new automated processes.

The Checkpoint-Restore Operator manages checkpoint retention well but has no way to create checkpoints automatically. This project adds a new CheckpointSchedule CRD and controller that triggers checkpoint creation through four mechanisms: cron-based time schedules, CPU/memory resource thresholds, Kubernetes cluster events (node drain, pod eviction, preemption), and pod annotations for application-level signaling. All triggers call the existing Kubelet Checkpoint API via the Kubernetes API server proxy. Deliverables include the CheckpointSchedule CRD, a CheckpointCreator that calls the Kubelet API, four independent trigger subsystems, a TriggerManager to coordinate them, a full controller-runtime reconciler, RBAC updates, unit and BATS integration tests, and sample configuration. Together with the existing retention policies, this turns the operator into a complete checkpoint lifecycle manager — admins declare both when checkpoints are created and how long they are kept, with no custom scripting required.

The LibreOffice BASIC IDE currently offers limited code assistance, hindering developer productivity with unreliable completion, no object browser, and no inline help (parameter/quick info). This project will implement a modern, comprehensive code assistance system. This involves creating [1] a robust backend analysis engine to parse BASIC code (editor/libraries) and introspect UNO objects for detailed symbol information (types, scopes, signatures), and [2] an efficient knowledge cache. These components will power [3] user-facing tools including: an integrated Object Browser for API exploration, significantly improved context-aware code completion (Ctrl+Space and enhanced '.'), and helpful Quick Info/Parameter Info tooltips. The final deliverable will be these features fully integrated and enabled by default, delivering a significantly more productive and intuitive BASIC development experience in LibreOffice.