aboutsummaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2020-05-24 14:23:36 -0400
committerMarcoFalke <falke.marco@gmail.com>2020-05-28 11:59:20 -0400
commitfacef3d4131f9980a4516282f11731361559509c (patch)
tree4a5d16ed625ed790f6fac0647c8bb8739f434343 /CONTRIBUTING.md
parentfae2fb2a196ee864e9a13fffc24a0279cd5d17e6 (diff)
doc: Explain that anyone can work on good first issues, move text to CONTRIBUTING.md
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a880182a6a..f34b1e1e15 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -39,6 +39,19 @@ unsure, you might want to leave a comment on the issue first.
You may also participate in the weekly
[Bitcoin Core PR Review Club](https://bitcoincore.reviews/) meeting.
+### Good First Issue Label
+
+The purpose of the `good first issue` label is to highlight which issues are
+suitable for a new contributor without a deep understanding of the codebase.
+
+However, good first issues can be solved by anyone. If they remain unsolved
+for a longer time, a frequent contributor might address them.
+
+You do not need to request permission to start working on an issue. However,
+you are encouraged to leave a comment if you are planning to work on it. This
+will help other contributors monitor which issues are actively being addressed
+and is also an effective way to request assistance if and when you need it.
+
Communication Channels
----------------------