v30.3-roots.1 · Commit 5: [PATCH 05/68] feat(qt): preserve Roots identity and GUI support on Core 30.3
CONTRIBUTING.md
Before: CONTRIBUTING.md · After: CONTRIBUTING.md
File metadata
index 7f42f0be3aa69c74b8b666db19b7ecad85f5c438..83c77b594f974a491be5a77ea6235714f4600b73 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. Before is on the left; after is on the right. Unified view fits narrow screens more easily.
CONTRIBUTING.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
-
Contributing to Bitcoin Core
|
| 2 |
-
============================
|
| 3 |
|
| 4 |
-
The Bitcoin Core project operates an open contributor model where anyone is
|
| 5 |
welcome to contribute towards development in the form of peer review, testing
|
| 6 |
and patches. This document explains the practical process and guidelines for
|
| 7 |
contributing.
|
| 8 |
|
| 9 |
-
First, in terms of structure, there is no particular concept of "Bitcoin Core
|
| 10 |
developers" in the sense of privileged people. Open source often naturally
|
| 11 |
revolves around a meritocracy where contributors earn trust from the developer
|
| 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 |
process than opening pull requests. Please refer to the [peer review](#peer-review)
|
| 25 |
section below.
|
| 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.
|
| 30 |
|
| 31 |
There are many open issues of varying difficulty waiting to be fixed.
|
| 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 |
Communication Channels
|
| 55 |
----------------------
|
| 56 |
|
| 57 |
-
Most communication about Bitcoin Core development happens on IRC, in the
|
| 58 |
`#bitcoin-core-dev` channel on Libera Chat. The easiest way to participate on IRC is
|
| 59 |
with the web client, [web.libera.chat](https://web.libera.chat/#bitcoin-core-dev). Chat
|
| 60 |
history logs can be found
|
|
@@ -290,12 +290,12 @@ workload on reviewing.
|
|
| 290 |
"Decision Making" Process
|
| 291 |
-------------------------
|
| 292 |
|
| 293 |
-
The following applies to code changes to the Bitcoin Core project (and related
|
| 294 |
projects such as libsecp256k1), and is not to be confused with overall Bitcoin
|
| 295 |
Network Protocol consensus changes.
|
| 296 |
|
| 297 |
-
Whether a pull request is merged into Bitcoin Core rests with the project merge
|
| 298 |
-
maintainers.
|
| 299 |
|
| 300 |
Maintainers will take into consideration if a patch is in line with the general
|
| 301 |
principles of the project; meets the minimum standards for inclusion; and will
|
|
|
|
| 1 |
+
Contributing to Bitcoin Roots
|
| 2 |
+
=============================
|
| 3 |
|
| 4 |
+
The Bitcoin Roots project operates an open contributor model where anyone is
|
| 5 |
welcome to contribute towards development in the form of peer review, testing
|
| 6 |
and patches. This document explains the practical process and guidelines for
|
| 7 |
contributing.
|
| 8 |
|
| 9 |
+
First, in terms of structure, there is no particular concept of "Bitcoin Roots
|
| 10 |
developers" in the sense of privileged people. Open source often naturally
|
| 11 |
revolves around a meritocracy where contributors earn trust from the developer
|
| 12 |
community over time. Nevertheless, some hierarchy is necessary for practical
|
|
|
|
| 24 |
process than opening pull requests. Please refer to the [peer review](#peer-review)
|
| 25 |
section below.
|
| 26 |
|
| 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 |
|
| 31 |
There are many open issues of varying difficulty waiting to be fixed.
|
| 32 |
If you're looking for somewhere to start contributing, check out the
|
|
|
|
| 54 |
Communication Channels
|
| 55 |
----------------------
|
| 56 |
|
| 57 |
+
Most communication about Bitcoin development happens on IRC, in the
|
| 58 |
`#bitcoin-core-dev` channel on Libera Chat. The easiest way to participate on IRC is
|
| 59 |
with the web client, [web.libera.chat](https://web.libera.chat/#bitcoin-core-dev). Chat
|
| 60 |
history logs can be found
|
|
|
|
| 290 |
"Decision Making" Process
|
| 291 |
-------------------------
|
| 292 |
|
| 293 |
+
The following applies to code changes to the Bitcoin Roots project (and related
|
| 294 |
projects such as libsecp256k1), and is not to be confused with overall Bitcoin
|
| 295 |
Network Protocol consensus changes.
|
| 296 |
|
| 297 |
+
Whether a pull request is merged into Bitcoin Roots rests with the project merge
|
| 298 |
+
maintainers and ultimately the project lead.
|
| 299 |
|
| 300 |
Maintainers will take into consideration if a patch is in line with the general
|
| 301 |
principles of the project; meets the minimum standards for inclusion; and will
|