Skip to content

Commit fa32ced

Browse files
author
MacroFake
committed
doc: Shorten explanation of "maintainers"
1 parent 59ac8ba commit fa32ced

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,9 @@ First, in terms of structure, there is no particular concept of "Bitcoin Core
1010
developers" in the sense of privileged people. Open source often naturally
1111
revolves around a meritocracy where contributors earn trust from the developer
1212
community over time. Nevertheless, some hierarchy is necessary for practical
13-
purposes. As such, there are repository "maintainers" who are responsible for
14-
merging pull requests, as well as a "lead maintainer" who is responsible for the
15-
[release cycle](/doc/release-process.md) as well as overall merging, moderation
16-
and appointment of maintainers.
13+
purposes. As such, there are repository maintainers who are responsible for
14+
merging pull requests, the [release cycle](/doc/release-process.md), and
15+
moderation.
1716

1817
Getting Started
1918
---------------
@@ -293,7 +292,7 @@ projects such as libsecp256k1), and is not to be confused with overall Bitcoin
293292
Network Protocol consensus changes.
294293

295294
Whether a pull request is merged into Bitcoin Core rests with the project merge
296-
maintainers and ultimately the project lead.
295+
maintainers.
297296

298297
Maintainers will take into consideration if a patch is in line with the general
299298
principles of the project; meets the minimum standards for inclusion; and will

0 commit comments

Comments
 (0)