roadmap/2021.md

@@ -23,9 +23,9 @@ attention. In general, the over-arching goals are therefore:
 ## Need to have
 
  * [ ] email delivery improvements:
-   * [ ] handle bounces in CiviCRM ([issue 33037](https://gitlab.torproject.org/tpo/tpa/team/-/issues/33037))
+   * [x] handle bounces in CiviCRM ([issue 33037](https://gitlab.torproject.org/tpo/tpa/team/-/issues/33037))
    * [ ] systematically followup on and respond to abuse complaints
-   * [ ] diagnose and resolve delivery issue (e.g. [yahoo delivery
+   * [ ] diagnose and resolve delivery issues (e.g. [yahoo delivery
      problems](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134))
    * [ ] provide reliable delivery for users ("my email ends up in spam!")
    * [ ] possible implementations:
@@ -48,7 +48,7 @@ attention. In general, the over-arching goals are therefore:
    * [ ] migrate to a static website and Discourse
    * [ ] fix formatting and improve moderation within Drupal
  * [ ] improve communications and monitoring:
-   * [ ] document "downtimes of 1 hour or longer", in a status page [issue
+   * [x] document "downtimes of 1 hour or longer", in a status page [issue
      40138](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40138)
    * [ ] reduce alert fatigue in Nagios
    * [ ] publicize debugging tools (Grafana, user-level logging in systemd
@@ -82,7 +82,7 @@ attention. In general, the over-arching goals are therefore:
    ([issue 81](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/81))
  * [ ] finish retiring old hardware (moly, [ticket 29974](https://gitlab.torproject.org/legacy/trac/-/issues/29974))
  * [ ] varnish to nginx conversion (#32462)
- * [ ] GitLab pages hosting
+ * [x] GitLab pages hosting (see [issue tpo/tpa/gitlab#91](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/91))
  * [ ] experiment with containers/kubernetes for CI/CD
  * [ ] upgrade to bullseye
  * [ ] cover for some metrics services ([issue 40125](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40125))
@@ -99,10 +99,11 @@ attention. In general, the over-arching goals are therefore:
    services through Docker, but this will likely not happen in 2021
  * [ ] static mirror network retirement / rearchitecture: we want to test
    out GitLab pages first and see if it can provide a decent
-   alternative
+   alternative (update: some analysis performed in [the static site
+   documentation](howto/static-component#alternatives-considered))
  * [ ] web development stuff: goals like "finish main website transition", "broken links on website"... should be covered in the web team, but the capacity of TPA is affected by hiro working on the web stuff
- * [ ] TODO: are service admins still a thing? should we cover for things
-   like the metrics team?
+ * [ ] are service admins still a thing? should we cover for things
+   like the metrics team? update: discussion postponed
  * [ ] complete puppetization: old legacy services are not in Puppet. that
    is fine: we keep maintaining them by hand when relevant, but new
    services should all be built in Puppet
@@ -121,14 +122,15 @@ certain to be able to complete within the next few months or
 so. Postponing those could cause problems.
 
  * [ ] email delivery improvements:
-   * [ ] handle bounces in CiviCRM ([issue 33037](https://gitlab.torproject.org/tpo/tpa/team/-/issues/33037))
+   * [x] handle bounces in CiviCRM ([issue 33037](https://gitlab.torproject.org/tpo/tpa/team/-/issues/33037))
    * [ ] followup on abuse complaints
    * [ ] diagnose and resolve delivery issue (e.g. [yahoo delivery
      problems](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134))
- * [ ] GitLab CI deployment, plan for Jenkins retirement
+ * [x] GitLab CI deployment ([issue 40145](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40145))
+ * [ ] Jenkins retirement plan (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40167)
  * [ ] plan for blog replacement? not the migration!
- * [ ] setup a long-term/sponsored discourse instance?
- * [ ] document "downtimes of 1 hour or longer", in a status page [issue
+ * [x] setup a long-term/sponsored discourse instance?
+ * [x] document "downtimes of 1 hour or longer", in a status page [issue
    40138](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40138)
 
 ## Q2