... | @@ -129,11 +129,20 @@ this roadmap is concerned. It should include items we are fairly |
... | @@ -129,11 +129,20 @@ this roadmap is concerned. It should include items we are fairly |
|
certain to be able to complete within the next few months or
|
|
certain to be able to complete within the next few months or
|
|
so. Postponing those could cause problems.
|
|
so. Postponing those could cause problems.
|
|
|
|
|
|
* [ ] email delivery improvements:
|
|
* [x] email delivery improvements:
|
|
* [x] 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 (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168)
|
|
* [x] followup on abuse complaints
|
|
* [ ] diagnose and resolve delivery issue (e.g. [yahoo delivery
|
|
(https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168) -
|
|
problems](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134), https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168)
|
|
we do a systematic check of incoming bounces and actively
|
|
|
|
remove people from the CiviCRM newsletter or mailing lists
|
|
|
|
when we receive complaints
|
|
|
|
* [x] diagnose <del>and resolve</del> delivery issue (e.g. [yahoo delivery
|
|
|
|
problems](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134),
|
|
|
|
https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168)
|
|
|
|
problems seem to be due to the lack of SPF and DMARC records,
|
|
|
|
which we can't add until we setup submit-01. also, we need real
|
|
|
|
certs for accepting mails over TLS for some servers, so we should
|
|
|
|
setup an MX that supports that
|
|
* [x] GitLab CI deployment ([issue 40145](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40145))
|
|
* [x] GitLab CI deployment ([issue 40145](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40145))
|
|
* [x] Jenkins retirement plan (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40167)
|
|
* [x] Jenkins retirement plan (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40167)
|
|
* [x] setup a long-term/sponsored discourse instance?
|
|
* [x] setup a long-term/sponsored discourse instance?
|
... | @@ -147,19 +156,17 @@ Second quarter is a little more vague, but should still be |
... | @@ -147,19 +156,17 @@ Second quarter is a little more vague, but should still be |
|
wait a little longer or that are part of longer projects that will
|
|
wait a little longer or that are part of longer projects that will
|
|
take longer to complete.
|
|
take longer to complete.
|
|
|
|
|
|
* [ ] retire old services:
|
|
* [x] <del>retire old services:</del> postponed
|
|
* [ ] SVN ([issue 17202](https://gitlab.torproject.org/tpo/tpa/team/-/issues/17202))
|
|
* [x] <del>SVN ([issue 17202](https://gitlab.torproject.org/tpo/tpa/team/-/issues/17202))</del> postponed to Q4/2022
|
|
* [ ] fpcentral ([issue 40009](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40009))
|
|
* [x] fpcentral retirement plan ([issue 40009](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40009))
|
|
* [ ] establish plan for gitolite/gitweb retirement ([issue 36](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/36))
|
|
* [x] <del>establish plan for gitolite/gitweb retirement ([issue 36](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/36))</del> postponed to Q4
|
|
* [ ] improve sysadmin code base
|
|
* [x] <del>improve sysadmin code base</del> postponed to 2022 or drive-by fixes
|
|
* [ ] avoid YOLO commits in Puppet (possibly: server-side linting, CI)
|
|
* [x] <del>scale/split gitlab?</del> seems to be working fine and we setup new builders already
|
|
* [ ] 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 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))
|
|
|
|
* [ ] scale/split gitlab?
|
|
|
|
* [x] onion v3 support for TPA services (https://gitlab.torproject.org/tpo/tpa/team/-/issues/32824)
|
|
* [x] onion v3 support for TPA services (https://gitlab.torproject.org/tpo/tpa/team/-/issues/32824)
|
|
|
|
|
|
|
|
Update: many of those tasks were not done because of lack of staff due
|
|
|
|
to an unplanned leave.
|
|
|
|
|
|
## Q3
|
|
## Q3
|
|
|
|
|
|
From our experience, after three quarters, things get difficult to
|
|
From our experience, after three quarters, things get difficult to
|
... | @@ -172,16 +179,29 @@ everything in the air, so obviously plans kind of went out the |
... | @@ -172,16 +179,29 @@ everything in the air, so obviously plans kind of went out the |
|
window. Hopefully this won't happen again and the pandemic will
|
|
window. Hopefully this won't happen again and the pandemic will
|
|
somewhat subside, but we should plan for the worst.
|
|
somewhat subside, but we should plan for the worst.
|
|
|
|
|
|
* [ ] deprecate blog comments? replace with discourse? plan for blog replacement? not the migration! test discourse instance https https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183
|
|
* [ ] establish solid blog migration plan, see [blog service](service/blog) and https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183 tpo/tpa/team#40297
|
|
* [ ] improve communications/monitoring
|
|
* [ ] improve communications/monitoring
|
|
|
|
* [ ] move root@ and tpa "noise" to RT (tpo/tpa/team#31242), make a real mailing list for admins so that gaba and non-tech can join
|
|
|
|
* [ ] vacations
|
|
|
|
* [ ] onboarding new staff
|
|
|
|
|
|
|
|
Update: this quarter and the previous one, as expected, has changed
|
|
|
|
radically from what was planned, because of the staff changes. Focus
|
|
|
|
will be on training and onboarding, and a well-deserved vacation.
|
|
|
|
|
|
## Q4
|
|
## Q4
|
|
|
|
|
|
Obviously, the fourth quarter is sheer crystal balling at this stage,
|
|
Obviously, the fourth quarter is sheer crystal balling at this stage,
|
|
but it should still be an interesting exercise to perform.
|
|
but it should still be an interesting exercise to perform.
|
|
|
|
|
|
* [ ] gitolite/gitweb retirement?
|
|
* [ ] blog retirement before Drupal 9 EOL (November 2021)
|
|
|
|
* [ ] gitolite/gitweb retirement plan ([issue 36](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/36))
|
|
* [ ] jenkins retirement https://gitlab.torproject.org/tpo/tpa/team/-/issues/40218
|
|
* [ ] jenkins retirement https://gitlab.torproject.org/tpo/tpa/team/-/issues/40218
|
|
|
|
* [ ] SVN retirement plan ([issue 17202](https://gitlab.torproject.org/tpo/tpa/team/-/issues/17202))
|
|
|
|
* [ ] fpcentral retirement ([issue 40009](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40009))
|
|
|
|
* [ ] setup submit-01 to deliver people's emails (tpo/tpa/team#30608)
|
|
|
|
* [ ] redo the user survey and 2022 roadmap (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40307)
|
|
|
|
* [ ] BTCpayserver hosting (https://gitlab.torproject.org/tpo/tpa/team/-/issues/33750)
|
|
|
|
|
|
# 2020 roadmap evaluation
|
|
# 2020 roadmap evaluation
|
|
|
|
|
... | @@ -760,4 +780,3 @@ was surprised to see that gitweb and git-rw are used equally by the |
... | @@ -760,4 +780,3 @@ was surprised to see that gitweb and git-rw are used equally by the |
|
team, which the previous calculation told us. The new ones seem to
|
|
team, which the previous calculation told us. The new ones seem to
|
|
better reflect actual use (3 monthly, 1 weekly, 6 daily vs 1 monthly,
|
|
better reflect actual use (3 monthly, 1 weekly, 6 daily vs 1 monthly,
|
|
2 weekly, 3 daily, 2 hourly, respectively). |
|
2 weekly, 3 daily, 2 hourly, respectively). |
|
|
|
|