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>Text analysis is a fascinating field that attracts people from many scientific fields. As of today, text analysis is executed through powerful scripts, scattered to many packages and libraries of different programming languages, each of which contains only a subset of available linguistic features and requires high technical knowledge to be operated. As a result, it is difficult to obtain a unified result, with all the desired features and many people, who lack a computer science background, are excluded from using them. The goal of the project is to build an online web GUI, that provides its users with an easy way to extract quantitive text profiles from multilingual texts. The text analysis will come from scripts that combine many existing NLP packages, written in many programming languages, like R's udpipe or Python's spaCy. The tool is going to be modular and open source, in order to be easily accessible and adaptable to everyone's needs. The project is going to boost and facilitate scientific research in NLP fields, as it will make text analysis available to people with little to none computer science knowledge (e.g. linguistics students).</p>
<p>The CLTK features the most sophisticated algorithm available for lemmatizing classical Latin. Lemmatization is the process by which inflected word-forms are grouped together under their dictionary headings. This allows us to gather accurate word-usage statistics, analyze authorship, and model subject matter in classical corpora. However the CLTK lemmatizer is not currently able to identify synonyms for a given word, or suggest translations into other languages.</p> <p>I propose to modify the existing CLTK lemmatizer to look up synonyms and translations for Latin and Greek. I will adapt CLTK’s unique ‘backoff’ approach to lemmatization in order to measure the probability of each possible synonym and/or translation for a target word given its context. Further, I propose to incorporate vector models for Latin and Greek based on word embeddings trained using the word2vec algorithm. Once synonyms, translations, and vector models are incorporated into CLTK, users will be able to perform cutting-edge tasks like sentence length document alignment. This will open new horizons for digitally assisted classical scholarship.</p>
<p>A package which uses the Minecraft Pi API and corresponding mod for Java version to build <em>cool</em> stuff. Accompanied with documentation and tutorials to help out people with little to no programming experience. Includes scripts to build everything from spheres and cubes to Calculator internals.</p>
<p>Ambisonics is a full-sphere surround sound technique: in addition to the horizontal plane, it covers sound sources above and below the listener. FFmpeg as of now has no-support for decoding standard B-Format sound into any user-decided speaker configuration. The project would focus on implementing a fully-featured Ambisonic decoder, which decodes standard B-Format and converts it into the required speaker configuration. This would enable FFmpeg to decode Ambisonic files, right at the user-end and he/she will be able to create his/her own speaker configuration. This decoder would be implemented as a filter in FFmpeg/libavfilter.</p>
<p>This project aims at developing efficient algorithm to analyze complex 3D data obtained from the Liquid Chromatography Mass Spectrometry (LCMS). The algorithm is optimized for direct processing of the data by overcoming redundant parameters such as user defined parameters. Moreover, it is also intended to make an algorithm adaptive and compatible with existing mass spectrometry software.</p>
<p>My proposal is about going through the library's essential files, conducting performance tests. Identifying bottlenecks. Documenting all the analysis done. Discussing solutions. Start implementing the changes. Documenting the process.</p>
<p>Add web GL support for texture (u, v) coordinate mapping, add support for additional camera features, and fix bugs in the web GL renderer.</p>
<p>AppRecommender is a recommender system for Debian packages. Currently, this application can only be run through terminal commands. The idea of this project is to integrate it with graphical package managers, in order to reach more users.</p>
<p>My primary goal is to implement customisable shortcuts for the Pitivi video editor. Users will be able to set their preference for every single currently existing shortcut in Pitivi, which will improve the usability as well as speed up their work.</p> <p>I will extend Pitivi to use the new GtkShortcutsWindow for viewing of the shortcuts, as well as refactor the Preferences window in Pitivi to handle the customisation. For Preferences, I want the UI to be modern and sleek, thus I will use GtkStackSidebar.</p> <p>Finally, I want to bring the JKL navigation shortcuts to the Pitivi timeline. Users will be able to playback forward and backward at various speeds (up to 4x), depending on the number of times they press the J or L key, and play or pause the playback by using K.</p>
<p>Balrog is the new age update server used by Mozilla to serve updates to Firefox. This project aims to address a situation in Balrog where multiple locale updates caused a race condition, leading to unnecessary retries by submitter jobs. This project proposes to resolve this situation by using an algorithm similar to a three-way merge algorithm, but for nested JSON data.</p>
<p>The main goal of this project is to provide a new network view which is capable of visualizing curated TCGA pathways that are more attractive and more intuitive for the biologists with better analysis facilities using rich data of cBioPortal.</p>
<p>Parsing current strace output is not an ideal solution, because:</p> <ul> <li>this is excessively difficult: the output is intended to humans, not robots;</li> <li>because of the way the syscall info is printed, particularly, by printf'ing it with all of the braces and commas by hand in every syscall parser, the output can contain inaccuracies, making the task of parsing even more difficult. </li> </ul> <p>A more correct way would be for parsers to store parsed data in memory in a more abstract representation, which then could be used by various outputting engines, for example, a JSON engine or an engine for the traditional strace output.</p>
The new git repo command doesn't handle file paths yet, and it forces users to dump all repository data at once instead of just requesting what they need. This makes scripting difficult and forces developers to keep using the older git rev-parse command. This project improves the git repo info command in two main ways: First, by adding path.* keys (like path.git-dir) that can return both absolute and relative paths. Second, by building a fast, lightweight search system (O(log N)) so users can easily query specific categories of information. As a stretch goal, the project will evolve git repo structure into a diagnostic tool by introducing metric distributions, such as object size and entry histograms.
A Device Tree (DT) is a data structure used to describe non-discoverable hardware to the OS or bootloader. It is written in a device tree source (.dts/.dtsi) file, which is compiled into the kernel image at build time. This structure provides a standardized way to describe a system’s hardware topology. Device Tree bindings are the rules and conventions used to describe devices within the Device Tree. These bindings define how to represent various hardware components. Device tree bindings were historically written in human readable (.txt) format and developers had to rely upon manually reading these files and writing device tree source files accordingly. Now, these files are being converted to DT schema (.yaml) format so that semantic validation can be done on device tree sources automatically.
The goal of this project is to enable support for the High-Level Shading Language (HLSL) in clangd, allowing shader developers to benefit from modern language-server features such as code completion, diagnostics, semantic highlighting, and symbol navigation. Although HLSL is largely based on the C++11 standard and can already be parsed by Clang, clangd’s support remains incomplete due to missing handling of HLSL-specific constructs, semantics, and resource types. Additionally, shader development introduces unique challenges, such as multiple entry points within a single file (e.g., vertex and pixel shaders), which are not fully addressed by clangd’s current architecture. The project will begin with an evaluation of clangd’s behavior on HLSL code to identify gaps, followed by the design of appropriate extensions. An RFC will be proposed to the LLVM community to validate the design and gather feedback. Based on this, the project will implement key improvements to clangd, focusing on built-in function completion, semantic analysis of shader constructs, improved diagnostics, and better handling of shader-specific configurations. The final deliverables include a documented analysis of current limitations, an RFC describing the proposed design, a structured set of implementation issues, and upstreamed improvements to clangd, along with test coverage and documentation.
The LibreOffice BASIC IDE currently offers limited code assistance, hindering developer productivity with unreliable completion, no object browser, and no inline help (parameter/quick info). This project will implement a modern, comprehensive code assistance system. This involves creating [1] a robust backend analysis engine to parse BASIC code (editor/libraries) and introspect UNO objects for detailed symbol information (types, scopes, signatures), and [2] an efficient knowledge cache. These components will power [3] user-facing tools including: an integrated Object Browser for API exploration, significantly improved context-aware code completion (Ctrl+Space and enhanced '.'), and helpful Quick Info/Parameter Info tooltips. The final deliverable will be these features fully integrated and enabled by default, delivering a significantly more productive and intuitive BASIC development experience in LibreOffice.
Physicists at the LHC need to perform ML inference on massive amounts of data. Currently, the bookkeeping of ML model files is an unsolved problem. The goal of this project is to evaluate the CernVM File System (CVMFS) as a platform to store, organize, and distribute model files. The two primary issues to tackle are latency and infrastructure. We know there is a latency with using CVMFS versus local storage, so I will rigorously benchmark the performance of CVMFS and determine ways to minimize this overhead. For infrastructure, I will test integrating different services with CVMFS such as Cern Document Server (CDS) or Kubeflow's KServe. The final deliverables will include extensive documentation on benchmarks and best-practices for using CVMFS, and an overall evaluation of CVMFS and the possible integrations like KServe. An example deployment of ML models from the ML4EP project using CVMFS will also be demonstrated.
This project aims to use self-hosted runners to run GPU-intensive tasks like LLM blueprint or (planned) AI Playground. The necessary infra is provided by Oracle, plan is to use Oracle Kubernetes Engine (OKE) with NVIDIA GPUs for this task. Any code or sample that requires GPU-intensive resources will be transferred to OKE infra instead of generic GitHub infra for faster and more efficient execution. For now, the idea is to have a specific policy that whenever any Jupyter Notebook code will be added to a trainer/examples/pytorch/** folder (e.g., in trainer/example/pytorch/image-generation/sample.ipynb), that action is transferred to OKE infra by the GitHub self runner. For security reasons, this process will require manual approval from one of the maintainers to trigger the self-runner build. I will set up the GitHub workflow to monitor changes in the respective folder. Once approved, the CI action will execute the code using the GitHub self-runner on the OKE infrastructure. Additionally, we will set up a dashboard for monitoring and metrics to understand usage patterns and identify bottlenecks. The scope of this project is set up on OKE, but theoretically, this is platform-agnostic; it can be deployed on any Kubernetes cluster with sufficient GPU resources.
This project addresses the lack of automated testing in InVesalius, which currently relies on manual verification, slowing development and risking regressions. By implementing a comprehensive pytest-based test suite (unit, functional, and GUI tests) and integrating GitHub Actions CI/CD, the project will ensure core functionalities like DICOM processing, 3D visualization, and GUI interactions remain stable as new features are added. Deliverables include: 1)A structured test suite covering the entire inVesalius codebase. 2)GitHub Actions workflows to automate testing on commits/pull requests. 3)Mock file systems and dependency isolation for safe, repeatable tests. 4)Well-documented test cases to guide future contributors. This will reduce reviewer workload, accelerate debugging, and foster community growth by lowering the barrier to entry for new developers.
This project aims to overcome Blender's limitations with spreadsheets and other functionalities. The goal is to have a web interface running alongside Blender. This web interface ideally should be able to show tabular data for objects that Blender knows about, have real-time updates, and execute operators on them. Key tasks for this project include setting up an HTTP web server or a WebSocket connection for communication between the web interface and blender, Sending data from Blender to the web interface, and vice versa, displaying data on the web interface with the ability to execute operators that reflect in Blender, and If time permits, a dynamically generated Gantt Chart for work schedule. Deliverables: 1) Showing tabular data 2) Ability to execute operators 3) Dynamically Generated Gantt Chart
This project aims to utilize LLMs to make the library more accessible to the community. There will be a Discord, GitHub and X (previously Twitter) Integration. By reducing the barrier of entry, we aim to bring more people into using scientific visualization libraries.
I propose to implement a common interface to deploy the power of SciML to dynamical systems on graphs. In achieving this, one new package will be developed (I refer to it temporarily as ``PDEsOnGraphs.jl'') and two will be contributed to: modernization of FEniCS.jl with integration with FEniCSx/DOLFINx, and implementation of staggered-grid discretizations in MethodOfLines.jl. I propose this work to empower researchers modeling flows - be it water, sewer, natural gas, electricity, traffic, blood, etc. - by utilizing the power of the julia, and specifically the SciML, ecosystem.
This project aims to improve the previous iteration of the project where the hypothesis of it was the existence of a relation between the body gestures and the time expressions we speak and using neural networks we try to accept or reject this hypothesis. So, I proposed a new multimodal graph-based neural network architecture to classify the body keypose points by constructing a spatio-temporal graph and audio features are fused with it to converge the model to test this hypothesis. Also, suggested transfer learning to overcome the lack of data.
Documentation is not written or updated as much as it should be because the overhead is too great. This project aims on integrating existing tooling to provide an intuitive and accessible process to write and edit documentation. The implementation of this solution can be broken down into two phases: 1. Hotswapping page content for code editor 2. Generating pull requests based on content delta