Upstream systems engineer. I work on Kubernetes correctness, observability, and cloud native telecom.
My way is simple. I find one bug, then I turn it into a rule I can reuse, and I check other projects for the same bug. After I fix it, I add a test and send it upstream.
| Merged upstream | 248 pull requests in 71 projects. 172 of them are in 46 CNCF and Kubernetes ecosystem repos. |
| CNCF related contributions | 3,807 |
| Kubernetes | GitHub org member |
| Governance | Nephio TSC member, LF Networking |
| OpenTelemetry | GitHub org member |
| Maintainer | M5Stack Platforms in upstream Zephyr, status: maintained |
Every merged PR is listed and linked here: open source portfolio
The CNCF number updates by itself from the CNCF DevStats GithubIDContributions API. It is a count of contributions, not a score. The other numbers are my authored, merged, public upstream PRs, last checked in August 2026.
Most of my work is Kubernetes DRA correctness. I read the scheduler and device allocation code, and I check the math and the state: sums, products, conversions, reservations, rollback, and saved allocations. They should not overflow, truncate, leak, or charge twice. I found and fixed five bugs of this kind in the Kubernetes v1.37 allocator: the driver and pool cache mixed together, rollback was not clean after backtracking, a saved shared device was charged twice, a bad validRange was not rejected, and a capacity too large to serve was not rejected. After that I ran the same check on other projects too, like Kueue, Volcano, CDI, and vendor DRA drivers from Intel QAT, Google TPU, IBM Power, and AMD ROCm.
k8s #140435 · #140431 · #140437 · #140666 · #140442
For observability I review OpenTelemetry C++ exporters by their lifecycle. One operation should not live longer than its owner, should not miss the finish signal, and should not settle zero times or two times when cancel and shutdown race together. HttpServer use after free #4289 · ES exporter lost wakeup #4298 · curl settle one time #4363
For telecom I work on the OCUDU NTN control path. I treat one SIB19 update as one transaction, not many small bugs. I check it from start to end: coroutine lifetimes, queue backpressure, validation, rollback, timing boundaries, and system information assembly. This work goes through Nephio governance and upstream merge requests.
The full analysis, the patch, the test, and the review discussion are all in my open source portfolio. What I do right now is in my open pull requests.
AMD ROCm™ Certified Associate, from AMD. It is about developing, optimizing, and deploying ROCm software for AI and HPC work on AMD Instinct GPUs. verify on Credly · my ROCm upstream work
I am on the Nephio Technical Steering Committee, I maintain the M5Stack platform in upstream Zephyr, and I run the O-RAN in B5G/6G track at COSCUP. I give tech talks in Taiwanese. I also make bilingual walkthroughs from real review discussions, because I want to make the step from using to contributing easier. I finished LFC102: Inclusive Open Source Community Orientation in July 2026.
Website · Publications · Honors · ORCID · LinkedIn · LFX · Credly · hctsai@linux.com
I am a research assistant at National Yang Ming Chiao Tung University, Taiwan. I grew up in a small fishing village in Dapeng Bay, Pingtung. I care about making the technical community easier to enter, especially for people who do not start with a big network or resources in English.





