Earlier quoted context omitted.
Who gets to define merit? Say a certain style was more likely to pass code review. And that style was more often associated with people with CS degrees, vs self-taught programmers. Even though it's a stylistic choice, functionally equivalent, one is "better" than the other and is introducing bias. It's very easy to do, especially because consistency is important for legibility, but a stylistic choice nonetheless. I t…
You should follow the project's style when you start contributing. If style is pointed out in code review, fix it.
It does illustrate the issue of using "meritocracy" without anything else. It's like saying "we follow a style guide", and then not providing that style guide. Obviously sub-optimal.
(The example breaks down since providing a style guide is doable, whereas providing a "merit guide" is hard/impossible? In that case, is it better to remove that? I don't know.)