This makes it more immediately visible to users reading the proposal
by email or just browsing the website. Things like "affected users",
"approval" and "deadline" are particularly things that rarely require
a whole paragraph to describe.

This also makes the contents greppable, which is particularly relevant
for the Status field, which could now be used for automatic
generation.

That front matter is not currently very well displayed by GitLab
wikis, but it's relatively readable.

I have *tried* to move the "Summary" in there as well, but the
formatting gets ugly quickly, as we need to use line continuation
hacks. Besides, it looks better in the wiki that way.

I have tried to do this automatically macros, but alas the format was
too irregular so I had to actually do this manually, which means I
also tweaked other things as I went along.

Hopefully the format will make future work like this much easier.

policy/tpa-rfc-2-support.md

 ---
 title: TPA-RFC-2: support
+deadline: 2020-06-17
+status: standard
+discussion: https://bugs.torproject.org/31243
 ---
 
 Summary: to get help, open a ticket, ask on IRC for simple things, or
@@ -308,10 +311,6 @@ on 2020-06-10, at which point it was submitted to tor-internal for
 broader approval. It will be marked as "standard" on 2020-06-17 if
 there are no objections there.
 
-# Status
-
-This proposal was adopted as a `standard` on 2020-06-17.
-
 # References
 
  * [ticket 31243][]