arcodange/dance-lessons-coach
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
f470fa3274a7d96aa46114a21d3d0d9b024d1b91
dance-lessons-coach/documentation/ROADMAP.md
Gabriel Radureau 1aef136436 📝 docs: cherry-pick 6 focused guides from PR #17 (option c) (#87) 
Co-authored-by: Gabriel Radureau <arcodange@gmail.com>
Co-committed-by: Gabriel Radureau <arcodange@gmail.com>
2026-05-06 06:37:17 +02:00

1.5 KiB
Raw Blame History

Roadmap & Future Enhancements

Tracking pending features and architectural improvements. Extracted from the original AGENTS.md (Tâche 6 restructure). Status updated continuously — items move to "Completed Features" section once shipped.

Potential Features

  • Database integration
  • Authentication / Authorization
  • Rate limiting
  • Metrics and monitoring
  • Docker containerization
  • ✅ CI/CD pipeline (ADR-0016, ADR-0017)
  • Configuration hot reload
  • Circuit breakers

Architectural Improvements

  • Request validation middleware
  • ✅ OpenAPI / Swagger documentation with embedded spec
  • Enhanced OpenTelemetry instrumentation
  • Metrics collection and visualization
  • Health check improvements
  • Configuration validation enhancements

Completed Features

  • ✅ Graceful shutdown with readiness endpoint
  • ✅ OpenTelemetry integration with Jaeger support
  • ✅ Configuration management with Viper
  • ✅ Comprehensive logging with Zerolog
  • ✅ Build system with binary output
  • ✅ Complete documentation with commit conventions
  • ✅ Version management with runtime info

How to Propose a New Feature

  1. Open a Gitea issue describing the use case and acceptance criteria
  2. If the feature implies an architectural decision, draft an ADR (adr/<NNNN>-<slug>.md) following the template
  3. Reference the ADR + issue in any PR introducing the feature
  4. Update this roadmap (move from "Potential" to "Completed" when shipped)
Reference in New Issue View Git Blame Copy Permalink