make a proper page for the 2025 roadmap (tpo/tpa/team#41821)

meeting.md

@@ -27,7 +27,7 @@ Those are just for TPA, there are broader notes on meetings in the
 
 # 2024
 
- * [2024-11-18](meeting/2024-11-18.md)
+ * [2024-11-18](meeting/2024-11-18)
  * [2024-11-11](meeting/2024-11-11)
  * [2024-10-15](meeting/2024-10-15)
  * [2024-09-09](meeting/2024-09-09)

meeting/2024-11-18.md

@@ -106,3 +106,5 @@ Removed items:
   autononmous delivery to Phase B
   
  [TPA-RFC-33-C]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/15#tab-issues
+
+Note that the roadmap will be maintained in [roadmap/2025](roadmap/2025).

roadmap.md

@@ -4,6 +4,7 @@ We keep our plans for the future (and the paste) here.
 
 <!-- update with `ls -d roadmap/*.md | sed 's/.md$//;s/\(.*\)/ * [\1](\1)/'` -->
 
+ * [roadmap/2025](roadmap/2025)
  * [TPA-RFC-61: 2024 roadmap](policy/tpa-rfc-61-roadmap-2024)
  * [roadmap/tails-merge](roadmap/tails-merge)
  * [roadmap/2023](roadmap/2023)

roadmap/2025.md

+# Priorities for 2025
+
+- Web things already scheduled this year, postponed to 2025
+  - Improve websites for mobile
+  - Create a plan for migrating the gitlab wikis to something else
+  - Improve web review workflows, reuse the donate-review machinery
+    for other websites (new)
+- Make a plan for SVN, consider keeping it
+- MinIO in production, moving GitLab artifacts, and collector to
+  object storage, also for network-health team (contact @hiro) (Q1 2025)
+- [Prometheus phase B][]: inhibitions, self-monitoring, merge the two
+  servers, authentication fixes and (new) autonomous delivery
+- Debian trixie upgrades during freeze
+- Puppet CI (see also merge with Tails below)
+- Development environment for anti-censorship team (contact @meskio), AKA
+  "rdsys containers" ([tpo/tpa/team#41769][])
+- Possibly more hardware resources for apps team (contact @morganava)
+- Tails 2025 merge roadmap, from the [Tails merge timeline][]
+  - Puppet repos and server:
+    - [Upgrade Tor's Puppet Server to Puppet 7][]
+    - Upgrade and converge Puppet modules
+    - Implement commit signing
+    - EYAML (keep)
+    - Puppet server (merge)
+  - Bitcoin (retire)
+  - LimeSuvey (merge)
+  - Website (merge)
+  - Monitoring (migrate)
+  - Come up with a plan for authentication
+
+ [Tails merge timeline]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-73-tails-infra-merge-roadmap#timeline
+ [Upgrade Tor's Puppet Server to Puppet 7]: tpo/tpa/team#41819
+ [tpo/tpa/team#41769]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41769
+ [Prometheus phase B]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/14
+
+Note that the web roadmap is not fully finalized and will be discussed
+on 2024-11-19.
+
+## Removed items
+
+- Evaluate replacement of lektor and create a clear plan for
+  migration: performance issues are being resolved, and we're building
+  a new lektor site (download.tpo!), so we propose to keep Lektor for
+  the forseeable future
+- [TPA-RFC-33-C][], high availability moved to later, we moved
+  autononmous delivery to Phase B
+  
+ [TPA-RFC-33-C]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/15#tab-issues
+
+## Black swans
+
+A [black swan event](https://en.wikipedia.org/wiki/Black_swan_theory) is "an event that comes as a surprise, has a
+major effect, and is often inappropriately rationalized after the fact
+with the benefit of hindsight" ([Wikipedia](https://en.wikipedia.org/wiki/Black_swan_theory)). In our case, it's
+typically an unexpected and unplanned emergency that derails the above
+plans.
+
+Here are possible changes that are technically *not* black swans
+(because they are listed here!) but that could serve as placeholders
+for the actual events we'll have this year:
+
+- Possibly take over USAGM s145 from @rhatto if he gets funded elsewhere
+* Hetzner evacuation (plan and estimates) ([tpo/tpa/team#41448](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41448))
+* outages, capacity scaling ([tpo/tpa/team#41448](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41448))
+* in general, disaster recovery plans
+* possible future changes for internal chat (IRC onboarding?) or sudden
+  requirement to self-host another service currently hosted externally
+
+Some of those were carried over from the [2024 roadmap](policy/tpa-rfc-61-roadmap-2024). Most
+notably, we've merged with Tails, which was *then* a "black swan"
+event, but is now part of our roadmap.
+
+# References
+
+This roadmap was discussed in November 2024 in two meetings,
+[2024-11-18](meeting/2024-11-18) and [2024-11-11](meeting/2024-11-11). It was also worked on in an
+[issue](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41821).