Discovery: define the process for upload, download and installation of Transifex translations

Description

Acceptance Criteria

  • Talk to Ned about the current edx-platform process

  • Create a wiki design proposal for how the process should work

    • Decide how frequently translations should be uploaded and downloaded

    • For example, edx-platform uploads and downloads once a week as part of the release process

    • Define how the process should work in the short term (for Jerome)

      • e.g. The end result is new language resource files with the latest translations that are checked into the appropriate repos

    • Should it all be done manually, or can we write some scripts to automate some or all of the steps?

    • Define how the process should work in the longer term (if different)

    • Define how an app is configured to specify the languages that it supports

    • How does the App Store and Play Store know the specified languages?

    • Is there a benefit to having the strings live in a separate repo?

      • Could we share common strings across iOS and mobile so they only have to be translated twice

      • How do different whitelabel apps specify the languages they want (and those they don't want to include)

  • Create stories for any work needed, e.g. automation, new configuration settings etc

Useful Resources

Steps to Reproduce

None

Reason for Variance

None

Release Notes

None

Customer Problem Statement

None

Status

Assignee

Christopher Lee

Reporter

Andy Armstrong

Labels

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Sub-Team(s)

None

Reach

None

Impact

None

Open edX Discourse Thread

None

Story Points

5

Epic Link

Sprint

None

Priority

Unset
Configure