Surviving large online communities with conciseness and clarity
summary
Open Source communities (Apache Software Foundation example) rely on short, structured messages: a subject line, a one-sentence summary, and a body with links and a clear next action. Concrete tools include precise quoting, radiating intent, and self-contained messages plus diagrams and a reduced vocabulary (ASD‑STE100 style). Long debates commonly run 10–100 messages; investing ~10 extra minutes to edit a post can save ~5 minutes for each of 50 readers and steer discussions to lazy consensus, reducing friction and closing decisions.
AI-written summary · about
chapters (16)
- 0:00Introduction to community challenges
- 1:33Defining conciseness and clarity
- 3:01Writing for an audience
- 5:26Types of community conversations
- 7:14The work behind concise writing
- 9:40Multi-level decision points in messages
- 13:33Removing noise from writing
- 15:19Practicing with Twitter
- 16:02Simple vocabulary in documentation
- 17:04Self-contained messages
- 19:32Radiating intent in messages
- 21:17Precise quoting techniques
- 23:03Reworking questions for clarity
- 24:06Using diagrams effectively
- 24:48Key takeaways and conclusion
- 26:30Q&A session
related talks
28mBuilding Open Source Communities
17mScaling Community, Code, Contributors
26mBuilding Open Source Communities
30mHow you write matters in open source
15mOpen Source Protips from the Trenches
49mCommunities Over Code: How to Build a Successful Project
17mBuilding Open Source Communities with Tierney Cyren
15mLessons Learned from Cultivating Open Source Projects and Communities