Capstone 17 · Independent
The Contribution
Everything else here is code you own, where you set the standards. This is the opposite, and it demonstrates something no personal project can: that you can read an unfamiliar codebase, work within conventions you did not choose, and take review from a stranger without it going badly. Find a project you actually use. Read its contributing guide properly. Start by reproducing an open issue and commenting what you found, which is a genuine contribution and how maintainers learn your name. Then fix something small: documentation that is wrong, a test that is missing, an error message that is unhelpful. Then take on something real. Discuss the approach in the issue before writing the code, because a pull request nobody agreed to is usually a wasted week. Keep it small, explain what and why, and respond to review by changing the code rather than defending it. It may not be merged. Maintainers are busy and priorities change. Document the attempt honestly either way: what you tried, what the feedback was, what you learned. That is still worth showing.
Concepts used
Your dataset
Not applicable. The project is somebody else's.
Milestones
Your workspace
Build the full project here. Work through the milestones in order, in both languages.