...
Project Role | Team member(s) |
---|---|
Technical Product Owner / LTSLT Owner | Stefano Cossu (LTS) |
Software engineers | Brian Hoffman, JJ Chen |
QA | Stefano Cossu, Brian Hoffman, JJ Chen |
Functional documentation | Stefano Cossu, Brian Hoffman, JJ Chen |
Scrum Master | Stefano Cossu |
Project Manager | Vitaly Zakuta (LTS) |
* Pierre-Anthony Lemieux deferred to John Cupitt for carrying out the development, remaining available for advising on Kakadu-specific topics. We have not yet established whether such consulting will be pro bono or for a fee. In the latter case, we should request a cost estimate, but ideally we would like to have one contractor billing for the whole project.
VII. Estimated Schedule (tentative)
...
Project Assumptions
Project Constraints
- Other DRS Futures integration priorities contending for developers' time
- Infrastructure capacity and cost (the tools should be scalable, but some batches could still take many weeks or months to complete)
Project Dependencies
Project Risks
Description | Plan | Impact | Owner |
---|---|---|---|
Remediation process takes an unexpectedly long time | Start with a small batch; extrapolate timing; increase batch size progressively; adjust forecast iteratively | Project timeline | |
Remediation process is unstable and requires frequent monitoring | Build solid exception handling; perform extensive load testing in advance | Staff time | |
Large numbers of image conversion tasks fail | Build non-blocking reporting system; allow automatic retrying for 5xx errors; review failures separately | Staff time; may require re-engineering remediation tools or infrastructure | |
Reference replacement does not go according to plans | Test small batch of replacement actions; back up databases; report failed replacement to avoid failures falling through cracks; test each image (HEAD req) before deleting old version | Lost references / broken images; old images cannot be replaced for a long time and impose extra storage costs |
IX. Acceptance
Accepted by [ TODO ]
...