Explore Projects

Current driverless print servers can be complex and resource-demanding in large part since they only run on full-scale operating systems like Linux. This project aims to port the different elements of OpenPrinting's printing stack (CUPS, libcupsfilters, etc.) to the Zephyr OS for simple future print server development on embedded devices. This will consist of systematically adding Zephyr modules and commits to the OS itself for each part of the printing stack. Importantly, Zephyr replacements and ports must also be used instead of the current Linux dependencies. This leads to further investigation into the capabilities of the Zephyr OS to support technologies such as Ghostscript and print buffering. Lastly, the stack must be tested on hardware to verify functionality and view benchmarks such as power consumption.

The proposal deals with the problem of the creation of a kubectl plugin for Armada, the creation of the desired plugin will allow users to communicate with Armada via kubectl. The solution this proposal provides is that in order to create a plugin for kubectl we need the help of armadactl i.e. command-line utility for Armada through which users submit their jobs to the Armada server. To develop a plugin for kubectl, we first must develop a base plugin for armadactl in Go that performs basic tasks such as submission and cancellation of jobs, creation of queues, etc. After the necessary coding for the plugin is finished, we now distribute that plugin over at Krew so that it is globally accessible. Once it is distributed at Krew, a user can install this plugin as a kubectl plugin and can interact with the Armada server and perform the aforementioned tasks.

<p>This project’s objective is to add an SSH proxy for the Cowrie (<a href="https://www.cowrie.org/" target="_blank">https://www.cowrie.org/</a>) honeypot. Currently, Cowrie emulates an SSH server using Python, and provides proxy functionality only for SSH exec commands, but no interactive terminal sessions. In this project we expect to implement the logic to <strong>forward SSH protocol messages</strong> from clients into backend SSH servers, thus allowing for <strong>full-fledged terminal sessions</strong>, and converting Cowrie into a <strong>high-interaction honeypot</strong>. Our proposal includes the addition of a <strong>backend management module</strong>, which will handle the virtual machines where commands received by the proxy are executed.</p>

This proposal aims to accelerate FreeBSD’s boot process by using the TSLOG framework to identify and target specific delays. Initial profiling revealed significant slowdowns caused by unnecessary sleep intervals in disk detection, timeouts in AT keyboard controller resets, and prolonged waiting in IPv6 configuration and the boot menu. The project will set up controlled test environments, apply targeted code modifications (including ZFS adjustments and adopting approaches from Linux), and iteratively validate improvements through repeated profiling. By systematically optimizing each boot phase while ensuring system stability, the project intends to deliver measurable reductions in boot time, ultimately benefiting the FreeBSD community through faster system reboots and a replicable methodology for future performance enhancements.

The NeoWarm swaddling device and NeoRoo mobile app have been developed to support Kangaroo Mother Care/Skin-to-Skin care for premature newborns and automatically collect vital signs information. The aim is to overcome the barriers to implementing KMC/STS and improve care for premature babies. The technology includes features such as automated monitoring of vital signs, alerts for abnormal readings, and shared goal-setting for education and discharge planning. To enhance the usability of the NeoRoo app, a participatory design study with A/B prototypes is being conducted, to improve the app's UI based on feedback. My rule is to implement the enhanced UI in Flutter and integrate the new UI with the DHIS2 backend server to ensure that the UI interacts seamlessly with the underlying logic and functionality provided by this server.

This project focuses on enhancing and improving the Chaos Center code base, specifically redesigning the Chaos Workflow APIs to provide an enhanced user experience. The main objectives include refining the functionality of the Chaos Workflow and Workflow Run APIs, modularizing the chaos-workflow package into separate packages, and addressing security vulnerabilities and golangci-lint issues in the Chaos Center backend components. The project aims to deliver a more robust and secure Chaos Center platform, offering improved usability and performance for users. - Expected outcome: The outcome of this project will be improved functionality, security, and usability of the chaos workflow GraphQL APIs and chaos-center backend components through the implementation of new features, refactoring of existing code, and addressing of security vulnerabilities.

<p>loklak is free software hosted on loklak.org which provides message search results from twitter in json format. loklak is a complete search engine back-end solution with a json api. Loklak’s API can be used to build twitter clones and client alike, one of them being loklak.net. One of the main features that’s pending in such a tool is the ease of adding angular micro services and modularizing the existing application to run on micro services. Alongside the data store of loklak is magnificent and provides the ability to build IoT platforms using the loklak server. In this proposal I would like to enhance the service architecture of loklak.net and build a proof of concept IoT application demonstrating the capabilities of the loklak server.</p>

This project aims to develop a Text-based User Interface (TUI) framework for Dart, addressing the lack of a structured way to build interactive terminal applications in the language. While Dart excels in GUI development with Flutter, it lacks a robust solution for TUI-based applications. This framework will provide essential UI components, efficient rendering, and event-driven input handling, enabling developers to create modern, cross-platform terminal applications. Key deliverables include a modular TUI library with core UI components, theming support, optimized rendering, comprehensive documentation, and real-world examples. This project will expand Dart’s capabilities beyond mobile and web, making it a viable choice for terminal-based development.

<p>Creating a Joomla 4.0 frontend template will be much easier by using an intuitive page builder. With this, users can desire the position of elements by a grid, buttons and drag'n'drop and select the information these elements should display. For a faster development the JavaScript framework Vue.js will be used, which provides a strong base for creating reactive components. The plan is to have one month for building the page builder and one for the implementation in Joomla. Final tests, integration and documentation is part of the third month. Years of experience in component, backend and frontend development helps to understand Joomla. Git and JS were part of past projects too. So let's give Joomla a page builder out of the box and give every user the possibilty to build customized templates.</p>

<p>Currently gatsby-source-plone plugin is unable to update,update, delete and create node after fetching data from plone site unless GatsbyJs development server is manually restarted or GatsbyJs site is rebuilt. This project plan is to enhance existing project "gatsby-source-plone" with features that allow "gatsby develop" development server to provide up-to-date instant live previews of pages that contain data from a Plone CMS source. Plone is an enterprise open-source CMS solution written in Python. The aim is to enhance "gatsby-source-plone" to provide a GatsbyJS development experience matching the experience provide "gatsby-source-filesystem" based plugins, which can create, update and delete nodes on from filesystem events.</p>

Metaflow's metadata service returns unbounded JSON for every list endpoint. A single GET /runs on a production deployment returns megabytes of data the caller immediately discards. For AI agents, this is worse: a failure-diagnosis workflow generates 2,021 HTTP calls to check 1,000 tasks. This proposal adds cursor-based pagination and server-side tag filtering to the metadata service (prototyped in PRs #9 and #10, 65 tests passing), integrates pagination into the Python client SDK, and builds agent-friendly query utilities that, across five common agent workflows, collapse 11,828 API calls into 16. Server-side work is already prototyped. GSoC starts at hardening, not greenfield.

Vitess uses arewefastyet to automatically benchmark its codebase and ensure no performance regression is introduced. This tool benchmarks Vitess every day, and is used to visualize the results of those benchmarks. It is an important tool in the development cycle of Vitess and is used by its maintainers and adopters. Arewefastyet' website has changed quite a lot over the last year, we want to continue improving it by finishing the migration to TypeScript and by using Shadcn components. Moreover, we want to make the website responsive and have a proper Figma that serves as a reference for current and future contributors. Expected Outcome: The mentee is expected to produce a Figma with the design of the website that will be co-authored with the mentor. Re-vamp most of the pages using Shadcn and the design defined with the mentor at the start of the internship period. Add type information for all/most components using TypeScript.

YCbCr is a color space used in video and digital systems to express color, where Y is the luma component and CB and CR are the blue-difference and red-difference chroma components respectively. This project aims to add YCbCr support to the Nouveau Vulkan driver (NVK), which opens the way for support for more applications and is also an important step towards Vulkan 1.1 compliance. Work on this project is split into 4 phases; first investigation and reading up the relevant parts of the Vulkan specification and the open-sourced NVIDIA hardware headers, second the actual implementation and coding, and finally the third and fourth stages being verification and review where I verify that the implementation is working and conformant, and fix any issues that pop up. All this would then be followed by a merge request implementing and enabling YCbCr support in the driver.

Title: Generic Gizmo System for Graphite Problem: Graphite currently has 6 separate shape-specific gizmo handlers (Circle, Star, Polygon, Arc, Grid, Spiral), each with duplicated code for hover detection, drag handling, and overlay rendering. Solution: A unified, data-driven gizmo system with three components: Registry — Declarative mapping of node parameters to gizmo types Generic Gizmos — Reusable components (Slider, Dial, Angle) that work with any compatible parameter Manager — Auto-instantiates gizmos based on registry lookup Deliverables: 3 generic gizmo types (SliderGizmo, DialGizmo, AngleGizmo) All 6 existing shapes migrated to the new system Old handlers removed, reducing code duplication Developer documentation for extending to new nodes

In recent years, FOSSology's REST APIs have expanded significantly, enhancing user accessibility, flexibility, and automation. However, the development is not yet complete, prompting some users to resort to mocking WebUI access solely for information retrieval. With the development of FOSSology's new React UI also underway, robust support for REST APIs becomes imperative. This project aims to finalise the development of FOSSology's REST API by exposing any remaining endpoints, enhancing and upgrading existing ones to V2, increasing test coverage, and improving documentation. The approach involves a comprehensive review of each module to ensure the availability and exposure of required APIs for frontend consumption. These efforts will streamline development workflows, enhancing the overall usability of the FOSSology platform and facilitating the development of the new React UI.

This proposal is about adding IPP-Scan support to go-mfp, OpenPrinting’s Go toolkit for multi-function printers and scanners maintained by Alexander Pevzner. Right now, go-mfp has solid IPP support for printing and a full eSCL implementation for scanning (WS-Scan is also being added). But there’s no IPP-Scan support yet, and that’s a gap. IPP-Scan (defined in PWG 5100.17) is the open standard for driverless scanning over IPP. It’s what Scanner Applications need to move away from the current eSCL-based approach. I’m proposing to build both a client and a server for IPP-Scan - the client for testing PAPPL scanner apps, and the server as a reference implementation that will also help with developing a future SANE backend for IPP-Scan.

<p>Multithreaded programming is becoming a mainstream programming practice, while multithreaded programming is difficult and error prone. jpf-trace-server, an extension of Java PathFinder (JPF), can store and analyze traces. The error traces caused by deadlock can also be viewed in a new shell panel from jpf-shell.</p> <p>In this project, we will develop jpf-trace-server to trace the execution of the threads and to provide feedback to the programmer to help them fix the bugs. Inspired by previous work on visualization in JPF, we would like to show the thread interleavings as traces in a new panel of jpf-shell. We would like to show the source code in the panel along with the transition information. The users should be able to walk through each transition of a selected error trace and the corresponding source code where it is executed.</p>

This project aims to integrate visual testing into the Kolibri Design System's (KDS) CI workflows to streamline the validation process for UI modifications. Currently, KDS lacks a visual testing service leading to manual effort in validating UI modifications. Leveraging tools like Puppeteer and Percy, the project proposes to automate the process of capturing and comparing screenshots of UI components before and after modifications, ensuring consistency and correctness. Key deliverables of the project are: 1. Integration of Percy into the existing Jest test suite, 2. Implementing visual testing for at least one UI component, 3. Establishing a mechanism for surfacing visual differences in pull requests. This will help enhance the efficiency and reliability of KDS development, fostering a consistent and polished user experience across Kolibri products.

<p>The aim of this project is to allow users to quickly edit the content of different components and modules of their websites without having to leave the front-end or going to a different page. This will save time when small changes need to be made. Normally if there is a typo on the page, one has to first check whether it is in the article's heading, its content, module title, module's content, banner, etc. And then open the corresponding edit page of the component.</p> <p>Upon the completion of this project, it will be much easier to edit the text of almost any part of the website. This project will also be helpful when the user wants to see the end product while modifying the page.</p> <p><strong>To conclude, we want to minimize the use of pop-ups and page-reloads involved in editing the content.</strong></p>

In SageMath, tensors are presently stored within the Components class as a dictionary, with each key representing indices and values indicating the tensor's corresponding values. This project seeks to advance tensor handling within SageMath by leveraging Python libraries such as PyTorch, NumPy, and SymPy. The primary objective is to develop classes similar to the existing Components class and its subclasses, storing tensors as numpy.ndarray and torch.tensor objects. This change promises memory-efficient storage of tensors and performance enhancements in tensor operations. Additionally, methods like sympy and sympysage_tensor will be implemented to streamline tensor porting between Sage and SymPy. The project's development stages will include code implementation and modification, testing across a variety of inputs, comprehensive code documentation, and building robust tests to ensure functionality and reliability.

As of now, Kanidm doesn't provide a way to allow two users to mutually authenticate each other. I would like to design and implement such feature, building upon and further polishing the design already discussed between the maintainers and me (see pull request #1416). The idea is to use ECDH to compute a unique TOTP for each user, make the users exchange said TOTPs with an out of band channel and then verify if they are correct, with no online communication required between the involved kanidm servers. To begin with I'll have to implement a feature that allows kanidm to store ECDH keys for its users, as they are required for the Identity verification system to authenticate subjects. Afterwards I will work on the core server-side logic of the system, and finally, if time will allow it, I am going to implement a frontend interface in the kanidm client for the identity verification system. I also plan on writing a journal of my experience with this project.

<p>This project aims to improve Ceph’s Python infrastructure, making the codebase clean, modern, and maintainable. A major part of this improvement would be migrating to advanced Pythonic idioms and porting all the components written in Python 2 to the new, and more feature-rich Python 3 version. This will be done while also maintaining support for Python 2 using a project-wide compatibility layer.</p> <p>With Ceph’s growing codebase and complexity, it is imperative to structure the Python code into independent packages for easy maintenance. The build system of Cython bindings for Ceph libraries like RADOS, RBD, and Ceph FS will be improved, making them ready to be deployed to PyPI. Some other open-ended goals of the project are to refactor and rewrite components of Ceph which have seen very little maintenance in the past.</p>

<p>Project Goals</p> <ul> <li>Since most of the app is built using Flutter, we should make full use of it and make the app support iOS devices as well.</li> <li>The app can be of more use if we add a section that will act as a Social Media Platform for Travellers.</li> <li>The Business-Logic/API-calls and the UI part of the app needs to be separated in the right way. Right now, All the API calls are made from the UI class itself.</li> <li>The UI/UX of the app also need improvements, especially the Profile and Intro screens. And the app also lacks some basic features like Form validation, Profile Picture selection during the Registration process, Using Gallery as a Source for the image at the time of Monument Detection etc.</li> </ul>