What is open source contribution?
- Author
- CRYPTO PORT Editorial
- Published
- Updated
- Reading time
- 4 min
In short
Contributing to open source means proposing fixes or improvements to publicly available code and having them merged. Nearly all crypto infrastructure is built this way, and translation or documentation counts just as much as code. The fact that every change is recorded with its author is a large part of what makes this field verifiable at all.
Key points
- Proposing fixes and improvements to public code
- Translation, docs and tests count as much as code
- Every change is recorded with its author
- Maintainers decide what gets merged
Definition
The practice of proposing changes or new features to publicly available source code and having maintainers review and merge them, including bug reports and documentation work.
Crypto software assumes anyone can read it. Beyond reading, there is a mechanism for anyone who finds a problem to propose the fix — that is open source contribution. In practice you submit a diff, and a maintainer reviews it and decides whether to merge.
Contribution is not limited to code. Correcting documentation, translating it, adding tests, or filing a bug report with clear reproduction steps all help real development substantially. The difficulty varies enormously, and plenty of people's first contribution was a typo fix.
For users, the value is the record. Looking at a project's repository shows when each change was made, by whom, and what discussion preceded it. The same place also reveals when updates have stalled for a long time, or when only one person ever commits.
Watch out for
- · Public code is not the same as safe code
- · Verify the source — lookalike repositories distribute malicious builds
- · Commit counts alone are a poor measure of project health