3 Matching Annotations
- Sep 2020
Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.
A huge part of the value on an RFC is defining the problem clearly, collecting use cases, showing how others have solved a problem, etc.
An RFC can provide tremendous value without the design described in it being accepted.
- defining the problem clearly is as valuable coming up with specific implementation/solution
- contribution guidelines: should explain motivation for change
- iterative process
- defining the problem clearly
- okay for proposal to not be accepted
- answer the "why?"
- iterative process: building on previous attempts/work