8.7. Reflection Checkpoint

Key Takeaways

• "Open source" is defined by an attached license, not by public visibility — a public repository with no license grants no reuse rights by default.
• GitHub supports open-source projects through community health file checklists and GitHub Sponsors funding, reducing friction for maintainers and contributors alike.
• Following is a lightweight activity signal in your feed; watching a repository produces specific, granular notifications — the two aren't interchangeable.
• The Marketplace hosts third-party Apps and Actions that extend GitHub, requiring the same permission scrutiny as any external integration.
• InnerSource borrows open source's collaboration practices for internal, proprietary code — it does not make that code open source or public.
• Forks stay connected to their upstream repository for contributing back; templates start a disconnected fresh history; topics and search drive discoverability of both.

Connecting Forward

With all seven syllabus domains covered, Phase 9 shifts from learning to test-day execution: pacing strategy, a condensed quick-reference for the concepts most likely to appear, and mixed-topic practice questions spanning every phase of this guide.

Self-Check Questions

• Why does the exam insist on separating "public" from "open source," when in casual conversation the two words are often used as synonyms?
• If InnerSource doesn't change a repository's license or public visibility, what tangible thing does it change inside an organization?