From Committer to PMC: My Second Year with Apache HertzBeat

Hello everyone, it's a great honor to be invited by the community to join the Apache HertzBeat™ PMC.

It has been roughly a year since I wrote my new Committer blog. That post ended with a line: "Becoming a Committer means taking on greater responsibility." This past year, I've been trying to put that into practice.

The Numbers From This Year

139 commits　41,285 ++　11,444 --

139 merged pull requests across 1,002 files in total. 88 of them landed after I became a Committer, and the center of gravity of my contributions quietly shifted — away from "fix the bug I hit, add the feature I need," and toward "the work that nobody asks for but somebody has to do."

Where the Work Moved

This year's work centered on four areas:

• Security hardening: systematically reviewed endpoint and permission configuration, and drove a round of hardening improvements.
• Release engineering: took part in preparing and releasing 1.9.0 — from database migrations and license materials to the upgrade guide — and for the first time looked at the project through the question "can this version ship?"
• Engineering infrastructure: got the native collector genuinely running, and improved CI and the build process.
• Alerting and stability: kept refining the alerting pipeline, and fixed memory leaks, regressions and more.

From Writing Code to Being Part of a Community

If one thing changed how I understand open source this year, it was reviewing.

So far I have reviewed 97 pull requests from the community and taken part in 207 issue and PR discussions. Those PRs came from more than forty contributors, and for many of them it was their first contribution.

Last year I wrote that a reviewer should give contributors "constructive feedback and recognition." Actually doing it, I found the hard part isn't spotting problems — it's calibration: when to hold the line and when to let something through; how to point out a problem without extinguishing someone's enthusiasm on their very first PR. I started from a single merged documentation PR myself, and I still clearly remember how it felt to be answered, and taken seriously.

What Joining the PMC Means to Me

For me the PMC isn't a bigger badge. It's one more shift in attention: from "my code" to "the project's health."

• Accountability to users: paying attention to the problems users hit when using and upgrading HertzBeat, so that every release is stable, reliable and smooth to upgrade to.
• Accountability to contributors: timely reviews, better docs and a lower barrier to entry, helping more newcomers grow into long-term contributors.
• Accountability over the long run: keeping technical judgement honest, and taking part in roadmap planning and community governance so that decisions are more transparent and collaboration runs more smoothly.

Advice for Open Source Developers

Last year I wrote that open source "begins with interest and grows through practice." This year I'd add one more clause: and grows through responsibility.

For developers just starting out, opening that first PR is still the single most important step. And once you've been around a project long enough, you'll naturally reach a turning point — you start noticing the problems that "belong to no one": stale docs, brittle CI, a dependency manifest nobody has reconciled, an edge case nobody has claimed.

Pick one of them up. It's the most natural path from contributor to maintainer, and it's exactly the kind of person a community needs most.

Acknowledgments

Thank you to Tom, Qingran Zhao, Aias00 and Calvin for their guidance, and to everyone in the Apache HertzBeat community for the careful reviews and patient guidance on every PR, and for the trust the community has placed in me.

If you'd like to contribute to Apache HertzBeat, documentation, issue fixes, and feature work are all good places to start — there's always someone in the community ready to respond to your ideas.

I look forward to taking this project further, together with many more developers.