cross-reference the gitlab labels proposals

Amazingly, those two didn't know each other... At least now we can
find one another when looking at one, but perhaps the triage stuff
could be merged in the labels proposal?

policy/tpa-rfc-19-gitlab-labels.md

@@ -269,3 +269,6 @@ discussion include:
 
 [issue tpo/tpa/gitlab#55]: https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/55
 [issue tpo/tpa/team#40649]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40649
+
+See also the [TPA-RFC-5: GitLab migration](policy/tpa-rfc-5-gitlab) proposal which sets the
+policy on other labels like ~Doing, ~Next, ~Backlog, ~Icebox and so on.

policy/tpa-rfc-5-gitlab.md

@@ -66,16 +66,16 @@ which is implemented in GitLab as [issue boards](https://docs.gitlab.com/ee/user
 Issues first land into a queue (`Open`), then get assigned to
 a specific queue as the ticket gets planned. 
 
-We use the `Icebox`, `Backlog`, `Next`, and `Doing` of the global
+We use the ~Icebox, ~Backlog, ~Next, and ~Doing of the global
 "TPO" group board labels. With the `Open` and `Closed` queues, this
 gives us the following policy:
 
  * `Open`: un-triaged ticket
- * `Icebox`: ticket that is stalled, but triaged
- * `Backlog`: planned work for the "next" iteration (e.g. "next month")
- * `Next`: work to be done in the current iteration or "sprint"
+ * ~Icebox: ticket that is stalled, but triaged
+ * ~Backlog: planned work for the "next" iteration (e.g. "next month")
+ * ~Next: work to be done in the current iteration or "sprint"
    (e.g. currently a month, so "this month")
- * `Doing`: work being done right now (generally during the day or
+ * ~Doing: work being done right now (generally during the day or
    week)
  * `Closed`: completed work
 
@@ -84,15 +84,15 @@ this policy.
 
 The `Open` board should ideally be always empty: as soon as a ticket
 is there, it should be processed into some other queue. If the work
-needs to be done urgently, it can be moved into the `Doing` queue, if
-not, it will typically go into the `Next` or `Backlog` queues.
+needs to be done urgently, it can be moved into the ~Doing queue, if
+not, it will typically go into the ~Next or ~Backlog queues.
 
-Tickets should *not* stay in the `Next` or `Doing` queues for long and
-should instead actively be closed or moved back into the `Icebox` or
-`Backlog` board. Tickets should *not* be moved back to the `Open`
+Tickets should *not* stay in the ~Next or ~Doing queues for long and
+should instead actively be closed or moved back into the ~Icebox or
+~Backlog board. Tickets should *not* be moved back to the `Open`
 board once they have been triaged.
 
-Tickets moved to the `Next` and `Doing` queues should normally be
+Tickets moved to the ~Next and ~Doing queues should normally be
 assigned to a person. The person doing triage should make sure the
 assignee has availability to process the ticket before assigning.
 
@@ -157,3 +157,4 @@ established timeline and this proposal does *not* enforce one.
  * [Wikipedia article about Kanban development](https://en.wikipedia.org/wiki/Kanban_(development))
  * [No bullshit article about issue trackers](https://almad.blog/essays/no-bugs-just-todos/) which inspired the
    switch to Kanban
+ * [TPA-RFC-19: GitLab labels](policy/tpa-rfc-19-gitlab-labels): policy on service-specific labels