How to get them to Commit?
summary
Open source contribution increases when projects show clear developer value: quick first PRs (the “alert hello world” immediate feedback), visible impact like Postman’s 20 million developers badge, and tidy GitHub repos with issue and PR templates, badges, releases and reviewer automation. Run events like Hacktoberfest and Google Summer of Code, publish contributor release notes, tag authors, offer swag and invites, and track early metrics so managers can justify resources and sustain contributor momentum.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:15Agenda
- 1:50Organizations
- 2:12Security Regulation
- 2:53Customer Experience
- 3:23Speed to Market
- 3:59Developer Experience
- 4:57Why Open Source
- 5:34Why Developers are Unique
- 6:22Learning New Tools
- 6:57Be Trusted
- 8:40Speak Their Language
- 8:58Messaging
- 10:16Postman
- 11:06Other buzzwords
- 11:54Make it simple
- 13:22Hacktoberfest
- 15:01GitHub
- 16:37Backstage
- 17:51Issues
- 18:27Reward Developers
- 19:50Recognition
- 22:55Everything is clear
- 23:17What makes it so tough
- 25:39How to increase developer productivity
- 28:07What type of open source project is it
related talks
10mDemystifying Contributing to Open Source
39mCommunity and Contributors Panel
35mBeyond Code: The Importance of Elevating Non-Code Contributions
27mNo Code Needed: From Emojis To Glory on the Contribution Ladder
38mHow to bring open source to a closed community
23mGet more people to participate in your project
14mBeyond the First PR: Why Contributors Stay in Open Source Communities
28mLet Me In: Open the Doors of your Organization for Student Contributors