Just as with the program code we should also act as good citizens of the open source community with the documentation. We should contribute back to the upstream documentation, especially where it's also relevant to us, and where we refer to or use the upstream documentation as a base.
By working upstream we can tap into the expertise of the larger community and contribute our part to maintaining a healthy overall ecosystem.
Some examples for contributing upstream:
- Fixing small issues such as typos and formatting we see in the upstream documentation while we work with it.
- Content we improve or write which also applies to Bitcoin.
- Documentation infrastructure such as the automated generation of RPC docs.
Just as with the program code we should also act as good citizens of the open source community with the documentation. We should contribute back to the upstream documentation, especially where it's also relevant to us, and where we refer to or use the upstream documentation as a base.
By working upstream we can tap into the expertise of the larger community and contribute our part to maintaining a healthy overall ecosystem.
Some examples for contributing upstream: