Well, personally I think that no one should be treated as damaged goods for the rest of their career, but before we go all kneejerk on ekr, let's make sure we u

Well, personally I think that no one should be treated as damaged goods for the rest of their career, but before we go all kneejerk on ekr, let's make sure we understand how things work at Mozilla. Mozilla separates our codebase for Firefox and other projects into discrete units of code or activity, called Modules. An overview: https://wiki.mozilla.org/Modules https://wiki.mozilla.org/Modules Module Owners have final say over the area their module covers, unless they are sub-module, in which case a disagreement can be escalated to the parent module. Module Peers are appointed by Module Owners to help them out based on a history of good contribution. In practice, this roughly means that peers and owners handle code review and merging of code for the code covered by that module. So, let's look at the list of Modules: https://wiki.mozilla.org/Modules/All https://wiki.mozilla.org/Modules/All Eric's peer of a few WebRTC-related modules and owner of the Media Transport module, which AFAICT is a submodule of WebRTC, owned by someone else. This is to be expected for someone who has done lots of good work around WebRTC and media. Reading that bug, as far as I can see he's making public comments on a public bug about his opinions of how something in some open source code should work. He's been recognized by his peers as a skilled (paid) contributor in the area and thus his opinion is valued. He's making arguments, not shutting down people. He's even discussing the issue and asking for a decision from the WebRTC module owner, who has more say over this than he does. Looks fine to me.