Owners::
Other docs:
TL;DR: We would like to propose an improved, official proposal process for Thanos that clearly states when, where and how to create proposal/enhancement/design documents. We propose to store done, accepted and rejected proposals in markdown in the main Thanos repo.
More extensive architectural, process, or feature decisions are hard to explain, understand and discuss. It takes a lot of time to describe the idea, to motivate interested parties to review it, give feedback and approve. That’s why it is essential to streamline the proposal process.
Given that as open-source community we work in highly distributed teams and work with multiple communities, we need to allow asynchronous discussions. This means it’s essential to structure the talks into shared documents. Persisting those decisions, once approved or rejected, is equally important, allowing us to understand previous motivations.
There is a common saying "I've just been around long enough to know where the bodies are buried". We want to ensure the team related knowledge is accessible to everyone, every day, no matter if the team member is new or part of the team for ten years.
Thanos process was actually following proposed process. We were just missing written rationales and official template that will make Thanos community easier to propose new ideas and motivate them!
Goals and use cases for the solution as proposed in How:
We want to propose an improved, official proposal process for Thanos Community that clearly states when, where and how to create proposal/enhancement/design documents.