Explore the GitHub Community Study Guide — GH-900

Explore the GitHub Community

This domain (10% of GH-900, roughly 6–8 scored items on a ~60-question exam) tests whether you understand GitHub as a social and open-source platform, not just a Git host. Expect scenario questions that ask you to pick the right community mechanism for a stated goal: funding a maintainer, staying informed about a project, reusing code inside a company, distributing a tool to other GitHub users, or lowering the barrier for outside contributors. The questions are conceptual — almost no CLI, no YAML syntax beyond recognizing a file name — but they are precise about which feature does what (star vs. watch vs. follow), who can use what (internal repositories require an enterprise account), and what each artifact costs or includes (Marketplace Actions are free; Sponsors takes no fee from personal-account sponsorships).

Benefits of Open Source and GitHub Sponsors

What "open source" means on the exam

Open source software is distributed with a license that grants anyone the right to use, study, modify, and redistribute the source. The Open Source Initiative (OSI) maintains the canonical definition and approves licenses. Exam-relevant benefits:

Costs/risks the exam may probe: maintainer burnout, unfunded maintenance, license compliance obligations, no guaranteed SLA/support, and security of dependencies.

Licensing — the part people get wrong

A public repository without a LICENSE file is still under exclusive copyright ("all rights reserved"). GitHub's Terms of Service allow others to view and fork it on GitHub, but not to modify, reuse, or redistribute it. "Public" ≠ "open source." Use choosealicense.com or the license picker in the GitHub web UI (Add file → Create new file → name it LICENSE → choose a template).

GitHub Sponsors

GitHub Sponsors lets people and companies fund the developers and organizations whose open-source work they depend on, paid through the sponsor's existing GitHub billing.

Key facts:

• Both personal accounts and organizations can be sponsored; both can also be sponsors.
• Payment models: recurring monthly sponsorships and one-time payments. Maintainers publish tiers (a small fixed number per frequency, up to 10 each) with optional custom amounts and rewards (e.g., logo in README, priority issue triage, early builds).
• Fees: GitHub charges no fee on sponsorships from personal accounts — 100% goes to the maintainer. Organization-paid/invoiced sponsorships may incur payment-processing fees. GitHub does not take a platform cut.
• Eligibility: the account must join the GitHub Sponsors program, complete a sponsors profile, verify identity/tax information, enable two-factor authentication, and have a bank account in a supported region. Payouts run through Stripe Connect (or ACH/wire for some regions).
• Visibility: a sponsorship can be public (badge and listing on the sponsored profile) or private.
• Sponsor button: add a .github/FUNDING.yml file to a repository to render a Sponsor button on the repo header. It supports GitHub Sponsors usernames plus external platforms — Patreon, Open Collective, Ko-fi, Tidelift, Liberapay, IssueHunt, Buy Me a Coffee, and up to 4 custom URLs.
• The GitHub Sponsors Matching Fund (GitHub matching a maintainer's first-year sponsorships) was a launch-era program and is not a current guarantee — treat "GitHub doubles every donation" as a distractor.

Commonly confused funding/appreciation mechanisms:

Common traps

• Choosing "star the repository" when the requirement says financially support → the answer is GitHub Sponsors.
• Believing GitHub takes a percentage of personal sponsorships. It does not.
• Assuming only individuals can be sponsored — organizations can be sponsored too.
• Thinking a public repo is automatically open source; no LICENSE = all rights reserved.
• Confusing FUNDING.yml (Sponsor button) with CODEOWNERS (review routing) or SECURITY.md (vulnerability reporting).
• Selecting GPL when the requirement is "allow use in closed-source commercial products with a patent grant" → Apache-2.0.

Worked scenario: Your company depends on a small library maintained by one developer. Leadership wants to reduce the risk of the project being abandoned and wants the company's logo shown as a supporter. → Use GitHub Sponsors from the organization account, choosing a recurring monthly tier whose reward includes logo placement, and make the sponsorship public. Starring, watching, or forking does not address funding or attribution.