Adopt a more formal decision making process

[andywhite37]

We have some potentially large/impactful decisions coming up to revitalize/reorganize the relude ecosystem of libraries. Some of these decisions have objective pros and cons that we can try to identify, while some might involve more subjective feelings or stances, and some might just need a decision to be made. We'll likely have to make some compromises both personally and within the project to be able to move forward.

Some examples for reference, but not for discussion here:

• Potential project re-organization (break things up into smaller, more cohesive packages)
• Monorepo/package set direction
• Whether to adopt the use of interface files as a way of doing things
• Breaking changes in a "2.0" release
• The future direction of ReasonML/rescript/ocaml/etc.

I talked to @mlms13 and we thought it would be good to maybe adopt a more formal decision making process, so we can feel like big decisions are discussed and vetted properly. We may not end up always agreeing on everything, but at least we can voice our concerns and have a chance to try to reach a place of harmony before moving forward.

I found this decision-record template, and it seems decent, but curious if anyone has any suggestions.