[OSPO Book] Keep Translations up to date: auto-create per-language issues on merged PRs to the English book

[fer-correa]

Area

Infra repo (automation, CI/CD, tooling)

Problem / Goal

• Problem: New chapters or updates merged into the English OSPO Book often lag in translation (pt-BR, es, ja, zh), creating inconsistency across languages.
• Proposal: Whenever a PR that adds/updates content in the English book is merged, create one tracking issue per supported language with the labels ospo-book and ospo-book-translations, referencing the triggering PR and outlining what needs translation. Assign the corresponding translation co-chairs per language - Translation Team.

Important note about AI/automation

• If GenAI-based translation automation is available, the only required step would be to directly open a translation PR per language with the correct reviewer assigned; the manual issues may become unnecessary.
• If no such automation is available, keep the per-language issue workflow described above.

Proposed change

On merge to main of a PR affecting the English book:

• An issue per language (pt-BR, es, ja, zh) is created - github action.
• Content: link to the triggering PR, list of changed files/sections, brief summary of the change, and guidance for translators.
• Assignees: co-chairs of each language translation team (see Translation Team link above).

Scope

• Applies to all merged PRs that add, revise, or remove content in the English book.
• Supported languages today: pt-BR, es, ja, zh. Can be extended later.

Labels to use

• ospo-book
• ospo-book-translations

Areas to cover

• Build config update
• PR preview environments
• Linters / link-check / spell-check
• i18n build pipeline
• Netlify
• Redirect
• Sitemap
• Image/font optimization
• Dependabot
• CODEOWNERS / branch protection
• Licensing

Acceptance criteria

• A repeatable process exists to create per-language translation issues on every merged English-content PR.
• For a pilot PR, the four issues (pt-BR, es, ja, zh) are created with correct labels, assignees, and a clear description.
• Translators and reviewers confirm the process is workable.

Links

No response

[alice-sowerby]

@fer-correa should we use this issue to capture the discussion about what translators think of using AI?