tc39 / tc39/tc39.github.io

(Metabug) Localization of core documents

Open
#226 0 comments 0 reactions 1 assignee View on GitHub

@chicoxyzzy is already working on this.

Since Dec 3, 2020.

content
Dominant language
HTML
Stars
336
Forks
63
Avg merge
12h
Merged PRs (30d)
8

Description

This bug tracks smaller pieces of work that break off of #218. The languages are currently based on who we have that can do the work. If you would like to propose a language please do so. The list we currently have for localization is:

Russian

  • Process document -- probably delay this as there will be a couple more changes over the next months
  • Code of Conduct
  • Jory's "how to participate" document or Allen's "patterns for participation"
  • agenda topic rules (to be linked from the agenda, as this doesn't change much)
  • README of How-We-Work, with a prioritization of which documents need translations. I would propose that "how to champion", "how to give helpful feedback", and "how to write an explainer" be the first ones. Last one will be terminology as that one changes the most.

German

  • Process document -- probably delay this as there will be a couple more changes over the next months
  • Code of Conduct
  • Jory's "how to participate" document or Allen's "patterns for participation"
  • agenda topic rules (to be linked from the agenda, as this doesn't change much)
  • README of How-We-Work, with a prioritization of which documents need translations. I would propose that "how to champion", "how to give helpful feedback", and "how to write an explainer" be the first ones. Last one will be terminology as that one changes the most.

Chinese - Simplified

  • Process document -- probably delay this as there will be a couple more changes over the next months
  • Code of Conduct
  • Jory's "how to participate" document or Allen's "patterns for participation"
  • agenda topic rules (to be linked from the agenda, as this doesn't change much)
  • README of How-We-Work, with a prioritization of which documents need translations. I would propose that "how to champion", "how to give helpful feedback", and "how to write an explainer" be the first ones. Last one will be terminology as that one changes the most.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.