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.
HPX's existing hierarchical communicator (PR #6834) implements four one-to-all collectives (broadcast, reduce, scatter, gather) with a configurable k-ary tree structure. This project will implement the remaining all-to-all collectives: all_reduce, all_gather, and all_to_all ,using the existing hierarchical communicator, produce rigorous three-way benchmarks (hierarchical HPX vs. flat HPX vs. tuned MPI), and prepare the implementation for integration into an upcoming HPX release.
Problem: SageMath's algebraic number fields (AA/QQbar) have performance bottlenecks in equality testing, arithmetic on high-degree numbers, and symbolic conversion—limitations that affect users in number theory and algebraic geometry. Solution: Integrate FLINT's qqbar_t (Calcium module) as an optional high-performance backend. FLINT is already a Sage dependency, and Calcium provides optimized algebraic number algorithms with rigorous numerical enclosures. Approach: >Create Cython bindings for qqbar_t in sage/libs/flint/ >Implement AlgebraicNumber_flint element and AlgebraicField_flint parent classes in sage/rings/qqbar_flint.py >Ensure coercion compatibility with existing AA/QQbar >Deliver tests, benchmarks, and documentation Deliverables: >Complete Cython bindings for core qqbar_t operations >Drop-in replacement classes for AA and QQbar with full arithmetic and coercion >Test suite and performance benchmarks >User and developer documentation The new backend will be optional initially, enabling side-by-side comparison, with the potential to become the default after validation. This will make algebraic number computations in Sage faster and more robust.
FreeCAD comes with a Robot Workbench, which is capable of 6-DOF robot simulations, trajectory planning and a vendor specific code export (KUKA). After the removal of some copyrighted model assets and years without an active maintainer, the workbench is functional but difficult to use and customise. The robots can only be defined via hand-written VRML and CSV/DH files, the bundled kinematics library has lagged behind the latest upstream release, the axis count for robots is hard coded to six and the documentation for beginners is sparse. Thus this project proposes an incremental modernization of the existing “Mod/Robot” module: 1. Standardised robot imports : Unified Robot Description Format (URDF) is one of the most common standards for describing a robot. Having an easy way to import robots directly from URDF will replace the painful CSV/DH file imports. 2. Generic joint-trajectory export : Having the possibility to export the joint & trajectory data will separate the export process from copyrighted vendor-specific pipelines. The users can post-process the exported data to their specific platform 3. Kinematics library refresh : FreeCAD currently has a local fork of KDL library that lags behind the upstream. Cleaning up this dependency will eventually prepare the path for arbitrary-DOF robots & better robot animations. 4. Documentation : This will help the existing users as well as attract a new user base towards the Robotics Workbench.
This project focuses on transforming Mogan STEM into a web-based, multi-user collaborative platform. Currently, the lack of a functional WebAssembly (WASM) version and real-time synchronization limits its use in modern collaborative research. To solve this, I will compile Mogan STEM using Emscripten, implementing a custom virtual file system to ensure stability. Furthermore, I will develop a real-time collaboration core based on Operational Transformation (OT) and WebSockets. This architecture allows multiple users to edit complex scientific documents simultaneously with "local-first" responsiveness and guaranteed global consistency. Deliverables include: 1. A stable browser-based version of Mogan STEM. 2. An OT-based synchronization server. 3. A complete end-to-end prototype supporting real-time multi-user collaborative editing.
Graphs are powerful tools for understanding relationships and structures — from social media connections to brain networks. Often, we want to study whether these structures exhibit unusual features. To do so, we compare the graph in question to a "baseline" or "generic" graph, called a null model; this gives us a point of reference to identify whether the features we see are truly unusual or simply a result of random chance. As such, the goal of this project is to expand the igraph library's ability to work with null models. Given a set of characteristics about a graph, we want to make it more flexible to 1) check whether a graph with these characteristics exist (graphicality), 2) create a graph with these characteristics (construction), and 3) derive other graphs that share the same characteristics (rewiring). With more flexible and performant tools for working with null models, igraph can better support the network science underpinning so many scientific domains.
This proposal focuses on improving the Implementer Tools in OpenMRS 3 by addressing current limitations and adding key features. The project aims to support object editing in config fields, enable UI-based translation overrides, improve extension handling, and add privilege-based display conditions. It also proposes implementing Carbon React-based dark mode, a color picker for branding, server-side configuration saving, and fixing UI inconsistencies. These changes are aimed at making the tool more complete and easier to use for OpenMRS implementers.
This project aims to enhance LLDB's disassembler by annotating machine instructions with source-level variable information, such as variable locations and lifetimes, based on debug data like DWARF. Currently, LLDB’s disassembler outputs only low-level instructions, requiring users to manually infer where source variables are located. By enriching disassembly output with variable annotations (e.g., which register or constant a variable is stored in), this project will make debugging optimized and low-level code significantly easier. The solution involves extending LLDB’s disassembly printing pipeline to query live variables at each instruction address, limited to variables that reside in CPU registers or are represented as constants, ensuring efficiency and clarity. Deliverables include: Annotated disassembly output in the LLDB command-line interface. Full test coverage against optimized and unoptimized binaries. Documentation and usage examples for developers and users. This work will be designed to be debug information format-agnostic wherever possible, making it extensible across formats like DWARF and PDB.
Rocket.Chat’s Message Composer currently displays raw Markdown syntax and emoji shortcodes while composing a message, only applying formatting after the message is sent. This impacts readability and usability, as users must interpret raw syntax instead of seeing the final formatted output. This project will introduce real-time Markdown rendering and native emoji support in the Message Composer. Users will be able to see bold, italic, and other formatted text as they type, along with correctly rendered emojis. Additionally, the project will provide a proof-of-concept for migrating from Rocket.Chat’s third-party emoji pack to native emoji support. Key Deliverables: 1. MVP implementation of real-time Markdown rendering in the Message Composer. 2. Native emoji support, replacing the existing third-party emoji pack. 3. Support for mentions with a defined style, ensuring visually distinct tags. 4. Text sanitization to maintain security and prevent unintended behavior. 5. Help tooltip for Markdown syntax, improving accessibility for new users.
Problem: KubeStellar (KS) lacks an automated system to measure and visualize data-plane performance (e.g., sync latencies) under AI workloads, making optimization and debugging challenging. Solution: 1. Instrument KS with OpenTelemetry/Prometheus to emit sync latency/error metrics. 2. Build a pipeline (TimescaleDB + Fluentd) to collect, store, and aggregate metrics. 3. Embed Grafana dashboards into KS UI for real-time monitoring. 4. Benchmark AI workloads (e.g., distributed TensorFlow) to validate scalability. Deliverables: 1. Go-based metric instrumentation in KS core. 2. Automated aggregation service (P95, error rates). 3. Prebuilt Grafana dashboards (latency, throughput). 4. Documentation + video demo. Impact: Enables data-driven optimization of KS for large-scale AI workloads.
My project aims to develop an immersive Augmented Reality (AR) Marine Ecosystem Simulation that will serve as an interactive educational tool within Catrobat's ecosystem. This simulation will allow users to explore marine environments through AR technology, visualizing complex ecological interactions such as food chains, coral reef dynamics, and the impacts of pollution in real-time. The primary challenge lies in creating a physically accurate, engaging simulation that runs efficiently on mobile devices while maintaining educational value. I propose to solve this by: - Developing a modular AR framework using Unity that integrates with ARKit and ARCore - Implementing realistic physics-based interactions between marine organisms - Creating an adaptive AI system that evolves the ecosystem based on user interactions - Designing intuitive interfaces that make complex ecological concepts accessible The project will deliver: - A fully functional AR marine ecosystem simulation compatible with Catrobat's existing applications - A library of interactive marine organisms with realistic behaviors and interactions - Real-time visualization tools for environmental factors (temperature, pH, pollution) - Educational scenarios demonstrating ecological principles - Comprehensive documentation and integration guides
Building a cli tool for kro resource management. using golang's cobra library. mentioned are the proposed tasks which are about to be completed under the project scope. Project goals: 1) Build a CLI tool to help developers and admins manage kro. 2) Create commands for common RGD operations [validate/generate/install/publish/package]. 3) Create commands to for RGD and instance viewing and dry-runs. 4) Create commands for monitoring and troubleshooting RGDs, instances and CRDs.
The Human Neocortical Neurosolver (HNN) is a computational tool that enables scientists to study brain responses at the cellular and circuit levels. However, the current version of HNN-core has a limitation in that it cannot simulate large batches of simulations. This hinders the efficient optimization of parameters, which is crucial for accurate modeling. To address this issue, I am working on improving HNN-core by adding batch simulation functionality. I am also developing a user-guide on advanced optimization techniques, specifically focusing on simulation-based inference (SBI), a deep learning-based Bayesian inference method. These enhancements will significantly contribute to the HNN's codebase, enabling researchers to extract crucial insights for developing theories about human brain response origins.
MusicBrainz database sees a lot of edits made on a daily basis. Tens of thousands of edits. That’s a large number. With each edit, there’s associated an edit note which provides additional information about the edit. Often, these edit notes, as well as some edits, contain external links, which we want to archive in the Internet Archive. This project idea aims at creating a Rust application that can archive the external URLs using Wayback Machine APIs.
Instructors face significant challenges when configuring autograding systems for their courses due to limited examples, insufficient documentation, and a lack of coverage for various features. To address these issues, I propose a comprehensive solution aimed at reducing the learning curve for instructors and enhancing the functionality of autograding systems. The project focuses on three primary areas: Firstly, I aim to improve autograding examples by creating tailored solutions for specific use cases, such as evaluating compilation speed and handling distributed/networked applications. These examples will feature detailed configurations in config.json, accompanied by comprehensive documentation. Additionally, existing examples will be revamped to meet current standards and encompass a broader range of programming languages and features. Secondly, I will enhance documentation and provide illustrative examples for new autograding features that lack proper guidance. Through thorough research and collaboration with mentors, I will develop demonstrations for features like generating random input/output and utilizing customized Docker containers. The aim is to facilitate understanding and usage of these features by instructors. Lastly, to provide instructors with a user-friendly platform for configuring autograding across various educational levels, I will establish a structured repository. This repository will house a diverse array of autograding examples organized by educational level, ranging from introductory to advanced courses. Furthermore, I will encourage crowd-sourced contributions to create a comprehensive collection of programming assignments and exercises, complete with their autograding configurations. To streamline the contribution process and ensure consistency in configurations, I will implement GitHub Workflow Actions. The repository will include detailed documentation and guidelines to facilitate contribution and usage.
The Makerchip platform has added custom visualization support for circuit simulations, allowing for improved insights into microarchitectural behavior and circuit debugging. This project seeks to extend the capabilities of the platform by implementing customized circuit visualization for various circuits, including SweRV, SERV, BaseJump STL, and fundamental circuits for educational purposes. Additionally, the project will incorporate neural networks and gamified circuit design visualization to further enhance the user experience. This feature will provide a clearer understanding of how each step of the code is functioning, leading to improved insights and faster debugging. By enabling users to visualize and analyze circuits in a more efficient and engaging manner, this project aims to improve the overall functionality and usability of the Makerchip platform.
The purpose of this project is to create a dashboard application that allows better control of their fields, to all farmers who want to take their business to a more technological environment. Thanks to the appearance of the new farming robots, we will be able to improve the control of the harvest and the state of the field.
For now spopt has implemented several basic facility location models, providing the free open source for researcher, or organizations to use. However, there are still many useful improvements can be made. This proposal suggests improving the spopt package by implementing the P-Median model with Near-Far Cost Allocation. In the article by Church (2018), it proposed a new p-median model which can distinguish between near and far facilities, use both explicit and implicit variables for capacity allocations. Based on that, the writer plans to implement the p-median model with near-far cost allocation. By this, the spopt package can provide more accurate and efficient solutions to spatial optimization problems, typically for the problems with large data points, and large demand volume. This proposal will introduce the reason why the writer chooses this project, the technical details of this project, and the plan and delivery schedules.
In this project, I aim to improve and expand the functionalities of the physics control module. This module was introduced to SymPy 2 years ago. The work done is commendable but has a good scope for improvement. There are many incomplete areas and there is a lot of potential for new implementations. I plan to learn the relevant theoretical aspects of control systems required to complete this project by referring to course textbooks and other CST packages available in the open literature. By the end of this summer SymPy will have a complete Control toolkit, so that it can match the functionalities of MATLAB and other popular software toolkits in this domain.
This proposal aims to solve the issue of using high-order functions with asynchronous functions when there is no platform support of continuations and without implementation of two variants of HOFs (synchronous and asynchronous). The plan is to add basic functionality of auto generation of CPS transformed HOFs in the dotty-cps-async compiler plugin.
This project aims to extend the support for aarch64 on rust-vmm/vmm-reference. rust-vmm enables the community to build custom VMM solutions. It currently supports booting up a dummy VM with no devices. The purpose of this project is to extend the existing functionality getting it closer to what is already available on x86_64.
Problem: Modern-day web browsers are pretty standardized and come with a certain guarantee that if a web page works in one browser, it will work in another web browser too except for a few minor cases. However, this is not true for email clients yet. The current state of the problem: The developer community is thus aligned to certain tricks and hacks to make sure the emails sent are properly rendered by these different email clients. There is no such package that solves this problem of creating responsive emails easily which can also handle cross browsers and clients compatibility issues. Proposed Solution to this problem: The end goal will be to implement a React-based component and utility methods-based lightweight library to provide a common interface for email building that users can install and use to build clean and responsive emails easily.
WebAssembly has become extremely popular among the developer community lately. It offers near native performance in a browser and is meant to not be a hand written language but to be the compilation target of source languages like C, C++, Rust etc. It provides a way to run code written in multiple languages on the web at near-native speed, with client apps running on the web that previously couldn't have done so. It, being a new language , does not enjoy wide support across platforms. The prospect of having a unified interface for web developers has long been elusive. It has the potential to provide the basis on which many apps can be built and deployed for a huge range of devices from IoT devices to fully fledged servers. But to enable developers to use it we need a WASI runtime ecosystem to support them. WasmEdge is one such project that aims to bring WebAssembly to the edge. To provide a unified interface accross multiple platforms, a interface between WasmEdge and the host operating system has to be built. This interface is specific to the platform on which the runtime is deployed and has to be built individually and specifically for each platform bearing in mind the features available. The native API provided by the OS should be used to implement many of the common operations like file manipulation, IO etc. These 'host functions' are crucial for the project to succeed and have been defined in WASI - the Web Assembly System Interface which is a modular collection of standardised APIs Currently, host specific functions have not been implemented in WasmEdge, for the windows platform. These functions are supposed to be implemented using the Win32 API and have to go rigorous testing before being deployed.
The goal of this project is to design and implement a UI for the New Document creation feature, which has long-standing discoverability and usability issues, along with old and new bugs. This is a UI front-end project, which will include creating a new composite GTK widget template. The main goal of my project is to create a UI for when there are a few templates designed by the user, which will solve the usability problem of this creation feature.
<p>Often, it's useful for users to compare different results on an image. To facilitate this, caMicrocope supports viewing the same image with different results, such as heatmaps, segmentations, and annotations, in a coordinated fashion. Since adjacent tissue slice images are usually quite similar, it can be useful to have a similar coordination between different images. This project focuses on creating a tool to allow a user to do this. The two different tissue samples may be differently situated in their images, and may require a user to change scale, position, and rotation to sync up the two images.</p>