Based on some conversations that I've started having, I think it's quite likely that SLAs will be an area of concern. The primary driver as I understand it is that we don't always have a clear path to getting things addressed in our code base. Lack of clear ownership (stewardship) and expectations of that commitment have become concerns for both external and internal contributors/stakeholders.
Some thoughts that I have on this are:
- Teams could define their own SLAs initially as we figure out if it makes sense to have standard SLAs.
- SLAs could be two way contracts. SLAs only come into play if prerequisites are met (i.e., we won't prioritize code reviews if you've not run linters, ran tests, etc...).
- We could use SLO vs SLA (Objective vs Agreement). Less of a commitment/contract and more of an internal measure.
- Initially I think the idea is to set some targets, see how often we meet them, and adjust as necessary. These learnings will help us do yearly resource planning.
Reading group already does this to some extent: Reading/Component responsibility.
Other thoughts on the topic if SLAs?