Building and maintaining a healthy community
summary
Explains how a large open project scales by splitting into task forces, setting clear scopes and dependencies, and using multiple channels (IRC, phone apps, Discourse) to reduce noise and missed threads. Describes a rep/mentor/council ladder that vets leaders, budgets events, and resolves disputes through documented facts, discussion and reflection. Cites 800 active Majla contributors, an annual meetup of ~200 people, and teaching tools like Webmaker (Thimble, Popcorn, Appmaker) as concrete successes.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:16Who am I
- 1:39What is a community
- 2:32Technology or people
- 2:50Elements of a community
- 5:17Open communications
- 6:17Open tools
- 6:31Community manager
- 7:05Enable people
- 7:57Trust
- 8:30Value for listening
- 9:00Avoid ego
- 10:55Tools for communication
- 13:14Divide the community
- 19:21Code of Conduct
- 19:34Conflict Resolution
- 24:49Ugly Faces
- 27:30Mozilla Reps
- 31:39Mozilla Student Ambassador
- 32:04Mozilla Webmaker
- 34:49Makeup Artists
- 35:46Mozilla Hive
- 37:44Outro
related talks
52mMaintaining an Open Source project without burning out
30mHow to Drive Consensus & Transparency in OpenSource Communities
17mWelcoming People (and Other Hard Problems)
34mBreaking Out of the Open Source Burnout Cycle
39mRemoving Barriers
26mThis Meeting Is Better Than An Email: A Panel Discussion on Facilitating Great Meetings
33mListening to a Forest to Improve Project Health
49mPanel Discussion: Care and Feeding: Burnout and Self Care in our Community