Commit f321ec83 authored by intrigeri's avatar intrigeri
Browse files

Update list of upcoming services (refs: #15501)

parent 164b9319
......@@ -60,18 +60,24 @@ area:
can last quite a few more years, but we should plan (at least
budget-wise) for replacing it when it is 5 years old, at the end of
2019, to the latest.
* New candidate services are being considered, such as Piwik
([[!tails_ticket 14601]]) and self-hosting our website
([[!tails_ticket 14588]]). At least Piwik will require lots of
resources and put quite some load on the system where we run it.
Both need to be hosted on hardware we control, where we can do our
best to guarantee our users' privacy. Once the Weblate service
reaches production status in 2018 and is advertised, it'll eat much
more resources; in passing, part of its job will be to often
rebuild the website, which is affected by the single-threaded task
performance limitations described above. OTOH there's no
security/privacy reason why our CI system has to be hosted on
hardware we control.
* The Tails community keeps needing new services; some of them need
to be hosted on hardware we control for security/privacy reasons
(which is not the case for our CI system):
- Added already: self-host our website
- Will be added soon: [[!tails_ticket 16121 desc="Schleuder"]]
- Under consideration:
- [[!tails_ticket 14601 desc="Matomo"]] will require huge amounts
of resources and put quite some load on the system where we run
it; it needs to be hosted on hardware we control.
- [[!tails_ticket 9960 desc="Request tracker for help desk"]]):
unknown resources requirements; needs to be hosted on hardware
we control.
- WIP and will need more resources once they reach production
status or are used more often:
- Weblate is a serious CPU and I/O consumer; besides, part of its
job is to rebuild the website, which is affected by the
single-threaded task performance limitations described above.
- survey platform
# Options
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment