Design Issue: Long Term Maintenance Plan and Security Posture

[rhosking]

There are number of understood and emerging tasks and processes that need defining, documenting and planning for when we consider the longer term viability of this project. The following are some already identified issues:

• [ ] How dependencies (largely software libraries) will be updated over time, by whom, when, and what is the priority and risk of doing (or not doing) this
• [ ] Put in place a incident response plan for any security incidents
• [ ] Review on-going data storage costs and data lifecycle automation and retention policies
• [ ] Consider putting in place a roster system for responsibilities for fixing issues in production. This could equally apply to Telescopes, Workflows, Kibana or other APIs and services we have deployed