What's changed: Expanded content (added diagrams)
6.1Contributing to Open Source
Open source (OSS) is a development philosophy of publishing source so anyone can use, modify, and redistribute it. People worldwide can review, use, and contribute—boosting transparency, reuse, and learning.
■ Forms of contribution and how to proceed Contribution is not only code: docs, bug reports, translations, reviews, and design all count. Code contributions generally follow fork → change on a branch → Pull Request (see the forking flow in the previous chapter). First-time contributors can start with approachable tasks labeled "good first issue".
■ Conventional project files
• README.md = overview and usage.
• CONTRIBUTING.md = how to contribute.
• CODE_OF_CONDUCT.md = expected behavior for participants.
• LICENSE = terms for use, modification, and redistribution.
Licenses range from permissive (MIT, Apache 2.0—Apache adds a patent grant) to copyleft (GPL, which requires derivatives to use the same license). Note that a public repo with no license defaults to "all rights reserved," so others cannot freely use it.
■ A good bug report Include steps to reproduce, expected result, actual result, and environment info (OS/version) so maintainers can reproduce and pinpoint the issue. Following an issue template/form prevents missing information. Be careful not to paste secrets or tokens.
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. Which file conventionally documents how to contribute?
Q2. How is the GPL license categorized?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.

