roadmap/2022.md

@@ -36,7 +36,9 @@ in the sense that the same team is split over both OKRs.
 [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
+# Progress updates
+
+## end of January 2022
 
 The translation CI work is already going steadily and could be finished
 in early Q1.
@@ -50,6 +52,34 @@ 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.
 
+## Q1
+
+(From the notes of the [2022-04-04 meeting](meeting/2022-04-04).)
+
+ * donate: lektor frontend needs to be cleaned up, some of the
+   settings are still set in react instead of with lektor's
+   `contents.lr`. Vanilla JS rewrite mostly complete, possibly enough
+   that the rest can be outsourced. Still no .onion since production
+   is running the react version (doesn't run in tbb) and .onion might
+   also break on the backend. We also don't have an HTTPS certificate
+   for the backend!
+
+ * translators: good progress on this front, build time blocking on
+   the i18n plugin status ([TPA-RFC-16][]), stuck on Python 3.8 land,
+   we are also going to make changes to the workflow to allow
+   developers to merge MRs (but not push)
+
+ * documentation: removed some of the old docs, dev.tpo for Q2?
+
+The TPA-RFC-16 proposal (rewriting the lektor-i18n plugin) was
+discussed a little more in depth. We will get more details about the
+problems kez found with the other CMSes and a rough comparison of the
+time that would be required to migrate to another CMS vs rewriting the
+plugin. See [tpo/web/team#28][] for details.
+
+ [TPA-RFC-16]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-16-replacing-lektor-i18n-plugin
+ [tpo/web/team#28]: https://gitlab.torproject.org/tpo/web/team/-/issues/28
+
 # Things that need to happen regardless of the OKRs
 
 We have identified some things that need to happen, regardless of the