Update CONTRIBUTING.md #31872

pull Syed-AbdurRahaman2006 wants to merge 1 commits into bitcoin:master from Syed-AbdurRahaman2006:patch-2 changing 1 files +4 −4
  1. Syed-AbdurRahaman2006 commented at 7:08 PM on February 14, 2025: none

    in line number 11 i changed the sentence because it is overstructured sentence in normal content from this line to "Open source often naturally revolves around a meritocracy where contributors earn trust from the developer community over time." to this "In open source projects, contributors gradually earn trust from the developer community, forming a natural meritocracy."

    <!-- *** Please remove the following help text before submitting: *** Pull requests without a rationale and clear improvement may be closed immediately. GUI-related pull requests should be opened against https://github.com/bitcoin-core/gui first. See CONTRIBUTING.md -->

    <!-- Please provide clear motivation for your patch and explain how it improves Bitcoin Core user experience or Bitcoin Core developer experience significantly: * Any test improvements or new tests that improve coverage are always welcome. * All other changes should have accompanying unit tests (see `src/test/`) or functional tests (see `test/`). Contributors should note which tests cover modified code. If no tests exist for a region of modified code, new tests should accompany the change. * Bug fixes are most welcome when they come with steps to reproduce or an explanation of the potential issue as well as reasoning for the way the bug was fixed. * Features are welcome, but might be rejected due to design or scope issues. If a feature is based on a lot of dependencies, contributors should first consider building the system outside of Bitcoin Core, if possible. * Refactoring changes are only accepted if they are required for a feature or bug fix or otherwise improve developer experience significantly. For example, most "code style" refactoring changes require a thorough explanation why they are useful, what downsides they have and why they *significantly* improve developer experience or avoid serious programming bugs. Note that code style is often a subjective matter. Unless they are explicitly mentioned to be preferred in the [developer notes](/doc/developer-notes.md), stylistic code changes are usually rejected. -->

    <!-- Bitcoin Core has a thorough review process and even the most trivial change needs to pass a lot of eyes and requires non-zero or even substantial time effort to review. There is a huge lack of active reviewers on the project, so patches often sit for a long time. -->

  2. Update CONTRIBUTING.md
    in line number 11 i changed the sentence because it is overstructured sentence in normal content from this line to
    "Open source often naturally revolves around a meritocracy where contributors earn trust from the developer community over time." 
    to this "In open source projects, contributors gradually earn trust from the developer community, forming a natural meritocracy."
    59fb58c58b
  3. DrahtBot commented at 7:08 PM on February 14, 2025: contributor

    <!--e57a25ab6845829454e8d69fc972939a-->

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    <!--006a51241073e994b41acfe9ec718e94-->

    Code Coverage & Benchmarks

    For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/31872.

    <!--021abf342d371248e50ceaed478a90ca-->

    Reviews

    See the guideline for information on the review process. A summary of reviews will appear here.

  4. achow101 closed this on Feb 14, 2025

  5. in CONTRIBUTING.md:10 in 59fb58c58b
       6 | @@ -7,10 +7,10 @@ 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
      13 | -purposes. As such, there are repository maintainers who are responsible for
      14 | +developers" in the sense of privileged people.In open source projects, contributors
    


    jonatack commented at 7:12 PM on February 14, 2025:

    NACK. Not worth the change, and the patch is missing a space here.

  6. l0rinc commented at 7:37 PM on February 14, 2025: contributor

    @Syed-AbdurRahaman2006, please stop this random spam!


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 03:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me