The CHAOSS Badging API currently supports two distinct badging processes under the same badging program:
- Event Badging
- Project Badging
While both processes share a common website and some infrastructure (authentication, GitHub/GitLab integrations), they represent different workflows, data flows, and responsibilities. These issues increase cognitive load, slow onboarding, slow and ineffective contributions, and make safe parallel development difficult.
We will refactor the Badging API to adopt a modular, layered architecture with explicit separation of concerns. This is necessary to improve the stability, clarity, and maintainability of the Badging System.
The CHAOSS Badging API currently supports two distinct badging processes under the same badging program:
While both processes share a common website and some infrastructure (authentication, GitHub/GitLab integrations), they represent different workflows, data flows, and responsibilities. These issues increase cognitive load, slow onboarding, slow and ineffective contributions, and make safe parallel development difficult.
We will refactor the Badging API to adopt a modular, layered architecture with explicit separation of concerns. This is necessary to improve the stability, clarity, and maintainability of the Badging System.