Memory hook: Visibility invites participation; a license defines reuse.
Must remember
Open source combines source availability with a license granting specified rights and obligations. A public repository without an explicit license does not automatically grant broad reuse rights. Read license terms and contribution guidance, especially when combining dependencies or redistributing modifications.
Contribute by improving documentation, reporting reproducible bugs, reviewing or submitting focused changes. Read existing discussions/issues first and respect maintainers' process. A fork supports independent work and upstream proposals; a template starts a new project from a scaffold. Discoverability improves with useful descriptions, topics, README content and maintained documentation.
InnerSource applies open collaboration practices within an organization. Shared ownership, clear contribution rules and transparent review can reduce silos while the code remains private. It does not require publishing confidential material or removing access controls.
GitHub Sponsors supports eligible maintainers financially. Following people/organizations helps discover their public activity; watching a repository subscribes to selected notifications. Stars express interest and help discovery but are not an assurance of quality or security.
Marketplace helps discover integrations and reusable actions. Evaluate maintainer trust, source code, permissions, update history and license before adoption. Installation or use can grant meaningful access. Community health includes clear support boundaries, respectful conduct and realistic maintenance expectations, not only download or star totals.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Collaborate openly inside the company | InnerSource with appropriate access controls. |
| Help maintain a project without writing a feature | Documentation, reproduction, review or supported sponsorship. |
| Adopt a Marketplace action | Review trust, code, permissions and version before use. |
Traps
- Public visibility is not a substitute for a license.
- Popularity is not a security review.
Active recall
1. What makes InnerSource different from public open source?
The collaboration principles can be shared while access remains internal.
2. Why read CONTRIBUTING first?
To align proposals with the maintainers’ workflow and expectations.
3. What is Sponsors for?
Financial support for eligible maintainers/projects.
4. Follow versus watch?
People/organization activity versus repository notifications.
5. What should be reviewed before installing an integration?
Its requested access, trustworthiness, maintenance and actual need.
Sources
- get-started · exploring-projects-on-github · contributing-to-open-source
- repositories · managing-your-repositorys-settings-and-features · customizing-your-repository · licensing-a-repository
- sponsors · getting-started-with-github-sponsors · about-github-sponsors
- apps · using-github-apps · about-using-github-apps