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.
Virtio is an open standard designed to enhance I/O performance between virtual machines (VMs) and host systems in virtualized environments. VirtioFS is an extension of the Virtio standard specifically crafted for file system sharing between VMs and the host. This is particularly beneficial in scenarios where seamless access to shared files and data between VMs and the host is essential. VirtioFS has been widely adopted in virtualization technologies such as QEMU and Kata Container. Apache OpenDAL is a data access layer that allows users to easily and efficiently retrieve data from various storage services in a unified manner. In this project, our goal is to reference virtiofsd (a standard vhost-user backend, a pure Rust implementation of VirtioFS based on the local file system) and implement VirtioFS based on OpenDAL. Through this project, VMs can access numerous data services through the file system interface with the assistance of the OpenDAL service daemon deployed on the host, all without their awareness. It ensures the efficiency of file system reading and writing in VMs through VirtioFS support. This storage-system-as-a-service approach conceals the details of the distributed storage system from VMs. This ensures the security of storage services, as VMs do not need to be aware of the information, configuration and permission credentials of the accessed storage service. Additionally, it enables the utilization of a new backend storage system without reconfiguring all VMs.
The project **Micro Front-ends Proof of Concept for Fineract 1.x & Mifos X** aims to propose and design architecture for the micro-frontend approach for our angular web app. We must identify which existing and new screens should be implemented as separate microservices UIs. Also, I will be working on enhancing the look and feel of the app.
Currently the ShapeTool that is implemented in Native Pocket Paint is missing in the Flutter version of Pocket Paint. My proposal would be to implement the ShapeTool in Flutter and also fully write a extendable testing system for the tool. Depending on the time constraints I would also extended the shape inventory to include more sophisticated shapes.
The goal of this project is to improve the user experience of search functionality provided by Documenter.jl by building an intelligent search system that will enable users to easily and quickly find the information they need. The system will use various pre-processing techniques and search algorithms to provide accurate search results and suggestions for related content.
I want to implement a feature for pocket that enables users to merge their existing projects, because it's not possible in the current version. Implementing a project merging feature will greatly improve the experience for pocket code users when it comes to building even more powerful applications and games. I've divided the problem into the following 5 milestones, with their subtasks to achieve: 1. Merging Projects Components with existing, simple conflicting variables protocol: 1.1 Merging Multiple Sprites 1.2 Merging Scenes 2. Implementing a Manual Conflict-Handler Interface: 2.1 User Interface for Merging Dialog: (choosing which conflict to merge, option to abort merge etc.) 2.2 Handling Local & Global Variable Conflicts 2.3 Handling Script Conflicts: View of Conflicting Scripts, Choose One 2.4 Handling Looks & Sounds Conflicts: Duplication User chooses 2.5 Handling Equal Sprites 2.6 Handling Equal Scenes 3. Merging options for UI 3.1 Abort Merge 3.2 Automatic Merge Without Conflict Search ( may not import everything) 3.3 Manual Merge ( Powerful Merge every conflict needs to be resolved) 4. Device specific configurations 4.1 Handling Screen Size & Resolution sensitive variables 4.2 Handling Screen Size & Resolution sensitive bricks 5. Merging Remix Graph 5.1 Implementing project merge history Each feature will be implemented using Kotlin or Java depending on source code files affected by changes, and each feature should be well tested.
<p>Thanos Querier component supports basic TLS configuration for internal gRPC communication. This works great for basic use cases but it still requires extra forward proxies to make it work for bigger deployments. It’s also hard to rotate certificates automatically and configure safe mTLS. This project aims to remove those simplifications allowing better TLS story for all Thanos metrics APIs!</p>
<p>This project is a gameplay specific project which aims to bring additional elements of fun for the player base by forming a working genome module which can be used flexibly with modules like SimpleFarming, WildAnimals and any other modules which may be developed in the future which have the scope of expanding with genetics. A prime focus of this project would be to get the genetics module completely integrated with SimpleFarming and EdibleFlora so that plants can now be bred with genetics. Since this adds different traits to different varieties of plants or any entities that have genetics, it creates a fun and immersive experience for a player to find desirable varieties of the entities he needs to craft ideal food sources from superior ingredients. The project also aims to enhance certain gameplay elements like cooking, health, and thirst to work with genetics to provide a good point of interaction between the player and genomes.</p>
<p>Inclusion of USER_LDT option in NetBSD kernel allows Wine32 applications to be run on amd64 architecture. This is useful primarily owing to the majority of Windows applications being 32-bit. My work involves getting the latest version of Wine to compile and run on i386 and amd64, and building Wine with WoW64 support which will allow running Wine32 applications on amd64.</p>
<p>Broadly I propose to implement, test and document the following features in Social Street Smart:</p> <p>(1) Hate Speech Detection using Deep Learning and maintaining dictionary of profanity words. (2) Click-Bait detection using Deep Learning . (3) Origin Detection of news/rumor using fact checking.</p>
<p>At CERN, the data from LHC collisions requires complex data types and functions to be processed. As a solution, the awkward-array library makes python implementation of these data types possible in a way which is portable to GPUs. Making this library work through C++ code would give it the ability to have precompiled C++ routines for faster implementation (past the initial load time) and later compatibility with vectorization primitives from C++ libraries.</p> <p>As part of this project, I will be working on expanding the awkward-array python library to include C++ compatible functions using pybind11. This will entail creating compiled C++ code in the form of python extension modules to be an expansion of the already-existing package. The classes I will be writing will be C++/python versions of the classes which have been already written in the main directory of the awkward-array project.</p>
<p>Terasology is an open world, open source game but it’s open in the sense that one can explore a single world as much as possible. The idea of this proposal is to add multiple worlds to the game and enable teleportation between two worlds. With Sector’s proof of concept done and ready, this project will serve to be a proof of concept of multiple worlds and efficient entity pool splitting. The deliverables of this project would be:</p> <p>1) An improved and more optimized way of queuing chunks for efficient loading and unloading whenever needed.</p> <p>2) A game with multiple worlds where a player can select multi-world options and can teleport among them using portals.</p>
<p>The project proposed aims to implement an <strong>Arabic speech recognition</strong> model using training data from the <a href="http://www.mgb-challenge.org/arabic.html" target="_blank"><em>MGB-3</em></a> Arabic datasets to perform speech recognition on a <strong>television news corpus</strong> captured in Cairo by Red Hen Lab. Another contribution will be to train a <strong>dialect identification</strong> model to perform Arabic dialect identification on the Television news corpus.</p>
<p>A large goal of both the SBOL and synthetic biology communities is to develop a useful and comprehensive workflow from experiment to publication. Many SBOL-compliant tools already exist which perform distinct and useful functions ranging from component design, modeling, composition, simulation, figure creation, storage, sharing, and publication. In 2016, ACS Synthetic Biology recommended that all authors submit genetic designs using SBOL. An example workflow for doing so was published in 2016 (Hillson), and each of the parts of the workflow can be fulfilled by extant tools, but the integrations between tools can be made more robust. For example, the SynBioHub service allows for storage and sharing of SBOL parts, VisBOL allows for creation of SBOL visual images from SBOL files, and iBioSim and SBOL Designer allow for creation and composition of SBOL parts. SBOL Designer and iBioSim allow for upload of parts to an instance of SynBioHub, but there are many opportunities to improve this workflow with authentication, security, and sharing capabilities.</p>
<p>Music Blocks is a free and open-source, browser-based software, designed basically for students to learn music in fun and interactive way. To get started with “music blocks”, newbies need to have a fundamental understanding of the software, what are the things can be done and importantly how things can be done. To address this requirement, “music block” has a user guide. But the existing user guide lacks most of the important information about the software components, how each building blocks in the software can be related to music and especially some examples of how to create music with the software. The objective of this project is to create a user manual which would be a simple and comprehensive guide while providing samples and related explanations. Deliverables of the project will be as follows:</p> <ul> <li>Improve the Music blocks user guide content to be easily approachable to newbies. </li> <li>Implement a documentation website for Music Blocks user guide. </li> <li>Prepare a downloadable version of the Music Blocks user manual in Portable Document Format(PDF).</li> <li>Make the website expandable for online contributions to documentation from the website itself.</li> </ul>
<p><em>Object-Oriented (OO) metrics</em> synthesize characteristics of OO entities (classes, methods) and of their relations, and if combined efficiently, can reveal to the programmer some of the design antipatterns that are specific to OO-systems. This project aims to provide PMD rule developers with straightforward utility methods that calculate metrics, thus enabling them to target systemic design flaws, through the creation of a <em>dedicated metrics framework.</em></p>
Ultimate Alarm Clock III (UAC) aims to evolve into a production-ready, cross-platform mobile application that delivers intelligent, condition-based alarm functionality. The core problem addressed is the limitation of traditional alarms, which lack contextual awareness and flexibility in triggering based on real-world conditions such as location, calendar events, or user activity. To solve this, the project will enhance UAC with advanced conditional logic and deep integrations, including Google Calendar synchronization, Google Assistant voice controls, and customizable task lists linked to alarms. Additionally, the system will improve reliability through enhanced alarm history logging and debugging tools, while enabling seamless synchronization with a companion app. Infrastructure improvements such as CI/CD pipelines, automated testing, and Play Store deployment workflows will ensure scalability and maintainability. A stretch goal includes developing an iOS version with native background execution capabilities to ensure consistent alarm behavior across platforms. The key deliverables include: Implementation of core features such as calendar-based alarms, voice interaction, shared alarms, and task lists Advanced developer diagnostics via alarm history and logging systems Companion app synchronization with real-time data consistency A robust CI/CD pipeline for automated testing and deployment (Stretch) iOS support with native integrations for reliable background execution Together, these deliverables will transform UAC into a scalable, production-grade application with intelligent, context-aware alarm capabilities and a strong foundation for future development.
This project enhances NiMARE’s performance and developer accessibility through a dual-phase optimization strategy. The first phase modernizes the contributor onboarding framework by updating development environment documentation and Git workflows to reflect current best practices, ensuring a lower barrier to entry for new developers. The core technical phase implements a fixed-width confidence interval stopping rule for ALE and MKDA workflows. By integrating an adaptive framework based on the Wilson Score Interval, the system dynamically prunes voxels as p-value convergence reaches statistical decisiveness. This approach significantly reduces computational overhead and execution time while maintaining Type I error control. Deliverables include an extensive benchmarking against standard 10,000-iteration runs, and—progress permitting—the expansion of NiMARE’s methodology through Signed Difference Mapping (SDM) and Publication Bias Diagnostics (Fail-safe N).
This project aims to transform the CircuitVerse mobile application into a fully functional, stable, and production-ready platform that matches the capabilities of its web counterpart. Currently, gaps in core features, inconsistent user experience, and technical instability limit the app’s effectiveness as a learning tool. By addressing these challenges, the project focuses on implementing missing web features, stabilizing authentication, and restoring key modules such as the interactive book to ensure a seamless and engaging learning experience on mobile devices. In addition to feature parity, the project emphasizes improving performance, fixing critical bugs, and enhancing UI consistency and accessibility. A scalable and maintainable architecture will be established to support long-term growth and easier development. Special attention will also be given to localization and multilingual support, making the platform more inclusive and accessible to a global audience. Overall, this initiative is important for CircuitVerse as it enables broader reach, improves usability for mobile users, and ensures that students worldwide can reliably access interactive digital circuit learning resources anytime, anywhere.
MetaCall's runtime introspection (metacall_inspect) requires loaded loaders and a live environment, leaving IDE tooling, CI pipelines, and Function Mesh with no pre-runtime project intelligence. This proposal builds metacall-ast - a standalone Rust static analyzer that uses Tree-sitter incremental parsing to extract symbols and cross-language dependencies from Python, JavaScript, TypeScript, C/C++, and Rust source files, emitting JSON structurally compatible with metacall_inspect (keys: funcs, classes, objects). The tool uses petgraph for in-memory graph construction, applies Tarjan's SCC algorithm to identify independently deployable Function Mesh units, and exposes a stable C ABI (mc_ast.h) for embedding in MetaCall core. An optional Dgraph sink enables persistent Code Knowledge Graph snapshots. Deliverables: core Rust library + CLI, language packs for 5 languages, inspect-parity JSON output, C ABI bridge, Dgraph sink, and a stretch intra-procedural dataflow (def-use chains), with full CI on Linux/macOS/Windows.
The project aims to extend API Dash with Git-backed collections, a visual workflow builder, and a collection dashboard. This will enable developers to version and share API collections, design and execute multi-step API flows, and monitor API health and performance within a single unified tool. Problem Being Solved: API Dash currently stores requests in a flat local structure without version control or collaboration support. The existing load-all/manual-save model limits reliable syncing, introduces risk of data loss, and prevents building higher-level features like analytics and workflows. Additionally, users lack visibility into API performance and have no structured way to define multi-step API interactions. Proposed Solution: 1. A refactored persistence layer using request-level autosave (Hive LazyBox) for reliable and granular data storage. 2. A GitHub integration layer to enable version control, sharing, and collaboration on collections. 3. A visual workflow builder with a node-based interface to define and execute multi-step API flows. 4. An execution engine to handle request chaining, conditions, and shared data flow between steps. 5. A dashboard system to aggregate and visualize API and workflow performance metrics. Key Deliverables: 1. Request-level autosave system replacing the current bulk-save model. 2. Git support for collections (connect, import/export, push/pull, commit history, rollback). 3. Visual workflow builder with execution support, run history, and DashBot-assisted workflow generation from natural-language prompts. 4. Collection and workflow dashboards showing success rates, failures, and latency signals. 5. Production-ready documentation, testing, and UX polish for real-world usage.
OpenSCAD currently supports Windows development/build setup through 2 key ways: MSYS2 and MXE. A MSVC based build has instructions circa 2012, but with significant changes in project structure, and updated/new third party libraries and dependencies, it would be useful to work on adding modern MSVC build support for Windows. Currently, most CI builds use MSYS2 instructions, which has a Unix style build system. The benefits of adding support for MSVC builds include having executable and library outputs (.exe/.dll), vcpkg support for third party libraries OpenSCAD depends on, and support for parallel builds for speed.
The Jaya R package implements the Jaya optimization algorithm, a gradient-free, population-based method for solving both single-objective and multi-objective optimization problems. The Jaya algorithm, introduced by Rao in 2016, has gained attention for its simplicity and effectiveness, as it requires no hyperparameter tuning, making it particularly useful for users who need fast and reliable optimization solutions. However, while the current version (1.0.3) of the Jaya package is functional, there is significant room for improvement in terms of computational efficiency, usability, and integration with the broader R ecosystem. This GSoC project proposes a major upgrade to the Jaya package with the goal of improving algorithmic performance, enhancing parallel computation capabilities, and expanding the package's compatibility with widely-used R tools. Additionally, the project aims to make the package more user-friendly by streamlining the interface and improving documentation. These updates will help integrate Jaya into modern optimization workflows, benefiting researchers, practitioners, and educators alike.
This project implements key components of KEP-2170, introducing the Kubeflow Training V2 API. Specifically, it focuses on creating the TrainingRuntime and ClusterTrainingRuntime for the JAX and TensorFlow frameworks, built upon the Kubernetes JobSet API. These runtimes will serve as blueprints for model training (including LLMs) within cloud-native ML pipelines. This abstraction allows Data Scientists and MLOps Engineers to easily reuse standardized runtimes and launch training jobs, particularly via the SDK, without needing deep knowledge of underlying Kubernetes complexities.
extending test coverage to root filesystem selection and documenting config(8). rump servers will be used to write test in ATF of NetBSD. This project shall improve on stability of NetBSD.