In [the last discussion about the tails merge roadmap](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/meeting/2024-11-11), we have:
> postpone[d] the "what happens when" discussion. We also identified that most services above "low complexity" will require their own discussions (e.g. "how do we manage the Puppet control repo", "how do we merge weblate") that will happen later.
So we try to schedule those items across the 5 years. And we can also discuss
specific roadmap items to see if we can settle some ideas already.
Or we postpone all of this to the 2026 roadmap.
Results of the discussion: We won't have time to discuss all of these, so maybe
we want to sort based on priority, and pick one or two to go more in depth.
Output should be notes to add to tpa-rfc-73 and a reviewed 2025 roadmap, then we
can call this done for the time being and come back closer to end of 2025. We
will adopt TPA-RFC-73 as a general guide / rough plan and review as we go.
Here are all the medium and high complexity items we might want to discuss:
## 2025
See also the milestone: %"TPA-RFC-73: Tails merge (2025)"
-[Security Policy](#security-policy)(merge, discussion delegated to anarcat)
-[Shifts](#shifts)(merge, brainstorm a plan)
- Puppet merge (merge, brainstorm of a plan):
- deploy dynamic environments (in progress)
- we can't use environments to retire one of the two puppet servers, because
of exported resources
- Upgrade and converge Puppet modules
- lots of default stuff get deployed by TPA when you hook up a server, we
could try turning everything off by default, move the defaults to a profile
