doc: Reword the Getting-Started section
What the developer wrote
Authored by MarcoFalke
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.
What changed, and why it matters
This commit only rewords the 'Getting Started' section in the project's CONTRIBUTING.md documentation. It removes a link to 'up for grabs' issues and adds guidance about finding good first issues. There are no code changes and no security relevance.
No security action needed. This is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to CONTRIBUTING.md, a contributor-facing documentation file. It rephrases advice for new contributors and removes a GitHub issues label link. No source code, build scripts, tests, or configuration files were modified.
Changed components
CONTRIBUTING.mdInspect captured patch +5 / −11
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 304055e5..0505b6b1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -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
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.