Skip to content

Keeping tracker issues in this repo up to date

Jump to bottom
r12a edited this page Nov 20, 2018 · 1 revision

We track 3 types of issue:

  1. spec-related: These are discussions in the repo of another WG that are related to i18n. They may be comments we have made after a review (should have an i18n-comment label), or items/questions that the WG has come up with themselves and to which an 'i18n-tracking' label has been attached.

  2. info-requests: Requests to experts for information about how a script/language works. They are located in the lreq repositories, in general, but may occasionally have been raised in a WG repo, such as CSS.

  3. browser-bugs: Tracking bugs filed against browsers or issues with browser support. Not sure where the main issue should be lodged.

Following are steps to follow in order to ensure that we have tracker issues in the i18n-activity repo for all issues we are tracking. Usually done once a week, but could be done on daily basis too.

[1] Check the digests.

These arrive in your mailbox, but you can also find them at https://lists.w3.org/Archives/Public/public-i18n-core/ (weekly) https://lists.w3.org/Archives/Public/www-international/ (daily)

eg. Weekly github digest (Review comments) https://lists.w3.org/Archives/Public/public-i18n-core/2018OctDec/0033.html This lists changes to issues in other WG repos.

and

Weekly github digest (I18n repos) https://lists.w3.org/Archives/Public/public-i18n-core/2018OctDec/0032.html This lists changes to issues in our repos, including lreq repos.

[2] Raise new i18n tracker issues for each issue that's not in our tracker issue list.

You need to check for

  1. new issues, which should be listed explicitly, but also for
  2. issues that are not listed as new, but that have been labelled over the past week using the i18n-tracking label. This will involve checking in the i18n-activity repo (https://github.com/w3c/i18n-activity/issues) to see whether the tracker issue has already been raised.

When you find something that's not got an issue in our tracker repo, do the following:

  1. create a new issue in the i18n-tracker repo.
  2. copy the title of the WG issue in question to the title field of the new tracker issue.
  3. remove all text in the Write area of the tracker issue down to, but not including, "**This is a tracker issue..."
  4. paste the url for the WG issue in place of the text "link_to_issue_raised" - do not remove the § sign
  5. IF this is an issue from a WG repo:
  • add a label for the document/spec referred to. Most labels use the short name for the spec. (Note, however, that WhatWG html issues are labelled using the html label.) These labels have a light grey-green colour. (Ask r12a if you need a new label.)
  • If there's an i18n-?lreq label in the WG repo, add the equivalent to the tracker issue (eg. a WG issue with i18n-jlreq label would get a jlreq label in the tracker repo). Also add the label spec-type-issue.
  1. ELSE IF the issue is a question for layout groups:
  • add the type-info-request label (red background).
  • Then add label(s) for the appropriate layout groups. These labels have a violet colour, eg. alreq. (Do not use the labels with script names, such as devanagari.)
  • Finally, add a yellow label(s) to indicate a relevant typographic feature (eg. line-break).

[3] Make a note of closed issues

For issues that have been closed by a WG or lreq group, add the label Close? to the issue in the tracker repo. This signals that we should check whether to close the tracker issue.

Clone this wiki locally