Skip to content

Conversation

@aoeui21
Copy link

@aoeui21 aoeui21 commented Jun 10, 2025

While reading how to contribute to Bitcoin Knots, I've noticed some links in CONTRIBUTING.md are pointing to the Core's repository.

@pithosian
Copy link

pithosian commented Jun 11, 2025

Should we clean up other instances while we're at it?

https://github.com/search?q=repo%3Abitcoinknots%2Fbitcoin%20https%3A%2F%2Fgithub.com%2Fbitcoin%2Fbitcoin&type=code

Note that files are only listed once; there may be more instances inside each file which aren't listed in the search results directly. Not all of these should be updated, mind; for example, links to PRs and issues on the /bitcoin/bitcoin repo won't be changed.

With a quick skim of the search results, I think probably:

  • doc/fuzzing.md
  • doc/build-freebsd.md
  • doc/build-netbsd.md
  • doc/build-openbsd.md
  • doc/build-osx.md
  • doc/build-windows.md
  • doc/README_doxygen.md
  • doc/cjdns.md

If we want to direct bug reports here, also:

  • build_msvc/bitcoind/bitcoind.vcxproj
  • build_msvc/bitcoin_config.h.in
  • release notes

@littledino2112
Copy link

littledino2112 commented Jun 14, 2025

Before updating the doc, I think it might be beneficial to clean up the current issues list. I was looking for some good first issues to get started but almost all of them were created in 2024 with no updated status. Looks like some have been finished (e.g. this one) @luke-jr is probably too busy to take a look at them but since Knots is getting some more attention now, probably a good time to clean them up to encourage people to engage.

Comment on lines -33 to -35
[good first issue](https://github.com/bitcoin/bitcoin/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
[good first issue](https://github.com/bitcoinknots/bitcoin/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
list or changes that are
[up for grabs](https://github.com/bitcoin/bitcoin/issues?utf8=%E2%9C%93&q=label%3A%22Up+for+grabs%22).
Copy link
Collaborator

Choose a reason for hiding this comment

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

Core's lists aren't irrelevant - probably more issues there to address than here.

1. Commit patches

For GUI-related issues or pull requests, the https://github.com/bitcoin-core/gui repository should be used.
For all other issues and pull requests, the https://github.com/bitcoin/bitcoin node repository should be used.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Currently, it's recommended to open PRs to bitcoin/bitcoin when possible, and only on bitcoinknots/bitcoin when the PR is inherently exclusive to Knots.


Note that translations should not be submitted as pull requests. Please see
[Translation Process](https://github.com/bitcoin/bitcoin/blob/master/doc/translation_process.md)
[Translation Process](https://github.com/bitcoinknots/bitcoin/blob/master/doc/translation_process.md)
Copy link
Collaborator

Choose a reason for hiding this comment

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

We need to actually have a translation process first.

Core stole the Transifex repo, so the older process no longer works for us

@luke-jr
Copy link
Collaborator

luke-jr commented Jun 14, 2025

Before updating the doc, I think it might be beneficial to clean up the current issues list. I was looking for some good first issues to get started but almost all of them were created in 2024 with no updated status.

I think almost all remain unresolved?

Looks like some have been finished (e.g. #71)

While there's been some stopgap work to address the most pressing problems, I don't consider it resolved just yet.

@littledino2112
Copy link

Yes, almost all are unresolved. It'll be great if you can spend some time on triaging so people know what the highest priority issues are.

@Ataraxia009
Copy link

I agree with @luke-jr over here

aA direct replacement of bitcoin with bitcoink nots urls is not desirable since it is a little bit more nuanced.

Trying and outlining that it is a fork and cover the nuances here for now is best

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.

5 participants