v29.4-roots.4 · Commit 5: [PATCH 05/37] product: establish Roots identity and Qt experience
CONTRIBUTING.md
Before: CONTRIBUTING.md · After: CONTRIBUTING.md
File metadata
index 25637b40aa9bc40ee0ebf5d423aa46dbbac21363..4efe2dc9c910794156f1f8ed0db962994fe2347a 100644
Download original patch · Release notes
Diff rows 1–51 of 51. Line numbers refer to the original before/after files.
+ Added− RemovedUnmarked lines are context.
Scroll the code area horizontally to read long lines. The two line-number columns refer to before and after.
CONTRIBUTING.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
|
-
Contributing to Bitcoin Core
|
|
2
|
-
============================
|
|
1
|
+
Contributing to Bitcoin Roots
|
|
2
|
+
=============================
|
|
3
3
|
|
|
4
|
-
The Bitcoin Core project operates an open contributor model where anyone is
|
|
4
|
+
The Bitcoin Roots project operates an open contributor model where anyone is
|
|
5
5
|
welcome to contribute towards development in the form of peer review, testing
|
|
6
6
|
and patches. This document explains the practical process and guidelines for
|
|
7
7
|
contributing.
|
|
8
8
|
|
|
9
|
-
First, in terms of structure, there is no particular concept of "Bitcoin Core
|
|
9
|
+
First, in terms of structure, there is no particular concept of "Bitcoin Roots
|
|
10
10
|
developers" in the sense of privileged people. Open source often naturally
|
|
11
11
|
revolves around a meritocracy where contributors earn trust from the developer
|
|
12
12
|
community over time. Nevertheless, some hierarchy is necessary for practical
|
|
@@ -24,9 +24,9 @@ as a new contributor. It also will teach you much more about the code and
|
|
|
24
24
|
process than opening pull requests. Please refer to the [peer review](#peer-review)
|
|
25
25
|
section below.
|
|
26
26
|
|
|
27
|
-
Before you start contributing, familiarize yourself with the Bitcoin Core build
|
|
28
|
-
system and tests. Refer to the documentation in the repository on how to build
|
|
29
|
-
Bitcoin Core and how to run the unit tests, functional tests, and fuzz tests.
|
|
27
|
+
Before you start contributing, familiarize yourself with the Bitcoin Roots build
|
|
28
|
+
system and tests. Refer to the documentation in this repository on how to build
|
|
29
|
+
Bitcoin Roots and run the unit tests, functional tests, and fuzz tests.
|
|
30
30
|
|
|
31
31
|
There are many open issues of varying difficulty waiting to be fixed.
|
|
32
32
|
If you're looking for somewhere to start contributing, check out the
|
|
@@ -54,7 +54,7 @@ and is also an effective way to request assistance if and when you need it.
|
|
|
54
54
|
Communication Channels
|
|
55
55
|
----------------------
|
|
56
56
|
|
|
57
|
-
Most communication about Bitcoin Core development happens on IRC, in the
|
|
57
|
+
Most communication about Bitcoin development happens on IRC, in the
|
|
58
58
|
`#bitcoin-core-dev` channel on Libera Chat. The easiest way to participate on IRC is
|
|
59
59
|
with the web client, [web.libera.chat](https://web.libera.chat/#bitcoin-core-dev). Chat
|
|
60
60
|
history logs can be found
|
|
@@ -289,12 +289,12 @@ workload on reviewing.
|
|
|
289
289
|
"Decision Making" Process
|
|
290
290
|
-------------------------
|
|
291
291
|
|
|
292
|
-
The following applies to code changes to the Bitcoin Core project (and related
|
|
292
|
+
The following applies to code changes to the Bitcoin Roots project (and related
|
|
293
293
|
projects such as libsecp256k1), and is not to be confused with overall Bitcoin
|
|
294
294
|
Network Protocol consensus changes.
|
|
295
295
|
|
|
296
|
-
Whether a pull request is merged into Bitcoin Core rests with the project merge
|
|
297
|
-
maintainers.
|
|
296
|
+
Whether a pull request is merged into Bitcoin Roots rests with the project merge
|
|
297
|
+
maintainers and ultimately the project lead.
|
|
298
298
|
|
|
299
299
|
Maintainers will take into consideration if a patch is in line with the general
|
|
300
300
|
principles of the project; meets the minimum standards for inclusion; and will
|