Translations of the OpenChain Specification, Curriculum and other material is welcomed. We have a policy and process for official translations. Our goal is to balance accuracy while encouraging contribution.

The official English versions of the OpenChain Specification can be found here:

• Version 1.0
• Version 1.1
• Version 1.2 (current)

The official versions of the OpenChain Specification are always provided in PDF format to ensure fidelity. It is possible to get an editable version of the OpenChain Specification for translation. Lead contributors can obtain a MS Word version of the official English version from Mark.Gisi @ WindRiver (dot) com to serve as a template.

The OpenChain Curriculum and all other material is welcome to be translated. As per the OpenChain Specification, we prefer to have one official translation of each item, and we prefer to coordinate translations where possible. Please see below for the official OpenChain translation policy and process.

• There is one official translation for each language.
• All translations are based on the English version.
• Every translation has one maintainer selected by the OpenChain Project.
• Translations should be reviewed by two or more people to ensure integrity, accuracy and completeness.
• Both reviewers sign off on a translation to confirm it is complete.
• Translations are made under the terms of the license of the material being translated.
• Translation version numbers must correspond to the official English version it is based on.

1. Receive nomination to perform translation via the main OpenChain mailing list. If approved by the Specification Work Team Chair then precede to complete the remaining steps.
2. Obtain names of maintainer and reviewer(s). Add them to the translation page listing for the given language
3. Direct all translation related discussions to the specification mailing list. Maintainer and reviewer will need to join this list:
   • https://lists.linuxfoundation.org/mailman/listinfo/openchain-specification
4. Maintainer obtains a MS Word or ODT copy of the English version to facilitate the translation:
   • MS Word Version 1.1
   • ODT Template
5. Create a github repository and assign maintainer admin access. If you are not familiar with Github we will assist you in checking in your work product files and creating the additional required files prior to the release of the translation.
   • The maintainer should include a CONTRIBUTORS.md file in the top directory that lists all the contributors.
   • The maintainer should include a License file should be the same as the version of the English spec being translated.
6. Submit final version for review in pdf format to the specification mailing list for review. This review is largely about the formatting.
   • The following disclaimer must be included in English and the translated language above the copyright and license notices found on page 2: “This is an official translation from the OpenChain Project. It has been translated from the original English text. In the event there is confusion between this translation and the English version, The English text shall take precedence.”
7. Once the formatted version is approved: send maintainer and reviewers formal email sign off requests via the specification mailing list. This sign off is largely about ensuring the translation content accurately and completely represents the text found in the English version.
8. Obtain sign offs from maintainer and reviewer(s).
9. Post translated pdf version to the OpenChain Translation web page. It should also be stored in the github repo.
10. Announce the availability of the translated version on the main OpenChain mailing list

We currently have contributions underway from the following languages:

• Chinese:
  • Maintainer: Hung Chang, Harman
  • Contributor(s):
    • Jingze Li, Tilburg University
    • Navia Shen, Huawei
• German:
  • Maintainer: Catharina Maracke, Berkman Klein Center for Internet & Society at Harvard University
  • Contributor(s):
    • Miriam Ballhausen, Lumesse GmbH
• Italian
  • Maintainer: Carlo Piana, Array Law
  • Contributor(s):
    • Marco Ciurcina, Studio Légale
• Japanese:
  • Maintainer: Kunai Takashi
  • Contributor(s):
    • Takashi Egawa (NEC)
    • Masao Taniguchi (NEC)
    • Hiroyuki Fukuchi (Sony)
    • Nobuo Imada (Hitachi)
    • Mieko Sato (Linux Foundation)
  • Japanese Specification Repository
  • Japanese Curriculum Repository
• Korean:
  • Maintainer: Haksung Jang, LG
  • Contributor(s):
    • Jongbaek Park, BKL
  • Korean Specification Repository
  • Korean Curriculum Repository
• Polish:
  • Maintainer: Rafał Malujda, Rafal Malujda Law Office
• Portugese:
  • Maintainer: Bill Weinberg, Linux Pundit
• Spanish:
  • Maintainer: Malcolm Bain, ID Law Partners
  • Contributor(s):
    • Daniel German, University of Victoria