According to TFA, it's not quite "if they feel like it", it's when there isn't consensus among the community but (1) it's clear that there is a problem and (2) the Go architects can agree on a path forward.
In the module system case, there was a lot of consensus in the community, including widely-used and pretty mature tooling, and the core team surprised the community by implementing their own approach unilaterally. That predated the current rules of engagement. But in a similar situation today where the core team felt the community’s consensus was wrong, I wouldn’t be too surprised if that happened again.
In the module system case, there was a lot of consensus in the community, including widely-used and pretty mature tooling, and the core team surprised the community by implementing their own approach unilaterally. That predated the current rules of engagement. But in a similar situation today where the core team felt the community’s consensus was wrong, I wouldn’t be too surprised if that happened again.