Reviewing Process in Dynamatic

[shundroid]

In the PR #460 I just opened, I noticed that the elastic-miter README.md hadn't been reviewed.

This raised a broader concern for me about the current review process in Dynamatic. I've noticed that some recent PRs were merged very quickly, sometimes without any suggestions like #449, even though they involved a significant amount of code.

This can lead to issues for users later on. I actually ran into trouble with the unreviewed README.md.

That said, I'm not suggesting we formalize the review process or slow things down. I value the flexibility and speed we have.
So, what if we agree on one principle?

If you approve a PR, you have the responsibility to explain how the code works and why the design choices were made. (including documents or other build files)

Would people be on board with that?

@murphe67 @Jiahui17 @Carmine50 @AyaElAkhras @schilkp