Separate `translation-tools` repo where to put tools that can be shared by different translation projects

Open
#399 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation, tooling

Research direction

Start by reading the discussion from pull request #378 and the related comments on this issue. Determine which tools are shared across translation projects and whether placing them in a separate translation-tools repository is warranted, including the alternative of using _scripts. Done means the repository structure and ownership decision are documented.

Written by the indexing model from the issue text.

Description

Probably out of the scope of this PR, but eventually I think it might be useful to have a separate translation-tools repo where to put tools that can be shared by different translation projects.
If the tools are in a separate repo, it is also not necessary to create a hidden dir that is not easily discoverable (using _scripts might be a better option, unless it interferes with something).

Originally posted by @ezio-melotti in https://github.com/python/python-docs-zh-tw/pull/378#pullrequestreview-1294513688

Dominant language
Python
Stars
282
Forks
226
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/python-docs-zh-tw

All issues in python/python-docs-zh-tw

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.