I spent last month contributing to Cloud Native Computing Foundation projects, on purpose and in the open. Not a hackathon, not a single big feature, but a deliberate sweep across many projects: fixing what was actually broken, filing what was genuinely missing, and reviewing other people's work where I had something useful to say. Here is what that looked like, and what I took away from it.
The rule I set for myself
One rule mattered above all: every contribution had to be real. Cloud native projects get a lot of low effort noise, and maintainers can spot a padding contribution instantly. A whitespace only pull request or a fake fix does not just get closed, it burns your credibility. So the bar was simple. If a change was not genuinely useful, I did not open it. Every defect I touched, I verified against the actual source first, and for code fixes I reproduced the bug before and after the change.
That rule shaped everything else.
Where I contributed
