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.
Development and Deployment of a Lossy Compression Tool 'Baler' that uses deep autoencoders to flexibly compress scientific data. Use Baler to compress data for LHC experiments like ATLAS and improve existing Baler model to be more robust and accurate while reconstructing data. Document and Benchmark Baler's performance for real-world physics experiment and explore it's capabilities on non-scientific data.
The overall goal is to modify the Dubbo SDK to work in mesh mode and streamline unnecessary processes. 1. For service invocation, add the meshEnable configuration in ConsumerConfig to enable the mesh mode and add the providerPort in ReferenceConfig to specify the provider's service port. Modify the SDK, read the providerBy and providerPort in the configuration to determine the address of sending RPC. In the mesh environment, providerBy should be the ServiceName of the Provider. In Mesh mode, Invoker should remove clusters. 2. For health checks, Istio comes with probes that align the life cycle of Dubbo and even the entire application with the life cycle of Pod. An active health check provided by Envoy removes unhealthy instances immediately and then joins the service route when the instance is healthy again. However, the readinessProbe implementation provided by Dubbo does not apply to mesh. If the registry is not configured in mesh mode, Dubbo's readinessProbe returns false, which needs to be modified here. 3. For traffic governance, you can use retry configuration, routing, load balancing and other traffic governance functions to find the methods to interact with Envoy (for example, the number of retries can be achieved by configuring the header).
Currently, the Newt editor supports Systems Biological Graphical Notation (SBGN) and Simple Interactive Format (SIF) formats while also allowing importing/exporting data in Systems Biology Markup Language (SBML) format. Conversion to SBML format from SBGN or SIF is lossy since the data models are not fully compatible. Information may be lost during conversion to SBML format. This is why supporting the SBML format in Newt is crucial. The main feature proposed to be implemented is for users to create SBML models from scratch in Newt without the need to convert them to other data formats. An additional palette will be added with the corresponding notation to the existing palette for the user to create new SBML models or edit an existing one by dragging elements from the palette.
Nominatim is OSM’s own geocoding software. When a user is searching for a specific place, Nominatim returns multiple results that are likely to be what the user is looking for. These search results are ranked based on their importance values that are being derived from looking at the popularity of the locations’ Wikipedia articles. However, not every place on Earth has its own Wikipedia article. As a result, each of the places that do not have their own Wikipedia articles does not have an assigned importance value to be used to rank them correctly among the other locations in the search result. OSM publishes aggregate map access numbers that are generated based on the users’ behavior when using the map. These access numbers are a good indicator of how popular a place is. The aim of this project is to integrate the map access numbers into Nominatim to compute an importance value for all places regardless of whether they have their own Wikipedia article or not. In order to fulfill the aim of this project, a set of deliverables needs to be defined and accomplished. These are: 1) Finding the most suitable method of importing GeoTIFF files 2) Developing the import functionality 3) Investigating and developing the importance value computation algorithm based on the map access numbers 4) Writing unit tests 5) Documenting the new changes
WebGL, being the OpenGL variant for Web, is the most popular graphics library which makes use of GPU for efficient and fast drawing of graphics. This project aims to implement some new features and enhance the current functionalities for p5.js and refactor the WebGL rendering pipeline so that multiple materials can be applied to geometry. Key areas to my proposals are - ● Correcting the inappropriate behavior of certain geometry in WebGL mode and the implementation of debugging tool for the current camera function. ● Refactoring of the WebGL rendering pipeline so that multiple materials can be applied to geometry.
<p>This project aims to add support for arrays and allocatables in LFortran. Specifically, features to be added for arrays are as follows,</p> <ul> <li>Declaring Arrays</li> <li>Operations on Arrays</li> <li>Indexing Arrays</li> <li>Passing Arrays as Functions/Subroutines Arguments</li> <li>Array Initializer Expressions</li> <li>Slicing Arrays</li> <li>Intrinsic Functions for Arrays</li> </ul> <p>For supporting allocatables, the main focus would be on generating instructions to allocate memory in heap using <code>malloc</code>. There are some miscellaneous goals as well, such as improving support for pointers and kinds and some bug fixes discovered along the way.</p>
<p>AnalySim is a data sharing platform similar to GitHub, but specialized for scientific projects. It seeks to simplify the analysis and visualization of datasets. AnalySim is designed to promote collaborations and to improve existing datasets through features like forking or cloning, features specialized to allow users to start new projects, collaborations or join existing teams or projects.</p> <p>First feature I would like to add to AnalySim is forking projects, which will help collaboration between researchers. One can fork someone else’s project and improve upon it by adding more data or improving analysis. Second feature I'm interested in is adding a new design template. Finally, I want to improve the existing documentation. If there's extra time, I would like to work on adding a component that allows for CSV file viewing.</p> <p>This project offers me a great opportunity to practice my technical skills of programming the web based technologies I learned in my classes. Specifically, I have experience in working with Angular, web development and web design. I aim at starting a career in software development where I want to put to practice the skills learned during this project.</p>
<p>Mainly the project will be developed in Android and it will make use of of the Liquid Galaxy capacity to display information over an interactive map, displays data obtained from a Firebase database.</p> <p>I will develop and Android Application: . Able to create different profile setups, users and administrators. . Able to display a location address through the Liquid Galaxy technology . Able to display on Liquid Galaxy tours, orbit over a POI so as the FlyTo function</p> <ul> <li>With a forms based sections to enter or access to the personal data </li> <li>With multi-idiom support </li> <li>Able to collect data from third parties (APIs)</li> <li>Integrated with the YouTube Android Player API </li> <li>A Firebase database (running on Google Cloud)</li> <li>Data visualization on the LG</li> </ul>
<p>The goal is to adapt or add all the algorithms that are exposed by the latest C++ standard (C++20). This includes, creating new algorithm implementations that expose a range based interface.</p>
<p>Testing software is essential. As a project gets bigger, the difficulty of testing the interactions of all its components increases. Property based testing, with libraries like QuickCheck and quickcheck-state-machine, seems to counter this problem. In this project we will use these libraries to test stateful code, with a main focus on parallel programs and programs with injected errors. The target is to benefit the whole Haskell community by providing guides, template examples and improving the api and functionality of these testing frameworks.</p>
<p>While creating a Portfile for MacPorts one has to manually write the file or depending on the upstream use tools such as pypi2port, cpan2port, etc. So as to not deal with different tools for each type of package, Universal Packaging Tool (UPT) can be used. Main aim of this project would be to bring macports support to upt and adding features to UPT such as recursive packaging and updation.</p>
<p>Skeptik[1] is a tool focused on compression of proofs, but it's also possible to generate proofs using it's infrastructure.</p> <p>There is a new algorithm developed by ANU employees, called Conflict Resolution algorithm[2], which has no implementation yet and can generate proofs in first-order logic.</p> <p>Conflict Resolution algorithm extends wellknown SAT solver DPLL[3] and CDCL[4] algorithm and tries to generalize it’s ideas for first-order logic. In CR we negate instances (substitutions) of decision literals (unlike CDCL where we negate decision literals), but main idea is the same: we decide to assign truthness to some atom and then try to propagate and achieve truthness of some other atoms. Eventually, we will reach a conflict or satisfactions and generate some conflict clauses if reached conflict.</p> <ul> <li>[1] <a href="https://github.com/Paradoxika/Skeptik" target="_blank">https://github.com/Paradoxika/Skeptik</a></li> <li>[2] <a href="http://arxiv.org/pdf/1602.04568v1.pdf" target="_blank">http://arxiv.org/pdf/1602.04568v1.pdf</a></li> <li>[3] <a href="https://en.wikipedia.org/wiki/DPLL_algorithm" target="_blank">https://en.wikipedia.org/wiki/DPLL_algorithm</a></li> <li>[4] <a href="https://en.wikipedia.org/wiki/Conflict-Driven_Clause_Learning" target="_blank">https://en.wikipedia.org/wiki/Conflict-Driven_Clause_Learning</a></li> </ul>
<p>I would like to work on developing an Integrated Development Environment (IDE) for PySoy. The aim of the IDE is to provide all the features of a text based IDE such as autocompletion, direct execution, e.t.c along with debugging tools.</p> <p>As a part of the project, I will be using iPython module. It is an extension to the Python interpreter offering additional features. I will be integrating PySoy specific UI and debugging tools to facilitate faster game development.</p> <p>April 22 - May 23 (Community Bonding Period)</p> <p>Discuss my ideas comprehensively with the CopyLeft Games community. For the pre-GSOC task, I will be writing the missing bindings and fix bugs (If any) in the necessary widget classes.</p> <p>May 23 - June 27 (Mid Term Evaluation)</p> <p>Develop PySoy specific IDE plugin set for Gedit. This includes plugins for autocompletion, direct execution and debugging of scripts from Gedit itself along with a handler created using iPython API.</p> <p>June 28 - August 23 (Final Evaluation)</p> <p>Develop Body debugging, Field debugging, and general debugging systems. Create an example PySoy script to demonstrate different features of the IDE.</p>
<p>While experienced IRC users have no problem getting used to Polari, the growing number of new users that are not familiar with IRC clients demands an improved and fast initial setup so that user retention is favored and a new room blank state, in order to add a more friendly look to the current blank state.</p> <p>A better initial experience would definitely help new users, but what about regular ones that are already used to Polari? Since this project aims towards improving the overall user experience for both new and accustomed users, contextual popups, enhanced nickname tab-completion, favorite users section contained in the user list and the clever filtering of their status messages would definitely prove to be valuable assets for the future versions of Polari.</p> <p>With the help of Florian Muellner and Bastian Ilso, whom will aid me as mentors in the process of developing these ideas, I plan on adding user-friendly features that would enhance the user onboarding capabilities of Polari, making it easier for people to use our application.</p>
<p>digiKam includes a basic tool to fix red eyes in Image Editor. there is no automatic mode (detection and correction), which makes the process of fixing red eyes in a batch of images a time consuming task. The objective of this project is to add automatic red eye removal feature to digiKam BQM and Image Editor to detect and correct red eyes automatically.</p>
<p>OSEM is an event management app tailored to Free Software Conferences. OSEM already has a feature to sell conference tickets to its attendees. At the moment the user has to buy the ticket online and pay on arrival at the conference. OSEM currently lacks the ability for a user to pay for its tickets as per their convenience. In this project, we aim to fill this gap in functionality by adding online ticket payment feature. This will improve user experience by making the ticket purchase workflow smoother.</p>
<p>TimeSync is the OSU Open Source Lab's time tracking system; a project that allows users to track their time spent on various projects and activities irrespective of the programming language and tools used by the project. The goal of this project will be to create ruby port of Pymesync ( a python module to interface with the TimeSync API ) which ultimately would serve as a Ruby Gem with the same functionality as that of pymesync. I will also create a ruby application from scratch using the Sinatra Framework that will use this ruby gem for serving the data. This ruby application application will have several features that provide visualizations for the user.</p>
<p>The main objective of this project is to reduce the memory errors faced by the Scilab code-base and ensure memory safety.</p>
<p>The random number generator(RNG) of Julia needs updating to a more reliable one. I'm going to implement a package (may be named RNG.jl) providing several RNGs, and a binding to Intel MKL(VSL.jl) for the RNG work. After comparing the performance of them the best one is supposed to replace the current RNG in Julia Base.</p>
This project focuses on solving a real gap in the current research workflow that is the disconnect between running experiments and turning those results into clean, publication-ready outputs. Right now, tools like Visdom are great for live experiment visualization, but the moment a researcher wants to use those results in a paper, everything becomes manual. Plots are exported as screenshots or loosely formatted images, experiment configurations are tracked separately (often in notes or notebooks), and comparisons across differnent runs are done by hand. This makes the process slow, error-prone, and difficult to reproduce. The proposed solution is to extend Visdom into a complete “experiment-to-publication” pipeline. Instead of stopping at visualization, the system will allow researchers to directly generate structured, reproducible, and publication-quality outputs from Visdom itself. The project introduces four tightly connected components: A publication-quality export engine that allows plots to be exported in formats like SVG, PNG, and PDF with proper resolution and formatting suitable for academic journals. An experiment metadata tracker that automatically records configurations, parameters, environment details, and results for every run, ensuring full reproducibility. A LaTeX generation system that converts plots into ready-to-use LaTeX figure blocks, eliminating the need for manual formatting in Overleaf or similar tools. A multi-experiment comparison suite that enables researchers to compare different runs with statistical summaries and generate both plots and tables for inclusion in papers. By building this system, Visdom evolves from a visualization tool into a full research workflow assistant. The end result is simple: what currently takes days of manual effort can be reduced to minutes, while also improving the reproducibility and consistency across various experiments.
The U.S. Forest Service's Aerial Detection Survey (ADS) program has produced tens of thousands of hand-drawn polygons marking forest health damage from aircraft. Due to GPS imprecision and flight geometry, these polygons have systematic spatial offsets of 50–500 meters from their true locations in NAIP satellite imagery. This project builds an automated pipeline to align ADS polygons with NAIP data, recovering historical annotations as a training dataset for forest health computer vision models. The GSoC work focuses on three objectives: (1) improve alignment accuracy through a learned refinement layer using self-supervised displacement estimation techniques from the mentor-provided references, (2) scale the pipeline to all ~48,000 Oregon ADS polygons to generate a weak training dataset, and (3) fine-tune a DeepForest model on the aligned annotations for NAIP-based forest health outbreak detection. Deliverables: an optimized alignment pipeline with quantitative evaluation, aligned polygon GeoPackage for Oregon ADS data, a computer vision model for forest health detection on NAIP imagery, and a blog post documenting the methodology for others to apply to their own datasets.
This project will add distributed linear solver support to LinearSolve.jl by expanding and hardening PETSc.jl integration. The goal is to let SciML users solve large-scale systems (Ax=b) on HPC clusters through the same high-level LinearSolve API they already use for local solvers. The work will focus on implementing and improving PETSc-based KSP wrappers, cache-aware re-solve workflows, preconditioner configuration, and distributed matrix/vector support with MPI. It will also include tests, benchmarks, and documentation so users can reliably switch between direct, iterative, and distributed methods without changing downstream solver code.
Device trees tell the Linux kernel how hardware is laid out. Currently, many of the rules for these device trees are written in plain .txt files. Because they are just text, they cannot be tested automatically, which forces maintainers to manually hunt for typos and missing properties during code review. The goal of this project is to convert a large number of these legacy text bindings into strict YAML schemas. Moving to YAML allows the build tools to automatically validate the hardware descriptions before the code is ever merged, saving everyone a lot of time. In addition to converting the bindings, the project includes tracking down and fixing the older hardware .dts files that inevitably fail when tested against these new, stricter rules, ensuring that everything builds and validates perfectly.
The istSOS backend already provides strong support for time-travel queries and versioned data through parameters like as_of and from_to. However, these capabilities are currently only accessible through manual API usage, which makes them difficult to use for most users. This project focuses on bringing these features into the web administration UI by building an intuitive and accessible interface for exploring historical data. Users will be able to select a specific timestamp or time range, view the exact past state of entities such as Things, Sensors, and Datastreams, and understand how data evolved over time without writing API queries. The approach is to design lightweight frontend components that map user input to existing backend parameters, keeping the backend unchanged while making the feature usable. In addition, a Commit History Viewer will be implemented to allow users to browse changes, view metadata like author and timestamp, and load past snapshots directly into the UI. By the end of the project, istSOS will have: - Time selection controls integrated into the UI (instant and range) - Historical views for all major entities - A commit history explorer for tracking data changes - A clean query mapping layer between UI and API - Proper testing and documentation for long-term maintainability Overall, the goal is to make time-travel functionality a first-class feature in istSOS, improving transparency, usability, and accessibility for both technical and non-technical users.