The 10 Commandments of Community Organizing
summary
Launched a nonprofit that attracts ~300 people to the kickoff, runs a CoderDojo chapter and an 11-month Coding in Cocktails curriculum teaching HTML/JS and version control, and adds mastery badges to push kids from Scratch into real coding. Uses Trello for task tracking, Calendly for scheduling, Slack for quick syncs, and GitHub Pages for demos. Delegating leadership grows event attendance ~50%. Operational rules: confirm the venue thrice, arrive one hour early, staff a chaos lead, feed volunteers, run retrospectives and act on the data.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:26Women in Technology
- 3:50Why do communities matter
- 5:25The 10 Commandments
- 10:25Setting Boundaries
- 11:27Own Your Calendar
- 15:03Build Your Network
- 19:12When to Slack
- 21:06Check in with Team
- 21:51Manage Expectations
- 24:17Volunteer Organizations
- 27:22Do Not Make Your Volunteers Heard
- 32:29Plan is Fire
- 33:53Work with Venues
- 36:38Chaos Lead
- 37:54Process Improvement
related talks
29mThings You Learn Organizing Communities
15mBuilding Tech Communities: Lessons from a Decade of Experience
45mPanel on Building Communities
33mRe-growing a DevOps Community (in Boston)
47mHow to (Re)build Community in 10 Easy Steps—Post Pandemic
46mCommunity BOF
38mTracy Hinds & Catherine Lopez - SeattleJS Conference 2017
08mActivating a Clojure Community