Principles from leaders across the community
summary
Advocates making team principles explicit and aligned, with concrete practices: PR template: why then how to reduce mystery bugs, a buddy system pairing tickets (one implements, one ensures delivery), and “default to agreement” reviewers to improve relationships. Encouragement with a light touch appears as daily teach-and-share, book clubs, and allotted learning time. Community claims: no developer left behind, mentorship and clear RFC-driven goals; proposal for a centralized add-on issue hub and a project manager to prioritize stalled PRs.
AI-written summary · about
chapters (20)
- 0:00Introduction and background
- 1:47What are principles
- 3:55Principles vs rules
- 5:41Unprincipled vs principled behavior
- 7:09Principle in action: HTML5 rule of least power
- 8:39Community principles from Robert Jackson
- 10:49Consistency in PRs and teamwork
- 12:52Inclusivity in community
- 14:17Default to agreement principle
- 15:20Encouraging continuous learning
- 18:53Community principles at large
- 19:56No developer left behind
- 20:39Clear communication and goals
- 21:41Respecting other communities
- 22:02Productivity and performance
- 22:46Training and mentorship
- 23:08Diversity and inclusion
- 23:49Future principles for Ember community
- 25:20Education as a community principle
- 26:48Call to action and conclusion
related talks
31mScaling Happy Engineering Teams
21mLeading and Growing an Open Source Comunity
28mBuilding Open Source Communities
47mThe Case for Principle-Based Engineering Management
01h 00mImproving Your Team(work)
29mCreating a Code Review Culture
25mDeveloper Joy – How great teams get s%*t done
21mPeople First Leadership