start plannning 2024 roadmap, draft (team#41436)

policy.md

@@ -22,6 +22,7 @@ and add it to the above list.
  * [TPA-RFC-45: Mail architecture](policy/tpa-rfc-45-mail-architecture)
  * [TPA-RFC-47: Email account retirement](policy/tpa-rfc-47-email-account-retirement)
  * [TPA-RFC-60: GitLab 2-factor authentication enforcement](policy/tpa-rfc-60-gitlab-2fa-enforcement)
+ * [TPA-RFC-61: 2024 roadmap](policy/tpa-rfc-61-roadmap-2024)
 
 ## Proposed
 
@@ -46,7 +47,6 @@ No policy is currently `proposed`.
  * [TPA-RFC-32: Nextcloud root-level shared folders migration](policy/tpa-rfc-32-nextcloud-root-level-folders-migration)
  * [TPA-RFC-36: Gitolite, GitWeb retirement](policy/tpa-rfc-36-gitolite-gitweb-retirement)
  * [TPA-RFC-39: Nextcloud account policy](policy/tpa-rfc-39-nextcloud-account-policy)
- * [TPA-RFC-42: 2023 roadmap](policy/tpa-rfc-42-roadmap-2023)
  * [TPA-RFC-44: Email emergency recovery](policy/tpa-rfc-44-email-emergency-recovery)
  * [TPA-RFC-46: GitLab 2FA](policy/tpa-rfc-46-gitlab-2fa)
  * [TPA-RFC-48: Enable new GitLab Web IDE](policy/tpa-rfc-48-enable-new-gitlab-web-ide)
@@ -84,6 +84,7 @@ No policy is currently `proposed`.
  * [TPA-RFC-34: End of office hours](policy/tpa-rfc-34-office-hours-ends) (merged in TPA-RFC-2)
  * [TPA-RFC-35: GitLab email address changes](policy/tpa-rfc-35-gitlab-email-address-changes) (one-time change)
  * [TPA-RFC-40: Cymru migration budget](policy/tpa-rfc-40-cymru-migration) (replaced by TPA-RFC-43)
+ * [TPA-RFC-42: 2023 roadmap](policy/tpa-rfc-42-roadmap-2023)
  * [TPA-RFC-43: Cymru migration plan](policy/tpa-rfc-43-cymru-migration-plan)
  * [TPA-RFC-49: document the ganeti naming convention](https://gitlab.torproject.org/tpo/tpa/wiki-replica/-/merge_requests/39)
  * [TPA-RFC-52: Cymru migration timeline](policy/tpa-rfc-52-cymru-migration-timeline)

policy/tpa-rfc-61-roadmap-2024.md

+---
+title: TPA-RFC-61: 2024 roadmap
+---
+
+[[_TOC_]]
+
+Summary: a roadmap for 2024
+
+# Proposal
+
+## Priorities for 2024
+
+### Must have
+
+* bookworm upgrade completion (50% done) before July 2024 (so Q1-Q2
+  2024), which includes:
+  * puppet server 7 upgrade: Q2 2024?
+  * mailman 3 and schleuder upgrade (probably on a new mail server),
+    hopefully Q2 2024
+  * inciga retirement / migration to Prometheus Q3-Q4 2024?
+* old services retirement
+  * SVN retirement (or not): proposal in Q2, execution Q3-Q4?
+    Nextcloud will not work after all because of [major issues with
+    collaborative editing](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/nextcloud#a-few-gotchas-with-collaborative-editing), need to go back to the drawing board.
+  * gitolite retirement, which includes:
+    * 12 TPA repos to migrate, some complicated
+    * archiving all other repositories
+    * lockdown scheduled for Q2 2024
+* email services? TPA-RFC-45 includes:
+  * draft TPA-RFC-45, which may include:
+  * mailbox hosting in HA
+* minio clustering and backups
+* make a decision on gitlab ultimate
+
+### nice to have
+
+* Puppet CI
+* review TPA-RFC process
+* tiered gitlab runners
+* improve upgrade automation
+* monitor technical debt ([tpo/tpa/team#41456](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41456))
+* review team function and scope (TPA? web? SRE?)
+
+### 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:
+
+* Hetzner evacuation (plan and estimates)
+* outages, capacity scaling
+* in general, disaster recovery plans
+* possible future changes for intenal chat (IRC onboarding?) or sudden
+  requirement to self-host another service currently hosted externally
+* some guy named jerry, who knows!
+
+## THE WEB - how we organize it this year
+
+This still need to be discussed and reviewed with isa.
+
+- call for a "web team meeting"
+- discuss priorities with that team
+- discuss how we are going to organize ourselves
+- announce the hiring this year of a web dev
+
+# Approval
+
+Approval by TPA, @gaba and @isa.
+
+# Deadline
+
+February?
+
+# Status
+
+This proposal is currently in the `draft` state.
+
+# References
+
+Previous roadmap [established in TPA-RFC-42](policy/tpa-rfc-42-roadmap-2023) and is in [roadmap/2023](roadmap/2023).