Local Community Building
summary
Explains how to run day‑long Code Retreats (six 45‑minute iterations solving Conway's Game of Life with mandatory pair programming and a rule to delete the code after 45 minutes) and Rails Bugmashes (simple meetups to submit pull requests to Rails, use IRC help, and update docs). Describes organizing three events (Boulder Feb 2011, Fort Collins June 2011, Bangalore May 2011), getting sponsorships and catered lunch, that two people suffice, that one organiser got two Rails commits and a participant jumped from 10 to 170 commits.
AI-written summary · about
chapters (17)
- 0:00Start
- 4:01The Plan
- 4:59What is a Code Retreat?
- 5:37How does a Code Retreat work?
- 6:07What does Code Retreat look
- 9:08Code retreat facilitator's job
- 13:35How many people does it take to hav a successful Code Retreat?
- 15:16Rails Bug Mash
- 20:18Organizing a Bug Mash
- 21:20Organizing a Code Retreat
- 23:32Raising Sponsorships
- 27:07Main points from Dr. Nic's Keynote - Everyone should take an active role in their Ruby Club
- 28:13Why do I do it?
- 29:03Why? A personal experience
- 31:04What I like about Ruby
- 31:41Conference Organizers
- 36:49Resources
related talks
47mMentoring technical practices, what works and not
15mGrowing at Work with Community-oriented Development
32mBuild a Better PyCon My Annual Reflection
18mLearn / Share / Repeat
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why
37mHow to Create Development Opportunities Through the Organizational Communities
40mLightning Talks Day 2
35mClosing Keynote