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.
PreliZ is a Python package aimed at helping practitioners choose prior distributions by offering a set of tools for various facets of prior elicitation. The main objective of this project is to expand these features and make them more robust, transforming PreliZ into a tool that easily integrates with other libraries such as PyMC, Bambi, and PyStan, while remaining agnostic to Probability Programming Languages (PPLs). The key outcomes of this project include generalizing Bambi's parsers, integrating PyMC for interoperability, establishing a common infrastructure for future PPLs, extending the `predictive_explorer` function to handle multiple inputs and outputs from various PPLs for comprehensive prior predictive distribution plotting, enhancing the `ppa` function to support models from PreliZ, PyMC, or Bambi for interactive prior updates, and improving the handling of PyMC models within PreliZ's `ppe` function while extending support to PreliZ and Bambi models.
The project focuses on the enhancement and refinement of a feature-rich and secure Mobile Wallet application tailored for Government to Person (G2P) payments, demonstrating a potent tool for fintechs and financial institutions. Originating as a Google Summer of Code initiative from 2017-2023, the project delivered the initial mobile wallet framework, evolving into a sophisticated reference application with two primary apps: PixieCollect and MifosPay, later consolidating focus on MifosPay. The developmental trajectory of the project saw significant milestones: integration with Mojaloop transaction flows, user experience enhancements, support for Kotlin, and implementation of standing instructions and merchant transactions. Further advancements include integration with Fineract CN, multi-theme support, migration to Kotlin, and a transition towards a multiplatform approach using Kotlin multi-platform. The project aims, in 2024, to finalize G2P functionalities, ensuring production-readiness, improving security, and adopting modern development practices such as Jetpack Compose and leveraging Mifos' Android SDK. It underscores a commitment to evolving into a generic wallet management system through the Mifos X framework, incorporating cutting-edge features like the latest Payment Hub EE version, a new notifications framework, and a redesigned architecture to align with the Open Wallet Foundation's principles. This ambitious endeavor promises to redefine the landscape of mobile wallets, emphasizing security, extensibility, and a seamless user experience for G2P payments and beyond.
The MBDyn Python Preprocessor aims to streamline the creation of input files for MBDyn simulations by bridging Python scripting with MBDyn's input format. Currently lacking support for all MBDyn entities, the preprocessor needs extension to cover all available entities. Additionally, integrating the preprocessor with Blendyn, a Blender add-on for post-processing MBDyn output, will provide a GUI based preprocessor for generating MBDyn input files. The project entails incremental development, starting with familiarization and planning, extending the entity library, managing model behavior, creating a model container, integrating with Blendyn, and finally, incorporating methods for aeroelastic models. These milestones culminate in deliverables that enable users to build entire MBDyn models using Python, including support for rotary-wing aircraft models, while ensuring completeness through thorough review and documentation.
This project aims to create an open-source python toolkit that efficiently and accurately converts Greeklish text to Greek text. This will be possible by creating a wrapper module that performs inference to the model and then integrating it to the gr_nlp_toolkit pipeline. The second part of the project involves extending the research to determine whether the utilization of more recent LLMs offers a superior balance of accuracy and speed
Summary: The project aims to extend istSOS to support the dataArray extension, which is commonly used in SensorThings for managing Observation entities. Currently, istSOS lacks support for dataArray, limiting its compatibility with SensorThings. By incorporating dataArray support, istSOS will become more versatile and user-friendly, allowing for efficient retrieval and creation of Observation entities. This extension is expected to enhance istSOS's performance by reducing the size of requests and responses, ultimately improving the user experience. The project's expected outcome is the successful integration of dataArray support into istSOS.
This project aims to enhance the multi-select plugin in the Blockly workspace by integrating the IDragger feature of Blockly 11. Currently, the plugin uses a custom block dragger, which has limitations, such as the inability to select certain workspace components like comments. The project proposes to implement a new MultiselectDraggable class that captures all selected blocks, allowing for individual drag operations. Additionally, the proposal includes testing the updated multi-select plugin with other existing Blockly plugins to ensure compatibility and resolve any conflicts. The tentative schedule outlines tasks for integrating IDragger and cross-testing with other plugins, with deliverables including code implementations, test environments, reports on errors and fixes, and a tentative timeline for completion. Future work suggestions include fixing issues related to the DragSelect library, improving performance, and integrating the plugin into App Inventor.
Currently, dotty-cps-async does not support effect systems, hindering its further development. Additionally, there is no mechanism to automatically convert existing standard monads to effect system monads, resulting in increased boilerplate code. To address these issues, a macro will be used to assemble code-based effects to CpsMonad. Additionally, automatic conversion of existing monads to effect system monads will be developed using additional monad converters that will be implicitly applied. The outcome will be the ability to use effect system monads through the async[[X] =>> Monad[R, X]] syntax, facilitating easy composition of various effect systems. Furthermore, automatic conversion of existing standard monads such as Option, Either, List, etc., to effect system monads will streamline and enhance the user experience, reducing boilerplate code.
sktime in its current state does not support categorical variables in input data and this has been an often requested feature from its users. This project aims to add categorical support (for exogeneous input) to the forecasting and transformation modules by reworking the base framework layer and datatypes module. Another objective is to ensure categorical data works when used in sktime pipelines and relevant compositors.
This project seeks to improve the capabilities of Large Language Models in interfacing RDF Data and RDF Knowledge Graphs. This is to be achieved through the creation of a vector database based on LLM representations of the ontologies present in the RDF Knowledge Graphs. This database would then be used to search for ontologies relevant to the user input and allow the LLM to make use of the information present in DBpedia. Deliverables are to include: the source code for development of the vector database, additional source code for integrating this database in the DPedia LLM plugin(s) (which would include user input processing (such as Named Entity Recognition) and database match ranking), as well as benchmarking/test results and all related documentation.
This project studies the development of a tiny worm called Caenorhabditis elegans, focusing on how its cells grow and interact from its early stages. It uses two special tools called Spatial Hypergraphs and Lineage Hypergraphs to map out and understand these interactions. Spatial Hypergraphs look at how cells are arranged and interact in space, which helps us understand how they communicate and influence each other. Lineage Hypergraphs track the family tree of each cell, showing how cells evolve and form different parts of the worm's body. By combining these tools, the project aims to get a complete picture of the worm's development, from a single cell to a fully formed organism. This work could help us learn more about basic life processes and improve medical and tissue engineering fields. The project is supported by international organizations interested in neuroscience and the use of advanced computer models to study brain and nervous system development.
This proposal outlines the development of Quick Replies Functionality for Rocket.Chat. The project aims to introduce a feature that allows users to create, manage, and utilize pre-defined responses, enhancing communication efficiency within the platform. Through seamless integration of AI technology, users will be empowered to generate tailored responses swiftly, streamlining interactions across various contexts. This proposal seeks to revolutionize communication workflows, boost productivity, and elevate the overall user experience within the Rocket.Chat ecosystem.
The current scneario of snaps in KDE and specifically in the discover is not that great. The permission manager for snaps is also very poor and inconsistent. This project aims to look into 1) Fixing the snap backend in discover 2) Fixing the UI of discover like the options of channels of a snap is not shown until the snap isn't installed and others 3) Creating a snap kcm for the plasma-settings and implement the snap permission manager there.
TARDIS provides ways to simulate and analyze supernovae. Currently, as a visualization tool, we have the "Spectral element DEComposition (SDEC) Plot," which generates the output spectrum of the supernovae. However, there is a lot of other information a researcher might need, and this project aims to solve one, i.e., getting the interaction information. TARDIS already has a Tracker functionality which tracks all the interactions in the ejecta, which requires some optimizations and refactoring. I will also be introducing another Tracking Functionality, which will precisely track the last interaction. The Current Tracking functionality has no tests to check if the data generated by it is correct. So, I will also be writing tests. I will also be documenting the trackers.
1.Examine the locking mechanism in RocketMQ and analyze any potential performance bottlenecks it may cause. 2.Design flexible lock optimization strategies to improve message sending and processing performance 3.Finally, the design of adaptive lock will be realized, the research results will be condensed into reports or articles, and our findings will be submitted to academic journals or conferences
This proposal aims to improve the performance of the Finite-Difference Time-Domain (FDTD) algorithm within the gprMax software by integrating XPU technology. This enhancement will focus on optimizing cache and memory efficiency, employing non-linear multistep update sequences for better data locality. The deliverables include a new XPUSolver class, optimized field update kernels, a robust testing framework, and comprehensive documentation.
The aim of this project is to enhance the Beam Yaml API by introducing ML and IO transforms to provide the users with more functionalities. The suggested set of transforms to be implemented are: 1. RunInference 2. ReadFromSpanner 3. WriteToSpanner 4. Enrichment Transforms I also want to add three use cases for the Yaml API, providing end-to-end pipelines demonstrating the use of the newly implemented transforms. The suggested use cases are: 1. Text processing with MLTransform and RunInference 2. Processing tabular data from Spanner 3. Enriching tabular customer data with Enrichment Transform. By expanding the capabilities of the Yaml API, the goal is to streamline the process of constructing and managing data pipelines using Apache Beam. This improvement will enable users to tackle a wider array of data processing tasks with greater ease and efficiency, potentially attracting a broader audience to leverage Apache Beam for their data processing needs.
This proposal outlines a comprehensive plan to implement a system that enables end-users to verify the integrity of their game files against reference checksums. The system will be composed of a server component for storing and comparing checksums and an extension within ScummVM for computing and submitting these checksums.
This proposal targets enhancing the security of OpenPrinting projects, which are foundational to printing software yet vulnerable due to their reliance on C, a language prone to memory safety vulnerabilities. The project aims to integrate these projects with the popular fuzzing framework Google OSS-Fuzz for more conprehensive testing of OpenPrinting projects. This approach not only aims to enhance the testing coverage of exising testing suites but also detect and mitigate vulnerabilities in OpenPrinting projects. This initiative is expected to significantly elevate the security posture of OpenPrinting projects, promoting a more secure open-source ecosystem.
The project aims to enhance the user experience of CircuitVerse organisation by creating a more intuitive and engaging interface suitable for both beginners and experienced users in digital circuit design. Key goals are as follows: integrating UI-based language contribution to enhance language support, improving various aspects of the website's UI, and implementing features like adding dedicated testimonials section, university showcase, and simplified search page. Additionally, the project involves SSO integration, supporting advanced authentication methods, and migrating the UI to Rails view components for improved code efficiency. Overall, the project seeks to elevate CircuitVerse's usability and functionality while maintaining its open and collaborative ethos.
Currently Chromebooks encrypt all user data safely, and they get “erased” by simply erasing the vault containing the encryption key, making the data unreadable. While this is definitely a way to achieve the end goal of making user data unintelligible after the user decided to erase their device, it is not compliant with the current state of the art guidelines on media sanitization defined by NIST. The goal of this project is extending the current method for device safety erase, proposing a way to safely erase data from a Chromebook’s internal storage based on sanitize commands and compliant with the NIST 800-88 Guidelines for media sanitization. This method will also be used during the ChromiumOS powerwashing process.
The Language Server Protocol (LSP) provides a way to write an IDE/editor extension that is compatible with any IDE/editor that supports the LSP. The project aims to address the limitations of the existing JSON Language server in Visual Studio Code (VSCode) by developing a comprehensive JSON Schema Language Server. Leveraging the Language Server Protocol (LSP), this project seeks to develop a Language Server Extension enhancing support for JSON Schema across a variety of platforms. The envisioned solution will fill the gaps in the current VSCode built-in server by introducing essential features such as schema linting, validation, JSON validation against a schema, and JSON linting based on schema. By packaging the language server as a .vsix file, it will be easily distributable and installable, facilitating widespread adoption among developers. Furthermore, the project includes the implementation of a robust automated testing system to ensure the reliability and quality of the language server, complemented by manual testing in both VSCode and Neovim environments to guarantee compatibility and usability.
Currently, Oppia has a pre-push hook which runs frontend unit tests on all files and lacks any backend unit tests in the pre-push hook which can lead to a lack of response for developers until it reaches the Github CI. Furthermore backend unit tests take quite long and similarly End-to-End, lighthouse and acceptance tests on the Github CI are all ran regardless of the PR's changes; all of these problems lead to developer distress. This proposal seeks to solve these problems by running frontend unit tests only on changed files and adding backend unit tests in the pre-push hook, to run similarly on only changed files. It also seeks to reduce Github CI and pre-push hook runtimes by optimizing backend unit tests. Alongside this, this proposal will reduce Github CI usage by running End-to-End, lighthouse and acceptance tests on only PRs which need them.
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.
Multivariate data visualization is useful when grappling with correlated data that naturally arises in a number of scientific fields, such as polarization microscopy, hyperspectral astronomy, various X-ray imaging techniques, geographical data, etc. While specialized and/or commercial tools exist in some of these disciplines, implementing support for multivariate color mapping in matplotlib would provide a unified framework and expand access across the various use cases. This feature has been proposed multiple times, but implementation is non-trivial as it affects the low-level classes that handle data normalization. A discussion on GitHub led me to develop a solution where the class ScalarMappable is replaced by VectorMappable. I have already demonstrated the feasibility of this approach, and developed a working implementation, including a test suite for the new functionality. This project aims to finish this implementation by creating tutorials, examples, and presenting color maps for various use cases. Additionally, tests, docstrings, variable names, and code organization must be updated to conform to the quality standards of matplotlib.