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.
CodeLabz is a platform where the users can engage with online tutorials and the organizations can create tutorials for the users. I'll design new screens and improve the design of existing screens. Many features in CodeLabz are currently static, so I'll render data from the backend and make them dynamic. I'll also connect the front to the backend, design backend in an optimized way.
To be able to use GitOps tools in combination with keptn, the main goal of this project is to find a proper way how the tools could interact with keptn and to build an integration for such tools. Deployment tools can be integrated via the helm service or via the job-executor service. Currently, there’s no way to integrate GitOps Tools in Keptn. Provide a way such that it could be integrated into keptn return deployment states after the state has been synced. This project would be done in collaboration with flux and keptn maintainers.
<p>Testing is a nice-to-have tool/utility for developers to check for breaks in early stages of development cycle which is less expensive. Automated testing makes the whole process less time time consuming. The goal of this project is to:</p> <ul> <li>Extend the framework and write tests for Physics modifiers, Curve types and remaining Deform and Generate modifiers.</li> <li>Generalization and refactoring of the framework to have non-duplicated code and classes.</li> <li>Working on a test object generation script to "fully" automate the testing procedure as there will be no need for interaction with the UI(Blender).</li> </ul>
<p>The presentation tool idea is to create an interface that is capable to create different sets of data configuration to be displayed on a Liquid Galaxy. The project consists of two main parts: an API and a web application. The web application will give the user the possibility to upload the wanted media and to select the displaying location, the chosen screen and the time interval each media will occupy. The API main function is to receive media and execute it in a Liquid Galaxy, it will get the created presentation and parse the sent data to run scripts that will execute on the Liquid Galaxy what the user planned in the web application.</p>
<p>EAC3 is one the most popular codecs for audio used nowadays, even been used as a base in the latest versions of object-based codecs. However, backwards compatibility is important, not everyone can be on the edge of technology or just feels comfortable with what they have. This project aims to achieve an automatic re encode from EAC3 to AC3, whenever a S/PDIF connection is been use, taking in consideration that the EAC3 codec was develop on top of the AC3 codec, so in best case scenario only a partial decode/encode would be required.</p>
<p>enviroCar App is currently in fully functional state yet there are some issues which allows users to create artificial types of cars with arbitrary attributes and lead to collecting wrong data which needs to be resolved and Re implementing current database layer based on sqlbrite which has been deprecated. The project also lacks some features that will be a lot helpful to users.</p> <p>I would like to propose following idea to improve app functionality and UX with app</p> <ol> <li>Improvement of the Car Selection Process in the enviroCar Android app.</li> <li>Re implementing existing database layer currently based on sqlbrite.</li> <li>Add a walk through screen to activities for users to know about all controls in applications</li> </ol>
<p>Feature completion for the Client/Server API, Sync Server, Room Server, and Federation component, plus various fixes and improvements to Dendrite and its related projects.</p>
<p>This project automates the task of sensing the health of the many Red Hen Lab remote capture stations, which are Raspberry Pi devices, and provides a responsive web dashboard that the management entity can use to easily perform her monitoring tasks. This has been achieved by implementing a set of scripts, whose execution in the capture stations is controlled over SSH and a comprehensive monitoring system using a centralized server (called Coop) built on the MERN stack - MongoDB, Express, React, Node.JS.</p> <p>The server consists of a Telemetry component which can communicate with the capture stations through SSH, a Control component which performs tasks like addition and updation of station metadata in the mongo database as well as report generation and backup upon user command and a frontend that allows visualization through a centralized dashboard that can be accessed through a desktop or mobile device with appropriate security credentials.</p>
<p>The PyOpenWorm data management tool aids in creating, storing, and sharing information about Caenorhabditis elegans and about the evidence supporting it. This initiative will focus on providing a primary source of distribution for that information. This specification will integrate a Bit-Torrent client into the existing PyOpenWorm codebase enabling researchers to transfer data sources. This will provide OpenWorm Foundation and the larger neuroscience research community with a peer-to-peer file sharing framework with the ability to limit access to sensitive information and also protect against malicious changes. It will pave the way for easier sharing and collaboration, ultimately leading to a better understanding of C.elegans.</p>
<p>GCC has support for built-in functions in C99/C11 standards along with features of IEEE standards. These functions do appropriate calculations according to the requirements of the users taking various types of arguments and returning values as required on supported data types of GCC like int, float. Such inbuilt functions help users, developers and GCC developers to minimize the repetitive calculations and efforts. There are optimization steps carried out to have faster compilation and running time of programs, folding and inlining being one of them. The purpose of this project is to implement more such functions in GCC which are added in ISO/IEC TS 18661 (supporting features of IEEE 754), folding them and expanding them inline wherever appropriate.</p>
<p>An effort to decouple D from the C standard library.</p>
<p>MailSync is a beautiful proof of work for the NDN project with the potential to make NDN's value understood through the popularization of this app. This project focuses on doing so by refactoring the app to remove unwanted behaviors occurring in the app. The project will add major testing code and benchmarking code to ensure that the application continues to be stable. Furthermore, additional security measures and validation will be added to the application. To popularize the app, the UI and UX of the app will be brought up to standards and NDN theme will be incorporated into the application.</p>
<p>The purpose of this project is to create a software tool that is capable of parsing popular online version control repositories, like GitHub, via their public APIs in order to detect open issues of projects, classify them based on several predefined configurable criteria and serve them via a public RESTFul API.</p> <p>A complimentary web application will also be created in order to consume this API and visualize the results of this service in an elegant and useful way.</p>
<p>Quiz extension is currently used on several WMF projects, such as Wikiversity but has lot of bugs and limited features for users.The project aims to <em>update and upgrade</em> MediaWiki Quiz extension while removing legacy code and <em>adding new features</em> to the extension.</p> <p>Benefits of this project include stability and functionality to the extension and comprehensive features for users of various Wikis.<em>Adding various custom features suggested by community would provide more power to user</em>.</p> <h4>Deliverables</h4> <p>The project will work on the following :</p> <ol> <li>Importing bugs from wiki and resolving them</li> <li>Provide Unit Tests for the extension making it fault tolerant.</li> <li>Updating source code to current MediaWiki standards</li> <li>Provide Custom CSS classes</li> <li>Updating user documentation</li> </ol>
<p>The usage of any open source software is primarily guided by the licenses binding it. Individuals/Organisations, generally make the decision of using an open source software, on this, i.e. the licenses. Vulnerability scanner, aims to, take it to a tad higher level. By being a comprehensive tool, which, using the industry standard CVE data and data from several other trusted sources matches packages with any reported vulnerabilities. Hence, providing another layer of information to Individuals/Organisations, helping them understand everything under the hood of an Open source software, better.</p>
<p>The streams based workflow engine will organize tasks into streams, allow parallelization of this streams, and work locally as well as integrated into common external HPC services. As well dat can be integrated to store intermediate and final data. This provides a framework for efficient, reproducible, and understandable bioinformatics pipelines.</p>
<p>Live Migration is a process of moving a running virtual machine from one physical system to another. There are usually two ways, precopy and postcopy. Postcopy migration is used for virtual machines which have a high memory dirtying rate, (higher than the bandwidth of the network that will be used to perform migration). The disadvantage of postcopy migration is, if there is a network failure then we are left with an inconsistent vm at both the source and the destination side. The aim of this project is to recover from the network failure, and complete the migration process. The project will include completing the process of sending the leftover memory pages. Project would start by making sure that the threads do not fail at both the source and destination end. This would be followed by re-establishing the network connection between the source and the destination. After this is done, the migration process is restarted. The vCPUs on the destination side were suspended due to page faults, so these pages are transferred first. Followed by the rest of the leftover pages on the source side.</p>
<p>The current PDF renderer in cups-filters, namely Ghostsscript and Poppler, are much heavy weight to mobile devices as compared to MuPDF which is significantly lightweight. Implementation of MuPDF is required in the cups-filters as it will save lots of memory, storage and CPU resources in mobile devices for printing job. Filters like pdftops, pdftoopvp, pdftoraster, pdftoijs and pdftopdf have to be modified in order to add support for MuPDF without dropping existing support for Ghostscript and Poppler.</p>
Astropy’s Python API is well-tested, but its underlying compiled layer (C, C++, Cython) lacks isolated testing. Because performance-critical extensions are currently only tested indirectly via high-level Python calls, deep bugs can easily be masked. This testing blind spot also blocks major architectural milestones, including the APE low-level package split, the Meson build system migration, and support for Python 3.15 free-threaded builds. This project will build a dedicated test suite to exercise each compiled extension module directly, entirely bypassing the public Python API. By engineering methods to probe these modules in isolation, including resolving complex runtime circular dependencies like `unit_list_proxy.c`; this work will establish a robust, reliable testing boundary between Python and the compiled code. Deliverables: C-API Audit: A mapped testing surface for active compiled extension modules. Isolated Test Suites: Direct pytest suites for compiled modules in astropy/table, time, timeseries, utils/xml, wcs, and erfa. Dependency Resolution: A C-level refactor (or minimal Python stub) to fix the `unit_list_proxy.c` circular dependency. Documentation: A new TESTING_EXTENSIONS.rst guide in Astropy's docs detailing how to run and extend these direct tests.
The project should fix the N+1 queries problems across the project with DataLoaders. The file run-ci-cd.yaml should will be split into 5 files and the docker layer will be removed.
This project develops agent-accessible CLI tooling for the Julia Bayesian ecosystem, delivering three main components: DoodlePPL CLI for model validation, code generation, sampling, and diagnostics with structured JSON output, MCMCChains.js, a TypeScript npm library enabling MCMC diagnostics and visualizations in the browser and TuringCLI, a command-line interface for Turing.jl that provides machine-readable JSON outputs, with all three deliverables building upon and extending the GSoC 2025 work on DoodleBUGS.
Open-weight LLMs are reproducible in principle but not verifiable in practice. You can download weights, but you cannot prove what data they were trained on or whether they were modified later. This project closes that gap by building a training pipeline where identical configurations produce identical model states, and any deviation is cryptographically detectable. A key insight from my experiments is that while training computation can be deterministic, PyTorch’s .pt serialization breaks verification: identical weights can produce different checkpoint files. This project resolves that by verifying tensor-level state using byte-stable formats rather than file-level artifacts. The deliverable is a 1B–3B model trained on a pinned Wikipedia dataset, along with a public manifest that enables independent reproduction and audit.
This project adds a Ninja build backend to DUB, the D package manager and build tool used by the D ecosystem. Currently, DUB primarily drives builds via direct compiler invocations. This limits incremental build performance, parallelism, and integration with modern build tooling. The proposal introduces a backend that allows DUB to generate Ninja build files and delegate compilation to Ninja. This enables faster incremental builds, better dependency tracking, improved parallel execution, and easier IDE/toolchain integration.
This project aims to enhance cBioportal's analytical capabilities by integrating Variant Allele Frequency (VAF) visualization into the Plots Tab and OncoPrint views. Currently, in Plots Tab we can visualize mutation types of particular gene across different cancer types but it is not possible to visualize VAF data for different samples across different cancer types. It is very crucial for researchers to understand mutation clonality and prevalence across cohorts through VAF. Similarly in OncoPrint view we cannot add tracks for VAF heatmaps across different genes. The proposed solution has two components. For the Plots Tab, we will introduce VAF (linked to a specific gene) as a selectable numerical data type of mutation for plot axes. Existing plot components will then automatically render Box-Scatter or Scatter plots. For OncoPrint, we will implement gene-specific VAF heatmap tracks displayed below the main alteration grid. VAF heatmaps corresponding to primary displayed mutations with a dedicated 0-1 color scale.