Those are mostly tests to see if we can get something that satisfies
markdownlint.

Mostly to be granted only as last resort. Demand that problems be
documented in the service page.

Also includes some clarification in the wording.

Also moves the dgoulet example down because it's actually a
counter-example.

The minutes were read and agreed upon by TPA, so I assume this
reflects the current will of the team. This will help in case there
are bits of the policy that are unclear in the future.

This is based on the current "vetting" policy but also includes a
reference to the Tor Core Membership policy, to which we delegate the
revokation bit. We also assert that admins MUST be core tor to have
access.

This also introduces a link to the core membership policy which we
refer to elsewhere in the document.

Mostly to be granted only as last resort. Demand that problems be
documented in the service page.

Also includes some clarification in the wording.

Also moves the dgoulet example down because it's actually a
counter-example.

The minutes were read and agreed upon by TPA, so I assume this
reflects the current will of the team. This will help in case there
are bits of the policy that are unclear in the future.

This is based on the current "vetting" policy but also includes a
reference to the Tor Core Membership policy, to which we delegate the
revokation bit. We also assert that admins MUST be core tor to have
access.

This also introduces a link to the core membership policy which we
refer to elsewhere in the document.

The policy was marked as "draft" in the document, but classified as
"standard" in the list because the deadline had expired without
objection, so it technically *was* standard.

In any case, it was implemented and now is therefore obsolete (because
it's useless to keep such an historical proposal forever).

They were called "lists" and "milestones" before. We don't use "list"
because we use the word "list" to list the queues in the
documentation, so it would be confusing. That might be a bad idea.

Without it, the "Open" queue has a lot of junk and new tickets get
lost in the noise. By moving most of that junk in the Icebox queue,
new tickets immediately pop up in the Open queue and can be properly triaged.

We add the Next label because it's already being used in a subproject
of tpa (gitlab) and because it's used globally. It also helps us
separate the "endless pile of ticket" in Open from the Backlog, as
now we can throw more things in the backlog without worrying about
overloading our monthly capacity.