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>Svmidbg will be a debugger using virtual machine introspection (VMI) that tries to be stealthy by leveraging hypervisor technologies to create undetectable breakpoints or as Mathieu Tarral calls them, <em>Advanced SoftHyperBreakpoint</em>. These kinds of hypervisor assisted breakpoints use second level address translation (SLAT), also called extended page tables (EPT) by Intel, or nested page table (NPT) by AMD to hide memory and to trap into the hypervisor (i.e. EPT Hooks). Although, it will not try to hide the hypervisor itself.</p> <p>By running under Boxy, an extension of the Bareflank hypervisor, it will effectively turn the current running host OS into a VM, and via VMI, allow kernel debugging similar to LiveKD, but unlike LiveKD, the host OS won't know it is being debugged. A companion PC connected via UART will control the debugger.</p> <p>Svmidbg will also target the Xen hypervisor with Drakvuf and its use of altp2m for stealthy breakpoints. I have worked on this part until now and will reuse work on the GDB protocol for this GSoC. The Boxy integration with LibVMI will be the main work of this GSoC. It will run on Linux (host and target) and on Windows (host with Bareflank only and target).</p>
<p>Rivet is a software package for performing data analysis on simulated particle collision events like those in the Large Hadron Collider. This project will focus on making Rivet performant on modern CPU architectures in HEP and HPC compute facilities, particularly ensuring that the central result caching and dispatching system is thread-safe and amenable to vectorized compiler optimizations. We will be working to Improve the Rivet's computational performance, make it thread-safe, profile and optimize the expensive computational components and ensure continuity of physics behaviour via the Gitlab CI engine.</p>
<p>This project aims to provide dynamic lighting and shadows in GDevelop using PixiJS. Plugins such as Pixi-layers, Pixi-lights and Pixi-shadows would be integrated with the game engine to achieve this.</p>
<p>This project focuses on adding various new features to Popper 2.0 like the addition of various runtimes, adding more subcommands, developing a searchable actions library, working on remote workflows and files, report generation, etc. It also focuses on building an Automated Popper Compliance Verification System which would verify that a pipeline is popper compliant.</p>
<p>The current state of things in Joomla! ensures that the major management of your Joomla! installation is done via the backend Administration. Which means that things like script updates, plugin updates, installation of extensions – modules, plugins and components can only be done through the Administrative panel of Joomla!. Getting all these done with this medium can be very cumbersome for System Integrators and for developers when testing just a very small thing on the Joomla! Installation. Added to all these problems is the speed in Access to perform these operations. The Idea is to add a CLI Application to the Joomla! CMS, that can perform the updates without going to the administrative panel which:</p> <ul> <li>Provides basic commands needed to perform site wide administration</li> <li>Architecturally fits in into future releases(e.g Joomla! 4.x, 5.x, etc) of Joomla! as well as backward compatibility for previous releases.</li> <li>Is extendable with a good plugin mechanism that allows future ideas to be integrated e.g Allowing commands to be added. </li> <li>Allows not just updates to be done but also allows changing of some settings.</li> <li>Ensures Proper Error and Exception Handling.</li> </ul>
<p>This project aims to implement a library that integrates with the existing coala code and allows writing native bears for coala that can leverage the power of ANTLR and enable them to advanced linting routines based on the parse-tree of a language with a given grammar.</p>
<p>This project consists of two main parts of the automated generation of documentation for Siddhi Complex Event Processing Engine.</p> <ol> <li>a maven plugin for automated documentation generation for a single extension module or the siddhi core. The metadata annotated using the @Extension annotation are retrieved using the ClassIndex library which is already used by siddhi for indexing the annotated processor classes. Afterwards, documentation is generated using the metadata using a template engine.</li> <li>Creating an index of the Siddhi Extension Repositories.</li> <li>Adding and committing the <code>docs/</code> directory content and the <code>mkdocs.yml</code> file to Git. Pushing the changes in the <code>docs/</code> directory content and the <code>mkdocs.yml</code> file to <code>origin master</code>. Automatically deploying documentation in each new release of Siddhi.</li> </ol>
<p>The Universal Space Operations Center, USOC, is an open-source tool that allows a simple and easy creation of a working groundstation to aid space projects. The program structure is divided into three main components:</p> <ol> <li>Communication software</li> <li>Graphical user interface (GUI)</li> <li>Controller for interaction between communication software and graphical user interface</li> </ol> <p>Due to the fact that the functionality of every experiment should be checked before lift-off, a communication software for up- und downlink is required. Based on the input of the user in a configuration file, the GUI and partially also the controllers can be written automatically. In this matter, USOC generates appropriate functionalities within the controllers for individual GUI contents, which can then be adapted manually. Changes in the configuration file are detected, localized and the corresponding GUI structures and controller functionalities are regenerated. If these are manually written functionalities, they are recognized and not overwritten. USOC also brings pre-coded functions, such as communication via serial ports and/or the Iridium satellite network, as well as a three-dimensional visualization of GNSS data.</p>
<p>This <em>Collect Pronunciation Dictionaries from Wiktionary</em> project aims to expand pronunciation dictionaries in CMUSphinx for new words and multiple languages from Wikimedia Foundation projects. Current Sphinx dictionaries only support limited words and languages, which is difficult to meet the needs of applications, so expanding dictionaries in Sphinx is an urgent need. It's critical to reuse existing pronunciation dictionaries to improve system performance, support new words appeared recently and more languages. A valuable pronunciation source is Wiktionary, which is a multilingual, web-based project to create a free content dictionary of all words in all languages. Although Wiktionary contains pronunciations for many words and multiple languages in a standard format like IPA, it’s not easy to parse those pronunciations from sources in different page formats and convert phonemes in different languages to one common format like CMUBET which can be used by Sphinx. This project will solve those problems and form at least 10 pronunciation dictionaries which will be tested on several ASR benchmarks for Sphinx.</p>
<p>Observing the user during early boot should not be sufficient to defeat the protection offered by Anti Evil Maid (AEM). Using time based one-time passwords instead of simple static secret text helps avoid screen observation based attacks. Installation of the improved AEM on removable media along with usage of Linux Unified Key Setup (LUKS) key files deters keyboard observation, as an attacker would also need to seize the boot media. These enhancements are then made even stronger by adding revokable TPM assisted anti-replay protection for AEM secrets.</p>
This project adds LAPACK bindings and JavaScript implementations for singular value decomposition in stdlib, with the main focus on the dgesvd routine (singular value decomposition (SVD) for GE matrices) along with several dependency routines. My plan is to implement the missing LAPACK dependencies in stdlib, port the core routines to stdlib’s ndarray/base API style, for both row-major (C-style) and column-major (Fortran-style) arrays and verify correctness against the Fortran reference implementations. The main deliverable is a working dgesvd implementation, the stretch goal is a working dgesvdq branch. Each routine will also include tests, benchmarks, examples, and documentation so the final result is a working SVD module in stdlib via LAPACK.
The Human Neocortical Neurosolver (HNN) is an open-source neural modeling tool designed to help researchers and clinicians interpret human brain imaging data. Currently, HNN primarily focuses on simulating neural activity within single neocortical columns. This project aims to extend HNN's capabilities by developing a Python API that facilitates multi-network simulations, enabling the modeling of interactions between multiple neocortical networks. This enhancement will provide neuroscientists with a more comprehensive tool to study complex brain interactions and better understand the neural mechanisms underlying MEG/EEG data. The project will involve designing and implementing the API, developing comprehensive documentation and tutorials, ensuring compatibility with existing HNN functionalities, and conducting validation tests to verify the accuracy and reliability of multi-network simulations. By expanding HNN's capabilities, this project will support a broader range of research applications, fostering innovation and collaboration within the neuroscience community
This project focuses on improving the overall user experience and feature completeness in Zulip’s settings panel, search filters, and UI components. By addressing a curated set of issues that have been prioritized by the community and where I already have hands-on experience, I aim to deliver impactful and user-focused enhancements. Key areas include redesigning and refactoring parts of the settings interface (such as the creation of an Imported Users settings panel, phone number custom profile fields, and making self-role management possible for admins), improving search and filtering capabilities (by adding filters like resolved/unresolved in Inbox and stream filters in Recent Topics), and making Zulip more customizable (e.g., default link preview visibility, hiding spammer emails from non-admins, and flexible name change permissions). Additionally, the project involves UI/UX improvements like migrating all buttons to the modern action-button framework and extending the messages_overlay system for advanced message movement interactions.
The ability to convert BRL-CAD database files to other formats is an important feature, especially being able to convert the BRL-CAD geometry into a format that a well-known finite-element solver like LS-DAYNA can read, this will allow the users to run a physical/ structural analysis using a geometry on which they invested a non-trivial amount of time creating in BRL-CAD. Considering that BRL-CAD and LS-DYNA support NURBS, the implementation of geometrically exact conversion between the two formats could constitute an attractive feature. The project proposal also involves some viable improvements to the existing .k to .g converter.
The main goals of this project are to improve the current set of Django benchmarks in djangobench by integrating them with Airspeed velocity and running them regularly and load test different ASGI and WSGI servers using locust to compare their performances
The architecture of the GHC compiler in its current state is anti-modular. Designed with GHC-the-program as the sole consumer in mind, it is very difficult for newer tooling to reuse its components. These problems extend to the inclusion of new backends such that implementations for various target platforms forked GHC frequently. The first step to improving the current design is the isolation of the different components and separation the codebase in layers for different purposes, described in the classic book "Domain Driven Design". This is already partly done, and in this project I join the existing effort by working on the next remaining subsystem: GHC's Core pipeline. In order to achieve my goal, I will proceed by using an incremental bottom-up approach: Starting at the bottom of the module hierarchy, I will push references to upper layers module-by-module up in the callstack until they are completely removed from each component. For the entry points of each in-scope component, I will then provide component-specific configuration types and corresponding initialization functions. The in-scope components are specific configurable tasks of the optimizer, and the optimizer as a whole. With this work completed, there will be significantly less references to the ubiquitous global states used throughout the whole compiler, namely the DynFlags and the HscEnv type, and significantly fewer imports of modules from upper layers, e.g. the driver.
Scala Native is an ahead-of-time and prevalent compiler for Scala. The traditional compilation is to compile Scala into Java Virtual Machine(JVM) bytecodes, which are executed by JVM. Scala Native compiles Scala into LLVM intermediate representation(LLVM IR) rather than JVM bytecodes. This property decreases the overhead of JVM and improves compilation performance. However, one of the most criticized aspects of Scala Native is its slow compilation efficiency and long build time, especially for large projects. Therefore, the optimization of Scala Native is urgently needed. The aim of this project is to build benchmarks to evaluate the performance of the Scala Native linker, and explore feasible solutions to accelerate the building task of Scala Native. Three aspects are going to be exploited: speeding up the optimizer, introducing incremental compilation, and changing the compilation and linking procedure. As a result, we expect to create benchmarks for evaluating the performance of Native Scala, and to reduce the build time by at least 20%.
<p>JMAP is an email application protocol to modernise IMAP, on top of HTTP using a JSON format. JMAP is designed to make efficient use of limited network resources and to be horizontally scalable to a very large number of users. Apache James is one of the first implementations of this new standard.</p> <p>Mail user agents generally allow displaying emails grouped by conversations (replies, forward, etc...). As a part of JMAP RFC-8621 implementation (<a href="https://tools.ietf.org/html/rfc8621#page-20" target="_blank">https://tools.ietf.org/html/rfc8621#page-20</a>), there are dedicated concepts: threads. JMAP Threads is already implemented In Apache James in a rather naive way: each email is a thread of its own. This naive implementation is specification compliant but defeats the overall purposes of threads: emails which related to a topic should belong to a thread.</p> <p>James’s data models, storage APIs, and some JMAP methods at HTTP level need to be changed to make sure the purpose of the thread is reached.</p>
<p>After the introduction of SPDX Specifications v2.2 JSON, YAML, and a development version of XML had been added as supported file formats. However , the tools-golang packages currently does not have the support to parse the SPDX files nor has the support to save a SPDX document in JSON format .</p> <p>The main objective of this project is to add support in the tools-golang package so that it can parse as well as save <a href="https://spdx.org/" target="_blank">SPDX® v2.2</a> files in JSON format .</p> <p>To add JSON support to the <a href="https://github.com/spdx/tools-golang" target="_blank">tools-golang</a> package the project will make use of the official go <a href="https://golang.org/pkg/encoding/json/" target="_blank">JSON package</a> . The SPDX specification has a <a href="https://github.com/spdx/spdx-spec/blob/master/schemas/spdx-schema.json" target="_blank">JSON schema</a> defined for the specification and has also provided a sample spdx document in <a href="https://github.com/spdx/spdx-spec/blob/master/examples/SPDXJSONExample-v2.2.spdx.json" target="_blank">JSON example</a> format . The Project mainly comprises the JSON loader and the JSON saver . The former converts JSON to SPDX Document struct while the later generates JSON from SPDX Document struct .</p>
<p>Enhance interoperability in the current Jenkins architecture by designing a plugin for Jenkins which emits and consumes CloudEvents. CloudEvents is an industry-adopted standard specification for describing event and event data (also referred to as Payload). This project enables Jenkins to produce CloudEvents (as a source) for common Jenkins events like a project build success/failure, which other tools (example Azure Event Grid) can consume. This project also enables Jenkins to be configured as a sink where external tools (example Amazon Kinesis) can send CloudEvents, and Jenkins can consume those events to perform a Jenkins action. Implementing this plugin in a workflow will give Jenkins users the ability to use and extend an event-driven Jenkins workflow to systems which use CloudEvents for defining their events.</p>
<p>A complete predictive text input solution for xrdesktop. It is an aggregation of three input modes: Dasher, Swype and a normal virtual keyboard. Combined, they form a VR input system that is highly effective for experienced users, but also usable for first-time users.</p>
<p><a href="https://github.com/nteract/testbook" target="_blank">testbook</a> is a unit testing framework extension for testing code in Jupyter Notebooks.</p> <p>Previous attempts at unit testing notebooks involved writing the tests in the notebook itself. However, testbook will allow for unit tests to be run against notebooks in separate test files, hence treating .ipynb files as .py files.</p> <p>testbook helps you set up conventional unit tests for your Jupyter Notebooks.</p>
<p>In recent years, deep learning has made remarkable progress in the area of NLP and CV with big data. In the area of chemistry, Graph Convolutional Networks, in which compounds and crystals are regarded as graphs, have attracted much attention.Deep learning frameworks for molecules such as DeepChem, Chainer Chemistry, and Deep Graph Library have emerged to more easily exploit these models of deep learning. On the other hand, these frameworks did not support inorganic crystal and the model support was biased towards Graph Convolutional Networks.JAX Chem is a JAX-based deep learning library for complex and diverse chemical modeling. JAX Chem’s motivation is to support not only models of Graph Convolutional Networks, but also Attention-based models like Transformer, and even models for wave functions involving complex physical equations like SchNetOrb or FermiNet. JAX is suitable for such complex modeling because JAX’s API allows you to write models declaratively. In the period of GSoC, I will implement the standard GNN model, the dataset utilities and the GCN model for MaterialInformatics, and the Attention-based model, as the beginning of JAX Chem.</p>
<h3>The Problem</h3> <p>All IDE/Quality Systems plugins, build tools need to use Checkstyle module metadata for their functioning. But as of now they have to maintain their own metadata which becomes time consuming and the onboarding process of a new third party application becomes cumbersome.</p> <h3>The Solution</h3> <p>If we could build and maintain universal internal metadata for all modules which IDE/Quality Systems plugins and build tools could use, it would be very useful and maintain uniform configurations across all partner applications. It would solve 3 major problems viz; Ease of Eclipse and Sonar Plugin Development, Third Party Application Integration and Automated Site Generation</p>