Skip to content

doc: Updated notes on how to contribute to Bitcoin Knots. - #314

Open
pdath wants to merge 2 commits into
bitcoinknots:29.x-knotsfrom
pdath:doc-contributing
Open

doc: Updated notes on how to contribute to Bitcoin Knots.#314
pdath wants to merge 2 commits into
bitcoinknots:29.x-knotsfrom
pdath:doc-contributing

Conversation

@pdath

@pdath pdath commented Jun 16, 2026

Copy link
Copy Markdown

The current documentation on how to contribute to Bitcoin Knots contains outdated and incorrect information. This makes it difficult for new contributors to assist, as it leads them in directions away from what is required.

I have updated the documentation regarding current communication methods, fixed many links that pointed to Bitcoin Core instead of Bitcoin Knots, and removed irrelevant documentation.

Comment thread CONTRIBUTING.md Outdated
@pdath
pdath force-pushed the doc-contributing branch from f0cc9b2 to b278e30 Compare July 2, 2026 10:27
Comment thread CONTRIBUTING.md Outdated
@pdath
pdath force-pushed the doc-contributing branch from b278e30 to afcc758 Compare July 2, 2026 10:38

@Retropex Retropex left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK afcc758fd375def1604e8afc4493fd09d14bf1fd

Comment thread CONTRIBUTING.md Outdated
@kwsantiago

Copy link
Copy Markdown

For full consistency with the comms-channel update in this PR (IRC + mailing list -> Discord), several later references still point contributors to IRC and the mailing list, which Knots no longer uses:

  • L322: "spread out over GitHub, mailing list and IRC discussions)."
  • L369: "discussed extensively on the mailing list and IRC, ..."
  • L391: "Then ask e.g. on IRC if someone could give ..."
  • L399: "if all else fails, ask on IRC or elsewhere ..."

Suggest updating these to Discord (and dropping "mailing list") so the whole document points to the same channel.

@pdath
pdath force-pushed the doc-contributing branch from afcc758 to 42cc637 Compare July 3, 2026 04:04
@pdath

pdath commented Jul 3, 2026

Copy link
Copy Markdown
Author

Thank you for your feedback. I have replaced the IRC references with Discord.

@pdath
pdath force-pushed the doc-contributing branch from 42cc637 to 6dd81c5 Compare July 3, 2026 04:23

@kwsantiago kwsantiago left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 6dd81c5

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md
Comment thread CONTRIBUTING.md Outdated
@pdath
pdath requested a review from luke-jr July 19, 2026 09:55
Comment thread CONTRIBUTING.md Outdated
@pdath
pdath force-pushed the doc-contributing branch from ab0fb5e to fdf2dc2 Compare July 27, 2026 01:32
Comment thread CONTRIBUTING.md Outdated

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates CONTRIBUTING.md to better reflect current Bitcoin Knots contribution and communication practices, replacing outdated Bitcoin Core references and removing guidance that no longer applies to this repository.

Changes:

  • Replaces several “Bitcoin Core” references/links with “Bitcoin Knots” equivalents (including issue links and translation process link).
  • Updates contributor communication guidance to point to the Bitcoin Knots Discord.
  • Simplifies repository guidance and adjusts the rebasing instructions.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md
Comment on lines 351 to 353
Where a patch set proposes to change the Bitcoin consensus, it must have been
discussed extensively on the mailing list and IRC, be accompanied by a widely
discussed extensively on Discord, be accompanied by a widely
discussed BIP and have a generally widely perceived technical consensus of being

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I lack the knowledge to update the documentation around a consensus change. It is such a large subject. BIP110 has challenged my own internal thoughts around how a consensus change should and could be made.

Generally, you would hope a consensus-level change would involve the users of Bitcoin and the developers of multiple node software implementations, each discussing the change using their own preferences, which could involve Discord groups, mailing lists, YouTube "shows", X, social media in general, etc.

This is more of an essay topic.

Can you chat with a CoPilot reviewer and get feedback, or is it only one way?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These reviews seem to be one-way.

@pdath
pdath force-pushed the doc-contributing branch from 164ffe2 to e342130 Compare July 28, 2026 04:21
@delcin-raj

Copy link
Copy Markdown

ACK

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
@pdath
pdath force-pushed the doc-contributing branch 2 times, most recently from 287a85c to 27b2fbf Compare August 4, 2026 06:00
Comment thread CONTRIBUTING.md Outdated
@pdath
pdath force-pushed the doc-contributing branch from 27b2fbf to dd62fc7 Compare August 4, 2026 09:04
Comment thread CONTRIBUTING.md Outdated
@pdath
pdath force-pushed the doc-contributing branch from dd62fc7 to 1123cf1 Compare August 4, 2026 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants