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.
This project aims to implement the ANY_VALUE() and GROUPING() functions in MariaDB, addressing longstanding gaps in compatibility with MySQL 8.0 and modern SQL standards. Currently, the absence of these functions limits MariaDB’s usability in applications that rely on advanced GROUP BY semantics, particularly when migrating from MySQL or working with rollup queries. To solve this, I will extend MariaDB’s SQL parser and execution engine to support both functions. For ANY_VALUE(), I will implement a new aggregate function that allows safe selection of non-aggregated columns under ONLY_FULL_GROUP_BY. For GROUPING(), I will introduce a function that distinguishes between NULL values originating from rollup aggregation and those present in the underlying data, by tracking rollup state during query execution. The primary deliverables of this project include fully functional implementations of ANY_VALUE() and GROUPING() in MariaDB, comprehensive MTR test suites validating correctness and MySQL compatibility, and updated documentation describing their usage and behavior. The final outcome will improve MariaDB’s standards compliance and provide developers with essential tools for writing expressive and portable SQL queries.
The project focuses on the eventyay Badge Creator into a reliable, production-ready badge printing system for live events. The plugin currently provides a visual layout editor, PDF generation, and basic check-in integration, but the connection between checking in an attendee and getting a badge in their hand is still fragmented and manual. There is no automated flow between a successful scan and a printed badge, no way to track or retry a failed print job, no support for pre-generating badges before peak check-in begins, and the entire badge module has no automated test coverage. This project addresses all of that. It delivers a fully automated check-in-to-print workflow where volunteers simply scan a ticket and the system handles everything else. Organizers gain the ability to configure badge printing behavior per station, manage layouts through a complete API, and pre-generate badges for all attendees before the event starts. The project closes with comprehensive test coverage across the full badge lifecycle and documentation covering both system architecture and event-day operation, making the system maintainable and ready for production use at events of any scale.
The LHC at CERN generates 30 petabytes of physics data every year. Current compression tools like LZMA treat this data like any other file and miss the statistical patterns unique to particle physics. The BOA Constrictor solves this by training a neural network to predict the next byte more accurately inside an entropy coder. The original BOA paper proved the concept works (4.03x compression on CMS data vs LZMA's 3.22x), but two gaps remain: Mamba doesn't install on Python 3.12, and nobody has compared alternative architectures under fair conditions. This project will build a benchmark suite comparing GRU, LSTM, MinGRU, Transformer, and Mamba under parameter-matched conditions. It will then optimize the best backbone using INT8 quantisation, pruning, and distillation, producing Pareto frontier plots showing compression ratio vs model size. Finally, it will explore physics-informed priors as an auxiliary loss to improve predictions. All code and results will be contributed back to the upstream BOA repository.
Karpenter is a dynamic Kubernetes node autoscaler that provisions compute resources in response to real-time workload demands. While Karpenter is powerful, it lacks a native UI for visualizing its autoscaling behavior and managing its custom resources. This plugin will integrate Karpenter-specific insights into Headlamp, leveraging Headlamp’s existing CRD support to provide a focused, user-friendly interface for understanding and managing Karpenter’s decisions. Expected Outcome: A Headlamp plugin that provides: 1. Show Karpenter Provisioners, NodePools, and NodeClasses, including their constraints and current status. 2. Real-time display of scaling decisions, such as which pods triggered provisioning and why. 3. A dashboard for pending pods with unmet scheduling requirements, highlighting why they couldn’t be scheduled. 4. Integration with Kubernetes events and Karpenter metrics to show provisioning latency, node lifecycle events, and cost efficiency. 5. A configuration editor for Karpenter Custom Resource Definitions(CRDs) using Headlamp’s existing CRD facilities. 6. Documentation and possibly a demo video or blog post.
<p>The Infobiotics Workbench (IBW) is a synthetic biology design tool with three major functionalities: stochastic simulations, which mimic the procession of complex biological pathways; verification of simulation rulesets; and biomatter compilation. Its simulations are driven by designs written in the domain-specific Infobiotics Language (IBL), which contains data that is then sent to the Biocompiler to be built into a Biocompiler Model internal structure.<br> Currently, IBW offers limited support for two standard biological languages, the functionality-based Systems Biology Markup Language (SBML) and the design-based Synthetic Biology Open Language (SBOL), a common medium of exchange for synthetic devices. While SBML is made use of by the simulation aspect of IBW, the design-based SBOL is used by the Biocompiler as a format to write its compiled design into. This project aims to enhance the Biocompiler’s ability to export and import SBOL and SBML. If IBW’s capacity to work with these two biological modelling standards is improved, its accessibility to computational biologists around the world would increase dramatically. Hence, this project will enable this integration.</p>
This project aims to ease the transition and implementation of Posits, an alternative numerical representation, for RISC-V systems. By creating a robust hardware abstraction layer (HAL), developers need not know if the target RISC-V platform has a hardware Posits implementation or requires a software implementation. This new POSIX-compliant C++ library (with ports planned eventually) will help make available the option to transition between IEEE Float / Doubles to Posits and should make the machine-specific selection and configuration seamless. The lack of such a HAL is a roadblock in Posit adoption and Posits represent a serious opportunity for free and open source silicon (FOSSi) systems. We will also update the existing posit implementations to the current standard and add consistent unit testing. Initial focus will be directed toward HPC support, where numerical computation efficiency may be best observed. Additionally, we will be conducting benchmarking studies to evaluate the performance of the HAL, identifying bottlenecks, and iterating on the design based on empirical data. The testing framework will also be part of the mentee's deliverables.
GIMP utilizes a Destructive Editing workflow – all changes are made directly to the image itself. A much requested feature is Non-Destructive Editing (NDE) which would allow users to make changes without overwriting the original image. This would mean they can easily revert prior edits, modify the settings of filters to see live changes, and rearrange the order that effects are applied in. GIMP’s image processing engine GEGL is fully capable of many NDE operations. However, these features are not fully exposed to users. The goal of this project would be to enable Non-Destructive Editing on individual layers and layer groups through “Layer Effects” such as drop shadows and brightness/contrast filters. A basic implementation consists of three milestones: 1. Research and design a NDE workflow that compliments GIMP’s current design and user base. 2. Implement “Layer Effects” for GIMP’s regular and text layers as well as layer groups. 3. Add support to the PSD plug-in to recognize and import equivalent “Layer Styles” and “Adjustment Layers” as NDE Layer Effects.
<p>Graphs are a ubiquitous and versatile data structure, which allow the representation of problems and systems across a vast array of domains like infrastructure networks, molecular models, language, and social interaction. Recent community work on graph computations has culminated in a standard API which casts graph computations as generalized linear algebra on sparse matrices. This enables performant, standardized graph algorithms which are easily differentiable by modern auto-diff tools. In this JSOC 2021 project I aim to provide automatic differentiation rules for all of the operations in the GraphBLAS C API which admit such rules. The SuiteSparse GraphBLAS (SS:GrB) implementation will be the primary target, and support for the several extensions to the specification in SS:GrB is also a goal. The primary application I am pursuing is an efficient implementation of graph machine learning in Julia, but it should be noted that graph computation and generalized sparse linear algebra have incredibly broad use cases including graph algorithms like breadth first search, and faster neural networks by taking advantage of sparsity and operators faster than typical multiplication.</p>
<p>My plan is to add a new backend by enabling WebGPU in OpenCV.js. There have been many sophisticated GPU backends including Cuda,OpenCL,Vulkan and Halide, these GPU backends can provide reference for porting some kernels' shader code of OpenCV GPU backend to WebGPU. The concepts of pipeline and buffer of OpenCV Vulkan backend have many functions that are similar to WebGPU API, so I will try to write a library to enable emscripten to convert the used Vulkan API to WebGPU API. Specifically, the mapping from OpenCV Vulkan backend to OpenCV.js using WebGPU can be roughly divided into three parts. First of all, mapping Vulkan buffer to WebGPU buffer to access the storage of WebGPU.Secondly, mapping Vulkan API calls for pipeline and command buffer to WebGPU API. Thirdly I’ll reuse Vulkan's shaders. It’s feasible to reuse Vulkan’s shader directly in Chrome. Another possible approach is using SPIRV-Cross to convert SPIR-V in Vulkan shader to readable, usable and efficient GLSL/HLSL.</p>
<p>De-novo sequence assembly is the process of constructing a contiguous long sequence out of shorter sub-sequences produced by sequencing platforms, without referring to a reference genome. It is an essential task in many biological studies today, including population and medical studies. The initial stages of de-novo assembly require the construction of a de-bruijn graph (DBG) from sequencing reads, the compression of a de-bruijn graph into a unitig graph, and the compression of multiple unitigs and nodes into contigs, supported by evidence from mapping paired-end reads. A coherent ecosystem of computational tools and packages allow researchers to quickly implement and test their ideas. For bioinformatics, Julia already offers such an ecosystem in the form of the BioJulia & EcoJulia projects, and additional independent packages. This project will add sequence assembly tools to the BioJulia ecosystem, specifically: 1) DBG construction from reads, 2) UG construction from a DBG and 3) Constructing contigs using unitigs. These tools will allow researchers to quickly construct and analyze the contigs obtained from a set of reads.</p>
<p>Natural Language Generation is the process of generating coherent natural language text from non-linguistic data. Though the community has been generally going for speech and text output for these models, there has been far less certainty in the inputs. A large number of inputs have been taken for NLG systems including images, numeric data, semantic representations and Semantic Web (SW) data. Presently, the generation of Natural Language from SW, more precisely RDF data, has gained substantial attention and has also been proved to support the creation of NLG benchmarks. However, most models are aimed at generating coherent sentences in English, whilst other languages have enjoyed comparatively less attention from researchers. RDF data is usually in the form of triples, . Subject denotes the resource, predicate denotes traits or aspects of the resource and expresses the relationship between subject and object.</p> <p>In this project we aim to create a multilingual Neural verbalizer, ie, generating high-quality natural-language text from sets of RDF triples in multiple languages using one stand-alone, end-to-end trainable model.</p>
We need enhanced integration tests to prepare OpenCost for graduation and enterprise readiness. This proposed project will deliver a comprehensive suite of integration tests designed to facilitate development and contribution by third parties, while protecting the stability of OpenCost for our tens of thousands of users. These tests will validate both the quality of the data collected by OpenCost, and the correct operation of the APIs. We have recently implemented a pipeline that builds real stacks for these tests to hit - we now need to fill that framework up with great tests. See the testing strategy document @ https://github.com/opencost/opencost/blob/develop/docs/testing/AUTOMATED_TESTING.md for the current state of testing, and the infrastructure that we have put into place to support this mentorship effort. Expected Outcome: 1) A comprehensive integration test suite as defined in the linked ticket. 2) All tests run and pass automatically in pre-existing per-push integration test pipeline. 3) Approach for each integration test is documented 4) Endpoint coverage % and parameter coverage % is calculated 5) Any unfinished or follow on work is documented via issues on OpenCost
A multimodal corpus is a treasure trove of language data. In this project, we’re diving into Farsi-language content from public broadcasts. Through the integration of many media formats, a multimodal corpus offers an abundant resource for linguistic analysis, allowing scholars to investigate patterns and behaviors of language across diverse modalities. Using Red Hen’s YouTube pipeline, the initiative aims to build a comprehensive and varied collection of Farsi-language content from public broadcast media. In order to do this, we will use yt-dlp to seamlessly acquire data from YouTube and other media sources, and OpenAI’s Whisper, which is an automatic speech recognition (ASR) system that can generate highquality subtitles for videos, will intervene in the case of videos without subtitles to guarantee that no important linguistic information is lost. One of our main goals is to pinpoint the most effective natural language processing (NLP) pipeline tailored specifically for spoken Persian. Ultimately, the envisioned pipeline will streamline the process, accepting a list of video URLs and seamlessly transforming them into a functional multimodal corpus within CQPweb.
The aim of this project is to use IVY as a framework and build that into TensorLy project so that TensorLy would be usable with any of the frameworks supported by IVY. This will allow TensorLy users to switch backends via IVY’s backend handler rather than their own native backend handler. Set of deliverables are as follows: Implementing the desired functions in tensorly/backend/ivy_backend.py which will enable users to now use IVY as a framework in TensorLy. Implementing TensorLy’s abstraction layer (functionalities like Tensor Decomposition, Tensor Regression and Tucker Tensors) by using IVY as the framework. Implementing new functions into Ivy’s Functional API which exists in TensorLy’s API but currently not present in IVY’s Functional API (for example: context, index_update, ndim, sign, logsumexp, Conj). Creating demos that demonstrate how the functionalities can be used while building projects using TensorLy when IVY’s backend handler is being used. Running tests and implementing benchmarks showcasing the difference in runtime performance. Documenting the benchmark evaluations in a notebook for further research. Extending features with suggestions from the community.
Currently, OpenDaylight project relies on Robot Framework to run CSIT (Continuous System and Integration Test). This has proven to be very stable and scalable framework for 10+ years, however times have changed and developers working in agile mode usually write system and integration code along with writing new features. In the new paradigm, Robot framework is more an obstacle than a help since developers have to ramp up in a new language that soon find very limiting compared to python or other language. The work in this internship is to look up modern open source test framework (python based) that are well supported and maintained (e.g. pytest, nosetest , etc), select one and write the core test libraries (e.g. REST, SSH, install ODL, etc) so that developers can start using this framework in addition to the existing Robot Framework. Interested Interns: DO NOT apply through this platform. Due to a bug, please go to https://wiki.lfnetworking.org/x/CKsZB Read the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org
Last year, work on GestureCap focused on developing an Arduino-based latency measurement system and optimizing the pipeline for low-latency performance. Additionally, OSC-based communication between Python and PureData was implemented to enable real-time audio processing. Building on this foundation, this project will introduce AI-driven gesture recognition using lightweight, GPU-accelerated models to improve accuracy and responsiveness. The gesture-music mapping will be expanded to support both trigger-based events (e.g., drum beats) and continuous controls (e.g., pitch, reverb, and panning), allowing for more expressive musical interactions. The project will also integrate GestureCap with MaxMSP and Ableton Live, making it more accessible to musicians and producers. Further improvements will focus on latency reduction, real-time inference optimizations, and testing OpenPose-based feature extraction as a potential enhancement. If time permits, a visualizer for live gesture-music interaction will also be developed. These advancements will refine GestureCap’s capabilities, ensuring a more responsive and expressive experience for users.
This project will involve refactoring the Human Neocortical Neurosolver (HNN-core) codebase to enable flexible development of neural circuits with customizable cell types. Currently, HNN-core contains hard-coded assumptions about cell types, locations, and connectivity that limit researchers' ability to implement networks with different architectures. I will restructure key modules to replace these hard-coded constraints with dynamic definitions, allowing users to flexibly select and connect cell types with different morphologies and electrophysiological properties. The solution involves refactoring cells_default.py for dynamic cell creation, modifying network.py to handle arbitrary cell types, and updating related components to support custom cell types. The proposed plan includes dynamic cell type implementation, updated network connectivity handling, a demonstration model with custom cell types, comprehensive documentation, and unit tests ensuring backward compatibility. This work will significantly enhance HNN's capabilities for hypothesis testing in EEG/MEG research while maintaining its user-friendly approach for neuroscientists.
<p>Current version of Newman ships with a command - newman run - that allows users to effortlessly run and test postman collections from the command-line. We are in the process of writing a new command - newman request - that will enable users to run single requests from the command-line. Newman request will be a drop-in replacement of curl which will allow users to show additional details like response time, size of data received, first byte time, DNS lookup time, etc. in CLI. Replacing curl with newman request in a curl command should run and send the request using Newman.</p> <p>Users will be able to use existing features of Newman like showing output with reporters of their choice that provide information about a single request in a format that is easy to both disseminate and assimilate. Existing reporters like HTML, JSON, progress, etc. will be supported. To achieve these objectives, we are using curl-to-postmanv2 plugin to convert the command to postman collection with a single item. The created collection is then run using postman-runtime.</p>
<p>Currently, Atarashi has 4 active agents types that use 9 different types of algorithms to find the similarity between license statements. According to the evaluation of all the agents and their types, it can be seen that there is a need for improvement in the speed as well as the accuracy of the agents. I’ll be implementing the basics of Lucene and percolate search on the top of different agents to increase the speed of the agent without much tweaking with their original algorithm.</p> <p>A python library for code comment extraction is needed to be created with various additional features for providing support to Atarashi as well as FOSSology. This will be packaged & published to PyPI for easy installation and usage.</p> <p>For any Machine Learning/Deep Learning model to be implemented we need a dataset of SPDX open-source licenses. There isn’t any dataset available online so we need to create our own dataset as per the requirements.</p> <p>I’ll be working on the improvement of the semanticTextSim agent and will be introducing a new part of it. Currently, we have doc2vec implementation and I’m planning to introduce the BERT embeddings for finding semantic text similarity.</p>
<h3>Improving Discussion Threads and UI/UX of Apache Allura</h3> <h4>Goals</h4> <ul> <li>Improve Discussion Threads (ForgeDiscussion) </li> <li>Improve landing page on installation and general UI improvements and UX bug fixes (Allura)</li> <li>Implementing a Mobile Web View similar to GitHub</li> </ul> <h4>Brief Points</h4> <ul> <li>Implement async loading of comments and allow them to be paginated. </li> <li>Improve emails sent out by the platform, look into how to integrate them with email clients like done by GitHub.</li> <li>Improve viewing attachments, allow embedding some types of attachments. Preview feature.</li> <li>Extend the models in the threads to allow voting(express +1, LGTM etc.) on individual comments. Add support for emoji.</li> <li>Improve the landing page of Forge.</li> <li>Implement a separate Mobile Web View, this involves extending the API and creating new views specifically for mobile web browsers.</li> </ul>
This project aims to improve the handling of transposed diffuse irradiance and optical loss modeling in the pvlib-python package. Currently, pvlib’s transposition models provide inconsistent output, with some providing only total sky diffuse radiation (e.g. isotropic), while others allow for outputting the isotropic, circumsolar, and horizon components. Due to this, the ModelChain workflow only allows users to define a single angle of incidence (AOI) model, and then applies the resulting incident angle modifier (IAM) to total irradiance, limiting physical accuracy. The proposed GSoC project will start by standardizing the outputs of diffuse transposition models already implemented in pvlib, introducing a consistent interface to return circumsolar, isotropic, and horizon components. Building on this, the project will extend ModelChain to support component-specific IAM calculations, enabling more accurate modeling of optical losses by distinguishing between direct and diffuse contributions. These enhancements will improve both the flexibility and accuracy of pvlib simulations while maintaining full backward compatibility. The project will include comprehensive testing and documentation to ensure reliability and ease of use.
Advanced magnetic resonance imaging techniques, such as RF pulse optimization, increasingly rely on complex, high-performance physical simulations like those defined in KomaMRI.jl. Currently, integrating these simulations into optimization loops is bottlenecked by the lack of native gradient propagation. This project aims to unlock gradient-based optimization within the Koma ecosystem by enabling reverse-mode automatic differentiation (AD) as a first-class feature. By systematically integrating state-of-the-art AD tools, specifically Enzyme.jl and Reactant.jl, this project will make both the standard BlochSimple method and the highly optimized, custom Bloch GPU kernels fully differentiable. Core deliverables include establishing AD correctness baselines against FiniteDifferences.jl, designing a memory-efficient Simulation data structure to minimize device-host transfers, and resolving low-level upstream compatibility issues with CUDA.jl and Enzyme. Ultimately, this project will provide the Julia MRI community with a robust, fully differentiable simulation stack, culminating in an interactive tutorial for 1D RF pulse optimization.
Onboarding new end users into a sophisticated system like Knative Eventing presents significant challenges, especially as it involves understanding not only the operational components but also a distinct architectural style - event driven architecture (EDA). These issues are also seen in the current documentation which is often too technical and not geared towards practical guidance. This project seeks to perform a thorough investigation into the barriers that prevent smooth user onboarding and sustained engagement. By identifying these obstacles and developing clearer, more actionable onboarding materials, we aim to enhance the ease of entry and ongoing use of Knative Eventing for all users. Expected Outcome: 1. Produce a detailed report based on user research that outlines the current onboarding experience for new users of Knative Eventing. This report will highlight key barriers and challenges in the documentation and setup process, and recommend actionable improvements to make the onboarding process more user-friendly and less technically daunting. 2. Implement the proposed changes within the Knative community by developing comprehensive onboarding materials and enhancing existing documentation to better support new users.
<p>Very often even if an application has a robust backend, the user interface is often the factor that decides whether it will be taken up or not by the end user. Or in other words, apps definitely get points for being pretty. The Zulip mobile application can be regarded as a work-in-progress. I shall work the on the following areas and improve it so the application may move closer towards completion.</p> <ul> <li><p>Overhaul and rebuild several major elements of the interface to achieve a more even, symmetric and uniform look.</p> </li> <li><p>Adopt principles of Material Design for the application.</p> </li> <li><p>Fix many small but annoying issues such as broken alignment in some menus, ripple and other effects overflowing into other elements, non-standard icons, animation delays, asymmetric margins etc.</p> </li> <li><p>Improve support for different resolutions and pixel densities so nothing is out of place on a 18.5:9 or 18:9 display, or in landscape mode.</p> </li> <li><p>Add to the documentation and improve it where possible.</p> </li> </ul>