As a PostgreSQL Commitfest Manager, I interacted with the PostgreSQL development community more broadly than usual. This particular commitfest was the first of five patch-review-and-commit events for the PostgreSQL 16 development cycle. To contribute to open-source communities, one needs to find a place to begin and navigate institutional knowledge. Many users face this challenge, which is reflected in worldwide surveys held by Timescale. The author of this blog post shares their experience as a CFM, including a timeline, observations, and lessons learned, in a future blog post. To volunteer for a commitfest, one should already feel comfortable interacting with the PostgreSQL development community, know what a commitfest is, be aware of the cfbot CI interface, have an email workflow set up, and consider contributing a patch before volunteering. As a CFM, my role involved sending emails to many people, ensuring administrative work, answering questions, and keeping contributors' patches flowing. The goal was to keep things flowing by helping those who got stuck, reminding contributors to give as much as they receive, and drawing community attention to small problems. The author emphasizes the importance of exercise restraint when exercising independent judgment at the end of the CF, finding a consensus from the community instead of asserting personal opinions.