> It seems people simply want to be outraged at Mozilla.
Nothing else seems to be working. Some users are against Mozillas forced default tracking/telemetry system and forced install of crust that should really be add-ons (Pocket, sync).
If you have any ideas for ways users can enable change which doesn't inconvenience you then please let them know.
Participate in the mailing lists, in the bug trackers.
Submit code patches and report bugs.
In short, participate in the Mozilla community.
Mozilla isn't some sort of impenetrable wall of silence, everything they do is open. The initial mailing list thread that start the entire outrage is open. People on it raised these exact concerns. People engaged them. They want to prevent these exact PR disasters.
"Nothing else seems to be working" is simply untrue if you simply look at the bugtracker and mailing list.
I would suggest that you bring "Nothing else seems to be working" to Google and the Chrome dev team. I haven't heard much outcry from that direction yet and they regularly come up with decisions previously undiscussed with the public and then push it through no arguments about it. Mozilla is not like that no matter how much you want to believe it.
For anyone looking on and thinking of following this advice, please don't treat Bugzilla like GitHub, where advocacy and general discussion is the norm. Bugzilla is for code reviews and for people who are otherwise working together so they can coordinate and get things done. It's not an open solicitation for people to jump in and voice their opinions about general project directions, etc. If you do try to use Bugzilla the wrong way, you'll likely be warned about generating too much noise and possibly banned.
Please do continue using social platforms like blogs, comment sites like this one, etc. for posting opinion pieces and weighing in. That's where general commentary belongs, and it'll be much more effective to boot, if you're interested in getting people's attention or changing minds.
> That is incorrect. Many bug reports are marked as private for security reasons.
Maybe you don't know how this works. Most (almost all) employees do not have access to these bugs, either. But community members can and do have access.
Early access to these reports can be worth literally millions of dollars in the wrong hands, and cause much more damage to our users. However, who gets access isn't decided by who gets a paycheck. It's decided by who is involved and participating and trustworthy. That can be literally anybody.
Bugs are also marked private without any security angle involved whatsoever. Often, these are related to initiatives done in cooperation with so-called "partners".
For an open source project, Mozilla appears to constantly settle on pretty shitty partners if it is true (as is alleged) that it's these partners that insist on secret communication shielded from any community interaction.
Such shady deals in smoke-filled backrooms are one of the small number of things that are hard to impossible to pull off in a community-driven project without constantly pissing off contributors.
Er... pretty much everybody in pretty much all industries prefer keeping their internal communications and their communications with their clients/providers private. Mozilla is one of the only industry actors who manages to keep most of its communications public.
No server-side code. No mobile apps. No public word on when this is going to happen. Yet, this proprietary technology is further integrated into Firefox.
Nothing else seems to be working. Some users are against Mozillas forced default tracking/telemetry system and forced install of crust that should really be add-ons (Pocket, sync).
If you have any ideas for ways users can enable change which doesn't inconvenience you then please let them know.