Community census: Understanding users & maintainer personas with a community survey
summary
The project runs a GitHub draft then a Google survey open for a month and collects about ~200 responses, giving concrete platform usage counts that confirm recent deprecations and highlight surprising pain points. Free‑text answers require heavy manual coding but reveal that documentation is the biggest task and that maintainer motivation is mostly intrinsic, leaving boring maintenance and outreach undone. Defines actionable maintainer personas—silent hero, helping hand, marketer, founder—and shows release voting, security fixes and technical debt as measurable sustainability signals.
AI-written summary · about
chapters (8)
- 0:00Introduction to open source villages
- 1:58My journey with Apache Cordova
- 3:45Running the community survey
- 8:06Motivation in open source work
- 8:28Maintainer personas overview
- 13:44Diverse roles in projects
- 14:27Assessing project sustainability
- 16:56Call to action for surveys and health checks
related talks
34mCommunity Data: What to Measure and Why?
36mMaintaining the maintainers: supporting open source tools
16mDoing Community Surveys for an Open Source Project
27mThese 4 questions will transform the way you think about the Ubuntu Community
48mJudging a book by its cover - how inclusive is your community?
43mBuilding Community - how to start and maintain a healthy and engaged community
43mBuilding and Supporting Open Source Communities Through Metrics
19mForm community programs to make your job easier