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.
KubeSlice currently uses a full-mesh topology for the slice overlay network, where every cluster connects to every other cluster in the slice. This results in unnecessary tunnel creation and resource consumption. This project proposes a topology-aware design, allowing users to define custom connectivity matrices for slices. Users can specify partial meshes. Additionally, the project will support configuring each cluster's VPN deployment type (client/server) to accommodate network constraints such as firewalls or NAT. Expected Outcome: 1. Extension of the Slice CRD to support custom topology and VPN role definitions. 2. Logic to establish tunnels based only on the defined connectivity matrix. 3. Support for various deployment topologies (full-mesh, partial mesh, hub-spoke). 4. Sample configurations and documentation on how to define and validate topologies.
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.
<p>OpenRoberta is a learning platform. It uses a graphical programming language (based on blockly) and has code generators/loader for many robots and embedded systems used in education (Extracted from the <a href="https://github.com/OpenRoberta/robertalab/wiki/Expression-block-...-and-more" target="_blank">project site</a>). As a result of this project, the following products are expected:</p> <ul> <li>A new expression block for evaluating longer and more complex expressions than those currently supported. Most of the arithmetic and boolean operations, list operations and function calls are supported by this block.</li> <li>User error reports and user help for this block.</li> <li>An investigation regarding concrete syntaxes for the NEPO language and support for different concrete syntaxes.</li> <li>A textual representation for the graphical language, this representation can be used in the expression block.</li> </ul>
<p>The GoPro Cineform codec is a cross-platform intermediate codec designed for editing high-resolution footage. It was original designed for compressed Digital Intermediate workflows for film or television applications using HD or higher resolution media. FFmpeg reverse engineered Cineform decoder currently supports progressive video files with image formats YUV 4:2:2 10-bit, RGB and RGBA 4:4:4 12-bit. This project aims to support more features present in cineform codec, namely Inverse Temporal Transform for p-frames, deinterlacing support, assembly instructions integration into the ffmpeg version, and making it faster by using threading models present in FFmpeg. The result of this project will be that Cineform decoder can be integrated with many tools that use FFmpeg libav.</p>
<p>This project aims to implement support for <strong>Molecular Dynamics</strong> in Avogadro.</p> <p>Molecular dynamics (MD) is a computer simulation method for studying the physical movements of atoms and molecules. The atoms and molecules are allowed to interact for a fixed period of time, giving a view of the dynamic evolution of the system. In the most common version, the trajectories of atoms and molecules are determined by numerically solving Newton's equations of motion for a system of interacting particles. In this project, we aim to provide support in Avogadro for reading MD trajectory files and analyzing the various aspects of the MD calculation like temporal evolution, particle movement characterization (eg. pair distribution functions) etc. Also, input generation and support for running MD calculations in common packages like OpenMM and GROMACS shall be focused upon in the later stages of the project.</p>
The Peersky browser currently lacks a unified system for managing both user-installed WebExtensions and core browser preferences. This project will implement full WebExtension support alongside a customizable peersky://settings page, creating a modular and privacy-focused experience within Peersky’s Electron-based environment. Deliverables include support for installing .zip and Git-based extensions, a persistent extension loader, Manifest V3 validation, CSP-based sandboxing, and a toolbar for pinning and managing extensions. The settings page will also allow users to change themes, set search engines, configure the home page, and manage built-in privacy tools like uBlock Origin and DScan. By the end of the project, Peersky will support a secure, extensible, and decentralized customization system—without relying on centralized extension stores.
CRIU currently supports unprivileged checkpoint/restore in limited cases, but rootless containers remain unsupported because they introduce additional challenges around user namespaces, ptrace permissions, seccomp suspension, cgroup handling, and UID/GID mapping. This project aims to add a dedicated rootless-container checkpoint/restore path to CRIU rather than extending the existing --unprivileged mode. The implementation will introduce a user-namespace-aware helper architecture for dump, preserve cgroup state when delegation permits it, correctly capture and restore UID/GID mappings using newuidmap and newgidmap, and establish proper restore ordering for user and mount namespaces. Deliverables include the new rootless-container support path in CRIU, cgroup handling improvements, UID/GID mapping support, expanded rootless zdtm coverage, and documentation for the workflow and limitations.
A Flutter plugin that integrates the OkHttp package (https://square.github.io/okhttp/) using the Dart Bindings from the package:jnigen and implements the package:http's Client interface. Several APIs from the OkHttp package are used, to make asynchronous requests. This implementation passes the conformance tests in package:http_client_conformance_tests. This plugin is expected to be able to stream response bodies as well. The plugin will also implement the package:web_socket_channel's WebSocketChannel interface. This will provide several features requested by Dart Users: (a) Support for KeyStore PrivateKeys (#50669), (b) Support for the system proxy (#50434), (c) Support for user-installed certificates (#50435). The plugin should be available as a standalone package at https://pub.dev/. It should be almost identical to cronet_http and java_http packages, and provide seamless integration in all Flutter Projects. This package is also expected to broaden its functionality to other platforms.
The project adds support for importing and exporting virtual machines (VMs) from KVM Hypervisor into the CloudStack. It helps administrators better manage resources and transfer VMs if needed. The CloudStack currently supports this functionality only on VMWare and support on KVM (as one of the most popular open source hypervisor) can tremendously help many other users of CloudStack. In terms of deliverables the following can be expected at the minimum: 1. Implement/extend listUnmanagedInstances API: Lists unmanaged virtual machines (not existing in CloudStack but existing on the hypervisor side) 2. Implement/extend importUnmanagedInstance: Import an unmanaged VM into CloudStack (this implies populating the database with the corresponding data) 3. Implement/extend unmanageVirtualMachine: Make CloudStack forget a VM but do not remove it on the hypervisor side 4. UI Changes to facilitate above API use through the web portal 5. Integration tests and documentations for ease of use
This project aims to extend the classbound R package into a general framework for exploring and comparing classification boundaries across a wide range of models and datasets. The project will develop a modular R package that supports additional classification algorithms, including user-defined methods, along with flexible data simulation utilities and support for real datasets. It will also extend functionality to high-dimensional settings using tour-based visualization techniques, allowing users to interactively explore data structure and corresponding decision boundaries. The package will be designed for extensibility and will include comprehensive documentation, examples, and a vignette. Final deliverables will include implementations of additional classifiers, enhanced simulation capabilities, high-dimensional visualization support, and complete documentation, enabling users to better understand and compare classification models through their decision boundaries.
The Macromedia Director engine is an incomplete engine in ScummVM. ScummVM has been working on it since 2020. It potentially adds a number of games to the growing list of supported games in ScummVM. This proposal aims to add support for Director Engine to get it closer to that possibility. This project proposes implementation of a number of unfinished functions including STUBed code and Director Xtras. The Lingo Dictionary will be helpful for figuring out the functionality offered by each STUBed function. The main focus of this project is to restructure the Director engine's internal data structure of storing Director movie files (.dir and .dcr) which enables saving them in Director. The project by djsrv available on GitHub is a great reference for solving this problem. The proposal also hopes to improve the support for a couple of director games namely, The Journeyman Project and Safecracker. Comparing these games to their original versions, this project hopes to make playable without any hiccups.
<p>The Mesh-RCNN technique was recently introduced to estimate 3D models from natural 2D images. It uses a combination of an object detection module which works on real-world images and produces a triangle mesh giving the full 3D shape of each detected object. Methodically, Mesh R-CNN comprises different modules for mesh prediction which provide functionality that would be cool to have in TensorFlow Graphics. TensorFlow Graphics already contains implementations of some key building blocks of Mesh R-CNN, like graph convolutions and the chamfer distance by the time of this writing. However, some other crucial parts of the Mesh R-CNN approach need to be implemented als modules into TensorFlow Graphics. This projects provides the means to implement Mesh R-CNN in TensorFlow Graphics and train it using an TensorFlow Dataset implementation of Pix3D, a Dataset for Single-Image 3D Shape Modeling.</p>
<p>Currently, there exists no software solution for checking whether a service mesh implements Service Mesh Interface or not.</p> <p>This causes the following problems:-</p> <ul> <li>For Service mesh maintainers, maintainers need to check whether the service mesh they are creating conforms to service mesh interface</li> <li>Users using service mesh don't know whether a feature is supported or not by the particular mesh they are using.</li> </ul> <p>In this project, aim is to:</p> <ul> <li>Build meshery as the underlying technology to support SMI Certification</li> <li>Generate a compatibility matrix identifying the SMI features that are supported per service mesh.</li> <li>Decide the definition of what behavior is expected and conforms to spec. vs not. Partial conformance could be defined by a minimum requirement. It may be that partial conformance allows for / encourages extensibility</li> </ul>
This project aims at building a visual AI Feedback Assistant that integrates to the ECA and BPMN modules to streamline the automation workflows, that would otherwise require the manual work. AI-powered visual editor will have intuitive interfaces, real-time suggestions, and automatic formatting, resulting in a more efficient and user- friendly automations. It integrates with various Natural Language Processing and Drupal Modules to create seamless integrated workflows. It works on Prompt Chaining and looping. The Visual AI ECA Assistant will streamline the process of creating the automated workflows with ease using just the prompts. The prompts will be enough to make the workflow itself. It can understand human language, parse it, find the triggers, condition and actions required, configures the modules, and gives the ready-made workflow to be used. The user will be able to fine tune the workflow with further prompts easily making the workflow more accurate and efficient.
<p>The broad goal is to enhance flashrom by adding new and (somewhat) obscure features and, merging pending patches. This project comprises several sub-projects -</p> <ul> <li>Locking/unlocking of access protection</li> </ul> <p>Build towards a single flashrom codebase. Basic patches exist in the ChromiumOS branch, but further work needs to be done.</p> <ul> <li>Support for Multiple Status Registers</li> <li>Support for OTP/Security Registers</li> <li>Add Support for EEPROMs</li> </ul> <p>Investigate changes arising in the core infrastructure (including libflashrom) and produce mergeable code that is sustainable.</p> <ul> <li>Common Flash Interface (CFI)</li> </ul> <p>Give flashrom the ability to auto-detect chips with CFI capability (similar to auto-detecting SFDP-capable chips).</p>
<p>Both Link Time Optimization (LTO) and C++20 Modules will benefit from a closer interaction between build system and compiler. LTO benefits from parallelizing the LTO step by spawning separate compilations and Modules can discover new dependencies during compilation. Both of these task are traditionally under control of a build system.</p> <p>Currently, GCC's LTO can use GNUMake's jobserver protocol to control its direct spawning subjobs. C++20 modules can make use of a proposed protocol[*], or use pre-scanning. This project aims to unify these approaches providing (a) client/server librar{y,ies} to manage communication (b) extend the proposed protocol to cover LTO requirements (c) provide a sample implementation for GCC/GNUmake.</p> <p>[*] <a href="https://wg21.link/p1184" target="_blank">https://wg21.link/p1184</a></p>
In the latest evolution of PipeCD, the plugin architecture for piped has been established (ref: PipeCD plugin-arch blog)(https://pipecd.dev/blog/2024/11/28/overview-of-the-plan-for-pluginnable-pipecd/) , paving the way for community-developed plugins. Previously, PipeCD already supported deploying applications using Terraform, with the Terraform plugin being developed by the maintainer team to ensure continued support for existing users. Meanwhile, OpenTofu has emerged within the Cloud Native landscape as a drop-in alternative to Terraform. To align with this development, we aim to extend PipeCD’s support to enable the deployment of OpenTofu applications, just as we have done for Terraform. Expected Outcome: 1. OpenTofu plugin for PipeCD 2. Possible update plugin SDK while develop the OpenTofu plugin 3. Possible update docs how to develop PipeCD plugin 4. Blog about how to develop a PipeCD plugin on https://pipecd.dev/blog/
RTEMS Deployment currently supports TAR and RPM package types for toolchain and RTEMS BSP configuration distributions. However, users of Debian-based Linux distributions and FreeBSD must currently use TAR packages, which cannot track dependencies, upgrades, or clean removals like a real package manager. This project will provide native packaging support for Debian (.deb) and FreeBSD (pkg) package types within RTEMS Deployment. A packaging abstraction will be implemented in Python and will be shared between both packaging backends by refactoring the existing RPM backend. This will provide a clean integration with our current deployment model. This will provide RTEMS toolchain installation and management support for developers using Debian, Ubuntu, and FreeBSD distributions with their native package managers. It will also provide integration tests, documentation, and a tutorial for future contributors to easily integrate other package types into RTEMS Deployment.
<p>The Arduino ecosystem has 2700+ libraries written in the ‘Arduino dialect’ of C++. For Micropython to become popular on Arduino it is required that:</p> <ul> <li>A large number of these libraries be ported to MicroPython.</li> <li>This porting must be efficient to do, to avoid time delays and uneccessary effort.</li> </ul> <p>The project idea aims to make a source to source compiler (known as a Transpiler) which can: ‘Translate’ a given example program of a library (in Arduino) to MicroPython automatically.</p> <ul> <li>Highlight any errors and parts of the code that it cannot translate effectively.</li> <li>Be easy to maintain as support for more library code is added down the road.</li> </ul> <p>Currently the project supports automatic transformation of many MicroPython statements, along with helpful messages of suggested libraries to import. It is a constant work in progress and will grow to support more automatic conversions in the future as Arduino's ecosystem matures.</p>
My project goal was to add DICOM file support to caMicroscope, a Whole Slide Image viewer. The viewer backend (OpenSlide) didn't support DICOM, so we needed a second backend. Surprisingly, before the coding period started, OpenSlide did get DICOM file support and this gave me the opportunity to tackle the bigger challenge of integrating BioFormats into caMicroscope. This would be extraordinary, as BioFormats is a Java library with no C wrappers available online. I started by refactoring caMicroscope code to use a single base Dockerfile which compiled OpenSlide. Then I made a Java wrapper and prepared its corresponding C caller. For this, I had chosen GraalVM C API, but once I found out about its level of performance and its requirement to achieve high code covergage first (for metadata collection), I rewrote it for Java JNI. To make it available to the two derivatives of our base image, I refactored this to be a separate project. We also needed to make this available to our Python image metadata server, so I wrote a wrapper in Python using cffi.
<p>Ingesting data into PEcAn is currently a user-hostile process for researchers. To simplify this process, the PEcAn team would benefit from an application that can download datasets from any data federation, and parse the metadata so that it can be automatically read into PEcAn. To help further them in this direction, I will create an ingest workflow for a single data federation, DataOne, as a proof of concept. This app will be able to resolve data by doi. I will also add drag and drop functionality to facilitate downloading data from unsupported data federations. This app will then facilitate the process of selecting the correct semantics necessary in order to ingest data into BETYdb (the PEcAn database) by walking the user through this complex process. This app will also serve future development by creating a probability distribution of the semantics selected by the users. This distribution can be used to train a machine learning algorithm that will suggest semantic selection with greater accuracy in the future.</p>
<p>Since OODT consists of different components like file manager, resource manager and work flow manager, all those components have their own configuration files and locations. This is complex to manage and creates problems when the platform is distributed across servers or geographically. Therefore, the objective of this project is to migrate the OODT configuration to an optional zookeeper module so that the OODT components can register themselves in the zookeeper ensemble accordingly and maintain each component’s state regardless of the scale of the cluster. The proposed zookeeper module will minimize the manual configuration required when configuring OODT components. That is, this module will make use of the inherited configuration at component level. For example consider the file manager. Almost all the configurations of file manager instances are identical. Therefore, new file managers which are coming up later will inherit the configuration of the initial file managers and will almost remove the manual configuration required when adding new nodes to the cluster.</p>
The state of Julia GPU support ranges from “very good” (CUDA.jl) to “on the way” (Metal.jl). Recently, the shared high-level interface GPUArrays.jl added support for KernelAbstractions.jl, which defines a common interface that can be used to write optimized kernel implementations once for all the downstream vendor-specific GPU packages such as CUDA.jl, AMDGPU.jl, Metal.jl, and oneAPI.jl. However, most optimized kernel implementations still live in the vendor-specific package they were written for, leaving the other packages to either reimplement their own version, use the current unoptimized fallback implementation from GPUArrays.jl, or in many cases, the operation is not supported. This project aims to rewrite these optimized operations in GPUArrays.jl using the KernelAbstractions interface to improve performance and functionality for all GPU backends at once. The end result being that users of the less mature backends will benefit from more functionality, as well as increasing the impact of future contributions for all users of the JuliaGPU ecosystem.
This project aims to extend the CloudNativePG operator to support declarative configuration of foreign data wrappers through its Database custom resource. PostgreSQL supports the SQL/MED (Management of External Data) specification, enabling access to external data sources through standard SQL queries. These sources—known as foreign data—are accessed via foreign data wrappers (FDWs), which are libraries that handle the connection and data exchange with the external systems. A variety of FDWs are available for PostgreSQL. Of particular interest for this project is the postgres_fdw extension, which facilitates access to other PostgreSQL instances. Expected Outcome: 1) A detailed design discussion documented in the upstream issue in CloudNativePG GitHub repository, involving mentors, maintainers, and the community. 2) A fully working pull request implementing support for declarative foreign data wrappers, complete with: a. Reconciliation logic for the Database resource controller b. Documentation c. Automated tests integrated into the CI/CD pipeline