spicy take, standards processes
A standards process that responds to complaints about the spec/tech/system with something like "file a formal spec change proposal if you'd like to see it changed" will only ever produce specifications that benefit the privileged
spicy take, FOSS, standards processes
This is basically the standards equivalent of the equally-exclusionary practice in FOSS to respond to criticisms with "well just make a PR to change it" or "well just fork the project then", all of these are just responses that try to dismiss the criticism without making it sound like they are
spicy take, FOSS, standards processes
(Because if you actually cared about the criticism, you would be asking yourself "what support does this person need to have their problem solved" and then you'd immediately discover that "file a PR/proposal" is completely outside the realm of the viable for most people)
