-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

The last week and a half, the dev team split up and took on specific focus areas. The aim being to spend a few days and quantify the technical debt and also validate the features we had already delivered ( or had hoped to have delivered ). This allowed us to run a sort of retrospective sprint. The result of which was checklists that allow us to measure a state of completeness in the following areas :

- - Post-build and regular image scanning + reporting - - Ability for a contributor to onramp rapidly - - Production band-aid's / flaky code that needed immediate attention - - Ensuring we've completed the initial set of user stories we'd set out to deliver on.

Over the next 2 weeks, our aim is going to be to try and close down as much of this debt as we can, before moving back to focusing on Feature development.

We've also started handing off SRE roles and developing a deployment pipeline to move towards a CD model in the coming weeks. As we move towards production with the SRE / Dev splits, there will be some code work that we need to work on, and we will try to track that via a priority task list, labelled as 'bugs/issues'.

In order to better organise the tasks, we've created 5 labels as follows : - - Contributor Process / Developer enablement - - Service Feature - - User - - Scanner + Testing - - Production Critical

We've also agreed, and reminded ourselves, to not work on things that are not on cards and in the current sprint.

And we've agreed to run daily standups at 10:00 UTC daily.

- -- Karanbir Singh, Project Lead, The CentOS Project, London, UK