doc: Reword the Getting-Started section

Explain how to find good first issues to work on.

Also, remove the mention of up-for-grabs for new contributors, because
up-for-grabs is usually stuff that people lost interest in and is often
no longer relevant.
This commit is contained in:
MarcoFalke
2026-05-28 08:53:32 +02:00
parent fab5733f5d
commit fa51f37f18

View File

@@ -19,22 +19,16 @@ Getting Started
New contributors are very welcome and needed.
Reviewing and testing is highly valued and the most effective way you can contribute
as a new contributor. It also will teach you much more about the code and
process than opening pull requests. Please refer to the [peer review](#peer-review)
section below.
In-depth reviewing and testing are the bottleneck of the project, and are the
most effective way anyone can start to contribute. It will teach you much more
about the code and process than opening pull requests, and may help you uncover
related issues and follow-ups to contribute code for. Please refer to the [peer
review](#peer-review) section below.
Before you start contributing, familiarize yourself with the Bitcoin Core build
system and tests. Refer to the documentation in the repository on how to build
Bitcoin Core and how to run the unit tests, functional tests, and fuzz tests.
There are many open issues of varying difficulty waiting to be fixed.
If you're looking for somewhere to start contributing, check out the
changes that are
[up for grabs](https://github.com/bitcoin/bitcoin/issues?utf8=%E2%9C%93&q=label%3A%22Up+for+grabs%22).
Some of them might no longer be applicable. So if you are interested, but
unsure, you might want to leave a comment on the issue first.
You may also participate in the [Bitcoin Core PR Review Club](https://bitcoincore.reviews/).
Communication Channels