
Joshua Poddoku
Open Source Technology Evangelist | DevRel | Turning conversations into contributors, AI-assisted and human-led
A recurring question I encounter in various workplaces is this: when a business opens its source, what does it take for a community to follow? I’ve noticed that the issue often lies beyond the code itself. People select tools based on their features but remain engaged due to additional benefits: clear rules, documented guidelines, a transparent vision, and a welcoming community. Unfortunately, these aspects are often sacrificed for the sake of speed, making them challenging to restore later.
My focus this Q4, 2026 - We’re seeing a surge in AI-generated code, pull requests, and issues, raising the barrier to human contribution at the point when most Open Source projects can least afford to lose people. I leverage AI frequently, primarily to support contributor dashboards, onboarding, and reviews. These reviews prioritize teaching over rejection. The initial engagement remains human-led.
- The Contributor Ladder: Surface → Builder → Steward, and where attention pays off
- Community Signals: how Open Source talks about AI-written code, updated every 12 hours
Tracking · updated Currently, the sentiment regarding AI-generated code shows Pushback on Bluesky (17) and Wary on Hacker News (32). This scale ranges from 0 for pushback to 100 for enthusiasm, based on everything I’ve tracked so far. AI-assisted, human-led. How I track it
If you’re building an Open Source project and want contributors, not only stars, let’s talk.
Worth reading right now
- Benchmarking quality gap human vs AI codeResearch · Bluesky
- Measuring sloppiness in LLM-generated codeResearch · Bluesky
- Team runs AI review bot in CI with limitsPractitioners · Hacker News
Notes from the Open Source World
Every week or two, I send a short, handpicked note on what's moving in Open Source and what the community signals are showing. You can unsubscribe from any email.