import OKRs from last meeting, slightly modified authored by anarcat's avatar anarcat
This page describes the mid-term plan for the TPA/Web team in the
year 2022. The previous [2021 roadmap](roadmap/2021) was built in a mostly ad-hoc
fashion, but we have tried to use the [OKR](https://en.wikipedia.org/wiki/OKR) system to establish
broader goals as well.
The objectives here asset for the first 6 months (or two quarters,
Q1/Q2) of 2022. They will be reviewed quarterly and a new set will be
generated for Q3/Q4.
Note that those OKRs are complementary to the main [TPA roadmap](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2022),
in the sense that the same team is split over both OKRs.
# 2022 Q1/Q2 web OKRs
* OKR: make the donate page easier to maintain and have it support
.onion donations ([milestone 22][])
* [new lektor frontend][]
* [vanilla JS rewrite][]
* [we can donate through the .onion][]
* OKR: make it easier for translators to contribute (almost done! not
ambitious enough?)
* translators can find their own copy of the website without help
* bring build time to 15 minutes to accelerate feedback to
translators
* allow the web team to trigger manual builds for reviews
* OKR: improve documentation across the organization
* [launch dev.tpo][] (Q2)
* "Remove outdated documentation from the header", stop pointing to
dead docs
* we have a plan to fix the wiki situation so that people can find
and search documentation easily
[milestone 22]: https://gitlab.torproject.org/groups/tpo/-/milestones/22
[new lektor frontend]: https://gitlab.torproject.org/tpo/web/donate-static/-/issues/37
[we can donate through the .onion]: https://gitlab.torproject.org/tpo/web/donate-static/-/issues/36
[vanilla JS rewrite]: https://gitlab.torproject.org/tpo/web/donate-static/-/issues/45
[launch dev.tpo]: https://gitlab.torproject.org/tpo/web/dev/-/issues/6
## Progress update, end of January 2022
The translation CI work is already going steadily and could be finished
in early Q1.
We are probably going to keep prioritizing the donate page changes
because if we postpone, it will be more work as updates are still
happening on the current site, which means more rebasing to keep things
in sync.
We observed that some of those tasks are already done, so we may need to
think more on the longer term. On the other hand, we have a lot of work
to be done on the TPA side of things, so no human cycles will be wasted.
# Things that need to happen regardless of the OKRs
We have identified some things that need to happen, regardless of the
objectives.
This key result, for example, was part of the "documentation" OKR, but
seemed relevant to all teams anyways:
* teams have less than 20 tickets across the three lists (backlog,
next, doing), almost zero open (untriaged) tickets
We also need to support those people as part of sponsored work:
* s9 usability - Q1/Q2
* support web maintaince based on the UX feedback
* Work on torproject.org usabilty issues based on user feedback
* Work on community.torproject.org usabilty issues based on user
feedback
* Work on dev.torproject.org usabilty issues based on user feedback
* phase 6 may bring more TPA work but we need to make the schedule
for it with TPA
* s30 - anti-censorship - Q1
* bridges.torproject.org - Q1
* s61 network performance - whole year
* support the work on network simulation
* s96 - china censorship - whole year
* support snowflake scaling
* support rdsys deployment
* support moat distribution
* support HTTP PT creation
* support monitoring bridge health
* support creation and publication of documentation
* support localization
* s123 - USAGM sites - Q1/Q2
* support the project on onion sites deployments
* most of the work will be from February to April/May
* new onion SRE and community person starting in February
Non-web stuff:
* resurrect bridge port scan
* do not scan private IP blocks: kez talked with cohosh/meskio to get
it fixed, they're okay if kez takes maintainership
* make it pretty: done
Some things were postponed altogether:
* decide if we switch to Weblate is postponed to Q3/Q4, as we have
funding then