Joshua Poddoku
banner
joshuapoddoku.com
Joshua Poddoku
@joshuapoddoku.com
Open Source technology evangelist, DevRel, Apache Committer. I help businesses apply first-principles thinking to community, GTM and governance around OSS.

📊 joshuapoddoku.com/community-signals
🌐 joshuapoddoku.com/work-with-me

Views my own.
It's simple to understand why community comes first before code

Code is the vehicle but community is the driver.

The driver's health and wellbeing comes first before everything existed.

Code can fail. But community won't if it is built with right principles and intent.
September 15, 2026 at 11:08 PM
I do have a similar question, this is really great to follow no AI slop policy. But what about ai-assiated, human-led code and how are projects really able to measure the % of slop?
September 15, 2026 at 6:42 PM
I think the easiest way is to measure difference between ai slop, ai generated, ai assisted code. Though technically all are done by ai.
September 15, 2026 at 6:35 PM
That would be a great thing to measure.
September 15, 2026 at 6:31 PM
Measuring sloppiness sounds like the next reality IQ test for developers and engineers
September 15, 2026 at 8:19 AM
It's time to filter contributors based on depth. We can eject such garbage PRs or issues at the initial point to avoid chaos.
September 14, 2026 at 10:46 PM
My notes are on Community Signals, to help maintainers and project owners see where contributors are heading, rather than ranking people.

I'd be grateful for your thoughts. Thank you for reading.

www.joshuapoddoku.com/community-si...
Community Signals | Joshua Poddoku
An automated read on how people on Bluesky and Hacker News are talking about AI-written code, from public posts matching a fixed set of phrases.
www.joshuapoddoku.com
September 14, 2026 at 8:45 PM
2/
• Low-effort AI PRs eating maintainer review time
• Projects closing the door, like libvips and Forgejo
• Unclear copyright on AI-written code
• Vibe coding and careful AI-assisted work treated as the same thing
September 14, 2026 at 8:45 PM
I think the only way forward is to measure the depth of the contributors shooting a PR. It is easier to sort at contributor level and not at issue/PR level.
September 14, 2026 at 8:19 PM
Much helpful for reviews. Are there any guidelines that drupal is implementing or implemented to let contributors understand the impact of ai generated code?
September 14, 2026 at 8:13 PM
I think the contributors should now think a clear way to understand the differences: ai slop, ai assisted, ai generated, human led etc.
September 14, 2026 at 8:11 PM
@alishabarretto.bsky.social would love these!
September 14, 2026 at 7:37 PM
Cfbr; great to see you on @bsky.app let's talk about what you're building!

I'm active on two projects:

- Community Signals, an effort to visualize the AI-generated code effect ( www.joshuapoddoku.com/community-si... )

- Clansurf, a local infrastructure (hardware + community) www.clansurf.com
Community Signals | Joshua Poddoku
An automated read on how people on Bluesky and Hacker News are talking about AI-written code, from public posts matching a fixed set of phrases.
www.joshuapoddoku.com
September 14, 2026 at 7:25 AM
Local Open Source llms for the win! I've similar project coming up in the islands of East Africa and Southeast Asia. www.clansurf.com
The shop that closes at five
Local providers are invisible to the people nearby. A working paper on Clansurf: offline, community-governed nodes that help neighbours find each other.
www.clansurf.com
September 14, 2026 at 7:16 AM
Interesting insight! What do you think is the biggest drawback of this phenomenon?
September 14, 2026 at 7:14 AM
Thanks for sharing!
September 13, 2026 at 5:42 PM
No ways. But engineering can be human-led for better ROI and longevity.
September 13, 2026 at 5:41 PM
I have no comments. But generalizing what anyone has encountered is - simply weaponizing the fear of the community.
September 13, 2026 at 3:00 PM