...
You can't get a job that requires a Github OSS history. You're severely disadvantaged in job hunting when OSS contributions are a major metric.
If people tested your suitability for a job by pair programming with you, or looking at code samples, you'd look just as good as someone who contributes to OSS. But because OSS is an important metric, you're disadvantaged.
Does this make clear how it's discriminatory?
(1) Are there any companies which literally remove a person's resume from the running if his/her fit seems to be good in other ways, just because they do not have a public facing github repo? Or is this just something that people are talking about but not actually implementing.
(2) In what sense is any job requirement not discriminatory? Requiring 5 years of Ruby experience discriminates against those with only 6 months of Ruby experience. Requiring a Masters degree discriminates against those with a Bachelors or no degree. Making the candidate do a programming test discriminates against people who don't perform well on tests. The question is whether the programmers that a company hires based on a Github criterion are measurably "better" than those hired using different criteria. As far as I know, no such comparison has been done.
I do not have time to interview hundreds of people, so we have to apply some filtering. Are we going to potentially filter out a good candidate because they didn't take the time to make themselves stand out? Maybe, but I'm okay with that.
If that single mother literally has no time outside of her 40 hour work week to be learning new things and staying current with technology, she will have a hard time finding new jobs regardless of the screening methods used.
This is also one contrived example. Not an entire "social class" of the programming population.
But it was always ok to bully nerds, physically or other way.
An embedded systems designer may exhibit less "merit" than a wizard of front-end programming when dropped into front-end programming - and vice-versa. There's no absolute, gold standard for merit, no matter how hard we try to find one.
That doesn't mean that we shouldn't try to hire the most suitable (meritorious?) people for our own companies. Just because merit is a hazy target, and subject to different caveats, doesn't mean that it doesn't exist, or that you can't judge one person as more effective than another for a specific set of tasks. That's why we make job descriptions specialized, so that match peoples skills and attributes to the needs of the job.
The idea of a meritocracy presumes that everyone starts off and continues through with the same level of access to opportunity, time, and money...
Meritocracy is simply the belief that meritorious people will (either deterministically or probabilistically) rise to the top. It is not the belief that the distribution of merit is fair.
A person who ate lots of lead paint as a child, had Down's syndrome, or some similar tragic circumstance, will have very little programming ability and very little merit. This is unfair. The lack of mentally retarded individuals in open source is not evidence against meritocracy.