Apache Way Panel: Software is Easy; People are Hard
summary
Panelists list concrete tactics: give up the keys by refusing to answer every question and handing work to others, code of conduct needs an enforcement plan, recruit from users and Stack Overflow rather than waiting, and reward noncode contributions like docs and design. Examples: Pony mail shows founders must shut up to let maintainers lead; the NCSA web server becoming Apache HTTP Server shows abandoned code can spark community. Apache incubator holds 59 projects and the Foundation has an Attic for retired projects.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:00Transition from a single dictator to sharing leadership with the community
- 6:00Giving up direction
- 9:05Being wrong
- 11:38Whos right
- 16:42Collaboration
- 17:09Dealing with people
- 17:36Code of Conduct
- 20:16Community over Code
- 29:01Step up
- 34:22Socialness
- 35:57Documentation
- 39:31Trapped
- 42:42Community
- 45:30Last advice
- 46:47Give permission
related talks
36mApacheCon@Home 2021: In conversation
48mPanel Discussion - Women In FOSS
45mPanel on Building Communities
40mPanel Debate Led by
42mPanel Discussion: It Takes a Village - The Case for a Versatile Open Source Workforce
49mPanel Discussion: Words Matter: Inclusive Language in Software, Open Source, & the Enterprise
49mPanel Discussion: Care and Feeding: Burnout and Self Care in our Community
40mPanel Discussion: Eliminating Common Barriers to Contribution for More Inclusive Communities