Thanks @sat and @SvenF 
That means a lot
Indeed, here are a couple of examples
As a formal requirement of the review? (I don’t imagine there’ll be much/any traction otherwise)
I think this is a very good suggestion. Otherwise the whole thread just becomes a big wall of words. But I do think it would be sensible to make this a formal requirement. The aim should be for the release thread to be as accessible as possible to all NNS voters. Many of these are individuals who would like to see a TLDR from each reviewer, rather than being drowned in words and scared off.
For anyone that doesn’t know, the markdown for this is as follows
<details>
<summary>Expand for a review of each commit</summary>
- Hello, I represent the review of a specific commit
- and I represent another one...
</details>
Expand for a review of each commit
- Hello, I represent the review of a specific commit
- and I represent another one…
Why does having a summary per commit mean there shouldn’t also be a summary for the whole proposal (which explains the main takeaways and why a reviewer voted to adopt or reject)? - basically a TLDR. I think what @cryptoschindler is suggesting is very sensible. I would add that I think this is what should sit outside of those expandable sections (while everything else, including the build hash verification screenshot, would be best collapsed by default).