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 add WebAssembly support to the Wild linker. Wild linker is a high-performance Linux linker written in Rust, and supporting the WebAssembly format would expand its applicability to even more Rust development scenarios. While LLVM's wasm-ld (lld) is currently the primary linker used for WebAssembly, Wild achieves link speeds that are often several times faster than lld for ELF linking across many scenarios, including mold, which was previously considered the fastest Linux linker. Since the fundamental linking process remains largely the same when adding WebAssembly support, much of the performance-critical implementation could be reused. Achieving similar performance gains for WebAssembly would therefore significantly reduce build times for Rust projects.
Pwndbg has supported LLDB internally since 2024, and in general availability as of the 2025.01.20 release. That support is, however, still in its infancy. Currently, all the test code in Pwndbg is still strongly tied to GDB, meaning that, aside from manual checks, there is nothing keeping changes to the codebase from silently breaking the LLDB subsystem. And, while there is support for attaching to and debugging programs running on platforms other than Linux, there are not as many features catering to the specifics of those platforms as there are for traditional Linux distributions. In particular, the process by which mobile debugging is done is still poorly documented, intricate, and not thoroughly tested. These shortcomings hold back LLDB Pwndbg from being as useful to its users as it can be.
<p>Daru is a Data Analysis Library in Ruby - whose user base would definitely increase by making it friendly enough to integrate with modern Ruby web frameworks such as Rails, Sinatra, etc.</p>
<p>During the summer, I am going to implement Kim Filter, which is broadly used for regime switching state-space models evaluation, on top of existing Kalman Filter. I will also create a bunch of well-tested, ready-to-use models with regime switching, including MS-AR, MS-DFM and MS-TVP.</p>
<p>Currently, in the Splash there is no an easy way to click a link, fill and submit a form, extract data from a webpage using Splash Scripts. I will develop a helper library with some helper classes like Element which will represent DOM Element. This class will allow to interact with DOM elements using Lua without any need of using splash#evaljs function.</p>
<p>Strace is an essential tool which has been ported to multiple architectures. To confidently ship release, we need to ensure each new commit has been tested on all supported architectures. This project intends to provide such functionality using existing tools like Docker, Travis CI, Open Build Service, etc. Multiple available options are compared in attempt of finding one which achieves high platform coverage, minimizes test time and ensures realistic replication of testing environment. The anticipated result of this project will be a working implementation of best solution as discussed.</p>
<p>Currently CVE Binary Tool’s binary scanning is slow and a software manifest of known packages can be used for quick scanning for CVEs as an early warning system. Here a database is built primarily of top packages from PyPI and the core packages of popular Linux distros like Ubuntu, Fedora, CentOS etc. and a parser that reads the packages from the list and maps them with the database. The checkers for these packages are created alongside.</p> <p>Also to improve user experience the creation of a backported fix checking utility can be made. It checks the packages with CVE in the scan and a database with the data including backported fix and provides an output if the CVE is fixed.</p>
<p>This project aims to design and implement support for encrypted mailing lists into GNU Mailman using PGP/MIME and GNUPG.</p>
The project aims to adapt the LuaSQL drivers, which provide an interface between Lua and various database management systems (DBMS), to work seamlessly with the latest version of Lua, 5.4. LuaSQL offers a common API for interacting with different DBMS, including ODBC, ADO, Oracle, MySQL, SQLite, Firebird, and PostgreSQL. However, the last version of LuaSQL was tested only against Lua 5.3, and it's essential to ensure compatibility with Lua 5.4 and potentially leverage new features introduced in this version. The primary focus will be on revising the Lua C API part of the code while ensuring minimal disruption to the existing functionality. Project Objectives - Compatibility Update: Ensure LuaSQL drivers are compatible with Lua 5.4. Code Revision: Review and revise existing Lua C API code for each driver to incorporate any necessary changes considering the new features and changes introduced in Lua 5.4. Potential Enhancements: Taking Advantage of any new features that could enhance performance, readability, or maintainability of the codebase. Documentation Update: Update documentation to reflect changes made to adapt Lua 5.4 and provide clear guidance for users. Testing: Conduct comprehensive testing to verify functionality across different DBMS. Distribution: Package the updated LuaSQL drivers for distribution to users.
<p>This requires completion and packaging of the udiff library. Potential goals include:</p> <ul> <li>Publishing an initial version to PyPI. </li> <li>Adding matrix/tensor calculus support.</li> <li>Adding tests.</li> <li>Adding documentation on use, which will be fairly minimal. </li> <li>Publishing a final version to PyPI.</li> </ul> <p>More Detail: <a href="https://uarray.org/en/latest/gsoc/2020/ideas.html#udiff-completion-and-packaging" target="_blank">udiff: Completion and Packaging</a></p>
This project will primarily change the command system for TechDraw from a pre-selection to a post-selection. So that the user can click on a command and then the feature they want to annotate. Additionally visual guidance will be added for these commands so it is natural the new post-selection. The tools that cannot be changed to post-selection will instead be grayed-out if the user has not picked a correct feature. Also the toolbars will be changed.
The objective of this proposal is to enhance the user experience of Mailman 3 by introducing two new features - systemwide user defaults and an improved UI for subscription management. These features will enable site admins to manage mailing lists more effectively and improve the subscription management UI for users.
<p>DFFML provides APIs for dataset generation and storage, and model definition using any machine learning framework, from high level down to low level use is supported. As the goal of DFFML is to build a community driven library of plugins for dataset generation and model definition, so that developers and researchers easily plug and play various pieces of data with various model implementations or generate datasets using the implemented features to increase the accuracy of output. For this, DFFML needs to implement large number of machine learning models as well as various features. I have planned to add the below listed Models/Algorithms to DFFML.</p> <ol> <li>Model 1: Ordinary Least Square Regression (OLSR)</li> <li>Model 2: Logistic Regression</li> <li>Model 3: k-Nearest Neighbour (kNN)</li> <li>Model 4: Naive Bayes</li> </ol>
<p>PyZombies proposed a web application to present all the content of the course, theory, and practical exercises, following the syllabus of Python para Zumbies. This web application intends to be an interactive book, in which the student can be able to run the exercise and get feedback about it.</p>
<p>Currently, the creation and management of Lua States in Lunatik bindings are made by the binding itself, which can difficult the interoperability of such systems, furthermore, leaving this task to the developer can increase the complexity of the binding. This project has the objective to move the states control to Lunatik, providing an API for these tasks in order to aid the binding development.</p>
This project aims to improve the accuracy, completeness, and accessibility of Indian holidays in the Open World Holidays Framework (OWHF). It focuses on verifying and updating national and subdivision-level holidays using official government sources, ensuring consistency across all 28 states and 8 union territories. In addition, the project will expand localization support by providing holiday names in widely used Indian languages, making the framework more accessible to a broader user base. To enhance long-term consistency and maintainability of calendar-based holidays, the project will also introduce generator scripts for solar and lunisolar holidays. These scripts will be used to generate and validate holiday dates across extended year ranges, while keeping the runtime implementation lightweight and dependency-free. The final outcome will be a more accurate, fully localized, and scalable holiday dataset for India, aligned with real-world usage and the design principles of the holidays framework.
In this proposal, I outline three projects. The following is a brief outline of each project problem, solution, and set of deliverables: Project 1) Improving Test Coverage Problem: Vorta has a current test code coverage of 72%, and we would like to get this in the 80% - 85% range. Additionally, current testing files need more a consistent file structure and organization. Solution: Work with organization mentors to prioritize test code coverage. Create unit and integration tests to reach our target code coverage. Reorganize and restructure testing file. Deliverables: At least 80% code coverage, with a stretch goal of 85%. Test files separated into unit tests vs integration tests. Consistency in file naming and structure across all test files. Project 2) Implement Profile Sidebar Problem: The current profile selector and setting tab implementation mixes global setting with profile specific settings. Solution: Move the profile selector and settings button to a collapsible sidebar. The settings button opens a new interface with options relating to global settings and profile management, while the individual profile buttons open to profile specific settings. Deliverables: A new sidebar with profile selector and setting button, as well as a new setting interface. Unit and integration testing accompanying all new features. Project 3: Test on Live Borg Binary Problem: Currently we test on static mock files of Borg JSON output. This task would improve testing to run on actual Borg versions/binaries. Solution: Test multiple versions of Borg using Tox to simplify testing. Implement these changes in setup.cfg Deliverables: CICD running tests on live Borg binaries with > 99% success rate. Include the option to run existing integration tests locally. Include thorough documentation of this process.
<p>NASA's SPICE toolkit is a collection of subroutines and functions designed to interpret and perform numerical computations on archived data returned from NASA's Space Science Missions. The commissioning of this project began in 1982 and saw the release of SPICELIB, the initial FORTRAN implementation of the SPICE Toolkit. NASA has since released ports of the SPICE toolkit to other interfaces such as C and MATLAB but the ease of use of these libraries is far from attractive.</p> <p>This project entails the design and implementation of a Ruby wrapper for the C version of the SPICE toolkit with a focus on clean extension code and an easy to use API.</p>
d-SEAMS currently uses an embedded Lua interpreter to provide user interactivity in tandem with YAML inputs for selecting workflows. The project seeks to replace this interface with a Python interface. This is expected to take place in two stages: - Replacing the Lua Interpreter with Python - Binding to C++ classes and functions directly With both of these milestones completed, feature parity will be kept with the existing code while also providing much more flexibility due to the Python library formed in the second deliverable.
<p>The Functional Mockup Interface (FMI) is a tool independent standard for the exchange of dynamic models and for co-simulation. The main objective of this project is to create an interface for model exchange and perform co-simulation.</p>
<p>The main goal of the project is, which the title says, to port Terra to Android devices. Once I already have Terra ported to android, my intention is to build an interface between Terra and the android API, that way I am sure Terra will support a lot of features common smartphones have as well as be able to use this features in different devices that have Android on it. This way, by the end of the project, we will not only have ported Terra to android but also develop an interface in which developers can easily access hardware sensors and functionalities to build their own applications.</p>
<h5>The project consists of developing an interface, in Lua, for the set of Cloud IoT Core APIs, through two REST resources:</h5> <ul> <li>cloudiot methods, to facilitate device manager tasks</li> <li>cloudiotdevice methods, to facilitate device communication over the HTTP bridge </li> </ul> <h5>The Proof of Concept</h5> <ul> <li>Another task is to provide a Proof of Concept by using a real world device such as NodeMCU/Raspberry Pi interfaced with temperature sensor to send the temperature data over to the Google Cloud IoT Core. </li> <li>Doing the reverse, sending the data to the device using the Google Cloud IoT Core. We expect this data to be a Code Snippet, which would run dynamically on the device every time it is interrupted by the new code received.</li> </ul> <h5>Development of a software interface with REST support in Lua</h5> <ul> <li>With a minimal GUI this application will make the life of a person using Lua REST APIs easier by providing a simple interface to send and receive data from an endpoint.</li> <li>Testing would be done using the Proof of Concept developed above.</li> </ul>