Changes

Page history
harmonize the roadmap priorities with service templates authored by anarcat's avatar anarcat 
We are using "Must have" instead of "Need to have" there, and it seems
like a more natural wording that we should also use here. It also
happens to reuse RFC-like vocabulary so it may be more explicit for
some people.
Show whitespace changes
Inline Side-by-side
roadmap/2021.md
View page @ 3fb7c3f7
...@@ -21,7 +21,7 @@ attention. In general, the over-arching goals are therefore: ...@@ -21,7 +21,7 @@ attention. In general, the over-arching goals are therefore:
service retirements) service retirements)
* better communication (particularly with developers) * better communication (particularly with developers)
## Need to have ## Must have
* [ ] email delivery improvements: * [ ] 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))
...@@ -207,7 +207,7 @@ but it should still be an interesting exercise to perform. ...@@ -207,7 +207,7 @@ but it should still be an interesting exercise to perform.
The following is a review of the [2020 roadmap](roadmap/2020). The following is a review of the [2020 roadmap](roadmap/2020).
## Need to have ## Must have
* [x] retiring old machines (moly in particular) * [x] retiring old machines (moly in particular)
* [x] move critical services in ganeti * [x] move critical services in ganeti
... ...
......