Triaging Content Localization Issues

The Training Team manages content translations in the LearnWP Content – Localization GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. project board. This is where translations and feedback are passed between translators and reviewers before content is finally published on

Project board overview

Issues in this project board pass through 5 columns, or statuses, as progress is made.

General contributors do not have access to add/delete labels, or move issues between columns/statuses. Translation Coordinators need to check each issue and manually move them between statuses on behalf of contributors.

Column nameAwaiting TriageLooking for TranslatorTranslation in ProgressReview in ProgressPublished or Closed
Issue detailsLocalization issues initially land here when created from the Content Translation Template.Issues that were once started but have since been abandoned are moved here for a new translator to continue working on.Issues are being worked on by a Content Translator.Translations are waiting for a translation review.Completed issues.
Issues can move to the next column after…A Translation Coordinator has confirmed an issue isn’t spam, has added labels, and provided the translator with necessary access to Learn.A Content Translator has volunteered to continue working on the translation.A Content Translator has completed the translation of the piece of content.A reviewer has completed a translation review and the content has been published.
Next destination“Translation in Progress” column.“Translation in Progress” column.“Awaiting Review” column.“Published or Closed” column.

The project board also has filters created for each locale. These give an overview of all issues that have a locale label added to them.

Screenshot of the LearnWP Content - Localization GitHbu project board. The five statuses are highlighted red, and the filtered views for each locale are highlighted blue.

Labels and filtered views are created for new locales when the first GItHub issue is submitted for that locale. Translation Coordinators familiar with GitHub are welcome to make these. But if you’d like assistance, feel free to reach out to Faculty Administrators to create these on your behalf.

Top ↑

Triage tasks

Follow the steps below to triage issues in each status.

Top ↑

Issues in the “Awaiting Triage” column

  1. Confirm the issue is not spam.
    • If it is, press Close issue.
  2. Remove the Awaiting Triage label.
  3. Add each of the following labels:
    • [Locale] – such as [Locale] French, [Locale] Greek, etc.
    • [Content Type] – Course, Lesson Plan, Online Workshop, or Tutorial
  4. Assign the issue to the Content Translator – the issue submitter.
  5. Add the Content Translator to Learn WordPress and assign them content.
  6. Change the status of the issue to Translation in Progress.

The Training Team would like to make sure contributions from the Content Translator and Translation Reviewer are both recorded. However, due to GitHub access restriction, we are only able to assign issues to people who have commented on the issue first.

If a Translation Reviewer has been noted in the issue, follow these steps:

  1. Remove the Needs Translation Reviewer label.
  2. Ask the reviewer to comment on the GitHub issue.
  3. Once they have commented, assign the reviewer to the issue along with the Content Translator, who should already be assigned.

Top ↑

Issues in the “Looking for Translator” column

Issues here were once started by a content translator, but have since been released for other people to work on. Look at the most recent activity on the issue to decide how to proceed.

  • If a contributor has recently volunteered to continue working on the translation, then:
    1. Add the Content Translator to Learn WordPress and assign them content.
    2. Change the status of the issue to Translation in Progress.
  • If no contributor has volunteered to working on the issue, then reach out in the following ways to find a translator:
    1. See if there is other content translated into that locale, either by looking through GitHub issues with that locale’s label, or looking through published content on Learn WordPress. Reach out to translators who have translated in the past and see if they would be interested in working on this piece of content.
    2. If that locale has a Translation Coordinator, reach out to them and see if they know anyone who could translate the content.
    3. If there is no Translation Coordinator for that locale, then you can reach out to the Locale Manager of that language and ask them who they think might be interested/available to help out.
      • The Locale Managers role is a Polyglots team role. Each locale’s managers can be found by clicking on the respective “View Team Page” link from this list of Translation Teams.

When reaching out to Locale Managers, it’s a good idea to do so in the #polyglots Slack channel or on the Polyglots team blog. This keeps the conversation public, and others interested in helping out will be able to jump in, too.

Top ↑

Issues in the “Translation in Progress” column

Generally, two weeks is a good amount of time for a contributor to translate a piece of content. If it has been more than two weeks since the last message in the GitHub issue, then feel free to @-mention the Content Translator and ask them for an update.

Once a Content Translator says their translation is complete, follow these steps:

  1. Confirm the translation is viewable to everyone.
    • If the translation is in a Google Doc, make sure the visibility is set to “public”. Ask the translator to change it if it isn’t.
    • If the translation was made directly on Learn WordPress, then create a public preview link and paste that in the GitHub issue as a comment.
    • Translation may also be attached to the issue directly.
  2. Change the status of the issue to Review in Progress.
  3. Notify the Translation Reviewer that the translation is ready to be reviewed.

If no progress has been made on a translation, and the assigned Content Translator hasn’t responded to a request for update for an additional two weeks, follow these steps:

  1. See if a part-way translation has been shared on the issue.
  2. If no part-way translation is shared, then leave a comment on the issue and press Close with comment.
    • Example comment: “It seems no progress has been made on this issue for some time. I’ll close this issue for now, but feel free to reopen the issue if you would like to continue working on it.”
  3. If a part-way translation is shared, then:
    1. Leave a comment notifying you’re opening this translation up for another translator to work on.
    2. Remove the current assignee on the issue.
    3. Change status to Looking for Translator.

Top ↑

Issues in the “Review in Progress” column

Generally, two weeks is a good amount of time for a contributor to review a piece of content. If it has been more than two weeks since the last message in the GitHub issue, then feel free to @-mention the Translation Reviewer and ask them for an update.

Once a Translation Reviewer says their review is complete, and the Content Translator has applied any feedback, follow these steps:

  1. Follow Publishing Translated Content and publish the content.
  2. Add a comment to the issue thanking contributors, and linking to the published content. Press Close with comment.

Top ↑

Issues in the “Published or Closed” column

These issues have been closed and do not need to be triaged.

Last updated: