In reply to Dovy.

Again, I think it's fair criticism that we could have done better regarding communication of this decision. Our modus operandi has always been to post on Make/Themes regarding intended changes, and solicit feedback, and then incorporate that feedback into the decision. We do things a bit differently now, in the post-Slack environment; and we're adjusting to it in our workflow, just like everyone else. So we could have done better.

The reason I found the editorial to be a bit ironic is because, of all the myriad decision-making processes in the WordPress development world, the TRT is the one that most tries to solicit input and feedback. There is no RFC for core decisions. There is no RFC for Plugin Review decisions. Wash/rinse/repeat for all the rest of the teams.

And honestly, nor should there be. The development of the entire project would come to a standstill if every major decision had to go through an RFC.

There already exist channels and means of communication to provide input into most WordPress-related decisions. That people don't know about them, or choose not to use them, does not constitute a good rationale to implement RFCs.