Open source software to the public free of charge
Explore maintainer wishlists.
Showing 5 of 200 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Edward Kang
My name is Edward. I'm a Master’s student at the University of Colorado Boulder in the US and I am passionate about Apache Fineract’s mission to improve the availability of financial services to people all over the world. Apache Fineract provides core banking APIs, but lacks a community-maintained layer for end-users. The former Self-Service API was removed, leaving vendors to build their own frontend from scratch. To support this new frontend, I am proposing a new Backend for Frontend (BFF) and associated frontend that enables improvements to end-user security, reliability, performance, and auditing. The focus of this project is to build a POC that is well-tested and documented so we can build a "release-ready" solution in the future. Deliverables include: 1) Standalone Spring Boot BFF application with its own user model and JWT-based authentication 2) Feign client integration with Fineract's core API via a dedicated service account 3) API Aggregations for User data summaries, account information, loan and savings views, and transaction capabilities 4) User registration flow with OTP and Identity Verification 5) User login flow with 2FA 6) Auditing for Basic Frontend Concerns 7) Open Banking Authentication Flow 8) A working frontend to demo these features Some stretch goals include but are not limited to: 1) MPIN for transaction authorization 2) Rate Limiting 3) HSM key storage
Mentors: Student: yc_lai
Apache Mahout's QDP is a GPU-accelerated quantum state encoding library bridging Rust, CUDA, and Python — yet its contributor experience lags behind its technical ambitions: unsafe blocks lack // SAFETY: justifications, public APIs are undocumented, Clippy warnings accumulate, and neither cargo doc nor Python API generation is enforced in CI. This project tackles all three layers in 12 weeks. Phase 1 narrows unsafe blocks with proper safety documentation, achieves 100% RFC 505-compliant API coverage, eliminates all Clippy warnings, and adds ≥25 GPU-independent unit tests. Phase 2 builds an automated Sphinx pipeline for the Python (qumat/) API and validates Rust ↔ Python interface consistency. Phase 3 fixes broken links on the Docusaurus site and integrates both cargo doc and Python doc generation into CI. Key deliverables: refactored unsafe blocks across 4 core files, 100% Rust API doc coverage, zero Clippy warnings, ≥25 new unit tests, automated Python API docs, a rustdoc.yml CI workflow, and a contributor documentation guide — creating a unified, drift-resistant documentation experience across QDP's Rust and Python interfaces.
Mentors: Student: Nidhi Bhawari
Apache Fineract is open-source banking software used by institutions around the world to serve people who don't have access to traditional banks. Every time someone opens an account, creates a loan, or uploads a document, the system has to read the incoming data, validate it, and save it. The current code that does this was written about twenty years ago, the data arrives as plain text, and the system manually picks apart each field by hand. This causes silent bugs, makes the code hard to change, and produces thousands of lines of repetitive plumbing. The Fineract community has already built a modern replacement that uses strongly-typed data objects, so data is automatically structured and validated the moment it arrives. The new system is in production for 13 features; around 57 features still use the old approach. My GSoC project is to move 5–7 of those remaining features onto the new system, one feature at a time, strictly following the migration guide the team has already written. Proposed features (subject to mentor confirmation): Holidays, Account Number Format, Codes / CodeValues, Office, Fund, and Calendar. For each feature, I will design new typed data classes, rewrite the related handler code, simplify the business logic to accept typed inputs, replace hand-written validation with built-in checks, and make sure all existing tests still pass. Where test coverage is thin, I will add new automated tests in line with the community's quality direction. This work reduces long-standing technical debt and makes future development faster and safer in a system that real banks depend on every day.
Mentors: Student: Peiyang He
Apache Fory provides high-performance serialization & deserialization and code generation from IDL, but it currently lacks end-to-end gRPC service integration for C++ and Rust. As a result, developers may still need to rely on external toolchains (e.g. protoc/prost) to generate service bindings, which prevents Apache Fory from being used as a complete gRPC solution. This proposal aims to enable Apache Fory to generate gRPC-compatible client and server code for both C++ and Rust, while reusing the existing gRPC runtimes (gRPC C++ and tonic). The core idea is to extend the Apache Fory compiler to generate service stubs and integrate Fory's serialization & deserialization into the gRPC pipeline by replacing the default codec (protoc and prost). The design decouples API definitions from transport- layer bindings and introduces reusable codec implementations. The project will also include comprehensive testing (unit, differential, and cross-language), CI integration, and documentation. This work will make Apache Fory a practical alternative to existing protobuf-based toolchains in gRPC frameworks and provide a reference architecture for adding gRPC support to other languages in the future.
Mentors: Student: Jhe Chen Li
This project improves AI agent reliability in Apache Airflow by addressing long-context degradation in realistic multi-turn development sessions. I will build auto-synced SKILL.md artifacts from Airflow’s contributor docs to prevent context drift, a community workflow for collecting and triaging real agent failure cases, and an Airflow-specific benchmark for evaluating workflow compliance on real tasks. The final deliverables include CI-backed skill generation, failure-case aggregation, benchmark scenarios with scoring, and a modular skills folder that reduces context pressure by loading only task-relevant guidance.