Backend Engineering Confluence Space
TL;DR
Why
- Backend Infra team requires an internal space to publish team-specific information and/or documentations (team members, initiatives, meeting notes, etc.).
- Combining Backend Infra team-specific documentations and Backend Engineering documentations feels awkward.
- Storing Backend Engineering documentations in Backend Infra space may set wrong expectations of sole ownership and accountability.
Impact
- There should be no impact at all, all previous links are automatically updated.
- [Hopefully] Increase contribution in backend engineering organization in keeping documentations up-to-date.