| Maintainer | GitHub ID | LFID | Chat ID | Company Affiliation | Scope | |
|---|---|---|---|---|---|---|
| Ace | pensivej | - | Ace@hopae.io | Ace | Hopae Inc. | sd-jwt-js |
| Gavin | zustkeeper | - | Gavin@hopae.io | Gavin | Hopae Inc. | sd-jwt-js |
| Lukas | lukasjhan | Lukas.Han | lukas.j.han@gmail.com | lukas.j.han | Hopae Inc. | sd-jwt-js |
| Berend Sliedrecht | berendsliedrecht | beri14 | sliedrecht@berend.io | - | Animo Solutions | sd-jwt-js |
| Mirko Mollik | cre8 | - | mirkomollik@gmail.com | Mirko | Fraunhofer FIT | sd-jwt-js |
- Reviewing code contributions.
- Managing issues and bugs.
- Maintaining documentation.
- Communicating with the community.
- Managing version control.
- Participating in project decisions.
- Building and sustaining a contributor community.
Before being considered as a maintainer, contributors should meet the following requirements:
- A history of substantial and consistent contributions to the project.
- A deep understanding of the project's goals, codebase, and best practices.
- Active involvement in the community, including helping others and engaging in discussions.
- Ultimately, the maintainers decide who will become the new maintainer through a majority vote.
- Inactivity or consensus decision can lead to removal.