RFC process for managing deep level design of Praefect/Gitaly

Problem

On Gitaly, we don’t really have a single architect driving the overall design of the system. We have several engineers working on different components in parallel. The lack of centralized design over Praefect internals can lead to compromises in architectural integrity if we aren’t all in sync while working individual issues.

Furthermore, successful Gitaly issues tend to be smaller in scope and favor breadth of work over depth. If an issue isn’t actionable, it becomes stale and eventually dies.

Proposal

We should adopt a formal RFC (or design document) process for guiding Gitaly/Praefect architecture in ways that issues don’t work well.