diff --git a/docs/HOWTO.html b/docs/HOWTO.html index d18b38f..a2119ab 100644 --- a/docs/HOWTO.html +++ b/docs/HOWTO.html @@ -1,9 +1,9 @@ - +
The table describes a set of scenarios, and provides a set of fairly detailed information about what to do given that scenario.
| Someone adds a *-tracker label to an issue in a WG repo. | +Someone adds a *-tracker label to an issue in a WG repo. |
Working with labels |
|---|---|---|
| A reviewer comes across an issue during a review and wants to raise it. | +A reviewer comes across an issue during a review and wants to raise it. |
Working with labels(See an i18n example of boilerplate for new issue.) |
| The HR group has reviewed & approved a new comment. | +The HR group has reviewed & approved a new comment. |
Working with labels |
| The HR group is satisfied by the resolution of an issue in the WG repo. | +The HR group is satisfied by the resolution of an issue in the WG repo. |
Working with labelsNote that no labels need to be changed or removed. Keeping the needs-resolution or tracker label may be useful later for post-mortems, or for issues that get reopened later, etc. |
| An issue that needs resolution in the WG repo is closed, but hasn't been closed in the HR repo. | +An issue that needs resolution in the WG repo is closed, but hasn't been closed in the HR repo. |
Working with labels |
| A tracker issue in the WG repo is closed, but hasn't been closed in the HR repo. | +A tracker issue in the WG repo is closed, but hasn't been closed in the HR repo. |
Working with labels |
| The spec WG wants to postpone resolution of an issue until the next version. | +The spec WG wants to postpone resolution of an issue until the next version. | If the HR group agrees:
Working with labels |
| The HR group decides to change a *-tracker label to *-needs-resolution. | +The HR group decides to change a *-tracker label to *-needs-resolution. |
|
| The HR group decides to change a *-needs-resolution issue to *-tracker. | +The HR group decides to change a *-needs-resolution issue to *-tracker. |
|
| The spec WG explicitly asks the HR group to provide specific advice for an issue. | +The spec WG explicitly asks the HR group to provide specific advice for an issue. | [Optional] This describes what the i18n HG does.
Working with labelsThere is no tooling at the moment to highlight such direct appeals for help, however, if the HR group is following their notifications and reading the new comments added to the WG repo they should spot these requests. |
| Someone in the HR group realises that an issue that has been labelled in a WG repo needs urgent attention. | +Someone in the HR group realises that an issue that has been labelled in a WG repo needs urgent attention. | [Optional] This describes what the i18n HG does.
Working with labels |
| The tooling created a tracker issue in the HR repo but there was no s:xxx label. This means that the issues don't show up in the 'board'. | +The tooling created a tracker issue in the HR repo but there was no s:xxx label. This means that the issues don't show up in the 'board'. | This sometimes happens because the tool fails to find the shortname for a repo like CSS that has many shortnames. It may also happen if the thing being tracked doesn't have a shortname, such as webex implementations, or CG documents that don't yet have shortnames.
Working with labels |
| A spec WG requests a transition call. | +A spec WG requests a transition call. |
The spec WG should have checked with the HR group that all issues with a *-needs-resolution label have been resolved, and each issue should describe that resolution. The spec WG does NOT need to reach agreement with the HR group for issues that are only marked with a *-tracker label. diff --git a/docs/howto.css b/docs/howto.css index 8503472..370dce5 100644 --- a/docs/howto.css +++ b/docs/howto.css @@ -1,6 +1,6 @@ body { padding: 1em; - font-family: Raleway; + font-family: Raleway, sans-serif; line-height: 1.6; } h2 { |