Oh no Your project became really popular
summary
Project growth triggers concrete changes: set office hours once a month and timebox access, publish a donations/GitHub Sponsors page and list specific funded tasks, use stock response for legal or data requests instead of signing liability papers, recruit helpers with 2–6 months’ user experience for support, ask explicitly for roles like Spanish and Farsi translators, pursue fiscal sponsorship or in‑kind support (cloud credits, donated office for sprints) and form a small advisory board.
AI-written summary · about
chapters (11)
- 0:00Unexpected project growth
- 1:05Protecting your project
- 3:12Legal and business requests
- 5:41Time and expectations
- 8:52Ask for help early
- 12:25Financial and in-kind support
- 16:19Finding allies
- 18:03Project structure for growth
- 20:55Embracing growth paths
- 21:59Transparency importance
- 23:13Question and answer session
related talks
24mFlourishing FLOSS: Making Your Project Successful
42mBuilding On-Ramps for Non-Code Contributors in Open Source
30mFlourishing FLOSS: Making Your Project Successful
39mScaling an Open Source Sponsorship Program
29mFlourishing FLOSS: Making Your Project Successful
38mHow to bring open source to a closed community
51mBuilding Strong and Sustainable Open Source Projects
37mFund Projects and Change Company Culture with a FOSS Fund