Or you know, D) they'd rather keep their own quality of life than significantly reduce it. They wouldn't be able to keep their mostly crime-free, large safety net high trust society with open borders, it's just not possible. There's already significant struggles in some European countries due to refugee immigration, and that's with fairly strict borders. It's a bit absurd that you're phrasing it as if the only sacrifice would be seeing poor people tbh.
But yes, the core reason is obviously selfish, but also understandable.
Hm, accidentally hit the submit button before the reply was fully done. Anyway, I think the story point completed, tickets done, pull requests submitted or even number of commits works somewhat well for measuring developer productivity, as long as nobody is aware of it. The least productive developers I've worked with did tend to have very few commits in comparison to more productive peers, but obviously that'd quickly change if they found out that it's a metric being watched, I see no reason for why story points wouldn't cause similar issues. Fight to get the "easy points", less collaboration etc.
It becomes more of a discussion and is less likely to bruise egos. In my experience I've had more success getting things done by building concensus that way, but ymmw.
You write a lot of words to explain how the maintainer could justify his malice. At the end of the day it's still done out of malice, though.
Unless he's gone absolutely bonkers, he's doing this to intentionally cause damage. The reason for it does not matter, as the definition you posted helpfully points out.
That's a very strange view. Of course people with a native language will make similar mistakes when learning a new language. Swedish speakers have issues pronouncing "jump" ("yump" ) and cheap ("sheep") because the language doesn't really have those sounds. Because were and was is the same word in Swedish, that's also a common mistake.