Refactor Documentation Team labels

Currently, docs team labels are a little inconsistent and not universally used.

For example:

docs-discussion ~"docs:P1" ~Documentation

These are just the ones in gitlab-com group. Others in gitlab-org group are:

With the introduction of scoped labels (https://docs.gitlab.com/ee/user/project/labels.html#scoped-labels-premium), we should take the opportunity to consolidate our labels and make them reflective of our desired workflow (https://docs.gitlab.com/ee/user/project/labels.html#workflows-with-scoped-labels-premium).

Possible steps:

  1. Discover if there are any documented uses of scopes labels. Can we leverage existing scoped labels for our purposes? Some are starting to use them: https://gitlab.com/groups/gitlab-org/-/labels?utf8=✓&subscribed=&search=%3A%3A. Plan and UX seem to be the earliest adopters.
  2. Come up with descriptive prefixes. We might need more than one because a prefix makes all the suffixes mutually exclusive. Some ideas include: docs::, documentation::, technicalcontent::, etc.
  3. Come up with desired suffixes. Some ideas include: ::fix, ::new, ::discuss, ::edit, ::community, ::author, ::review etc.
  4. Decide if we want to duplicate labels across the gitlab-org and gitlab-com groups, or if we move everything to sit under gitlab-org group. Axil almost has gitlab-docs moved, so is this project (technical-writing) the only thing left in gitlab-com?

Let's start a docs::discuss 😉

CC @gl-docsteam @clenneville @MattPennaThe3rd @tauriedavis

Edited by Craig Norris