Outdated references in docs/assisting-with-translations.md and docs/become-a-contributor.md
Summary
Both docs/assisting-with-translations.md and docs/become-a-contributor.md contain outdated references that mislead new contributors — including two broken URLs (HTTP 404) and a volunteer coordinator contact that has been invalid since June 2020.
I’m happy to submit a PR fixing these once maintainers confirm the preferred direction — particularly for the contact/ownership question (Q1 below).
Verification output (click to expand)
All HTTP status codes verified with curl -sI -L on 2026-04-23.
=== Verification timestamp: 2026-04-23 17:07:05 UTC ===
[1] Transifex legacy URL in become-a-contributor.md
https://www.transifex.com/projects/p/bitcoinorg/
Result: HTTP 404
[2] Transifex URL in assisting-with-translations.md
https://www.transifex.com/bitcoinorg/bitcoinorg/
Result: HTTP 404
[3] Current canonical Transifex URL (should work)
https://app.transifex.com/bitcoinorg/bitcoinorg/
Result: HTTP 405 (405 on HEAD = exists, accepts GET)
[4] Issue #3397 where Will Binns was removed
https://github.com/bitcoin-dot-org/bitcoin.org/issues/3397
Status: HTTP 200
Issues in docs/become-a-contributor.md
1. Will Binns listed as volunteer coordinator (in two places)
The file instructs new contributors to email [email protected] twice:
Alternatively, email volunteer coordinator Will Binns ([email protected]) with a short list of your interests and skills…
Help improve Bitcoin.org another way. Email volunteer coordinator Will Binns ([email protected])…
However, Will Binns was publicly removed as the site’s maintainer by @Cobra-Bitcoin in Issue #3397 (closed, June 24, 2020):
"I have removed Will Binns as the site's maintainer […] I'll be taking over the day-to-day activities on the site more actively from now on."
This doc has been directing new contributors to a coordinator who has had no official role on the project for nearly 6 years.
2. Transifex URL returns 404
The file links to:
https://www.transifex.com/projects/p/bitcoinorg/
Two reasons this URL is dead:
- The
/projects/p/<slug>/ format is legacy Transifex URL structure.
- Transifex migrated their web application domain from
www.transifex.com → app.transifex.com (Transifex announcement, 2023).
The current canonical URL is https://app.transifex.com/bitcoinorg/bitcoinorg/.
Issues in docs/assisting-with-translations.md
3. Transifex URLs use the old (now-404) domain
The file links to https://www.transifex.com/... in several places (e.g. https://www.transifex.com/bitcoinorg/bitcoinorg/). Per the domain migration cited above, the canonical location is now https://app.transifex.com/.
4. Deprecated Transifex CLI and API v2 instructions
The "Handling Translations on GitHub" section instructs contributors to run:
tx init
tx set --auto-remote https://www.transifex.com/bitcoinorg/bitcoinorg/
tx pull -a -s --skip
tx set --source -r bitcoinorg.bitcoinorg -l en translations/bitcoinorg.bitcoinorg/en.yml
tx push -s -t -f --skip --no-interactive
These commands use the legacy transifex-client (Python), which:
Transifex now ships a new CLI at github.com/transifex/cli with different command syntax and API v3-based config. The instructions currently in this doc will not work.
Proposed scope for a PR
A single PR touching both files could:
- Replace the two
[email protected] references in become-a-contributor.md with the correct current contact path (needs maintainer input — see Q1).
- Replace all
www.transifex.com/... URLs with app.transifex.com/... equivalents across both files.
- Rewrite the
tx CLI instructions to use the current Transifex CLI and API v3, or link to current Transifex documentation.
Questions for maintainers before opening a PR
- (Q1) Who is the correct current contact for volunteer coordination, since Will Binns has not been in that role since 2020? Or should contributors simply be directed to open an issue?
- (Q2) Is the Transifex project
bitcoinorg/bitcoinorg still the active translation project, or has it moved?
- (Q3) Should the CLI section for pushing/pulling translations be fully rewritten to use the new Transifex CLI, or removed in favor of linking to current Transifex documentation?
Happy to split this into two separate PRs (one per file) if preferred.
Evidence references
Outdated references in
docs/assisting-with-translations.mdanddocs/become-a-contributor.mdSummary
Both
docs/assisting-with-translations.mdanddocs/become-a-contributor.mdcontain outdated references that mislead new contributors — including two broken URLs (HTTP 404) and a volunteer coordinator contact that has been invalid since June 2020.I’m happy to submit a PR fixing these once maintainers confirm the preferred direction — particularly for the contact/ownership question (Q1 below).
Verification output (click to expand)
All HTTP status codes verified with
curl -sI -Lon 2026-04-23.Issues in
docs/become-a-contributor.md1. Will Binns listed as volunteer coordinator (in two places)
The file instructs new contributors to email
[email protected]twice:However, Will Binns was publicly removed as the site’s maintainer by @Cobra-Bitcoin in Issue #3397 (closed, June 24, 2020):
This doc has been directing new contributors to a coordinator who has had no official role on the project for nearly 6 years.
2. Transifex URL returns 404
The file links to:
Two reasons this URL is dead:
/projects/p/<slug>/format is legacy Transifex URL structure.www.transifex.com→app.transifex.com(Transifex announcement, 2023).The current canonical URL is
https://app.transifex.com/bitcoinorg/bitcoinorg/.Issues in
docs/assisting-with-translations.md3. Transifex URLs use the old (now-404) domain
The file links to
https://www.transifex.com/...in several places (e.g.https://www.transifex.com/bitcoinorg/bitcoinorg/). Per the domain migration cited above, the canonical location is nowhttps://app.transifex.com/.4. Deprecated Transifex CLI and API v2 instructions
The "Handling Translations on GitHub" section instructs contributors to run:
These commands use the legacy
transifex-client(Python), which:Transifex now ships a new CLI at github.com/transifex/cli with different command syntax and API v3-based config. The instructions currently in this doc will not work.
Proposed scope for a PR
A single PR touching both files could:
[email protected]references inbecome-a-contributor.mdwith the correct current contact path (needs maintainer input — see Q1).www.transifex.com/...URLs withapp.transifex.com/...equivalents across both files.txCLI instructions to use the current Transifex CLI and API v3, or link to current Transifex documentation.Questions for maintainers before opening a PR
bitcoinorg/bitcoinorgstill the active translation project, or has it moved?Happy to split this into two separate PRs (one per file) if preferred.
Evidence references
www→app): https://help.transifex.com/en/articles/7171815-web-application-s-domain-change