Panel: How to ensure the Git community is...
summary
Git relies on paid programs like Google Summer of Code and Outreachy to onboard contributors, sees a rough time-to-merge ~1 month median but an anecdotal range from one week to 11 years, and admits it currently lacks good metrics. Roadmap items include making a SHA-256 default and shipping a pluggable object database and refbackend, while borrowing UX ideas from JJ and git-history (commands like history drop/reword/split). Nontechnical hires (tech writers, CLI UX designers) and localized hackathons are proposed to improve docs, onboarding and retention.
AI-written summary · about
chapters (14)
- 0:00Git community health panel
- 1:08Attracting new Git contributors
- 5:03Merge time for Git contributions
- 8:56Keeping contributors engaged
- 12:23Non-technical roles in Git
- 15:09Improving Git’s user experience
- 19:43Git 3.0 future and breaking changes
- 23:15Git performance improvements
- 26:42Monorepos vs submodules
- 29:11Will Git survive another 20 years
- 30:35Should Git be opinionated
- 32:20Value of Git commit messages
- 35:09Commit messages in GitLab/GitHub
- 43:14Q&A
related talks
24mBridging the Gap: Encouraging African Talent to Open Source
37mYou Don't Need More New Contributors — You Need Onboarding That Actually Works
28mLet Me In: Open the Doors of your Organization for Student Contributors
35mPanel Discussion: CNCF Mentees
30mOpen Source Beyond Software
53mCan we optimize communities
44mBuilding On-Ramps for Non-Code Contributors in Open Source
40mBridging the Gap: Mentorship Programs for Your Open Source Journey