... | @@ -17,8 +17,8 @@ stabilisation" before "new services". Furthermore, some services are |
... | @@ -17,8 +17,8 @@ stabilisation" before "new services". Furthermore, some services are |
|
way more popular than others, so those services should get special
|
|
way more popular than others, so those services should get special
|
|
attention. In general, the over-arching goals are therefore:
|
|
attention. In general, the over-arching goals are therefore:
|
|
|
|
|
|
* stabilisation (particularly email but also GitLab, schleuder, blog)
|
|
* stabilisation (particularly email but also GitLab, Schleuder, blog)
|
|
* better communication (particularly with devs)
|
|
* better communication (particularly with developers)
|
|
|
|
|
|
## Need to have
|
|
## Need to have
|
|
|
|
|
... | @@ -26,7 +26,7 @@ attention. In general, the over-arching goals are therefore: |
... | @@ -26,7 +26,7 @@ attention. In general, the over-arching goals are therefore: |
|
* [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))
|
|
* [ ] systematically followup on and respond to abuse complaints (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168)
|
|
* [ ] systematically followup on and respond to abuse complaints (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168)
|
|
* [ ] diagnose and resolve delivery issues (e.g. [Yahoo](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134),
|
|
* [ ] diagnose and resolve delivery issues (e.g. [Yahoo](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134),
|
|
[state.gov](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40202), [gmail](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40170), [gmail again](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40149))
|
|
[state.gov](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40202), [Gmail](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40170), [Gmail again](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40149))
|
|
* [ ] provide reliable delivery for users ("my email ends up in spam!")
|
|
* [ ] provide reliable delivery for users ("my email ends up in spam!")
|
|
* [ ] possible implementations:
|
|
* [ ] possible implementations:
|
|
* [ ] setup a new MX server to receive incoming email, with
|
|
* [ ] setup a new MX server to receive incoming email, with
|
... | @@ -97,11 +97,11 @@ attention. In general, the over-arching goals are therefore: |
... | @@ -97,11 +97,11 @@ attention. In general, the over-arching goals are therefore: |
|
* [ ] "provide development/experimental VMs": would be possible through
|
|
* [ ] "provide development/experimental VMs": would be possible through
|
|
GitLab CD, to be investigated once we have GitLab CI solidly
|
|
GitLab CD, to be investigated once we have GitLab CI solidly
|
|
running
|
|
running
|
|
* [ ] "improve interaction between TPA and devs when new services are
|
|
* [ ] "improve interaction between TPA and developers when new services are
|
|
setup": see "improve communications" above, and "experimental
|
|
setup": see "improve communications" above, and "experimental
|
|
VMs". The endgame here is people will be able to deploy their own
|
|
VMs". The endgame here is people will be able to deploy their own
|
|
services through Docker, but this will likely not happen in 2021
|
|
services through Docker, but this will likely not happen in 2021
|
|
* [ ] static mirror network retirement / rearchitecture: 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](howto/static-component#alternatives-considered))
|
... | @@ -184,7 +184,7 @@ The following is a review of the [2020 roadmap](roadmap/2020). |
... | @@ -184,7 +184,7 @@ The following is a review of the [2020 roadmap](roadmap/2020). |
|
|
|
|
|
## Need to have
|
|
## Need to have
|
|
|
|
|
|
* [x] decommissining of old machines (moly in particular)
|
|
* [x] retiring old machines (moly in particular)
|
|
* [x] move critical services in ganeti
|
|
* [x] move critical services in ganeti
|
|
* [x] buster upgrades before LTS
|
|
* [x] buster upgrades before LTS
|
|
* [x] within budget: Hetzner invoices went from ~1050EUR/mth on
|
|
* [x] within budget: Hetzner invoices went from ~1050EUR/mth on
|
... | @@ -404,7 +404,7 @@ Based on those metrics, here are some highlights of this graph: |
... | @@ -404,7 +404,7 @@ Based on those metrics, here are some highlights of this graph: |
|
* centralized logging system (although with no sysadmin responding,
|
|
* centralized logging system (although with no sysadmin responding,
|
|
that's expected, since they're the only ones with access)
|
|
that's expected, since they're the only ones with access)
|
|
* TLS (which is used to serve all websites and secure more internal
|
|
* TLS (which is used to serve all websites and secure more internal
|
|
connexions, like email)
|
|
connections, like email)
|
|
* PostgreSQL (database which backs many services)
|
|
* PostgreSQL (database which backs many services)
|
|
* Ganeti (virtualization layer on which almost *all* our services
|
|
* Ganeti (virtualization layer on which almost *all* our services
|
|
run)
|
|
run)
|
... | @@ -501,7 +501,7 @@ GitLab is a huge accomplishment. It's the most used service, which is exceptiona |
... | @@ -501,7 +501,7 @@ GitLab is a huge accomplishment. It's the most used service, which is exceptiona |
|
|
|
|
|
Yet people are extremely happy with it. Out of those 11 people, everyone but a single soul has said they were happy with it which gives it one of the best happiness score of all services (rank #5)!
|
|
Yet people are extremely happy with it. Out of those 11 people, everyone but a single soul has said they were happy with it which gives it one of the best happiness score of all services (rank #5)!
|
|
|
|
|
|
Most comments about GitLab were basically asking to move more stuff to it (git-rw/gitweb and Jenkins, namely), someone even suggesting we "force people to migrate to Gitlab". In particular, it seems we should look at retiring Jenkins in 2021: only one user (monthly), and an unhappy comment suggesting to migrate...
|
|
Most comments about GitLab were basically asking to move more stuff to it (git-rw/gitweb and Jenkins, namely), someone even suggesting we "force people to migrate to GitLab". In particular, it seems we should look at retiring Jenkins in 2021: only one user (monthly), and an unhappy comment suggesting to migrate...
|
|
|
|
|
|
The one critic about the service is "too much URL nesting" and that it is hard to find things, since they do not map to the git-rw project hierarchy.
|
|
The one critic about the service is "too much URL nesting" and that it is hard to find things, since they do not map to the git-rw project hierarchy.
|
|
|
|
|
... | @@ -525,7 +525,7 @@ So "fixing email" should probably be the top priority for 2021. In particular, w |
... | @@ -525,7 +525,7 @@ So "fixing email" should probably be the top priority for 2021. In particular, w |
|
|
|
|
|
### RT
|
|
### RT
|
|
|
|
|
|
While we're talking about email, let's talk about Request Tracker, a lesser-known service (only 4 people use it, and 4 declared never using it), yet intensively used by those people (one person uses it hourly!), so it desserves special attention. Most of its users (3 out of 5) are unhappy with it. The concerns are:
|
|
While we're talking about email, let's talk about Request Tracker, a lesser-known service (only 4 people use it, and 4 declared never using it), yet intensively used by those people (one person uses it hourly!), so it deserves special attention. Most of its users (3 out of 5) are unhappy with it. The concerns are:
|
|
|
|
|
|
* "Some automated ticket handling or some other way to manage the
|
|
* "Some automated ticket handling or some other way to manage the
|
|
high level of bounce emails / tickets that go to donations@ would
|
|
high level of bounce emails / tickets that go to donations@ would
|
... | @@ -534,13 +534,13 @@ While we're talking about email, let's talk about Request Tracker, a lesser-know |
... | @@ -534,13 +534,13 @@ While we're talking about email, let's talk about Request Tracker, a lesser-know |
|
|
|
|
|
### CiviCRM
|
|
### CiviCRM
|
|
|
|
|
|
Let's jump the queue a little (we'll come back to BBB and IRC below) and talk about the 9th most used service: CiviCRM. This is one of those services that is used by few of our staff, but done so intensively (one person uses it hourly). And considering how important its service is (donations!), it probably desserves to be higher priority. 2 people responded on the happiness scale, strangely, one happy and one unhappy.
|
|
Let's jump the queue a little (we'll come back to BBB and IRC below) and talk about the 9th most used service: CiviCRM. This is one of those services that is used by few of our staff, but done so intensively (one person uses it hourly). And considering how important its service is (donations!), it probably deserves to be higher priority. 2 people responded on the happiness scale, strangely, one happy and one unhappy.
|
|
|
|
|
|
A good summary of the situation is:
|
|
A good summary of the situation is:
|
|
|
|
|
|
> The situation with Civi, and our donate.tpo portal, is a grand source of sadness for me (and honestly, our donors), but I think this issue lies more with the fact that the control of this system and architecture has largely been with Giant Rabbit and it’s been like pulling teeth to make changes. Civi is a fairly powerful tool that has a lot of potential, and I think moving away from GR control will make a big difference.
|
|
> The situation with Civi, and our donate.tpo portal, is a grand source of sadness for me (and honestly, our donors), but I think this issue lies more with the fact that the control of this system and architecture has largely been with Giant Rabbit and it’s been like pulling teeth to make changes. Civi is a fairly powerful tool that has a lot of potential, and I think moving away from GR control will make a big difference.
|
|
|
|
|
|
In generaly, it seems the spam, bounce handling and email delivery issues mentioned in the email section apply here as well. Migrating CiviCRM to start handling bounces and deliver its own emails will help delivery for other services, reduce abuse complaints, make CiviCRM work better, and generally improve everyone's life so it should definitely be prioritized.
|
|
Generally, it seems the spam, bounce handling and email delivery issues mentioned in the email section apply here as well. Migrating CiviCRM to start handling bounces and deliver its own emails will help delivery for other services, reduce abuse complaints, make CiviCRM work better, and generally improve everyone's life so it should definitely be prioritized.
|
|
|
|
|
|
### Big Blue Button
|
|
### Big Blue Button
|
|
|
|
|
... | @@ -563,7 +563,7 @@ The new website is a great success. It's the 7th most used service according to |
... | @@ -563,7 +563,7 @@ The new website is a great success. It's the 7th most used service according to |
|
|
|
|
|
The single negative comment on the website was "transition still not complete: links to old site still prominent (e.g. Documentation at the top)".
|
|
The single negative comment on the website was "transition still not complete: links to old site still prominent (e.g. Documentation at the top)".
|
|
|
|
|
|
Maybe we should make sure more resources are transitionned to the new website (or elsewhere) in 2021.
|
|
Maybe we should make sure more resources are transitioned to the new website (or elsewhere) in 2021.
|
|
|
|
|
|
### Metrics
|
|
### Metrics
|
|
|
|
|
... | @@ -571,7 +571,7 @@ The metrics.torproject.org site is the service that makes people the happiest, i |
... | @@ -571,7 +571,7 @@ The metrics.torproject.org site is the service that makes people the happiest, i |
|
|
|
|
|
### Blog
|
|
### Blog
|
|
|
|
|
|
People are pretty frustrated by the blog. of **all** people that answered the "happiness" question, **all** said they were "sad" about the service. in the freeform, comments mentioned:
|
|
People are pretty frustrated by the blog. of **all** people that answered the "happiness" question, **all** said they were "sad" about the service. in the free-form, comments mentioned:
|
|
|
|
|
|
* "comment formatting still not fixed", "never renders properly"
|
|
* "comment formatting still not fixed", "never renders properly"
|
|
* \[needs something to\] produce link previews (in a privacy preserving way)
|
|
* \[needs something to\] produce link previews (in a privacy preserving way)
|
... | @@ -583,7 +583,7 @@ A positive comment: |
... | @@ -583,7 +583,7 @@ A positive comment: |
|
|
|
|
|
* I like Drupal and it’s easy to use for me
|
|
* I like Drupal and it’s easy to use for me
|
|
|
|
|
|
A good summary has been provided: "drupal: everyone is unhappy with the solution right now: hard to do moderation, etc. Static blog + Discourse would be better."
|
|
A good summary has been provided: "Drupal: everyone is unhappy with the solution right now: hard to do moderation, etc. Static blog + Discourse would be better."
|
|
|
|
|
|
I outline the blog first because it's one of the most frequently used service, yet it's one of the "saddest", so it should probably be made a priority in 2021.
|
|
I outline the blog first because it's one of the most frequently used service, yet it's one of the "saddest", so it should probably be made a priority in 2021.
|
|
|
|
|
... | @@ -600,7 +600,7 @@ Pain points: |
... | @@ -600,7 +600,7 @@ Pain points: |
|
|
|
|
|
> I've ran into sync issues with a lot of users using the same pad at once. These forced us to not use nextcloud for collab in my team except when really necessary.
|
|
> I've ran into sync issues with a lot of users using the same pad at once. These forced us to not use nextcloud for collab in my team except when really necessary.
|
|
|
|
|
|
So overall Nextcloud is heavily used, but has serious reliability problems that keep it from correctly replacing Google Docs for collaboration. It is unclear which way forward we can take here without getting involved into hosting the service or upstream development, neither of which are likely to be an option for 2021.
|
|
So overall NextCloud is heavily used, but has serious reliability problems that keep it from correctly replacing Google Docs for collaboration. It is unclear which way forward we can take here without getting involved into hosting the service or upstream development, neither of which are likely to be an option for 2021.
|
|
|
|
|
|
### onion.tpo
|
|
### onion.tpo
|
|
|
|
|
... | @@ -610,7 +610,7 @@ And thankfully, the latter is a priority that was originally aimed at 2020, but |
... | @@ -610,7 +610,7 @@ And thankfully, the latter is a priority that was originally aimed at 2020, but |
|
|
|
|
|
### Schleuder
|
|
### Schleuder
|
|
|
|
|
|
3 people responded on the happiness scale, and all were sad. Those three (presumably) use the service yearly, monthly and weekly, respectively, so it's not as important (27th service in poplarity) as the blog (3rd service!), yet I mention it here because of the severity of the unhappiness.
|
|
3 people responded on the happiness scale, and all were sad. Those three (presumably) use the service yearly, monthly and weekly, respectively, so it's not as important (27th service in popularity) as the blog (3rd service!), yet I mention it here because of the severity of the unhappiness.
|
|
|
|
|
|
Comments were:
|
|
Comments were:
|
|
|
|
|
... | @@ -650,7 +650,7 @@ Every other service not mentioned here should consider itself "happy". In partic |
... | @@ -650,7 +650,7 @@ Every other service not mentioned here should consider itself "happy". In partic |
|
* remove the "never" option for the service? same as not answering...
|
|
* remove the "never" option for the service? same as not answering...
|
|
* the **service group responses are hard to parse** - each *option*
|
|
* the **service group responses are hard to parse** - each *option*
|
|
ends up being a separate *question* and required a lot more
|
|
ends up being a separate *question* and required a lot more
|
|
processing than can just be done directly in limesurvey
|
|
processing than can just be done directly in Limesurvey
|
|
* worse: the **data is mangled** up together: the "happiness" and
|
|
* worse: the **data is mangled** up together: the "happiness" and
|
|
"frequency" data is interleaved which required some annoying data
|
|
"frequency" data is interleaved which required some annoying data
|
|
massaging after - might be better to split those in two next time?
|
|
massaging after - might be better to split those in two next time?
|
... | @@ -696,8 +696,8 @@ as CSV with the following procedure: |
... | @@ -696,8 +696,8 @@ as CSV with the following procedure: |
|
* Export questions as: **Question code**
|
|
* Export questions as: **Question code**
|
|
* Responses:
|
|
* Responses:
|
|
* Export answers as: **Answer codes**
|
|
* Export answers as: **Answer codes**
|
|
* Colums:
|
|
* Columns:
|
|
* Select colums: use shift-click to select the right question
|
|
* Select columns: use shift-click to select the right question
|
|
set
|
|
set
|
|
3. then click "export"
|
|
3. then click "export"
|
|
|
|
|
... | @@ -724,7 +724,7 @@ above numbers are quite meaningless: GitLab was at "60" which could |
... | @@ -724,7 +724,7 @@ above numbers are quite meaningless: GitLab was at "60" which could |
|
mean 10 people using it hourly *or* 20 people using it weekly, which
|
|
mean 10 people using it hourly *or* 20 people using it weekly, which
|
|
is a vastly different usage scenario.
|
|
is a vastly different usage scenario.
|
|
|
|
|
|
Instead, i've come up with a magic formula:
|
|
Instead, I've come up with a magic formula:
|
|
|
|
|
|
```math
|
|
```math
|
|
H = 10*5^{(A-3)}
|
|
H = 10*5^{(A-3)}
|
... | | ... | |