EnAccess Idea List for Google Summer of Code 2026

Introduction

These project ideas are curated directly from the MicroPowerManager roadmap and focus on areas that are explicitly desired, not experimental, and well-aligned with the current direction of the project.
Each idea is scoped to be achievable within a GSoC timeline while delivering concrete, reviewable outcomes that improve MPM’s maintainability, usability, and adoption

1. Documenting MPM Core Domain Entities and System Architecture

MPM has grown into a feature-rich platform, but documentation has not kept pace with development. Many core entities (customers, appliances, meters, transactions, tariffs, deployments, etc.) and their interactions are poorly documented or undocumented, making onboarding new contributors and operators difficult.

Reference Issue

• Goals & Deliverables
  • Audit existing documentation and identify gaps
  • Produce clear documentation for core MPM entities and their relationships
  • Document key workflows (payments, deployments, device lifecycle)
  • Add architecture diagrams and sequence flows where appropriate
• Skills Required
  • Technical writing
  • Basic PHP (Laravel) understanding
  • Markdown and documentation tooling
  • System design fundamentals
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 175 hours

2. Inventory and Deployment Management Module

MPM lacks a unified, first-class system for tracking physical inventory (devices, meters, appliances) from procurement through deployment and retirement. This makes it difficult for operators to accurately manage stock levels, deployments, and asset lifecycles.

Reference Link

• Goals & Deliverables
  • Design inventory data models aligned with existing MPM entities
  • Implement inventory tracking (stock, assignment, deployment status)
  • Link inventory items to customers, sites, and deployments
  • Provide basic UI and API endpoints for inventory operations
  • Documentation and migration guidance
• Skills Required
  • PHP (Laravel)
  • Database modeling
  • REST API design
  • Basic Knowledge of JavaScript and CSS
  • Vue.js
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 350 hours

3. Cloud Service Status and Health Tracking

Operators and maintainers currently lack visibility into the health of MPM cloud services. When issues occur, it is difficult to quickly determine service status, affected components, or historical uptime.

Reference Link

• Goals & Deliverables
  • Define health indicators for core MPM services
  • Implement service health checks and status reporting
  • Persist and visualize historical uptime and incidents
  • Provide a status dashboard for operators and admins
  • Alerting hooks for degraded or failing services
• Skills Required
  • PHP (Laravel)
  • Monitoring and health check concepts
  • REST APIs
  • Basic frontend development
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 175 hours

4. Backend Refactoring for Maintainability and Testability

Parts of the MPM backend have accumulated technical debt, including large service classes, duplicated logic, and unclear domain boundaries. This makes ongoing development slower and increases the risk of regressions.

Reference Link

• Goals & Deliverables
  • Identify high-impact refactoring targets in the backend
  • Extract reusable services and clarify domain responsibilities
  • Improve type safety, naming consistency, and structure
  • Increase unit and integration test coverage
  • Produce a refactoring guide for future contributors
• Skills Required
  • PHP (Laravel)
  • Refactoring techniques
  • Automated testing
  • Software design principles
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 350 hours

5. Modern SMS Gateway Support

SMS remains a critical communication channel in many MPM deployments, but existing SMS gateway support is deprecated or limited. A modern, extensible approach is needed to support multiple providers reliably.

Reference Link

• Goals & Deliverables
  • Review and document existing SMS gateway implementation
  • Design a pluggable SMS gateway interface
  • Implement support for at least one modern SMS provider
  • Add retry, failure handling, and delivery status tracking
  • Documentation for adding new SMS providers
• Skills Required
  • PHP (Laravel)
  • External API integration
  • Messaging systems
  • Error handling and observability
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 350 hours

6. REST APIs for Data Import and Export

Operators often need to move data in and out of MPM for reporting, migrations, or integration with external systems. Current import/export mechanisms are limited and not standardized.

Reference Link

• Goals & Deliverables
  • Identify key entities suitable for import/export (customers, payments, devices)
  • Design RESTful endpoints for bulk data import and export
  • Support common formats (CSV, JSON)
  • Validation, error reporting, and partial success handling
  • Documentation and example workflows
• Skills Required
  • PHP (Laravel)
  • REST API design
  • Data validation and parsing
  • Performance considerations
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 175 hours

7. OpenPAYGo Device Integration

OpenPAYGo is a widely adopted standard for PAYGo energy devices. Native support in MPM would significantly improve interoperability with compliant devices and reduce custom integration effort.

Reference Link

• Goals & Deliverables
  • Study the OpenPAYGo specification and reference implementations
  • Design integration points within MPM
  • Implement OpenPAYGo-compatible device workflows
  • Token generation, validation, and device state handling
  • Documentation and example device integrations
• Skills Required
  • PHP (Laravel)
  • Documentation
  • PAYGo and IoT concepts
  • Cryptography basics (for token handling)
• Mentors
  • Obinna Ikeh
  • Daniel Mohns
• Expected Timeline
  • 350 hours