Panel Discussion: The 5 Ws and...
summary
Defines concrete entry steps: ask a manager for one hour to contribute, join or form starting groups, scan project issue lists for docs or triage tasks, and use GitHub Discussions or mailing lists rather than ephemeral Slack. Explains resolution practices — documented decision processes, mediator-led conversations, or agreeing to disagree — and cites a practical example: a company-run security vulnerability workshop that finds and fixes real bugs. Highlights payoffs: faster hiring pipelines, shared roadmaps, and measurable contributions that move projects forward.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04Benefits and challenges of open source participation
- 4:16Open source road maps
- 6:02Resolving conflicts
- 8:49Passion and conflict resolution
- 9:30Collaboration spaces
- 12:43Inclusivity in communities
- 13:24Why businesses should support open source
- 15:30Business value and networking
- 16:55Hiring through open source
- 18:21Getting involved in open source
- 20:05Security and steering groups
- 21:07Bidirectional support
- 21:28Closing remarks
related talks
45mPanel on Building Communities
46mDistributed teams that actually work
49mCommunities Over Code: How to Build a Successful Project
27mThese 4 questions will transform the way you think about the Ubuntu Community
39mCreating an Inclusive Community
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
19mForm community programs to make your job easier
43mBuilding Community - how to start and maintain a healthy and engaged community