8.2. How GitHub Supports Open-Source Projects
Beyond hosting the code, GitHub actively invests in making open-source projects easier to maintain and easier for newcomers to join.
💡 First Principle: GitHub supports open source through both product features and direct programs — community health files (README, CONTRIBUTING, CODE_OF_CONDUCT) that GitHub actively surfaces and checks for via the community standards checklist, sponsorship infrastructure (8.1) that funds maintainers, and broader initiatives that promote open-source visibility and best practices. The throughline is reducing friction: for maintainers to sustain their work, and for contributors to find and understand a project quickly.
⚠️ Exam Trap: GitHub's community health file checks (README, CONTRIBUTING, CODE_OF_CONDUCT, etc.) are a checklist against best practices, not a legal requirement — a repository can be missing every one of them and still function technically, it just becomes harder for contributors to engage with.
Reflection Question: A repository's community standards checklist shows several missing files. What's the practical, day-to-day consequence of leaving them missing, if there's no technical requirement to add them?
