14. Canonical Replacement
14
1. On the technical front we need more resources to:
t.a.1 — tackle outstanding build issues (e.g. automate ARM build of Java based docker images)
t.a.2 — Improve QA by implementing automated testing (both component and AGILE stack level)
t.a.3 — Identify and resolve performance bottlenecks
t.a.4 — Provide resources to resolve software related issues (prioritized by a project level taskforce)
— Fix high priority software bugs— Implement “worthy” improvements (request from project
partners, or from external users such as open call winners)
t.a.5 — Provide technical support to AGILE users (open call winners, other users)
t.a.6 — Improve the quality and/or the attractiveness of the AGILE development environment
(implement protocols, implement "catchy" device support, etc.)
2. dissemination
d.a.1— Dissemination activities which, while not foreseen in the current DoA, could enhance the
exploitation of the AGILE project results.
3. security
s.a.1 — Handling lack of expected Canonical contribution to the Security work-package
Project Status Assessment