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>I propose to work on the Kurmanji-English language pair, with the aim of improving it to the state of the art level, in terms of coverage and accuracy.</p>
Scrum Helper is a Chrome extension that helps developers automatically generate scrum reports from their source control activity. Today, it works exclusively with GitHub, leaving out a large portion of development teams who rely on GitLab, Gitea, or Bitbucket for their daily workflows. This project extends Scrum Helper into a true multi-platform tool. By introducing a clean plugin-based adapter architecture, each SCM platform gets its own isolated integration while the core reporting logic stays platform-agnostic. The result is a more maintainable codebase that any future contributor can extend with minimal effort. By the end of this project, developers on GitHub, GitLab, Gitea, and Bitbucket will all be able to generate automated scrum reports from a single extension, without changing how they work.
The Sugar Shell is the core desktop environment of Sugar and is responsible for activity launching, the Journal, the Frame, and system integration through DBus. The current Sugar Shell is built on GTK3, and several core components still depend on deprecated GTK3 APIs, which must be migrated to GTK4. This project focuses on the GTK4 migration of the Sugar Shell. The work includes replacing deprecated GTK3 APIs, migrating container and layout APIs to GTK4 equivalents, updating event handling using GTK4 event controllers, migrating styling to GTK CSS, and updating display and geometry handling using modern GTK4 display APIs. The migration will be done incrementally, component by component, starting with core components such as the Frame, Home View, Activity Launcher, Journal, Clipboard, and Control Panel. Each component will be migrated, tested in a running Sugar session, and submitted as small patches to ensure that the Sugar Shell remains stable and usable throughout the migration process. By the end of the project, the Sugar Shell will run on GTK4, core components will be migrated to GTK4 APIs, deprecated GTK3 APIs will be removed from migrated components, and migration documentation will be provided to support the remaining GTK4 transition work in the Sugar project.
Drupal Starshot Recipes speed up site building, but writing them requires deep technical skills. This project introduces an AI Recipe Generator that translates plain natural language requests directly into valid, installable Drupal Recipes. By leveraging the drupal/ai module, the system features Context Injection to map existing site entities and prevent configuration collisions. Furthermore, it utilizes a "Self-Healing Validation Loop" integrated with the Symfony YAML parser and the Drupal.org JSON:API to strictly validate module dependencies and eliminate LLM hallucinations. This tool lowers the technical barrier to entry, empowering non-technical users to build complex site features instantly while saving developers hours of manual debugging.
The goal of this project is to integrate pitch-correction into Blender's video sequence editor (VSE). While the editor supports retiming video and audio through the retiming keys, one particular feature that is missing for audio clips is being to preserve the original pitch of the audio when it is sped up or slowed down. So, this project will add a "Pitch Correction" toggle option to the audio strips in the editor, allowing the audio to retain its natural tonal quality if retimed.
This proposal addresses the lack of debugging tools for pocketpy, a lightweight Python interpreter for game scripting. It will develop a VSCode debugging extension along with Debug Adapter Protocol (DAP) support. The solution includes a debugger core that integrates with pocketpy's interfaces to support breakpoints, variable inspection, and call stack visualization, paired with a VSCode extension providing an intuitive debugging interface. Deliverables include a DAP-compatible debugger core, a VSCode extension with debugging configuration capabilities, and APIs for runtime inspection of variables and stack frames.
The Large Hadron Collider (LHC) particle track reconstruction faces increasing computational demands, driving exploration into novel methods like Quantum Computing QC. However, evaluating these requires assessing factors such as performance and sustainability. This project aims at developing a modular Python benchmarking framework to systematically compare classical algorithms e.g., Neural Network based against quantum approaches e.g., VQC simulated via PennyLane for tracking tasks using TrackML dataset. The framework will evaluate algorithms based on physics performance efficiency, purity, computational cost runtime, memory, quantum resource requirements gates, depth, and sustainability indicators simulated/projected energy consumption. The key deliverable is the framework itself, providing the community with a tool for quantitative comparison, understanding performance/sustainability trade-offs, and informing future directions in deploying potentially sustainable computing solutions for High Energy Physics.
The goal of this project is to enhance the Volesti library by implementing a sparse variant of the Billiard Walk sampling algorithm, which proposes to leverage lazy Cholesky-based solutions in order to preserve sparsity during rounding and sampling operations. Taking advantage of the sparse linear algebra infrastructure already present in the library, this project aims to improve the computational performance by implementing new methods that will perform dynamic, on-the-fly operations directly through triangular solves, avoiding explicit dense matrix transformations.
Organisations such as the Royal National Institute of Blind People (RNIB) are currently manually adjusting appearance settings like staff size change, line thickness change etc. in Musescore to aid users with low vision, as these features are scattered throughout the software. This manual adjustment process consumes significant resources and bandwidth, posing challenges for effective access and use of the software by individuals with visual impairments. The idea is to address this issue by introducing a new settings feature in MuseScore. This feature will provide a list of standard accessibility profiles, such as normal, large, etc., each one customised to specific needs of users with low vision. These profiles will collectively update a set of appearance settings, including staff size, page size, and other relevant ones, to enhance accessibility for users with visual impairments.
The project aims to build and publish python-cookiecutter templates for new PyBaMM-based projects. It is designed to simplify the setup process of the development environment for researchers and scientists interested in utilizing PyBaMM for battery modeling who may lack familiarity with managing Python environments or repositories. The project intends to enhance the accessibility and usability of PyBaMM for newbies and experienced users alike. Providing a standardized template with best practices and automation tools would lower the barrier to entry for adopting PyBaMM in battery modeling projects. This would in turn make battery modeling more accessible, efficient, and collaborative for the research community. The project also intends to implement "Model entry points'', allowing community contributors to create and share models of their repositories using the cookiecutter template without directly adding them upstream. This would not only let community contributors retain ownership and choose license terms but also grant flexibility to the PyBaMM team in supporting models, Including all of GitHub's functionality and infrastructure contained within the template.
The UI Toolkit serves as a component library tailored for crafting web interfaces within the Jupyter ecosystem, encompassing platforms such as Jupyter Hub, Jupyter Widgets, and Jupyter Lab. With the introduction of this toolkit, the aim is to capitalise on its capabilities to enhance UI consistency and alleviate maintenance overhead. Here's a structured plan to achieve this: 1.Use toolkit search/input for all search/inputs: filebrowser, extension manager, debugger kernel source 2.Use toolkit button for all buttons: Dialog, extension manager, notification, running tabs 3.Use toolkit tree view for all tree view: table of content, debugger variables and running tabs 4.Use toolkit for the settings editor 5.Add icon component to the toolkit 6.Use toolkit icon for LabIcon 7.Add window split component to the toolkit 8.Add tree grid component to the toolkit 9.Add dock panel to the toolkit 10.Explore switching default renderer in lumino by the toolkit: a.Menu b.Tab panel c.Dock Panel I am committed to collaborating closely with my mentor, @Frédéric Collonval, to tackle these challenges efficiently and deliver tangible results within the stipulated timeframe of the Google Summer of Code program.
The Oppia development team is looking to enhance the quality of their software by implementing Acceptance Testing on the develop branch. The problem lies in ensuring that the application’s functionality aligns with user expectations and that bugs are detected and fixed before release. The solution is to automate tests for every PR, ensuring that key user journeys remain unbroken, thereby enhancing the reliability and user experience of the software. This project involves writing acceptance tests for all user stories and fixing any minor UI/UX issues that cause e2e test flakiness. The deliverables include a complete suite of acceptance tests that are easily auditable and maintainable, ensuring that critical user journeys can be tracked, and new tests can be added for new features in an organized manner.
Incremental compilation is a technique that helps increase compilation speed by recompiling only changed files instead of your whole program (also known as performing a clean build). By the time of this project, the Kotlin/Wasm compiler supports only clean builds. This project enhances the Kotlin/Wasm compiler to support incremental compilation, thereby improving the development experience by reducing build times and increasing productivity.
<p>Information obtained from an <strong>Inertial Measurement Unit</strong> (IMU) is constrained due to physical limitations such as noise, drifts, misalignments and offsets. Since obtaining the state of a robot/vehicle requires integrating IMU outputs with time, the errors in the integrated estimates grow very fast. This project develops tools to accurately <strong>model the errors</strong> that affect IMU outputs, to <strong>estimate their relevant parameters</strong> and to understand <strong>how each parameter changes with time</strong>. Additionally, a <strong>sensor-fusion based pipeline</strong> is proposed for <strong>regularly correcting the estimated IMU parameters</strong>. The proposed method does not require any external mechanical setup and is designed to ideally work on low-computation processors and/or microcontrollers.</p>
<p>LoopSim framework aims to facilitate workflows with loops i.e workflows without specific start and end services. LoopSim requires an interface to create these types of workflows using some kind of graph.<br> It currently relies on a Closed Source software yEd - Graph Editor for workflow creation. The objective of this project is to remove this dependency on a closed source software and build an open-source solution tailored for LoopSim requirements.</p> <p>We also need to integrate this project with the existing parser so as to automate the flow from running the script and building the workflow to parsing it. The proposed solution will make it easier to web host the LoopSim project.</p>
<p>Description: The test system needs to be refactored and split up to speed up testing processes with the already existing docker container. Tests need to be split up in more sections/test suits so that we can execute them in parallel using our docker container The underlying FeatureContextFiles need to be refactored, cleaned, adapted where necessary and code duplications need to be removed Since we are on our way to introduce APIv2, it is a good time to check if our current Testsuite (Behat) is adequately equipped to extensively test our new API. If not an alternative should be found and implemented (in accordance with the rest of the team)</p>
<p>The dnn module of OpenCV.js has the ability and potential to develop interesting interactive deep learning applications on the Web. I'd like to expand the tutorials to attract more users and developers. In addition I used to write a sample image classification application with OpenCV.js which can be seen as a preliminary investigation, the link is <a href="https://github.com/akineeic/opencvjs-dnn-test" target="_blank">https://github.com/akineeic/opencvjs-dnn-test</a>.</p>
<p>Aim of this project is to introduce machine learning methods to learn about the surroundings for a robot’s navigation, we want to develop an agent which will learn all the corner cases and conditions which it needs, to properly navigate, without stating some predefined rules. The whole process of learning will be carried out by using the data it will get fed in such surroundings during real life scenarios. This project will be an expansion of the previous work “Learning socially acceptable behavior using machine learning techniques on graph data” (<a href="https://github.com/robocomp/sngnn" target="_blank">https://github.com/robocomp/sngnn</a>) in that project algorithms were developed to produce a single score for the robot to navigate, but it required high number of queries to work. This time we are aiming for generating these scores as a heatmap(such as the heat maps shown in <a href="https://ljmanso.com/sngnn" target="_blank">https://ljmanso.com/sngnn</a>) which can produce all the scores at once, this will be more efficient and faster than the previous work done. To solve this issue of generating all the scores at once we will try to generate a bitmap image using CNNs. As we are dealing with graphs of scenarios here we will be using GNNs.</p>
<p>The main research question or problem is to split the videos into named show and dated show. Identify anchor/show names or recognizes what show it is. Using the IMDb dataset (Will discuss in the proposal) to identify show names from anchor names (identified using MSCeleb). We Split the newsscape videos into smaller segments, one for each TV show, with annotations of show title, channel, time, date. Currently, the most time-consuming process in the program is that of going frame by frame and extracting faces. We can speed up using multi-threading.</p>
<p>New Camel website is a major migration of <a href="http://camel.apache.org/" target="_blank">http://camel.apache.org/</a> website. This work is focused on Camel 3 final release in September.</p> <p>Tools used to generate the website:</p> <ol> <li>Git :- a source code management tool used to fetch document sources from different GitHub repositories.</li> <li>Node.js :- a JavaScript runtime used to build the website. You will need to use Node.js version 10.</li> <li>yarn :- a blazing fast dependency and package manager tool used to download and manage required libraries.</li> <li>Gulp :- a task automation tool. Used to build the Camel Antora UI theme.</li> <li>Hugo :- a static site generator. Simplified, it takes the documentation from the content folder and applies templates from the layouts folder and together with any resources in static folder generates output in the public folder.</li> <li>Antora :- a documentation site generator. It uses Asciidoc documents from different sources in the Camel and Camel K repositories where user manual and component reference documentation resides and renders them for inclusion in this website.</li> <li>Maven (optional) :- a build tool used to run the complete website generating process</li> </ol>
<p>The main goal of this project is to implement and evaluate an adaptive radix tree as an alternative to the current underlying data structure of PostgreSQL’s buffer manager. The authors of ART presented experiments that indicate that it is a promising data structure for in-memory indexing of common data types. It is also space efficient, supports fast lookup operation, provides data locality and preserves order. Such properties can be useful during data integrity ensuring process and relation or index removal. Moreover, not only it utilizes the CPU cache more optimally and avoids cache misses, but also opens new perspective directions in the area of IO optimizations, such as prefetching and write combining.</p>
<p>Opportunistic IPsec is an attempt to encrypt the internet at large. The idea is to build VPN tunnels directly to all internet hosts irrespective of the communication used. An initial proof of concept was created that leverages LetsEncrypt certificates for use with IKE and IPsec. The goal of this project is to turn this proof of concept into production quality code that makes it trivial to enrol and deploy on any server and any client.</p> <p>The project has the following objectives:</p> <ul> <li>Automate Client, Server configuration and the enrollment and updating of LetsEncrypt certificates for use with libreswan.</li> <li>Implement a DNS/DNSSEC based method for advertising Opportunistic IPsec support using LetsEncrypt for servers.</li> <li>Design a non-DNS based method for publishing support of LetsEncrypt based Opportunistic IPsec for servers.</li> <li>Enhance libreswan to allow a secure fallback to the existing NULL Authentication method.</li> <li>Ensure the working of two behind the same NAT. Along with ensuring the working of two clients behind NAT, with one not using IPsec.</li> <li>Support the recovery from server OR client reboot/crashes. Along with ensuring no lockouts happen.</li> </ul>