Skip to content

Commit

Permalink
remove irrelevant sections
Browse files Browse the repository at this point in the history
  • Loading branch information
Cara Haas committed Oct 23, 2023
1 parent ebad11e commit fb322ba
Showing 1 changed file with 0 additions and 49 deletions.
49 changes: 0 additions & 49 deletions doc/developer/design/20231002_cluster_vision.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,52 +122,3 @@ query plan changes, which do not serve customers' production workflows, if they

**Much Later**
* Clusterless.

## Minimal Viable Prototype

<!--
Build and share the minimal viable version of your project to validate the
design, value, and user experience. Depending on the project, your prototype
might look like:
- A Figma wireframe, or fuller prototype
- SQL syntax that isn't actually attached to anything on the backend
- A hacky but working live demo of a solution running on your laptop or in a
staging environment
The best prototypes will be validated by Materialize team members as well
as prospects and customers. If you want help getting your prototype in front
of external folks, reach out to the Product team in #product.
This step is crucial for de-risking the design as early as possible and a
prototype is required in most cases. In _some_ cases it can be beneficial to
get eyes on the initial proposal without a prototype. If you think that
there is a good reason for skpiping or delaying the prototype, please
explicitly mention it in this section and provide details on why you you'd
like to skip or delay it.
-->

## Alternatives

<!--
What other solutions were considered, and why weren't they chosen?
This is your chance to demonstrate that you've fully discovered the problem.
Alternative solutions can come from many places, like: you or your Materialize
team members, our customers, our prospects, academic research, prior art, or
competitive research. One of our company values is to "do the reading" and
to "write things down." This is your opportunity to demonstrate both!
-->

## Open questions

<!--
What is left unaddressed by this design document that needs to be
closed out?
When a design document is authored and shared, there might still be
open questions that need to be explored. Through the design document
process, you are responsible for getting answers to these open
questions. All open questions should be answered by the time a design
document is merged.
-->

0 comments on commit fb322ba

Please sign in to comment.