From the article: "It has been working now without our acceptance, without controls, without communications".
This person has been doing volunteer work for a long time, attempting to create a helpful environment. Then suddenly, from above a machine is turned on that shits all over that effort. Makes one feel unwelcome, and unseen...
This right here is the crux of the matter. But it seems to be how Mozilla operates. They frequently show a lack of awareness and consideration towards their long time supporters. I doubt this particular incident will lead to any changes, but I really wish they'd do some introspection...
Unless there is some sort of blowback, this sort of thing is likely to happen again to someone, and I understand how some people may not want to be involved anymore, and I understand how Mozilla will keep being Mozilla (just like other organizations will continue their current behaviors until some catalyst changes that behavior).
This person is already a stakeholder, you don't have a choice to add or not add them, you have a choice to include or not include them. And it's a gamble to not include them for this exact reason.
I'm all for keeping stakeholder counts as low as possible but you can't do it by just pretending some of your stakeholders don't exist, that's no good and in my experience, usually ends exactly like this.
Mix that with incidents like this and you basically are seeing the real time stagnation of open source contributions. You'll only contribute if you work at a top company who chooses to have staff support it.