GitLab closes these issues automatically only when the destination
branch is the default branch, i.e. `master` currently:
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically

I'm wondering if we should make the `stable` or `devel` branch our default
branch (assuming we merge more branches into these branches than into `master`),
but for now let's workaround the problem via documentation.

Bump our signing key's expiration date

Closes #17133

See merge request !17

Fix first list (and test gitlab)

See merge request !18

refs: #17133, tails/sysadmin#17391

 - Bump expiration date for master key and active RMs' subkeys
 - Revoke inactive RM's subkey

refs: #17133, tails/sysadmin#17391

Split buttons have a significant learnability and discoverability cost.

- Benevity is used by most companies, at least Apple and Google so I'm
  making the instructions for Benevity the default.
- People donating through Benevity might not know that they are using
  Benevity (eg. sometime from Google), so it might not be useful to
  mention the name "Benevity".
- If people search for "Tails" they might end up with hundreds of
  results for animal shelters. Searching for "Riseup Labs" is the way to
  go.
- On Benevity, there is an option called "Tails via Riseup Labs".

Grammar fix to signing key revocation doc: it's -> its

See merge request !13

Add fundraising meeting

See merge request !6

Small fix to personas doc: Avril -> April

See merge request !14

Our Contact page was badly linked before the new About page but it
became slightly worse with the release.

So I'm adding 2 more links to /about/contact even though the proper
solution would be to have a proper "About Us" section. (#17700)

README.md: add "License and source code distribution" + logo

See merge request tails/tails!7