Next Steps for the Caddy Project Maintainership - Announcements - Caddy Community
Key Takeaways
- The Caddy project maintainer is stepping back from personally reviewing all comments, issues, and PRs.
- A maintenance team is being granted tag and release privileges to help manage the growing project.
- The decision aims to increase the project's bus factor (currently 1) and remove the maintainer as a bottleneck.
- Project activity has surged over the years, with forum traffic increasing 2-5x and GitHub notifications rising from 1-3 to 10-25 daily.
- The increased workload now involves more niche external configuration questions and routine support that others can handle.
The long-time sole maintainer of the Caddy project, now 11 years old and hugely popular, announced a significant shift in project management due to overwhelming growth. Historically, the maintainer personally triaged 1-3 daily notifications and managed a small backlog of issues and PRs, easily keeping up with the project's development. As the community matured, knowledge accumulated, and the volume of support requestsânow averaging 3-5 forum topics and 50,000 daily page viewsâhas drastically increased, leading to an unmanageable GitHub inbox of nearly 200 notifications daily. To ensure the project scales better and to unblock development where the maintainer was the bottleneck, tag and release privileges are being granted to a maintenance team. This move is intended to increase the project's bus factor, involve the community more deeply in leadership, and allow the maintainer to focus on less routine tasks.
