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.
ClangIR is the newest attempt to tackle the lack of a higher-level intermediate representation for C++. Said representation would greatly benefit the community by enabling a myriad of passes that are either impossible or too complex to execute in LLVM IR, benefiting thousands of developers and legacy code. Ensuring ClangIR's success, however, requires coverage, correctness, performance, and an acceptable build time overhead. This proposal aims to increment the ClangIR compiler to compile part of the LLVM’s SingleSource test suite, further advancing its development. This includes but is not limited to, implementing missing AST visitors, operations/instructions, types, and testing. After sufficient implementations, it should be possible to use the SingleSource programs to analyze the compilation through ClangIR, evaluating its trade-offs against the traditional lowering process.
This proposal aims to contribute to addressing the challenge of generating formal SPARQL queries from natural language questions, thereby facilitating intuitive question-answering from open knowledge graphs, such as DBpedia. Among the three major approaches to this task, i.e., classification, ranking, and translation [Chakraborty et.al, 2019], this proposal will primarily focus on the latter one (translation). The key motivation behind choosing the translation approach is the significant performance improvement observed with the use of pre-trained language models such as T5 or GPT models in translation tasks.
Improve existing functionalities and add new ones to IntelOwl for release of v4. - Allow plugin secrets to be stored and managed from GUI #978 - Allow analysis of multiple IOCs in one call #732 - Add support for external authentication methods #121 - Provide navigable JSON result for each analyzer #959 - Add hashes to File_Info analyzer #270 - Allow plugin configurations to inherit (extend) from each other #752 - Allow editing plugin params from the GUI #433
The project I want to focus on is developing a more compact version of DIY robot for younger students,opposed to the more modular design it currently has . This robot will have a compact design with little or no expandability in order for the students to engage more in the robot’s programming and understand various concepts. For that reason, we will have to ensure the robot’s resilience to avoid accidents and make it durable. Apart from that, I plan on developing use-case scenarios in greek, ready to use by the teachers, including course objectives and possible extensions for each one.It would be nice to also develop extensive and simple guidelines of how to print and assemble the robot for everyone to follow, despite their technological background. Since we want the students to focus on programming and learning to develop their own algorithms, it is important to develop an easy-to-use, kids-friendly environment, preferably a desktop app, integrating Google’s Blockly. During the last GSoC, an API system was developed, so that using Blockly is expected to be easy. So, I would love to connect both the compact version and the full one with Scratch/Blockly following ELLAK ‘s aesthetics, like this existing prototype. The app should be colourful and have an interactive design, specially designed for students, also having multiple pop ups and information about their actions and whether they were successful or not. I would like to turn programming into a fun activity, so that the children can learn while having fun. However, since Blockly’s integration requires modifying the core library, I plan on rewriting some parts of the Raspberry Pi’s code concerning movement control. There will be a custom functionality library for special control of every electronic part and sensor.
<p>CalibrateSDR is designed to accurately determine the frequency offset of an SDR via an IQ recording sample. Cheaper SDRs use a low-quality crystal oscillator which usually has a large offset from the ideal frequency. Furthermore, that frequency offset will change as the dongle warms up or as the ambient temperature changes. The end result is that any signals received will not be at the correct frequency, and they would drift as the temperature changes. CalibrateSDR can be used with almost any SDR to determine the frequency offset. As of now, it uses the synchronization channel symbols from DAB+ digital audio stations to determine the offset. The primary focus of this project is to extend the applicability towards more signal standards, so as to make it helpful for the SDR community. As DAB+ is mainly used in Europe, Signal standards like GSM, LTE, NOAA-Weather Satellites, DVB-T (use their sync pulses within the data) can be used. Currently, it uses the pyrtlsdr package, which makes it work with RTL-SDR. Piping the API to work with other SDRs will also make the project have a wide range of applications in the SDR Community.</p>
<p>This project should broaden the functionality of being able to specify flags for compilation profiles, which is so far quite limited. It should also allow the support of different argument types. Therefore the user should be able to specify project local arguments, which are not overwritten by main package arguments when a project is used as a dependency and also argument types, which are applicable for the whole project.</p>
<p>The Axiom Beta currently uses CMV12000 which is a high-speed CMOS image sensor with 4096 by 3072 pixels.The pixels are located at different channels and are read out at a different moment in time. My aim is to remap the pixels on the outputs to their correct image array location.</p>
<p>Debuggers are essential tools in aiding developers to do their work more efficiently. They are inherently tied to the target operating system, and therefore require platform-specific work in order to deliver functional parity between different platforms. Swift is a multi-platform programming language, and having a good debugging experience in all platforms is beneficial for the language. With that in mind, I propose to improve LLDB’s support on the Linux operating system by: fixing Swift type metadata parsing for ELF objects; unifying queries of dynamic type resolution under the RemoteMirrors API; and, finally, enabling tests which currently do not run on Linux, or are marked as expected to fail.</p>
<p>This Project intends to add the PRU support to RTEMS, using the Beaglebone Black (BBB). The BBB has an Texas Instruments AM3358 SoC with an Programmable Real-Time Unit (PRU). The PRU is able to connect to the SoCs i/o within one cycle. This will enable the RTEMS community to develop heavily i/o dependent tasks on the Texas Instruments SoCs with PRUs.</p>
<p>The aim of this project is to integrate seamless support for the WOFF File Format 2.0 into FreeType so that these fonts can be recognized, decompressed, and loaded as any other SFNT font. This includes study and comparison of how SFNT fonts are wrapped into WOFF 1.0 and WOFF 2.0 files, exploration of existing libraries for WOFF 2.0 and Brotli compression, and finally, writing code to allow FreeType to handle WOFF 2.0 fonts.</p>
<p>CLocal gcp will be a tool which can be used to test Google cloud products locally before running them in the actual cloud platform. And later migrating them to the cloud. This will save cost and will be a more developer friendly experience.</p>
<p>The Humanitarian OpenStreetMap Team (HOT) applies the principles of open source and open data sharing for humanitarian response and economic development. HOTs provides free, up-to-date maps are a critical resource when relief organizations are responding to disasters or political crises. This is a great initiative started back in 2010. I have chosen this project because of two major reasons, first being the organization itself and the motive behind the project which I found very interesting and important to work on, secondly the technology stack the project is using Javascript/NodeJS for APIs and React for the frontend.</p>
<p>digiKam is a desktop application for photos management. Providing a wide range of plugins for exporting photos to web services (e.g dropbox, flickr, facebook, google, etc.), digiKam's export tool allows users to easily upload their photos to cloud storage services, social networks or sharing platforms.</p> <p>Current export tool authentication process makes it far from easy-to-use for users. In addition, authentication protocols varies much for each web service, generating many difficulties for implementation and maintaining. Hence, this project is aimed to resolve those problems by implementing authentication flow with O2 library, in order to make export tool more user-friendly and more flexible for development and maintenance.</p>
<p>The focus of this project is to add sectors to the Terasology engine. Sectors are a level of entity storage between block-scope and world-scope, which allows entities that would usually be put in the global scope to be split into multiple groups. Each of these groups can be run on a separate thread, or even on a separate server node.</p> <p>Sector-level entities are still loaded when their chunks are unloaded, allowing simulations to continue when the player is away, but they can be stopped if a whole sector is unloaded to increase performance.</p>
<p>Using PostgreSQL (PG) on the daily basis for years I found that there are some use-cases when you need to load (e.g. for a further analytics) a bunch of not well consistent records with rare type/columns number mismatches. Since PG throws exception on the first error, currently the only one solution is to preformat your data with any other tool and then load to PG. Frequently it is easier to drop certain records instead of doing such preprocessing for every data source you have.</p> <p>The naive solution here is to wrap up an insert of each record into subtransaction, however, it will ruin COPY performance and burn transaction IDs (XIDs) very rapidly.</p> <p>Parallel execution may help both to boost COPY performance on multi-core systems and to catch errors via running the separated worker processes.</p>
<p>My project is to implement a complete micro blogging system on top of Matrix. With the available infrastructure, I can build a web client for Matrix designed specifically for this.</p>
<p>Using Ceph's JSON dump we can create a utility to help decipher whether or not a disk is safe to remove from within a Ceph cluster. Since Ceph shuffles placement groups when a disk is added or one dies then the user must be able to discern which disks are safe to remove. Using Ceph’s JSON output of a given cluster a user can be presented with an easy to understand representation of removable disks.</p> <p>This project consists of one main component, a standalone command line utility.</p>
The eventyay platform consolidated its talk and video components into a single codebase, but the integration between them remains manually wired and fragmented. Organizers must manually keep talk rooms and video rooms in sync, there is no system for assigning MCs to video rooms, and the video interface shows no speaker or session context — all four gaps confirmed through direct codebase audit and live instance testing. I will build the missing integration layer and deliver: an event-driven room sync system using Django signals and the existing Channels broadcast infrastructure, a full MC assignment system with model, API, admin UI, and email notifications, and a speaker metadata pipeline that pushes TalkSlot data into the Vue.js video interface in real time. Having worked in this codebase, I noticed these gaps firsthand while testing my own PRs — creating a room in the talk component and switching to video still requires manual coordination. I've worked with the exact role-assignment and notification architecture this project replicates for video rooms.
WebAssembly's call stack limit is unspecified by the spec and varies across host environments. As a result, any Kotlin/Wasm program that uses mutual recursion or deep tail calls is vulnerable to stack overflow at runtime, with no way to guarantee safe execution across browsers and runtimes. Kotlin's existing tailrec modifier mitigates this for simple self-recursion by rewriting functions as loops, but it cannot handle mutual recursion or indirect calls, and requires an explicit annotation that many developers will not add. The WebAssembly Tail Call proposal (standardized and part of the Baseline target since 2024) addresses this at the instruction level with return_call and return_call_ref, which discard the current stack frame before transferring control and reduce stack consumption from O(n) to O(1) regardless of recursion structure. This project integrates that proposal into the Kotlin/Wasm compiler backend. The work covers adding the missing RETURN_CALL opcode to the Wasm IR layer, detecting tail call positions in the code generation pipeline and emitting return_call and return_call_ref in place of the current call + return two-instruction sequence, writing a test suite covering mutual recursion and virtual dispatch across multiple host environments, and benchmarking return_call against the existing loop transformation to evaluate the tradeoffs.
This project enhances ros2_tracing by addressing its key limitation: recording trace data previously had to be started before application launch to capture initialization data, which is critical for later analysis. The solution introduces a dual session tracing mechanism using LTTng’s snapshot mode, which preserves initialization data in memory and saves it to disk when recording begins at runtime. This ensures all required events are recorded. The added features will significantly improve debugging workflows for ROS 2 developers. Additional contributions include snapshot session support, new tests, and updated documentation.
Managing large libraries of media files efficiently is challenging, especially when dealing with diverse formats, extracting metadata, and performing fast searches. This project aims to develop a lightweight CLI-based Library Content Manager that automatically scans directories, extracts metadata using FFmpeg/TagLib, and organises media files in an SQLite database for efficient querying. To ensure speed, this tool will monitor directories in real-time (using inotify/ReadDirectoryChangesW), and to encourage personalisation, custom user-defined tagging, and fast search/filtering via structured queries will be implemented. Users can interact through a Command Line Interface or an IPC-based API, enabling integration with external tools. A dedicated plug-in will be developed to allow a seamless and intuitive integration with ossia score. Performance is crucial and thus multithreading, batch processing, and optimised indexing strategies will be implemented to ensure responsiveness even when handling large libraries. Existing solutions are either GUI-heavy or lack structured querying but this tool offers the best of both worlds. Therefore, this tool will provide a robust and extensible solution for organisation of media files, making it a great help for artists, developers and creative professionals.
This project aims to enhance SU2's computational fluid dynamics (CFD) capabilities by optimizing the Neural Network implementation (MLPCpp) within its Non-Ideal Compressible Fluid Dynamics module. I will address key performance bottlenecks in the current system, including inefficient variable mapping, suboptimal network selection, sequential evaluation, and limited inverse regression approaches. My solution involves implementing hash maps for faster lookups, refactoring network selection, improving evaluation with SIMD instructions, batched inference, and improving inverse regression with literature-backed starting points. The project will be delivered through two main pull requests: the first focused on an improved data-driven tutorial with step-by-step guides and troubleshooting resources, and the second containing the optimized source code implementation and comprehensive benchmarking results, making data-driven approaches more accessible and efficient for all users.
Juice Shop is an intentionally vulnerable web application designed for practicing security testing and improving security skills. Blockchain technology is becoming increasingly popular with adoption coming in within large MNCs as well, and there is a need for security experts who can test blockchain-based applications. This proposal aims to integrate blockchain-based challenges into Juice Shop to provide an opportunity for users to learn about blockchain technology and its security aspects in a fun way. As part of GSoC 2023, The aim is to integrate multiple blockchain based challenges including plain smart contracts to NFT based contract vulnerabilities into Juice Shop starting from very beginner level challenges to covering a few advanced challenges. I will be adding: 2 Easy 2 Medium 1 Difficult challenges as part of this GSoC.