MySQL Community Design Proposal
Use this page to draft a design proposal in a format that is easier for community reviewers to follow. The form helps capture proposal metadata, requirements, impact areas, implementation notes, and QA considerations, then lets you preview and export the result as Markdown, JSON, or CSV.
Export ▼
Document metadata
Capture enough context for reviewers to understand ownership, contact details, status, and intended target release.
1. High-Level Description
Keep this section approachable. A reviewer should understand the problem, motivation, and intended scope before reading the implementation details.
2. Requirements
Use direct, normative language where appropriate. These requirements should satisfy the motivating stories above.
3. Impact Checklist
Use this as a fast reviewer summary. It signals which interfaces or subsystems are touched, but every checked item still needs detail later in the proposal.
4. High-Level Specification
Explain the design in enough detail for reviewers to evaluate correctness, usability, observability, compatibility, and risk.
Configuration / Knobs
Keep this section detailed. It is often where ambiguity creates the most review churn.
5. Low-Level Design
Use this section when implementation detail is needed for review or handoff.
6. QA Notes
Capture edge cases and validation considerations without overly constraining independent QA exploration.