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 @@ - + HR label cheat sheet - + @@ -32,7 +32,7 @@

Working with labels

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.
  1. The tooling creates a tracker issue in the HR repo, and applies the following labels: pending, s:xxx, tracker.
  2. The HR group looks at the issue and decides whether it should continue with the tracker label.
  3. @@ -41,7 +41,7 @@

    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.
  1. Create a new issue in the HR tracker repo, describing the issue. (There should be some boilerplate instructions.)
  2. Apply a pending label.
  3. @@ -51,7 +51,7 @@

    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.
  1. Create a new issue in the WG repo, based on the text reviewed by the HR WG.
  2. Add a *-needs-resolution label to both the WG repo and HR repo.
  3. @@ -66,7 +66,7 @@

    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.
  1. The HR group indicates that it is satisfied in the issue in the WG repo.
  2. The HR group closes the issue in the HR repo.
  3. @@ -74,7 +74,7 @@

    Working with labels

    Note 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.
  1. The tooling will add a Close? label to the issue in the HR repo, signalling that the HR group should consider whether the issue is resolved.
  2. The HR group discusses the current status.
  3. @@ -83,7 +83,7 @@

    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.
  1. The tooling will add a Close? label to the issue in the HR repo, signalling that the HR group should consider whether to stop tracking that issue.
  2. The HR group discusses the current status.
  3. @@ -92,7 +92,7 @@

    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:

  1. The HR group closes the issue in the HR repo, but adds a Recycle label.
  2. @@ -101,20 +101,20 @@

    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.
  1. Make a comment in the WG repo issue to indicate what resolution you are looking for.
  2. Change the *-tracker label to *-needs-resolution in both the WG and HR repos.
The HR group decides to change a *-needs-resolution issue to *-tracker.The HR group decides to change a *-needs-resolution issue to *-tracker.
  1. Change the *-needs-resolution label to *-tracker in both the WG and HR repos.
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.

  1. Add the Advice requested label to the issue in the HR repo.
  2. @@ -124,7 +124,7 @@

    Working with labels

    There 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.

  1. Add the Needs attention label to the issue in the HR repo.
  2. @@ -133,7 +133,7 @@

    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.

  1. The new issue will come into the HR repo with a pending label, indicating that you need to check is has the appropriate additional labels. While doing that, simply invent a s:xxx label in GitHub and assign it to the relevant issue(s) (eg. s:webex). The label doesn't have to represent an actual shortname for the board to pick it up. The board will automatically display issues with that label in a new section.
  2. @@ -141,7 +141,7 @@

    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 {