This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
openchain:spec-translations [2017/07/18 07:16] mgisi |
openchain:spec-translations [2017/07/19 04:59] mgisi [Translation Checklist] |
||
---|---|---|---|
Line 30: | Line 30: | ||
- 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. | - 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. | ||
- Obtain names of maintainer and reviewer(s). Add them to the translation page listing for the given language | - Obtain names of maintainer and reviewer(s). Add them to the translation page listing for the given language | ||
+ | - 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 | ||
- Maintainer obtains a MS Word or ODT copy of the English version to facilitate the translation: | - Maintainer obtains a MS Word or ODT copy of the English version to facilitate the translation: | ||
- | * {{:openchain:OpenChainSpec-1.1.TranslationTemplate.docx | MS Word Version 1.1 (current)}} | + | * {{:openchain:OpenChainSpec-1.1.TranslationTemplate.docx | MS Word Version 1.1}} |
- | * ODT Version 1.1 (current) - to be created. | + | * {{:openchain:openchain-odt-template.odt |ODT Template}} |
- | - Create a github repository and assign maintainer admin access. If you are not similar 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. | + | - 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 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. | * The maintainer should include a License file should be the same as the version of the English spec being translated. | ||
- | - Direct all translation related discussions to the specification mailing list. Maintainer and reviewer will need to join this list. | ||
- | * Openchain-specification@lists.linuxfoundation.org | ||
- Submit final version for review in pdf format to the specification mailing list for review. This review is largely about the formatting. | - 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 3: “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.” | * The following disclaimer must be included in English and the translated language above the copyright and license notices found on page 3: “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.” | ||
- 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. | - 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. | ||
- | - Receive the sign offs. | + | - Obtain sign offs from maintainer and reviewer(s). |
- Post translated pdf version to the OpenChain Translation web page. It should also be stored in the github repo. | - Post translated pdf version to the OpenChain Translation web page. It should also be stored in the github repo. | ||
- Announce the availability of the translated version on the main OpenChain mailing list | - Announce the availability of the translated version on the main OpenChain mailing list |