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.
The main aim of my project is to add some new features & solve various major issues or Bugs in the mifos-mobile-cn app and at the same time also extend the features of its app in various ways which can help improve the user experience and ultimately the productivity of the app. I also intend to take up some ideas from the ideas page of Mifos and inculcate them in my project which can provide the best features for the user. Some Features Are -: 1. Major UI changes , 2. Adding Shimmer RecyclerView , 3. Adding fingerprint authentication system in this app, 4. Adding option for Support different languages in the setting fragment and so on. Some Bugs And Issues in This App : 1. Modifying Register Activity, 2. Fixing all Hardcoded string of the whole app, 3. Resolving All The Layout Designing Warnings Of The App and and so on.
The goal is to design and implement the solution to the Airavata Data Catalog to record the metadata extracted from the Literature, Experimental and Computational data in support of Small Molecule Iconic Isolation Lattices (SMILES) Data. More precisely, this includes the data synchronization with the end-users. Currently, Airavata is extending an open-source project called “open-inventory” with additional features. Airavata uses three individual and unrelated databases to save the Literature data, Experimental data, and Computational data. Having these in usage, the chemical compounds are represented with ambiguous keys and missing data. Therefore, the scientific representation of the compounds with a specific structure; scientific data model (SDM), and related ontology (SDMO) is much better to analyze the behavior of a compound. In particular, a common data model should be used to synchronize the data efficiently.
<p>Refactoring tools help pharo developers to perform a number of predefined refactorings in automated fashion. However, besides the options provided by Pharo, there is still some missing refactoring options and a list of open issues.</p> <p>The goal of this project is to improve the Pharo’s refactoring support by</p> <ul> <li>Adding three missing refactoring options: inline method, inline variable and find and replace duplicate code.</li> <li>Improving the usability of refactoring tools by adding: preview dialogs and shortcuts for a number of refactoring options, such as: extract method, extract temp, inline method.</li> <li>Improving the extract method refactoring option: checking for duplicated instances of the refactored code and letting the user specify arguments.</li> </ul>
<p>The goal of this project is to provide users of the mlr package with a way to visualize what happens during the tuning process that identifies the best hyperparameters for a learner given the data. Looking at popular packages in the machine learning community such as sklearn or caret, the model evaluation visualization process either requires lots of boilerplate code or is sparsely implemented across packages. This project will rectify the situation for R users of the mlr package by implementing three new features: plotting of a single hyperparameter against a scoring function, plotting multiple hyperparameters and scoring functions, as well as support for ablation analysis. The design of the features will focus on ease of use for the end user and customization. Users can choose to leverage automatically generated plots or use the data in some other manner downstream.</p>
Currently, the Metrics Controller in the Keptn Lifecycle Toolkit only allows querying a single value per metric. This project will enable users to define timeframes for metrics and get standardized aggregated results for the given timeframe. The addition of time frames for metrics would provide developers with a lot of flexibility when analyzing their application’s performance as they would be able to easily switch between different timeframes to get a better understanding of how their application is performing. This can be achieved by modifying the structure of the Metric CRD by adding certain fields and then modifying the APIs of our Metric providers to support these newly added fields. The metrics controller would be able to query metrics over a timeframe and then return raw values from the providers which can then be passed to the aggregation functions to calculate the desired aggregated value. These values would be updated in the Metric CRD.
Description: Notary is a CNCF incubating project that aims to provide signing and verification capabilities to ensure delivery integrity and security. It supports creating and storing signatures for container images, SBOM, vulnerability scanning results, etc. to ensure the artifacts someone produced have not been tampered by others. Notary only has an Azure Key Vault plugin for storing keys in Azure Key Vault, which is used to sign and verify artifacts in the OCI registry. [HashiCorp Vault](https://github.com/hashicorp/vault) is a popular KMS and we see more and more users rely on it in the on-premise environment. Expected Outcome: Develop a Key Management System (KMS) plugin with [HashiCorp Vault](https://github.com/hashicorp/vault) for Notary CLI (Notation), which can be used to store the keys for Notation signing and verification.
LPython currently doesn't support classes and object oriented programming paradigm. This goal of this project is to implement classes and OOP features like inheritance and polymorphism in LPython at the ASR and LLVM level. This will enable porting of standard library modules in Python to LPython. The project involves adding class semantics to the Abstract Semantic Representation (ASR) in LPython, allowing for the inclusion of member functions with local scope and enabling seamless integration of object-oriented programming (OOP) features. This entails modifications to the ASR nodes, the AST-to-ASR conversion process, and the ASR-to-LLVM translation to facilitate function calling and method invocation. Additionally, the project includes extending operator functionality, transitioning from dataclass to struct decorators, implementing limited dunder functions, and thorough integration testing.
In today's data-driven world, leveraging legacy data can be a game-changer for businesses. By integrating AI with Retrieval-Augmented Generation (RAG), organizations can unlock the hidden potential of their historical data. RAG combines the power of large language models with a retrieval mechanism that fetches relevant information from vast datasets. This approach not only enhances the accuracy and relevance of AI-generated responses but also ensures that valuable insights from legacy data are utilized effectively. Whether it's improving customer service, optimizing operations, or driving innovation, RAG empowers businesses to transform their legacy data into a rich source of actionable intelligence, paving the way for a more informed and strategic future. Deliverables: Detailed research and conceptual framework document (whitepaper) to implement AI that uses mainframe data.
<p>Having a great development environment is one of the many things that ensure ease of developing software. It increases productivity and interest in software building. Another very important aspect in software development is testing. With a strong testing infrastructure, the cases of buggy code being patched to production can be reduced a lot. Also the load on committers/reviewers drops down drastically with this as obvious bugs fail to pass the automatic testing phase and alerting the developers that something has gone wrong before they ask for reviews. Through this project we can aspire to improve upon both these aspects and hence result in a big enhancement to the developer experience. This project will involve clearing out various issues relating to enhancement requests tied to these areas as well as developing new tools to support our vision of a better development and testing infrastructure.</p>
lpython is a statically typed compiled programming language with syntax inspired by Python programming language. lpython also aims to have first-class support to work with Python and C libraries. lpython has multiple backend targets like C, C++, and LLVM IR that can be compiled to target executables with appropriate C/C++ compiler or the LLVM compiler toolchain. As lpython is statically typed and ahead-of-time compiled it offers much better performance than cpython. The current state of lpython is not feature-complete nor bug-free. I propose to add an interactive shell for lpython, so that the developers can quickly prototype ideas, and improve the debug information generated for the LLVM backend so that users can execute a single line of code at a time and pretty print variables and complex datatypes.
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.
The symbolic package for Octave, octsympy, is a highly demanded package and an important project to the community. As such, it is important to keep it in a healthy state. To create a balanced project, we divide the project into 3 parts to deal with *present*, *past* and /future/ goals respectively. The *present* part aims to work towards 3.0.0 milestones, such as supporting the latest versions of Sympy & Octave and improving the CI. The *past* part deals with long-standing bugs that had fallen through the cracks, fixing those lost and forgotten bugs. Finally, the /future/ part will look at how we can improve maintainance going forward. We will try an experimental work based on the Pythonic project. That being said, exactly how far we get may depend on mentor guidance. In any case, our goal is to make octsympy easier to maintain in the future.
Inspired by the pMix and Amati projects, this plugin will be built using the JUCE framework for the interface and libFaust with LLVM and interpreter backend API to compile Faust code. The user will be able to write Faust code in any VST-aware host and can be saved or recompiled on the fly. There are six components to the plugin, the editor, the console, a section for editing the parameters, a block diagram displaying the DSP, a preference page to change the settings, and a keyboard section where the user can enter MIDI inputs. The plugin will also support polyphonic Faust DSP objects, and the parameter inputs will be created depending on Faust code. Amati project is currently used as a starting point for the project, so it will use much of the existing code. However, changes might be made to them if needed.
<p>OpenTimelineIO is an interchange format and API for editorial cut information. OTIO includes opentime, a library for dealing with time. In order to deal with time intervals of clips/sequences it makes sense to have operators that help with temporal reasoning. Such operators have been given by James F. Allen. The core OTIO API is written in C++. A lot of other higher level languages are popular for tooling. Many such languages (such as Lua, Go, Ruby, etc) are not directly compatible with C++ but have ways to interact with a C-API. So it would help if we have a C wrapper for OTIO. Java is one of the most versatile languages, also powering one of the most pervasive platforms - Android. Mobile Computing is becoming more powerful and widespread by the day. Having Java bindings will help us get OTIO support to all the Java compatible platforms.</p>
The Debezium Management Platform currently deploys pipelines only to Kubernetes. This project adds host-based deployment support, enabling users to deploy Debezium Server pipelines to bare-metal servers and cloud VMs via SSH and Docker. The implementation integrates into the platform's existing event-driven architecture by adding a new EnvironmentController for host targets, an SSH-based provisioning service that validates and prepares remote hosts, a lightweight agent deployed on each host for managing the Debezium Server lifecycle via REST APIs, and a status polling mechanism for monitoring deployments. Key deliverables include the host registration API, automated provisioning with remediation, the Debezium Host Agent, Docker-based deployment engine, config drift detection, and comprehensive integration tests using Testcontainers.
This project aims to extend the existing Marine AR Module Builder into a more accessible, scalable, and educator-friendly toolkit for creating augmented reality learning experiences in Unity. The primary objective is to reduce the technical barrier for educators and developers by introducing intuitive editor tools, structured workflows, and reusable systems for building marine AR modules. The proposed system will include drag-and-drop environment upgradation, streamlined actor placement and configuration, and reusable behavior templates for movement, interaction, and ecological logic. To improve flexibility and maintainability, modules will support extensive JSON/script-based definitions, enabling structured and streamlined content creation. Validation tools will be implemented to detect missing assets, invalid configurations, and performance issues, ensuring reliability and usability.
As highlighted during the 2025 Blender Conference, one of the primary challenges facing the Compositor is managing complexity. To address this, the goal of this proposal is to make it as accessible as possible by porting over familiar nodes from Geometry Nodes. This project aims to: - Develop a future-proof classification between the two modules. - Port matrix & math utility nodes into the Compositor: Matrix SVD, Bit Math, Boolean Math, Integer Math, Compare, Float To Int, Hash Value, and Random Value. - Extend GPUType to include boolean, integer and integer vector types. - Ensure UI and behavior consistency between ported nodes and existing ones, including full support for the GPU Compositor. - Implement regression testing for all newly ported nodes. - Document the rationale behind node selection, implementation and functionality in the new context.
<p>Mercurial has an extension called Largefiles, which allows storing large files outside of the normal history to decrease needed bandwidth for clones and pulls. Large files are stored in a central location and you fetch them only when you need them. Largefiles extension supports by design storing files in the same location as the main repository hosting server. It can be workaround by configuring a web server to redirect largefiles request to some other URL, but this solution does not provide sufficient flexibility. The Project goal is to allow user to specify remote server where large files are stored. Instead of downloading all files from the the main repository, client would download them from remote store, which could greatly decrease load from the main server. Remote store can live anywhere on the web e. g. in the cloud, so connection among clients and the store should be secure.</p>
<p>Tiled doesn’t support saving custom objects and reusing them with their predefined properties, currently for doing so, an object can be duplicated, but then, when one of the duplicates is updated, the other won’t.</p> <p>Tiled also offers a type system, a type is a property that can be given to an object, it provides sharing custom properties between objects, but can't define properties like the geometry of the objects or the specific graphics.</p> <p>This issue appeared many times on GitHub, solving it will have a great impact on productivity while working on big projects which require reusing a certain object and frequently applying changes to it.</p> <p>This project aims to create a template system in Tiled, templates will save the properties of an object and will allow creating multiple instances of it, sharing the same properties.</p>
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 aims to create a benchmark dataset for tree species classification using multi-sensor airborne data (RGB, HSI, and LiDAR) from the National Ecological Observatory Network (NEON). The goal is to build a reproducible, well-documented dataset of hand-annotated tree crowns and use it to train baseline models for each modality individually and in combination. Alongside this, we’ll explore integration with DeepForest to support crown detection and classification workflows. Deliverables: 1. A finalized, curated data product for tree species classification using NEON data added to TorchGeo. 2. Baseline models for each modality and multi-modal combinations. 3. Reproducible training pipelines and clear documentation. 4. A utility to simplify NEON data access. 5. Integration work and documentation linking this effort with DeepForest.
Proposal Summary This project aims to modernize ERDDAP™ page rendering by migrating it to a templating framework. The current rendering process relies on manually constructed HTML, which makes it difficult to maintain and customize. By implementing a template-based system, we will improve code maintainability, enhance flexibility for customization, and support modern web development practices. Deliverables Identify a suitable templating framework (e.g., FreeMarker, Thymeleaf, or another appropriate choice). Refactor ERDDAP™’s HTML generation logic to use the selected template engine. Ensure the new system maintains full feature parity with existing pages. Improve documentation on how to modify and extend ERDDAP™ templates. Implement tests to verify rendering consistency. This upgrade will make ERDDAP™ more maintainable and adaptable for future development.
<p>The primary aim of this project was to bring professional efficiency by reducing boilerplate code, reducing the number of configuration lines with additions of some important features like multi-language translation support, reusable token validation, server-side logging, and fast response time by reducing build size. Increasing test coverage (>95%) and adding headless browser tests (using selenium) for success and failure responses with interactions between different pages.</p> <p>This will make the code of <a href="https://github.com/openwisp/openwisp-wifi-login-pages/" target="_blank">openwisp-wifi-login-pages</a> more robust to handle any stressful conditions with backend <a href="https://github.com/openwisp/openwisp-radius" target="_blank">openwisp-radius</a>.</p>
<p>Project Goals</p> <ul> <li>Since most of the app is built using Flutter, we should make full use of it and make the app support iOS devices as well.</li> <li>The app can be of more use if we add a section that will act as a Social Media Platform for Travellers.</li> <li>The Business-Logic/API-calls and the UI part of the app needs to be separated in the right way. Right now, All the API calls are made from the UI class itself.</li> <li>The UI/UX of the app also need improvements, especially the Profile and Intro screens. And the app also lacks some basic features like Form validation, Profile Picture selection during the Registration process, Using Gallery as a Source for the image at the time of Monument Detection etc.</li> </ul>