Contributor Retention and Participation Metrics in Bitcoin Core (Project Health Observability) #34330

issue Conrad8910 openend this issue on January 18, 2026
  1. Conrad8910 commented at 10:41 am on January 18, 2026: none

    Note: I’m approaching this from a research and analysis perspective rather than as a code contributor.

    This issue shares descriptive, non-normative metrics related to contributor retention and participation patterns in the Bitcoin Core repository, derived from publicly observable GitHub activity over time.

    Long-lived open-source projects commonly track indicators such as review latency, bus factor, CI reliability, and test coverage. Contributor retention and participation depth are complementary project-health signals, particularly for repositories with high review load and long-lived maintenance requirements.

    Recent longitudinal analysis of participation data suggests: A large fraction of historical participants become inactive within a year of their last recorded activity. Long-term active contributors represent a small fraction of total historical participants. High exit rates are observable even among contributors whose pull requests were frequently merged.

    These observations are purely descriptive and do not assert intent, motivation, or off-repository contribution. “Inactive” refers only to the absence of observable GitHub activity within a defined time window.

    This issue does not propose: Changes to Bitcoin Core policy or consensus rules Modifications to maintainership or decision authority Normative claims about how governance should function

    The purpose is limited to:

    1. Assessing whether retention and participation metrics are useful additions to existing project-health observability.
    2. Determining if existing tooling already captures these signals adequately, or if gaps exist.
    3. Enabling reproducible discussion around contributor lifecycle dynamics that may affect review capacity, onboarding, and long-term maintenance load.

    If this repository considers contributor retention metrics out of scope, that clarification would itself be useful for aligning expectations around which project-health signals are tracked here versus elsewhere.

    Methodology, assumptions, and raw aggregation logic can be shared or adjusted for comparison if helpful. Thank you.

  2. maflcko commented at 8:09 am on January 19, 2026: member

    Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

    Meta tracking of meta metrics seems ideal to do elsewhere.

    There is https://groups.google.com/g/bitcoindev, or https://delvingbitcoin.org/, or any other place that you feel is well suited.

  3. maflcko closed this on Jan 19, 2026

  4. maflcko commented at 11:03 am on January 19, 2026: member

    Also, looking at the LFX retention metric, it seems mostly stable over the last decade, and at least this (highly volatile) metric did not seem to worsen over the timespan.

  5. Conrad8910 commented at 8:37 pm on January 20, 2026: none

    Thanks for the clarification and for the pointer to LFX Insights.

    Understood that contributor retention and participation metrics are considered out of scope for the Bitcoin Core issue tracker and better discussed in other venues such as bitcoin-dev or Delving Bitcoin.

    I’ll take the discussion there. Appreciate the reference to existing retention dashboards.


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-01-27 06:13 UTC

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