PresidentDevDogs: Google Developer Group on Campus at UGA (Athens, GA)
DevDogs is the Google Developer Group on Campus at UGA, and everything we build is open source. When I joined the board, contributing here meant showing up already knowing the stack. Most of my time as an officer has gone into changing that. The club now runs on a weekly cycle the board adopted: every meeting holds one workshop per active project, each workshop closes by announcing the next feature on that project’s roadmap, and announcing it opens a week-long competition. Teams build on their own time and present at the next meeting, and the winning team’s pull request is the one that merges.
I joined the board as Technical Chair in May 2025, became Vice President that January, and have been President since May 2026. I set the technical direction that pulled our projects into one monorepo, four applications and eight shared packages on pnpm and Turborepo. That consolidation folded in the Optimal Schedule Builder, the work of 62 contributors, and retired the Community Resource Forum. I also wrote the contributor CLI, so getting from a clone to a running app is a handful of commands. I recruit, onboard, and mentor people through their first pull requests.
My largest technical contribution is DevDogs Platform, which I designed, built, and deployed almost entirely on my own. It is the club’s public site, officer console, documentation, and OAuth server, running on Cloudflare Workers through OpenNext. Three of our apps share one Postgres database, a schema each, and they reach the platform through its RPCs rather than through its tables, so a team gets features nobody on it had to build. Moderation is the clearest case: a contributor adds one foreign key column to their own table, and its rows become reportable with the report flow and the moderator queue already there.
Competing teams need a backend of their own and the club’s budget is extremely limited, so the platform provisions each team a free Supabase project through OAuth, fronts it with a Cloudflare Worker for a stable hostname, and wakes or pauses it around the competition.
Our CI holds no secrets at all. GitHub runs a pull request’s own workflow definition, and our contributors push branches to the repository rather than to forks, so anything the validation workflow can read is readable by whoever opened the PR. Everything needing a credential runs after the merge gate.