Fostering New Contributors In SWT: Lessons In Community Management
summary
SWT documents cleaning and process changes that produced concrete results: closed ~1,400 old bugs from a 2,500-ticket Linux backlog by adding a triage keyword and faster Bugzilla replies, made native builds and tests runnable in the IDE and on Maven (migrated tests to JUnit4, standardized on Eclipse formatter), enforced Gerrit review feedback and beginner guides, and reintroduced GTK3 support — outcome: four new contributors in 16 months and about 200 Linux bug fixes in 2016.
AI-written summary · about
chapters (13)
- 0:00Community management intro
- 1:30What community management means
- 5:25SWT’s decline and revival
- 6:55Bugzilla for new contributors
- 10:15Triaging old bug reports
- 16:51Mailing lists in SWT
- 19:20Patch reviews and feedback
- 23:22Code standards and reviews
- 26:14Documentation and wiki
- 28:46Balancing contributor needs
- 32:23Accessible builds and tests
- 37:49Results and growth
- 39:43Company vs community projects
related talks
27mWelcome & Community Roundup
27mThese 4 questions will transform the way you think about the Ubuntu Community
22mPanel Discussion: The 5 Ws and...
50mThe 7 biggest mistakes we made in 10 years of running a major open source project
39mMaintaining a big open source project: lessons learned
25mHow to Grow and Mentor an Open Source Community & Achieve Collaboration with Over 170...
48mJudging a book by its cover - how inclusive is your community?
49mCommunities Over Code: How to Build a Successful Project