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>Vert.x is a toolkit for building reactive applications on JVM. It also has a lot of extensions for working with different services, for example with RabbitMQ and MySQL. For now, there are no officially supported client for interaction with Apache Cassandra.</p> <p>The main goal of the project is to create a C* client; it should be:</p> <ul> <li>implemented as a wrapper around DataStax Java Driver</li> <li>reactive and non-blocking</li> <li>polyglottic: scala, javascript, kotlin, ruby, groovy should be supported.</li> <li>full featured </li> <li>well documented</li> <li>support streaming of query results</li> </ul>
<p>This project aims to add enhancements to Scrapy's Feed Exporter components. These enhancements consists of item filters, feed post-processing and batch delivery triggers. Currently there are no convenient ways to filter items before they can be exported. Item filter feature will provide such ways and interface. A Feed post-processing enhancement will enable plugins such as compression, minifying, beautifier, etc. which can then be added to the Feed exporting workflow. Batch creation was a recently introduced feature but was limited to only item count constraints. Batch Deliver triggers will be able to make the constraints flexible and give more control to user to create batches.</p>
<p>JPF is the most popular model checking tool for Java applications. It is extensible and there are lots of extensions for various purposes. Jpfnhandler is one of such extensions. Its goal is delegating the execution of SUT methods from JPF to JVM level. One goal of this project is to improve jpf-nhandler performance using the cache layer. The latter prevents invoking methods more than once and problems caused by this. It also considerably increases the jpfnhnandler efficiency as each method is executed only once. If jpfnhandler encounters delegated method that has been executed, it just reflects result of its invocation. Another goal is to extend the converter component and including convertor classes for missing incompatible model classes.</p>
<p>istSOS has gone through a lot of improvements since 2009. This has somehow affected the simplified interaction with measurements and SOS service settings. The aim of my project primarily is to create OAT extension in RESTFull Web api and OAT extension having data analysis and statistical tools for istSOS which will be used to automate the creation of statisticat documents using OAT library and harvesting the data from an istSOS server and then publishing the result on Open Data Portals(CKAN).</p> <p>The data analysis and statistical tools suite will cover all the features of OAT.Methods. Further I will create data analysis and statistical tools suite suite for istSOS.</p>
This proposal aims to improve the scalability and maintainability of Fossbot robot software project by splitting the front-end and the back-end into separate services, with the long-term goal of transforming the application into a microservices-based architecture. The proposal includes rewriting the front-end in React, optimizing the back-end using Flask and Celery, implementing websockets for real-time communication, incorporating Monaco as an online code editor, and dockerizing the platform for consistent and reliable deployment. The proposal includes a commitment to continuous bug fixing and code improvement throughout the project's lifespan. The proposed deliverables include a modular and scalable platform with improved user experience and functionality.
This project aims to provide first-class DuckDB support for Martin TileServer. DuckDB, with its spatial extension and native ST_AsMVT and and ST_AsMVTGeo functions, enables efficient vector tile serving directly from analytical file-based datasets such as GeoParquet. With PostGIS, this is not possible since it’s a transactional database and not suitable for reading analytical columnar datasets. Martin currently has support for PostGIS tables and views as well as file formats such as MBTiles and PMTiles to build and server vector tiles. This project will extend Martin’s architecture to DuckDB and provide support for persistent DuckDB databases with spatial tables as well as local and remote GeoParquet files.
The Software Package Data Exchange (SPDX) is an open source standard for communicating software bills of material information (including components, licenses, copyrights and security references). To support SPDX, an online tool has been developed which provides an easy all-in-one website to upload and parse SPDX documents for validation, comparison and conversion and search SPDX license list. This project will provide enhancements and support for the online tools including: - More automated and high-quality deployment for software updates - Removing some of the dependencies on a Python Java Bridge by moving features like license matching over to a native Python implementation - Improving performance and quality of the online tools implementation
The aim of this project is to implement an http4s Ember WebSocket client, a pure functional WebSocket client in Scala and integrate it with other libraries in the Typelevel ecosystem. WebSocket is a computer communication protocol that enables two-way communication between a client and a server, which is widely used in numerous applications including messaging and real-time notifications, as well as GraphQL subscriptions and executing commands in a Kubernetes Pod. An Ember implementation of the WebSocket client would benefit from the ability to cross-compile to multiple platforms (JVM, ScalaJS and Native). It would also potentially achieve high performance due to Ember being built on fs2 and thus can take advantage of highly optimized fs2 runtimes.
<p>Xi-Mac, Xi Editor's official macOS frontend is still very barebones and thus making Xi Editor on Mac not yet fit to act as a developer's main editor. This project aims to implement new front end elements to accommodate upcoming features to Xi such as a language server plugin or improving the find and replace functions. Intended elements to implement for this project include a status bar, an autocomplete menu, a view to show definitions, a quick look navigation view, split views and various other improvements to the general feel and aesthetic of the front end to make Xi feel like a native macOS product.</p>
This project aims to bring the power of Retrieval-Augmented Generation (RAG) into the Scala ecosystem by building a robust Scala interface to interact with RAG pipelines. I will design a Scala-compatible wrapper to connect with Python-based components like FAISS and Hugging Face Transformers via gRPC or HTTP APIs. The project will also include developing idiomatic Scala modules for preprocessing, querying, and evaluating textual data, making it easier for Scala developers to integrate RAG into NLP or search applications. By providing seamless interoperability and modular architecture, this will empower the Scala community to build intelligent, language-aware systems more efficiently.
This project aims to add multiple features and optimisations to Beacon App’s backend, which is built with Apollo-GraphQL, Node.js and Express.js, and MongoDB. The app provides its user to share their location in real time and hence eases traveling in groups. Building upon the current app, users should be able to create groups, have multiple beacons within a group, preschedule beacons, deactivate beacons, share routes, and have a seamless app experience. Moreover the backend should be optimized enough to handle location sharing of multiple beacons in real time. Also writing a script that automates the deployment of backend to cloud, if a user wants to have their own server and database.
<p>Hackage have a dedicated Builder application which builds the package, documentation and report same to the hackage server. While this information provided is limited, Hackage and builder are in a perfect position to extend it and provide additional details like Code Coverage, Test Report.</p> <p>The main objective of this project is to make these pieces of information available about a package and provide this information through badges. These Badges will be generated dynamically with the current stats.</p> <p>This project also aims to fix various issues of the Builder and add a new feature to hackage which will let maintainers trigger a rebuild in case they feel build failed due to a problem from our side.</p>
Non-rigid Iterative Closest Point (N-ICP) is a classic method used for the registration of non-rigidly deforming shapes. Non-rigid registration seeks to find a series of transformations that aligns one surface to another. This process is a necessary step prior to performing tasks such as shape analysis, dynamic surface reconstruction, and object retrieval. As well as its simplicity, a key benefit of the N-ICP algorithm is its extensibility, allowing it to be adapted/enhanced for specific applications. Currently, there is no implementation of N-ICP within CGAL. This project seeks to develop a novel component for the CGAL library that follows the common design practices used in Open Source projects.
The goal of this project is to provide comprehensive documentation of the LALRPOP Parser, Intermediate Code Representation (ICR), and Code Optimization techniques utilized in Solang. Solang is a compiler for the Solidity Programming language, targeting the Ethereum Virtual Machine (EVM) and WebAssembly (Wasm) platforms. The documentation will encompass a detailed exploration of the parser's functionality, the structure of the intermediate representation, and various code optimization strategies employed within Solang. Additionally, we aim to propose improvements and enhancements to these components based on the latest research and advancements in compiler construction. Specifically, we will focus on suggesting advancements in error handling techniques, enhancing the ICR, and introducing more effective code optimization techniques.
The Performance Farm project aims to emphasize Postgresql performance as it evolves by conducting benchmarks and posting the results on a webpage. The project has three sections: A client script responsible for getting the most recent Postgres version, compiling and installing it, and then executing PgBench to collect results in JSON format. An API that accepts results, parses them, and saves them in a database while providing endpoints from which they may be retrieved. A website that parses and collects API responses and shows them as tables, graphs, and textual information. The proposed project aims to enhance the project by adding features such as generating and managing EXPLAIN query plans, adding custom queries to the benchmark suite, and integrating profiling tools into the performance farm.
<p>My interest lies in software engineering (especially debugging) and machine learning applications. I am very interested in the project <strong>Help migrate a TensorFlow library to TensorFlow 2.x</strong>. According to my understanding, the main change from TensorFlow 1.x to TensorFlow 2.x is migrating from the static graph as default to the dynamic graph as default. Since using the static graph leads to lots of indirection between the code we write and the code we run, it is actually difficult to debug. However, using a dynamic graph, the code we wrote is the code we run, this helps us with debugging, profiling, etc. Thus I am very excited about contributing the migration to TensorFlow 2.x.</p>
<p>The current state of Question Tool client side app is in functional state, but there are both, a large number of issue remaining, and an equally large number of required features to be implemented. A user can post an instance and others can only interact by either reacting on the instance (Like the instance), or by posting an answer to that instance. But, Question Tool currently has very less user interaction because of no notifications or emails about what is happening with any instance idea or with their replies. Question tool’s user experience is also not upto the marks as per now, which can also be the possible reason for some users less collaboration. The project also lacks some features that will be a lot helpful to the users.</p>
OpenCV is used extensively in computer vision, tackling almost all major computer vision problems. Many Modern CV applications work with video frames. However, these applications can be improved by using an ensemble of video frames with the accompanying audio signal, increasing the efficiency of the signal used for prediction. OpenCV is actively working on the support for audio processing, thereby making the proposed application possible out of the box in OpenCV. After the incorporation of the speech recognition sample in OpenCV, The goal of this project is to add real-time speech recognition samples using audio and visual data streams by using an ensemble of lip-reading techniques and speech recognition techniques.
This project aims to develop a pipeline for producing calorimeter shower datasets in point-cloud form for a given detector and various types of particles. Its central goal is not only to compress detailed Geant4 shower information into a compact point-cloud representation, but to do so while preserving the physics content needed for the downstream. The work will proceed in two major stages. First, electromagnetic (EM) showers will be used to establish the pipeline, optimize point-cloud construction, and define a robust validation protocol. Second, the same framework will be extended to hadronic showers, which are more challenging due to larger fluctuations, invisible energy, delayed components, and a stronger dependence on material and interaction modeling.
I'm building a VS Code extension that brings the power of CScout’s whole-program C analysis directly into the editor. My goal is simple, let developers understand large C codebases more effectively without ever leaving VS Code. Using this extension, one will be able to browse identifiers, find all references, explore call graphs, check metrics, and even preview refactorings in the IDE itself. We will have to extend CScout by adding a clean REST/JSON API on top of the SWILL web server. This API will be the bridge to let external tools (like my VS Code extension) query the data from CScout in a structured way.
<p>The purpose of this proposal is to create a toolbox for automatic improvement of lexical component of a language pair. This toolbox might become a great way of improving language pairs by filling gaps in dictionaries and reducing the amount of human work at the same time. Even the released Apertium pairs are not perfect and sometimes do mistakes that can be easily fixed.</p> <p>The idea is to mine existing machine translation postediting data in Mediawiki Content Translation, extract a set of potential postediting operators and then study and turn these operators into information that can be inserted in Apertium language pair (in form of monodix/bidix entries, lexical selection rules, transfer rules and so on).</p>
<p>Many components of Git are still in the form of shell and Perl scripts. This has certain advantages of being extensible but causes problems in production code on multiple platforms like Windows. I propose to rewrite a couple of shell and perl scripts into portable and performant C code, making them built-ins. The major advantage of doing this is improvement in efficiency and performance.</p> <p>Much more scripts like git-am, git-pull, git-branch have already been rewritten in C. Much more scripts like git-rebase, git-stash, git-add --interactive are still present in shell and perl scripts. I propose to work in git-rebase and it's sub-commands.</p>
<p>The Main Objective of this project is to create a Learning to Rank system which will eventually be integrated in Xapian. This project can be broken down into the following components.</p> <ol> <li>Optimizing the existing code.</li> <li>Integrating the remaining rankers (ListMLE and AdaRank) and scorers (ERR scorer) from vhasu's 2014 work.</li> <li>An automated test suite for the existing Letor code, covering both the higher-level API and the lower-level pieces.</li> <li>Revising existing Documentation and writing practical code examples.</li> <li>Testing for performance and scale with INEX2009 or similar data-set by using Letor.</li> </ol>
Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. The tool has a powerful plugin based transformer architecture where developers can write their own custom transformer plugins to fulfil their re-platforming needs. However, concepts like path mappings etc could be simplified for better adoption. Example - writing a Move2Kube custom transformer needs developers to understand various concepts such as path mappings etc, can we reduce this learning overhead by simplifying the Move2Kube architecture? Expected Outcome: - Come up with a simplified alternative design for plugin architecture for M2K - Migrate existing components to support the new design with backward compatibility (good to have).