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 develop a Benchmark Polytope Import Suite for the volesti library, enabling automated conversion of standard Linear Programming instances and metabolic network models into H-Polytopes compatible with volesti. A user-friendly CLI tool will allow researchers to perform conversions easily without directly interacting with the code. Additionally, a curated benchmark collection with regeneration scripts will support reproducible testing and demonstration of the pipeline. The project will follow best software engineering practices, including, unit, integration and end to end tests, as well as comprehensive documentation and tutorials. By providing a robust and easy to use import suite pipeline, this project will expand volesti's accessibility and usability for researchers in volume approximation and sampling of convex bodies.
<p>PSLab is a new addition to FOSSASIA Science Lab. This tiny pocket lab provides an array of necessary equipments for doing science and engineering experiments.</p> <p>It can help enthusiastic and teachers with providing features like</p> <ul> <li>Oscilloscope</li> <li>Waveform Generator</li> <li>Frequency Counter</li> <li>Programmable Voltage Source</li> <li>Current Source</li> <li>Data Logger</li> </ul> <p>The control and measurement functions are written in Python programming language. Now they are being implemented as an Android application. The existing firmware and hardware functionalities also require upgrades and brush ups. I'm going to help with those! :)</p> <p>PSLab is interfaced and powered by USB port of the computer!</p>
<p>New serverless-computing platforms such as Google Cloud Functions, AWS Lambda, and OpenLambda provide RPC handling to cloud customers. The RPC handlers are inherently ephemeral; these services do not guarantee the persistence of state between invocations, so serverless-computing must be used in conjunction with a cloud database. We propose building an RPC-aware storage engine that runs alongside these serverless-computing platforms. There are several opportunities for tight integration: (1) client RPC calls introduce new, meaningful consistency boundaries; (2) RPC schedulers aware of database replicas can make better locality decisions; and (3) coordinating handler pausing with database change batches would improve performance. Our database will coordinate with handler workers via gRPC calls.</p>
Currently, Carbon Explorer's trace output is both verbose and hard to use. There are a large range of improvements that could be made here. This is especially true when considering its use as part of Compiler Explorer. Possible tasks include: Add a mode to only output the abstract machine execution trace and enable this by default. Add a mode to filter out the evaluation of the prelude and other imports and enable that by default. Include nicely rendered snippets of source code during the evaluation trace to highlight the code being evaluated at each step. Come up with a set of design improvements to the textual rendering to make it more comprehensible for people just arriving on the project and more easily scanned quickly. (Might involve fancier terminal output, colorized output, line drawing, etc.) Stretch goal: interactive tools to incrementally step as a precursor to the debugging features.
<p>The majority of the code in Homebrew is written in Ruby which is a dynamic language. This means that types are checked when the code is run. My project aims to incorporate Sorbet, a static type checker which would provide the benefits of static type checking to a developer. Adding static type checking helps developers rectify potential errors before the actual runtime. It also provides faster debugging of pre-existing bugs even by new developers, as they can easily jump to class/method definitions without having prior knowledge of the directory structure of the project. Sorbet serves as a tool to reduce brittle code, increases a developer’s confidence in their work and is a great tool for refactoring. I believe that this project has a lot of potential and the impact that it is going to have on the overall development cycle is going to be huge.</p>
This proposal outlines several key areas for improvement in the Sample Platform, which is CCExtractor's platform for managing tests, uploading samples, running regression tests, and more. The proposal highlights the need to regularly update code with stable packages for compatibility and security, address bugs and improve functionality such as status reporting to GitHub, implement effective CI/CD, enhance artifact download, and introduce a regression finder feature. The proposal also discusses the importance of Sample Platform in maintaining the stability of CCExtractor and ensuring safe changes in pull requests. To implement these goals, the proposal suggests deprecating support for Python 3.7 and supporting Python 3.10 and 3.11, replacing outdated software, upgrading to Flask 2, and fixing various technical issues with the platform.
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 DeepChem project aims to create high-quality, open-source tools to democratize the use of deep learning in drug discovery, materials science, quantum chemistry, and biology. Among its suite of various machine learning models, it has a wide variety of graphs-based neural network model implementations aimed to solve the applications such as predicting the solubility of small drug-like molecules, binding affinity for small molecules to protein targets, analyzing protein structures, and existing useful descriptors. This project seeks to bring a new tool to the DeepChem suite for solving message passing problems based on the recent advancements in the GNNs research. The project aims to implement a Multiplex Molecular Graph Neural Network (MXMNet) model, a Graph Neural Network (GNN) to Deepchem.
OpenFASOC is an open-source framework for autonomous generation of optimized integrated circuit blocks given user specifications. It is a growing project divided into multiple circuit block generators, one of which is a novel temperature sensor design. While the generated temperature sensor circuit is adequate, its resulting physical layout is not. A multi-voltage domain structure causes issues with routing between circuit components, which needs to be reworked. To do so, the OpenROAD tool will be studied to implement a better generated layout by tweaking the OpenFASOC flow. An opening to a design space exploration (DSE) optimization technique for the flow parameters is also proposed. Deliverables: an updated, working generator flow that outputs OpenFASOC's temperature sensor physical layout (GDS and DEF files) in SkyWater 130nm with no LVS, DRC or simulation errors.
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.
After WasmEdge provides an experimental API, WASI Socket, for supporting Berkeley Sockets API in Wasm. WasmEdge enabled a new way to open a new socket, listen to an existed socket, and send and receive data. Moreover, it will be nice if we can do more things in the related features such as SSL support. To achieve this feature, one possible way is to compile the OpenSSL library to Wasm and link it as a library. However, the performance may be not good, because all the computation jobs are done at the wasm level. Here is an alternative way, instead of the previous one, we can wrap the OpenSSL library to Wasm external functions. For example, binding `ssl_connect` to `(import "openssl" "ssl_connect" ... )`. Unfortunately, this is not an easy way to do it. To simply the workload, we decide to implement the WASI-crypto proposal first, and then use this proposal to make the above things happen.
<p>Graph neural networks is a powerful generalization of a whole class of neural (and not only neural) architectures on the data, organized in a graph. The graph representation is on itself a powerful tool, allowing to explicitly show dependencies between features or attributes and abstract this prior from the architecture level to the level of the data.</p> <p>Particular special cases of graph networks are already successfully used in particle physics and, therefore, implementing such tools for ROOT in general as a leading particle physics data analytics framework, and TMVA in particular is of utmost importance.</p> <p>Implementing a generalized version of graph networks as we propose in this context, as opposed to implementing every possible architecture like Deep Sets or Message Passing NNs, will ensure the wide applicability and the ease of modification and adaptation for a particular task.</p>
This project aims to integrate visual testing into the Kolibri Design System's (KDS) CI workflows to streamline the validation process for UI modifications. Currently, KDS lacks a visual testing service leading to manual effort in validating UI modifications. Leveraging tools like Puppeteer and Percy, the project proposes to automate the process of capturing and comparing screenshots of UI components before and after modifications, ensuring consistency and correctness. Key deliverables of the project are: 1. Integration of Percy into the existing Jest test suite, 2. Implementing visual testing for at least one UI component, 3. Establishing a mechanism for surfacing visual differences in pull requests. This will help enhance the efficiency and reliability of KDS development, fostering a consistent and polished user experience across Kolibri products.
This project successfully developed two AI-powered tools to enhance software quality at Eclipse Adoptium. The first, GlitchWitcher, implements the REPD (Reconstruction Error Probability Distribution) model, using an autoencoder for supervised anomaly detection to proactively predict software defects. The project's primary deliverable evolved into VitAI, an advanced, modular multi-agent AI assistant for interactive test triage. VitAI's architecture features a custom MCP (Model Context Protocol) server for providing an interface to interact with a specialized agent and a Retrieval-Augmented Generation (RAG) system. The RAG system provides deep, context-aware responses by querying a vector database of project documentation, issues, and build data. This work was supported by automated data pipelines and is showcased in a live interactive demo.
DigiKam is an advanced open-source digital photo management application that runs on Linux, Windows, and MacOS. The application provides a comprehensive set of tools for importing, managing, editing, and sharing photos and raw files. However, many Digikam users can take a lot of types of document pictures containing the text in them, which is needed to extract and saved for specific reasons. The project aims to implement a new generic DigiKam Plugin using Optical Character Recognition to process images in batch with Tesseract, an-open-source OCR engine. In this summer, I am going to handle use-case data set, create a working version for OCR of Tesseract to validate pre/post processing algorithms for general cases based on test data and improving the performance of OCR Digikam plugin
The project Scrum Helper is designed to aid individuals in generating and injecting daily scrums into popular email clients such as Gmail, Outlook, and Yahoo. This initiative focuses on automating repetitive tasks involved in daily scrum reporting by leveraging user activity data from platforms like GitHub. The goal is to streamline scrum generation, improve developer productivity, and promote efficient communication within teams. Key Features: 1.Cross-Platform Support: Generate scrums in Gmail, Outlook, Yahoo, or via a standalone popup. 2.GitHub Integration: Auto-fetch activity to pre-fill scrum content. 3.Customizable & Shareable: Preview, edit, copy, and save scrum templates. 4.Secure & Optimized: OAuth-based access, responsive UI, and error handling.
This project addresses the challenge of accurately digitizing degraded 17th-century Spanish manuscripts, which suffer from irregular layouts, archaic grammar, and low scan quality. The solution integrates a hybrid OCR pipeline: a Mask R-CNN model segments text blocks into lines, a fine-tuned TrOCR transformer recognizes printed/handwritten text, and a T5 + LLM hybrid system corrects errors while preserving historical grammar. An open-source annotation tool enables historians to validate outputs and expand datasets. Deliverables include: (1) a production-ready OCR pipeline, (2) post-correction module with fallback strategies, (3) annotation tool for dataset refinement, and (4) comprehensive documentation. This tool will enable scalable, accurate digitization of cultural heritage texts.
<p>The Moira API microservice serves as the backend for the web UI and it would be nice if the engineers who use Moira are able able to automate routine operations such as managing triggers with tools like Ansible. However, the API is undocumented currently and they have to study Moira’s source code or inspect the network requests from the web client to know the network requests they have to make and the responses to expect.</p> <p>As part of the 2020 Google Summer of Code, I wish to:</p> <ul> <li>Develop an up-to-date OpenAPI/Swagger description of the endpoints exposed by the API.</li> <li>Generate language-specific client libraries from the API description file - with special focus on a Golang client.</li> <li>Setup automated contract tests to test the OpenAPI document against the actual implementation.</li> </ul>
Liquid Galaxy RPG is a multiplayer 2D fantasy action game built for the Liquid Galaxy multi-screen display system, where a continuous tile-based world spans all LG screens simultaneously. Four players join via a Flutter mobile controller app, competing in King of the Hill (2v2 PvP castle capture) or cooperating in Dragon Raid (4-player boss fight with wave-based enemies). The game is built on Phaser 3 served via Node.js WebSocket — each LG screen opens one URL in Chromium on Ubuntu 16.04 rig. A unique AI Cheerleader powered by the Gemini API runs on each player's phone, delivering private personalized motivational messages via Flutter TTS based on live game events.
<p>The idea is to add new features as well as to improve existing features in the Catrobat iOS app (Catty). The app mainly focuses on making programming easy for children and share the created program among the Catrobat community. The features to be implemented are:</p> <ul> <li>Landscape mode: At the time of creating a new project in pocket code iOS application, the application will ask the user to select the orientation of the device using a pop message similar to that of the android application. The device orientation will be change on the basis of the user's choice.</li> <li>Google Sign-In and tagging: This will allow the user to sign-in to the Catrobat community with their google account along with their Catrobat account. I will integrate this feature using the google framework <code>GoogleSignIn</code>.</li> </ul>
The Red Hen Anonymizer is a software that uses deep learning and signal processing techniques to anonymize audio-visual data. The proposed project aims to expand the software’s capabilities by adding two new features for visual data anonymization, namely Level Wise Anonymization and Anonymization using StarGANv2. Additionally, the project proposes to add a new feature for audio data anonymization, namely Anonymization According to the Anonymized Face, while retaining the existing features. The new algorithms are based on deep learning and require GPU power for training. The objective is to create a versatile and robust software, with a user-friendly interface. The final deliverable will be a complete anonymization engine integrated into a web application, providing users with a convenient one-click anonymization options that meets their specific needs.
The sbi (Simulation-Based Inference) library currently constructs neural density estimators via opaque factory functions that accept loose keyword arguments. This design leads to delayed validation errors crashing deep inside PyTorch rather than at configuration, tangles data preprocessing (Z-scoring) with model architecture, and prevents experiment configurations from being serialized, making reproducibility difficult for researchers. This project will refactor the neural network builder infrastructure into a modular, three-tier Layered API. By transitioning to strongly-typed Python dataclasses, the new API will introduce DensityEstimatorBuilder for fail-fast validation and a fully decoupled ZScoreConfig to isolate data standardization. This object-oriented approach ensures that invalid configurations are caught immediately and allows architectures to be easily inspected and saved.
<p>PyTorch-Ignite is a great library built on top of pytorch. It provides an extremely simple engine and event system to work with, which work really well in a distributed environment. It also has a set of very handy metrics which can be used right out of the box. This is why I would like to become a contributor for the PyTorch-Ignite library. I wish to work on the metrics module because I have worked in Brain-Computer Interface, Computer Vision, Augmented Reality and am familiar with a myriad of different metrics. I am also familiar with using pytorch library and have built, trained and tested many models with it, making me a suitable candidate to work on the metrics module of PyTorch-Ignite. Contributing to PyTorch-Ignite can help me learn more about using pytorch in a distributed environment, writing test cases for your code, get used to the GitHub workflow in general.</p>
Inspektor Gadget enables users to inspect Linux containers and Kubernetes workloads, offering the powerful capability to monitor traffic for currently running applications. So far, gadgets can only passively monitor events, the ability to generate specific events would be a great addition to the existing features. For example, if users could trigger a DNS request from a specific pod or make an HTTP request to a particular endpoint, Inspektor Gadget could check if the request succeeded or not. Users would then be notified if there are errors/outages/problems in the cluster. Expected Outcome: As part of the mentorship, you will: 1. Explore the best way to implement event generation, external program vs implementing it within Inspektor Gadget. 2. Develop DNS/HTTP event generator and see how it works with gadgets. 3. Use the event generation in our integration testing.