As the project grows and becomes more complex, there is a need for a more structured way to propose, discuss, and document significant technical changes. While we currently use Architecture Decision Records (ADRs) to document durable decisions, we lack a formal process for the preceding phases: technical direction exploration (RFCs) and detailed implementation planning (Technical Designs).
Goals:
- Formalize the Engineering Process: Clearly define how technical changes move from roadmap ideas to public delivery.
- Introduce RFCs: Establish a "Request for Comments" process to reach consensus on technical direction before significant effort is invested.
- Introduce Technical Designs: Provide a framework for detailing implementation plans, covering edge cases, security, and privacy.
- Improve Discoverability: Ensure these new processes are well-integrated into the existing documentation so that contributors can easily find and follow them.
As the project grows and becomes more complex, there is a need for a more structured way to propose, discuss, and document significant technical changes. While we currently use Architecture Decision Records (ADRs) to document durable decisions, we lack a formal process for the preceding phases: technical direction exploration (RFCs) and detailed implementation planning (Technical Designs).
Goals: