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>p5.js has multiple methods for I/O handling. I propose to work on Improving the file I/O methods by identifying, documenting and finding solutions and limitations to these functions. Creating new methods for dealing with files of different types will also be done if required, along with the corresponding unit tests and documentation.</p>
<h4>Description:</h4> <p>The aim of this project is is to develop a web interface for DoMo-Pred which can help to simplify the analysis of protein-protein interactions in yeast, or, if possible, in all kinds of organisms.Just upload or input pairs of protein IDs and run then the web interface will return the result and researcher can easily share the result with their colleagues and visualize the network of those interactions with significant scores. Also, the result after sort with significant scores can be used for performing other analysis.</p> <h4>Project details.</h4> <ul> <li>Users can upload PWMs and domain files (or use built-in data or their own trained data as well as input list of protein IDs) the application will call DoMo-Pred to analyze then return the result as a table.</li> <li>An easy to use admin tool for change built-in dataset,like uploading more PWMs and domains and add more organisms or to remove certain PWMs and domains.</li> <li>Sort the result by score after evaluation, then pick those interaction with significant scores (under user specified cutoff) which can be download and used to perform different analysis.</li> <li>Use Cytoscape.JS to visualize the network of those interactions with significant scores.</li> </ul>
<p>KDE Reports aims to provide insight about KDE projects from one place instead of having to go through different sources. The project goal is about adding the Phabricator to list of data sources that KDE Reports can fetch from. Phabricator is a suite of web applications which make it easier to build software while working with teams. It manages a set of tasks in a workboard and organizes them in a workflow. KDE Reports will use the Phabricator API to get these data about different KDE projects from Phabricator, show graphs and make reports about them. An extension part for the project is refactoring the code, increasing test suite coverage and upgrading to Rails 5.</p>
<p>Vert.x is a toolkit for the Java Virtual Machine enabling the implementation of reactive, highly concurrent, polyglot applications. Thanks to its eventbus, any application can interact with Vert.x applications. The TCP EventBus bridge is a bridge built on top of TCP, meaning that any application able to create sockets can use the EventBus from a remote Vert.x instance. The main project idea is to create TCP EventBus clients for C , Rust , C# and Python. For each language, a library will be developed in order to let an application developed with the language to interact with the Vert.x Event Bus easily.</p>
While Python Stingray is powerful for X-ray timing, its computational overhead creates a massive bottleneck for processing multi-megabyte event files. My project builds upon Stingray.jl's high-performance foundation by introducing advanced cross-spectral analysis, time lags, and energy-resolved timing tools natively in Julia. To do this It took me Long research Hours and proper Interests matching around my Idea and I Finally came up with the Idea of building structured Powerspectrum and Crossspectrum types, alongside time lag and coherence tools for mapping black hole reverberation. My deliverables also include variability-energy spectroscopy tools, multi-threaded Lomb-Scargle periodograms for unevenly-sampled data, and intuitive one-liner Makie.jl plot recipes. Everything is backed by comprehensive test suites and cross-validated against the Python Stingray package to guarantee absolute scientific accuracy.
This project aims to improve playlist management in ListenBrainz by making it easier for users to search, organize, and interact with their playlists. Currently, while some backend support exists, the user experience lacks intuitive features for managing personal playlists effectively. To address this, I plan to implement four main features. First, I will complete and enhance playlist search directly on the user playlists page. Second, I will introduce tag-based organization, allowing users to categorize and filter playlists efficiently. Third, I will add in-playlist track sorting options such as sorting by title, artist, date added, and shuffle. Finally, I will enable users to view their MusicBrainz collections as playlists and optionally save them within ListenBrainz. The project will involve backend changes such as adding new database tables and API endpoints, along with frontend integration using React to provide a smooth and consistent user experience. The final deliverables will include a fully functional playlist search feature, tag-based organization system, track sorting functionality, and MusicBrainz collection integration, along with tests and documentation for all components.
Poppler (The C++ PDF rendering library used by Okular) does not support font subsetting as of now. In simple terms, if someone creates an annotation containing content "hello" with font Cantarell then the embedded font object inside the PDF will contain mappings for a lot of characters other than 'h', 'e', 'l' and 'o'. This leads to unnecessary increase in size. This project aims to solve this problem. My approach is to implement font subsetting by:- - Parsing appearance streams and default appearance of all modified annotations/forms on save, and build a structure containing key-value pairs of (fontname, ref) and the characters to be rendered with that font. - Another class consumes this structure, uses Harfbuzz to generate subsetted fonts, and replace the old font objects with the new ones.
Alaska's Arctic coastline is eroding rapidly, and tracking these changes at scale requires automated coastline extraction from satellite imagery. Manual digitization is too slow, and the existing pipeline has several gaps: training data includes cloud-affected and artifact-contaminated pixels, the dataset covers only 2017-2019, the model underperforms near coastal bluffs and in shadowed regions, and the pipeline outputs binary raster masks rather than the GIS-ready vectorized coastlines needed for erosion modeling. To address this, I have already studied the codebase end-to-end, fixed the bugs that were preventing the pipeline from running, and replaced the baseline U-Net with an Attention ResUNet - a pretrained ResNet-34 encoder with attention-gated skip connections and a combined BCE + Dice loss - achieving a Dice score of 0.941 and IoU of 0.921 on the current dataset. During GSoC, I will close the remaining gaps: integrate PlanetLabs Usable Data Masks to exclude bad pixels from training; expand the dataset to cover 2020 onward; improve segmentation in cliff and shadow regions; investigate SWIR and elevation data as additional inputs; and produce vectorized coastline outputs with per-transect erosion rates. The result will be a pipeline that runs from raw PlanetLabs imagery to quantified shoreline change, ready to apply across Alaska.
In Rust, trait visibility currently implies implementability. If a trait is visible within a given scope, it can also be implemented in that same scope. However, we do not always want everyone to be able to implement it. To address this, the so-called “sealed trait” pattern is used, which allows a trait to be used while restricting its implementation. This is typically achieved by defining a public trait in a private module. Similarly, field visibility implies mutability. However, we do not always want readable fields to be writable as well. As a result, developers often use private fields together with public getter methods. The Restrictions RFC extends the Rust syntax to be able to explicitly restrict the implementability of traits and mutability of fields. For example, `pub(super) impl(self) trait Trait {}` means that `Trait` can be used within the parent module, while its implementation is restricted to the current module. `pub(super) struct Struct { pub mut(self) field: u8 }` means that `Struct.field` is readable within the parent module, while its mutation is restricted to the current module. These impl and mut restrictions are optional. Although the RFC was accepted in 2022, implementation efforts have stalled. Our goal for this project is to implement both impl and mut restrictions in the Rust compiler.
Maglev is OneBusAway's next-generation, high-performance Go REST API server designed to replace the legacy Java architecture. To achieve full production readiness for real-world transit agency deployments, this project focuses on four core deliverables. First, it ensures strict 1:1 API parity through automated, field-by-field output validation against the legacy server integrated directly into CI. Second, it executes a complete Go rewrite of the GTFS merge and transformer modules, creating native CLIs that enable runtime multi-feed loading directly into Maglev. Third, the project integrates the GTFS-Flex specification to support demand-responsive paratransit services, and finally, it expands the existing GTFS-RT pipeline to handle real-time structural trip modifications. Together, these enhancements will transform Maglev from a fixed-route Western transit tool into a globally deployable platform capable of serving diverse transit ecosystems across South Asia, Africa, and Latin America.
The Ziff–Gulari–Barshad (ZGB) model describes how CO and O₂ molecules adsorb and react on a metal surface represented as a square lattice. CO occupies a single site, while O₂ dissociates into two oxygen atoms placed on adjacent sites. When a CO and an O atom meet, they form CO₂, which leaves the surface and frees up space. As the CO partial pressure (yCO) changes, the surface transitions from oxygen-poisoned (no CO₂ production) to reactive (CO₂ formation) and eventually to CO-poisoned. Apothesis is a kinetic Monte Carlo simulator that models these surface reactions with high precision. Building on the ZGB model and the Apothesis simulator, PyApothesis provides a clean, Python-first workflow for running, analyzing, and sharing Kinetic Monte Carlo experiments. From a single script you can change simulation parameters (temperature, pressure, lattice size, seed), define custom adsorption/reaction/desorption processes, and run reproducible simulations — then immediately visualize results with publication-ready plots. PyApothesis includes time-series coverage plots, stacked-area composition views, process-rate and event-count analyses, spatial coverage maps and profiles, and real-time playback of the lattice (color-coded by species) to inspect microscopic behavior as it unfolds. It automatically produces a comprehensive analysis report (plots, logs, and statistical summaries) so users don’t have to dig through raw files, and it exposes hooks to incorporate lightweight ML models for surrogate predictions, parameter scans, or pattern detection directly from Python. Altogether, PyApothesis turns complex surface-kinetics simulations into an interactive, interpretable, and reproducible toolkit ideal for both researchers and students.
This project will build friendly automation tooling to support community translation of the p5.js reference documentation (including p5.js core and p5.sound). The p5.js reference (API documentation) is authored in English via JSDoc comments in the source code, and the website currently offers documentation in five languages (English plus Spanish, Simplified Chinese, Korean, and Hindi) . As p5.js evolves, keeping these translations up-to-date is challenging. The goal is to create GitHub Actions and workflows that do not automate translation itself (which requires human nuance) but instead assist volunteer translators. These tools will automatically track changes in the English “source” docs, flag or open tasks for updates in other languages, suggest new translation needs (for newly added APIs), and streamline communication with translation contributors.
My proposal aims to enhance VouchMe, a blockchain-based testimonial platform, and revamp the UI of TNT (Trust Network Tokens), an ERC721 token system for verifiable trust relationships, to create a robust decentralized trust ecosystem. For VouchMe, I will improve user experience and security by integrating user profiles with Decentralized Identity (DID), enabling direct testimonial sharing via Waku, adding one-click social media sharing, and implementing a burn function to allow users to remove testimonials. Additionally, I will integrate comprehensive smart contract tests to ensure security and reliability. For TNT, I will redesign the landing page and create user-friendly interfaces for creating, managing, and viewing TNTs, ensuring a clear and seamless experience. The deliverables include a fully functional VouchMe with these enhanced features: profiles, DID, Waku-based sharing, and shareable testimonial cards, along with a polished TNT UI for improved usability and accessibility.
The proposal aims to add two new functionalities to the project Nettacker to increment the effectiveness of the tool and also enhance the user’s experience. These include (1)Adding the SSL/TLS modules to restore the functionality that were present in Nettacker v0.0.2, (2)Creating comparison functionality for comparing the current scan with another scan using scan ID. (3)And to make the necessary changes to the API & it’s Web UI to implement these new functionalities.
RTEMS (Real-Time Executive for Multiprocessor Systems) is a real-time operating system (RTOS) designed for embedded systems. The goal of the project is to improve the POSIX compliance of the OS, specifically by enhancing the Asynchronous Input/Output (AIO) interface. The main objective of this project is to implement missing methods such as lio_listio(), correct behaviors that do not comply with POSIX specifications, and add missing features to existing methods.
This project tries to solve the problem of importing two new file formats called H5P and IMS Content Package (SCORM). These packages' metadata needs to be extracted and used to create a course node ( topic node and resource node ) which will later be used to render the files for educational content. To make the content available offline, this project aims to download all the externally linked reference links and embed them along with the file. This will be achieved using various npm packages like JSZip and fast-xml-parser to parse and extract the metadata from the content files and JavaScript to download the externally linked files and embed them into the files for offline use.
Current limitations: The current Back End for the Functional Annotation of Animal Genomes project (FAANG) provides users with a public rest API to access data. But it has a few limitations. First, in order to fetch data from different Elasticsearch indices or to fetch details of different documents, user has to make multiple API request calls. Second, users have to write CURL queries to work with the API which users may find complicated. Proposed solution: The main aim of creating a new backend for the Functional Annotation of Animal Genomes project (FAANG) is to make accessing and handling required data for users much easier than the current setup. In order to achieve this the following are the main tasks for the project: First, creating a Back End for Fetching Data (BE Read): To create a GraphQL Server which will make it easy to fetch the required data using advanced operations like join and aggregations by making a single API call to the Back End. Second, creating a Front End for Fetching Data (FE Read): To create a UI for selecting which data is to be fetched. Hence using a GraphQL Server, user only needs to make a single API call, and with a better UI, user wont have to worry about writing queries for fetching data. Deliverables : 1. Basic Fetching of documents (single and multiple documents of an elasticsearch index) 2. Implementing Dataloader in the GraphQL server for decreasing DB hits 3. Implementing Filter and Join functionality between elasticsearch indices for fetching data from the GraphQL server 4. Implementing Aggregation for data to be fetched from the GraphQL server 5. Implementing Frontend interfaces to make data fetching easier and reduce mistakes from the user's side
<p>This proposal aims to bring a selection of much needed improvements to the knife tool in Blender which will better the modelling workflow of the tool. It proposes such changes as the ability to undo individual steps of the cutting process, a visual measure of distance and angles per cut, more precise angle control in constrained angle mode, the ability to snap cuts to global or local orientation, knife usage in multi-object edit mode and an edge removal mode.</p>
<p>QuTiP's data layer provides the mathematical operations needed to work with quantum states and operators, i.e. <code>Qobj</code>s,. As part of Google Summer of Code 2020, the data layer was rewritten to allow new backends to be added more easily. Backends using in-memory spares and dense matrices already exist, and we would like to add a backend that runs on GPU, either through Cupy or TensorFlow. This will decrease the computation time thus making it feasible to work on larger qubit systems.</p>
<p>In this proposal, I layout my strengths in machine learning, open source code and TensorFlow, and argue why I am the best candidate to work with the "Convert Matlab ML examples to Python / JAX" project proposed by the TensorFlow team.</p>
<p>FreeBSD's default mixer utilities are not the best; <code>mixer(8)</code> is very basic and outdated, end users have to tweak <code>sysctl(8)</code> values to do simple things and programmers have to write DIY implementation for their programs (e.g <code>audio/mixertui</code>). This project aims to improve mixer handling for OSS on FreeBSD and make life for both programmers and users easier.</p>
<p>MinPlatform is a project to get open-source EDK2 firmware booting mainstream boards. However, other than the Intel RVP development boards, presently it only supports the UP Xtreme and System76 Galago Pro 3 (discontinued).</p> <p>Therefore, I propose to develop a board port to an Acer Skylake platform. This adds another board port to the tree, resulting in open-source firmware being a little more widely available. I also hope that it encourages further work in this area.</p>
<p>Show logs and debugs in info editor. Add UI features to make it comfortable to work with logs such as filtering, searching, enable/disable on the fly.</p>