Meritocracy is when people spontaneously adopt something because they genuinely like it,
I'll tell you what's not meritocracy:
- suddenly drop all support for a big software stack leaving the sole choice to use the new, half baked one withouth a proper migration window/path, even when you see people are having trouble with the hurried migration
- leverage your dominance in the windowing toolkit space (ie, having a great bunch of 3rd party apps using your toolkit) and make it difficult to use the toolkit separated from the rest of the stack, removing functionality and breaking compatibility with 3rd parties on each point release, in the name of *branding*
- make all your related projects and components a big interdependent mess, promoting a "my way or the highway" approach to adoption of your project (example)
- btw, the previous example illustrates another non-meritocratic point: what the hell are you doing in a 3rd party app bugtracker telling them to be anything??
- breaking collaboration with any project that "competes" with you, so you further reduce *choice*, the basic property of meritocracy
Hope this tiny list helps to enrich your definition.