"What would you suggest people who encounter a problem such as this do if they personally don't have the ability to personally fix the problem themselves?" The

"What would you suggest people who encounter a problem such as this do if they personally don't have the ability to personally fix the problem themselves?" There's a difference between getting someone's attention, and then them disagreeing with you. If you are trying to get attention, i'd go with the mailing list in this situation. If they just disagree with you, sometimes, you gotta accept that someone doesn't agree with you about the product vision and let it go (this assumes your constraints - they don't have ability/time to fix themselves). They will either be right or wrong, and it will succeed or fail. "This isn't an issue specific to chromium or even google. There are a lot of projects that seem to have an inside and an outside with those on the outside rightly-or-wrongly feeling unheard." Sure, and i think companies/people should be very clear with governance models, participation models, etc. I also think they should be very clear about things like this. Actually one of the hugest clashes i often see is open source projects that do have a product vision end up clashing with minorities of their user bases who don't fit in that product vision (either due to changes or never fitting in the first place), etc. Those clashes often seem much more emotional for people. (I honestly don't know enough about chrome anymore at all to know whether that's the case. I'm only talking about the general situation you are describing). A lot of the inside vs outside cases that i've seen fall into "product vision decided inside, you are welcome to participate if you want but we aren't changing it" style of project. It's more rare (though i've seen it) to see "we have no vision of where we are trying to go but we still are going to semi-ignore random contributions/etc. We're gonna make it so you think we might care, but not actually try enough that anything happens " Worse, a lot of the time the latter prevents other competing projects from existing because people spend time trying with the existing one then are too burned out to do anything else. The product ones often at least give straight answers, even if people hate the answers.