Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<p>The purpose of the project is to implement asynchronous lifecycle events for libvirt’s storage API. Lifecycle events allow applications to get notifications about the state of the object, as well as for object creation, deletion etc, without having to pull libvirt at regular intervals asking for the state of the VM. This implementation will also include adding support to virt-manager for storage events. Also, part of the project is extending event-test.py from libvirt-python to watch for storage events and print messages about them, as well as add asynchronous event support for nodedev objects. Also extending the python API for the implementation in virt-manager and libvirt-python. After the implementation of the storage API, project includes implementation of asynchronous event support for nodedev objects, followed by extending the python API, implementation in virt-manager and in libvirt-python. When this part is finished, I'll continue working on nodedev, and add event support for udev and netcf drivers.</p>
<p>Computational models of biological systems play an important role in advancing science as they give insights about the biology without the need for performing real experiments. A significant challenge in the systems biology field is the reproducibility and reusability of such models and making these accessible to the broader biology community. To address this issue, computer-readable formats and tools for modeling complex biological systems have been developed. Standards such as Simulation Experiment Description Markup Language (SED-ML) and tools like Systems Biology Simulation Core Library (SBSCL) can represent such complex biological models and numerically simulate them. But until now only a subset of these standards have been implemented in SBSCL. Essential features that will catalyze reproducibility, exchangeability, and reusability are lacking so far. Namely, i) implementation of full support for simulation experiments; ii) plots and visualization of simulation studies; iii) support for standard archive formats; iv) support for Open Source solvers, and v) support for hierarchical models.</p>
<p>Boost is one of the most fundamental collections of C++ libraries, powering thousands of projects, but also driving the development of C++ best practices and C++ standards. Boost.Multprecision is the Boost library providing number types with precision higher than that of C++ built-in types. The library offers support for integer, floating-point and rational data types at compile-time fixed, arbitrary and variable precision.</p> <p>Currently, many operations are already supported for arbitrary precision, but tests exist only for up to 1024 bits. The purpose of this project is to 1) extend testing for precision of thousands of bits and 2) add arbitrary-precision support for more complicated functions and constants. This includes adding tests for arithmetic operations of higher precision, extending tests for simple functions, extending special functions to higher precision, adding support for higher precision constants (and adaptive precision algorithms) and optimising several of the operations (see Milestones for details).</p>
<p>Aim is to develop a Page Builder interface for frontend part in styles section using VueJS, with a Drag and Drop GUI for module positions. Using Bootstrap Grid System to make it easier to design web pages which would be responsive on all screen sizes. User will be able to fully customise the site template style, using interactive area to</p> <ol> <li>Drag and Drop module position box.</li> <li>Reordering/changing position Bootstrap classes based on input.</li> <li>Select module chrome for each position.</li> <li>Resize different positions, by changing BS classes. eg- <code>col-sm-3</code> to <code>col-sm-4</code>.</li> <li>Add new module position.</li> </ol> <p>Updating "params" column in <code>#_template_styles</code> and implementing page renderer in index.php to preview the style based on JSON input from "params"</p>
This proposal is based on the LLVM project for GSoC 2026 with the same title, from Tue Ly, Nicolas Celik and Krishna Pandey. Discourse: https://discourse.llvm.org/t/gsoc-2026-libc-enable-float80-and-float128-math-support-on-unsupported-targets-for-llvm-libc/89647. Float80 (x87 80-bit extended precision) and Float128 (IEEE 754 binary128 quad precision) are high-precision floating-point formats critical for correctly rounded math implementations. However, not all compilers or architectures support these types natively which prevents LLVM libc from building and testing its high-precision math routines on these platforms. The goal of this project is to implement software support for these types in LLVM libc in a compiler and architecture agnostic way. Deliverables: - Implement float80 and float128 in a compiler and architecture agnostic way. Implement generic basic arithmetic operations that work on all supported architectures. - Demonstrate compiling and passing tests on unsupported targets (float80 on Mac ARM64, float128 on MSVC).
<p>With the development of software container technology, developers can manage and deploy their software effectively. The software can start up and run on the container more and more quickly. The Dockstore is a platform for users to share tools encapsulated in Docker. Furthermore, in order to share tools as seamlessly as possible, GA4GH create a set of APIs for the biology scientists. In this project, I would like to make the Dockstore support these APIs. In this way, people can create their tools based on the APIs so that their tools can be work with others’ tools seamlessly. It will absolutely help the cooperation between scientists due to they can create their tools based on or cooperate with others’ more easily. Our project has three main goals. The first is to communicate with GA4GH community so as to decide the APIs standard and their implementations. Then, I need to implement and test these APIs with java so that the Dockstore can support the APIs. The last goal is realize cross indexing of tools across all sites that support the standard. When finish cross indexing, Dockstore can search all the tools from all websites which support the standard.</p>
<p>Recently, there has been a lot of interest in the research community (IRTF / IETF) towards parallely implementing and standardizing a new TCP extension called TCP Prague, which is targeted to be an evolution of Data Center TCP (DCTCP). DCTCP starves the throughput of other TCP flows (e.g., Reno, Cubic, etc) when they co-exist; so one of the goals is to ensure that TCP Prague can co-exist with other TCP flows without degrading their throughput. Although TCP Prague is still a work in progress, some related modules have been finalised and briefly experimented, such as: the Low Latency, Low Loss, Scalable throughput (L4S) service architecture, DualQ Coupled AQM, Modified ECN Semantics for Ultra Low Queueing Delay. Availability of these modules in network simulators like ns-3 is crucial to boost up the ongoing efforts of standardizing TCP Prague. In this project, the aim is to implement the above mentioned modules in ns-3. Additionally, the functionality of these modules will be tested, and the necessary documentation with some examples will also be provided.</p>
<p>This project aims to extend the collection of fonts supporting Greek script in the Google Fonts Catalog. Indeed, today 35 typefaces supporting Greek script are available. Moreover, only 2 fonts are explicitly intended for display text.</p> <p>Arima Madurai is a font created by Natanael Gana and Joana Correia of NDISCOVER. It is a multiscripts display font with 8 weights from thin to black and have a strong calligraphic influence. It has a lot of personality so it can be recognisable in headlines or brand names uses. Regarding the history of Greek script, it is both interesting and challenging to design a typeface with a calligraphic feel: in terms of design but also in terms of study.</p> <p>Arima Madurai already supports Tamil, Malayalam and Latin scripts and I would like to add Greek extended script to the glyphset. The fact that the font already supports multi scripts is a real benefit to the project: Arima Madurai already acts in non latin typographic environment and therefore displays a large set of shapes that can be used to match the Greek glyphs with the other ones.</p>
The Volcano Dashboard serves as the frontend for displaying Volcano resources. Currently, it supports resources like Volcano Jobs, Queues, and Pods, but editing often involves raw YAML, which is not user-friendly for modifying or creating new resources. To improve user experience, this project aims to enhance the Dashboard's interactivity and user-friendliness, as well as support the display of hierarchical Queues and HyperNode resources. Expected Outcome: 1. Improve resource display and editing interfaces by providing more user-friendly interaction methods, such as using forms or visual editors instead of direct YAML editing for creating and modifying resources. 2. Support the display of hierarchical Queues and HyperNode resources with mouse-click expand/collapse functionality to clearly visualize resource relationships. 3. Optimize the user interface design to enhance aesthetics and ease of use. 4. Refactor the backend code to improve maintainability and scalability. 5. Display both key information and full information for resources, with an option to switch between views. 6. (Optional) Support the display and management of more resource types.
NanoBSD has long provided a reliable framework for building embedded FreeBSD images, but its legacy pipeline remains monolithic and resource intensive, source based workflow. This project modernizes the NanoBSD image creation process by allowing decoupling of the build and assemble phases using pkgbase which is a package-driven assembly model. Furthermore by using tools like makefs, mtree, and mkimg, the new pipeline will enable fast, reproducible, and cross-architecture image generation without requiring root access. The key deliverables will include - PkgBase Integration into the current NanoBSD image creation pipeline, modernize the Boot support by implementing GPT layouts and UEFI booting for both x86 and aarch64 (ARM). The project will also focus on providing tier 1 support for Aarch64 devices. Also if time allows the support for ZFS filesystem will be added in the NanoBSD image with various eMMC storage optimizations to increase the life of those class of storages. Along with the support for automated first boot configuration will also be implemented using nuageinit.
Git's partial clone allows cloning repositories without downloading all objects (blobs, trees, ...). These objects are fetched on demand from the remote when needed. However, when a user needs metadata about these remote objects (size, type, hash, ...), Git has no efficient way of doing this without downloading all the object content. The server side support for `object-info` protocol was implemented by Calvin Wan in 2021. Eric Ju built the client-side `remote-object-info` for `cat-file --batch-command`. This project finishes Eric Ju's work on `remote-object-info` for `git cat-file --batch-command`, resolves the pending feedback from Junio Hamano and Jeff King, and extends support for `%(objecttype)`. The main technical fix is to replace the insufficient `strstr()` format validation with an `allow_list` to prevent crashes on unsupported placeholders, and extending the v2 protocol server and client to handle `%(objecttype)`. After the project, Git will have a working `remote-object-info` for `cat-file --batch-command` supporting `%(objectsize)`, and a v2 protocol extension adding `%(objecttype)` support on both server and client, with tests and documentation.
<p>Knative is an extension of Kubernetes and is specifically designed for serverless workloads. Knative Serving, as one of the core components of Knative, runs scalable containers based on ingress gateway as its network layer to route traffic and control the flow of API calls. Currently, Istio is the default ingress gateway of Knative Serving. Other community-based gateway implementations such as Kong and Gloo are also supported.</p> <p>APISIX, a dynamic, real-time, and high-performance API gateway, comes with an ingress controller which can be used in Kubernetes. The ingress controller of APISIX, however, has no support for Knative. This limits its use scenarios. This project aims at providing support for APISIX for Knative. Main tasks include</p> <ol> <li>understanding the mechanism of Knative Serving and APISIX ingress controller.</li> <li>Implement support for APISIX as Knative ingress gateway</li> <li>Writing tests documentation, or articles for the newly added feature</li> </ol> <p>As a result, APISIX ingress controller will be an alternative Knative network layer to manage ingress traffic.</p>
<p>The objective of this project is to add processor support and a board support package (BSP) for the ARM Cortex-M4F microcontrollers on RTEMS. In addition, I will be adding an ethernet driver and lwIP for networking, and console and clock ticks support for the BSP.</p>
Swarm external secrets project enables Docker Swarm services to consume secrets from external secret managers, but it still lacks several features needed for secure and production ready deployments. At present, some providers rely on older credential models, transport security can be improved, and support for newer secret backends and modern authentication workflows is limited. This project aims to close those gaps by making the plugin more secure, extensible, and operationally reliable. The proposed work will focus on adding modern identity-based authentication methods such as JWT and OIDC flows for Vault and related providers, improving TLS and mTLS support with better CA bundle handling, and strengthening secret lifecycle support such as version awareness and rotation compatibility. In parallel, the project will expand provider support by integrating additional backends such as 1Password, Doppler, and Infisical. The deliverables will include secure authentication improvements, stronger transport security, new provider implementations, improved tests and documentation, and better observability so that swarm-external-secrets becomes a more enterprise-ready secret management solution for Docker Swarm.
<p>Currently LabPlot has some support for the plotting of live data, which can be read from file/named pipe, TCP socket, UDP socket, local socket and serial port. The goal of this project is to provide support for the plotting of data received via MQTT protocol from a certain broker. LabPlot currently doesn’t provide any support for MQTT, even though it would be quite important for LabPlot to provide this kind of support, since it is a scientific data plotting software and MQTT protocol is widely used to transmit certain sensor data.</p> <p>This project would increase LabPlot’s usability regarding analyses of scientific data, monitoring data collected by sensors, that is transmitted by MQTT protocol, or even make LabPlot usable in the field of Internet of Things or Smart Home Appliances.</p> <p>The project would involve extending LiveDataSource class, ImportFileWidget, LiveDataDock and AsciiFilter in order to set up a connection with a MQTT broker based on information provided by the user. Then LabPlot could receive and handle MQTT messages, save and plot the data transmitted by them. Already existing functionality for other types of live data source will be adapted to this protocol as well.</p>
OpenMRS lacks a printable visit summary, forcing patients to verbally relay medical history during referrals and care transitions. This project adds a Visit Summary PDF generator to the existing openmrs-module-patientdocuments module, reusing the proven Patient ID Sticker pipeline (DataSetEvaluator, XML Renderer, Apache FOP). The backend gathers visit-scoped clinical data (vitals, diagnoses, lab results with reference ranges, allergies, medications, visit notes) via batch queries, renders it as XML, and transforms it to PDF through XSLT. An extensible VisitSummarySectionProvider SPI allows any module (billing, appointments, pharmacy) to contribute sections without modifying the core module. Configuration uses deploy-time Initializer keys for section toggles, concept UUIDs, and page sizes (A4/A5/A6). The frontend adds a print button in the O3 visit-detail-overview-actions slot with iframe-based PDF preview and download fallback. Deliverables include the complete backend pipeline with all clinical sections, extensible SPI architecture, configurable XSLT stylesheet, REST endpoint with privilege enforcement, frontend print extension, comprehensive tests, and documentation.
<p>In this project, my work will mainly focus on to develop new features for Amahi 12. Amahi is one of the best open-source media server software available right now and is well known for its easy to use interface and functionalities. The "Platform" is the core software of Amahi and it is in development for the last 7 years. Amahi 11 is the latest version of Amahi and it is officially released last year in 2018 and provides support for fedora 27. Amahi 12 is currently in the development phase and will be released soon with support to fedora 30.</p> <p>Main Objectives:-</p> <ul> <li>Improve Platform and implement new features for Amahi 12.</li> <li>Fix existing plugins and provide them support for the latest version of Amahi.</li> <li>Update Dockerfile and create new docker image supporting latest Amahi.</li> <li>Completely implement backend and plugin of friending feature. This will help Amahi users to share files and Shares with other Amahi users with permissions control.</li> <li>Implement let's encrypt feature for Amahi to generate certificates for establishing secure connections with yourhda.com subdomains.</li> </ul>
<p>Soletta has its own implementation of the lightweight machine to machine (LWM2M) protocol. The LWM2M protocol is used to remotely control IoT devices, these include: Firmware updates, status reporting and etc. Although Soletta already implements the LMWM2M Server and the LWM2M Client, Soletta's implementation is lacking some main features, namely: an LWM2M Bootstrap Server, Message Encryption and Data Access Control.</p> <p>The idea is to:</p> <ul> <li>Add support to LWM2M Bootstrap Server on Soletta, as specified by OMA, enhancing IoT developers' choices on how to bootstrap their machine-to-machine devices.</li> <li>Add support to CoAP Message Encryption inside Soletta's implementation of LWM2M, giving IoT developers' an increase sense of security when using LWM2M through Soletta.</li> <li>Add support to Data Access Control, allowing a LWM2M Client to support one or more LWM2M Servers, by determining which server is authorized to perform which operation. The LWM2M specification specifies Access Control Objects to handle authorization, and they will be implemented from scratch.</li> <li>Deliverables include API Code, Internal Code Changes, Unit Tests, Doxygen Documentation and Sample Applications.</li> </ul>
Problem: IP cameras are frequent targets for cyberattacks due to their widespread use and often weak security. Current honeypots like SweetCam lack comprehensive protocol support and realistic emulation, limiting their effectiveness in detecting and analyzing threats. Solution: This project aims to transform SweetCam into a versatile, multi-protocol honeypot by: 1. Expanding protocol support for RTSP and ONVIF, enabling deeper interaction with attackers. 2. Introducing template-based device emulation using YAML to simulate real-world cameras (e.g., Dahua, Hikvision). 3. Improving usability with Docker enhancements, automated configuration, and a realistic HTTP interface featuring error simulation and multi-language support. Deliverables: 1. A production-ready SweetCam with RTSP/ONVIF support and 5+ device templates. 2. Optimized Docker deployment (multi-stage builds, Compose profiles). 3. Enhanced HTTP interface (login flows, error simulation, i18n). 4. Comprehensive documentation, including setup guides and protocol specifications. Impact: This upgrade will equip researchers and defenders with a powerful tool to study attacker behavior, improve IoT security, and contribute to the broader honeypot ecosystem.
Support some enhancements to Policy Exceptions. Expected Outcome: 1. Support list of PolicyException namespaces (--exceptionNamespace flag) 2. PolicyExceptions to have a status object and report readiness in printer column 3. Support imageReferences in Policy Exceptions for verify image rules
<p>Postgresql allows developers more freedom to extend the provided capabilities in an application-specific manner compared to other popular open-source Relational Databases. One example of this is the ability to write user-defined functions in other languages besides SQL and C.</p> <p>Julia is still a new language but with a growing community and increasing popularity due to its several strong points, among which are the Python-like straightforward syntax, speed, and interoperability with other languages.</p> <p>Of course, Julia is nowhere near as established as Python (for which the PL extension is included in the standard releases of Postgresql). Still, as it becomes more widely adopted, I think that adding a more functional pl/Julia to the list of pl handlers available to developers will soon be seen as a useful contribution to the community.</p> <p>In this project I will implement the tasks defined in the project description on the wiki, some of which are also listed as open issues on GitHub, namely:</p> <p>Support triggers</p> <p>Support event triggers</p> <p>Support inline code execution, a.k.a DO statement</p> <p>Support input parameters as arrays</p> <p>Cache procedural language code instead of looking it up every time</p>
<p>This project will span multiple high-priority areas of Zulip, some of which include:</p> <ol> <li>Zulip has support for older versions of RHEL-based GNU/Linux distros. Moreover, CentOS is dead now. Recently I <a href="https://github.com/zulip/zulip/pull/17719" target="_blank">added support for Fedora 33</a>. I will work on adding support for newer versions of said distros and look into supporting Rocky Linux, which aims to replace CentOS.</li> <li>Zulip provides a great way to import data from other chat platforms, such as Slack. I will work on making the transition to Zulip smoother and easier.</li> <li><a href="https://github.com/zulip/docker-zulip" target="_blank">docker-zulip</a> has many production users. However, the project hasn't received the requisite attention. In this project, I will work on revamping the project and troubleshoot any issues that may arise. Zulip 4.0 will be released in a few days. I will work on having it work smoothly on docker-zulip.</li> <li>Apart from these, improving the existing developer tools, integrations to other third-party services, and testing infrastructure will also be a priority.</li> </ol>
Information Delivery Specification (IDS) is a standard for defining information requirements in a computer interpretable form, written in XML. Manually writing XML in compliance with the IDS schema can be an extremely difficult task for non-technical BIM users, giving rise to a need for a web interface to compose IDS specifications in a user-friendly manner. The current implementation suffers from bugs, outdated UI, and lacks important authoring usability features. The primary goal of this proposal is to rebuild the web app on a new foundation - the IfcOpenShell WASM build, eliminating the need for a API backend, improving privacy, and enabling innovative features like in-browser IFC compliance checking, contextual autocompletions, and enhanced UX/UI. The new implementation will be comprised of 3 modules: 1) IDS Module - for composing and editing IDS specifications in a user-friendly way. 2) WASM Module - to interface with IfcOpenShell WASM. 3) Application Module - built with Svelte 5 and shadcn-ui to deliver a modern, responsive UI. Additionally, this proposal introduces a built-in XML (IDS) editor, in-browser audit report generation, and integration with Bonsai’s websocket-based Web UI system for fetching "smart context" from Blender.
The write operation in flash can only change bits in a specific way and the erase operation changes all the bits of a block to 1s. So to modify any bit the whole block needs to be copied to another memory, erased on the flash, and then copied again from the other memory with the change. Due to this “erase overhead” write operations may require copying a lot of data to modify a small amount. Most flash chips support multiple erase-block sizes and flashrom keeps a list of these sizes and ranges for all supported flash chips. Currently, flashrom tries these functions one by one and uses the same function until the operation is completed or an error occurs. Usually, the first function works correctly but this function erases the smallest erase-block so flashrom would have to use it multiple times to complete the erase operation on a large region, which could have been done more efficiently using functions using larger erase-blocks, thus resulting in a transaction overhead. If a large erase-block size to erase a small region is chosen it would result in a larger erase overhead. So the erase-block size should be picked according to the size of the region left to be erased. Also checking in advance to tell if the programmer supports the given erase function and then sorting the supported functions in order of the erase-block sizes can further help the function selection.