refs team#41721

refs team#41721

refs team#41721

refs team#41721

It's good to have some meaningful defaults. For the cases of exception
it's nice to know why we decided to stray from the defaults.

I find it easier to read that way, and then it can be used to link
directly to individual years.

it was duplicated from the one above

During the TPA roadmap meeting of 2024-11-18 we decided to bump the
priority of 2 items to 2025: Monitoring migration and coming up with a
plan for authentication.

refs team#41721

The current procedure didn't actually work, as it assumes apt queries
only available in bookworm. Install then remove forktracer.

With a unique sorted class list, future changes in actions will be less
cumbersome.

refs team#41721

As discussed during merge planning and during last roadmap meeting,
spread the timeline in 5 years (2025-2029).

refs team#41721

refs team#41721

refs team#41721

refs team#41721

In the TPA roadmap meeting of 2024-11-11 we discussed that Colo and
Registrars could only depend on merging the Password store and not be
otherwise changed. I made it explicit that documentation also needs
update.

refs team#41721

without this, we build an entire NAT stack (or userspace slirp pipe)
for no good reason, which loads kernel modules and can fail because of
our kernel lockdown.

I'm not sure that this is the dashboard that lavamind had in mind when
he mentioned it on IRC. The URL does show some "healthy" indicator after
running some self-diagnostics, so it's already some information..