Since this project is expected to be standardized, consensus is important in the development of any feature. Many renowned software projects have a standardized feature proposal and feedback process, examples of which are listed below:
There are, however, downsides to having such process (and enforcing it): Ruby issue
In order to minimize the overhead incurred by a standardized process, I would urge to keep it lightweight and flexible. It also shouldn't deter the feature author from submitting their work for review and approval.
Since this project is expected to be standardized, consensus is important in the development of any feature. Many renowned software projects have a standardized feature proposal and feedback process, examples of which are listed below:
There are, however, downsides to having such process (and enforcing it): Ruby issue
In order to minimize the overhead incurred by a standardized process, I would urge to keep it lightweight and flexible. It also shouldn't deter the feature author from submitting their work for review and approval.