follow service page renames authored by anarcat's avatar anarcat
...@@ -85,9 +85,9 @@ attention. In general, the over-arching goals are therefore: ...@@ -85,9 +85,9 @@ attention. In general, the over-arching goals are therefore:
* [x] implement an ENC for Puppet ([issue 40358](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40358)) * [x] implement an ENC for Puppet ([issue 40358](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40358))
* [ ] avoid YOLO commits in Puppet (possibly: server-side linting, CI) * [ ] avoid YOLO commits in Puppet (possibly: server-side linting, CI)
* [ ] publish our Puppet repository ([ticket 29387](https://gitlab.torproject.org/tpo/tpa/team/-/issues/29387)) * [ ] publish our Puppet repository ([ticket 29387](https://gitlab.torproject.org/tpo/tpa/team/-/issues/29387))
* [ ] reduce dependency on Python 2 code (see [short term LDAP plan](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/ldap#short-term-merge-with-upstream-port-to-python-3-if-necessary)) * [ ] reduce dependency on Python 2 code (see [short term LDAP plan](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/ldap#short-term-merge-with-upstream-port-to-python-3-if-necessary))
* [ ] reduce dependency on LDAP (move hosts to Puppet? see [mid term * [ ] reduce dependency on LDAP (move hosts to Puppet? see [mid term
LDAP plan](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/ldap#mid-term-move-hosts-to-puppet-possibly-replace-ud-ldap-with-simpler-dashboard)) LDAP plan](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/ldap#mid-term-move-hosts-to-puppet-possibly-replace-ud-ldap-with-simpler-dashboard))
* [ ] avoid duplicate git hosting infrastructure * [ ] avoid duplicate git hosting infrastructure
* [ ] retire gitolite, gitweb ([issue 36](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/36)) * [ ] retire gitolite, gitweb ([issue 36](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/36))
* [ ] retire more old services: * [ ] retire more old services:
...@@ -119,7 +119,7 @@ attention. In general, the over-arching goals are therefore: ...@@ -119,7 +119,7 @@ attention. In general, the over-arching goals are therefore:
* [ ] static mirror network retirement / re-architecture: we want to test * [ ] static mirror network retirement / re-architecture: we want to test
out GitLab pages first and see if it can provide a decent out GitLab pages first and see if it can provide a decent
alternative (update: some analysis performed in [the static site alternative (update: some analysis performed in [the static site
documentation](howto/static-component#alternatives-considered)) documentation](service/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 * [ ] 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
* [ ] are service admins still a thing? should we cover for things * [ ] are service admins still a thing? should we cover for things
like the metrics team? update: discussion postponed like the metrics team? update: discussion postponed
... ...
......