Firefox

17952 readers

445 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

k_o_t@lemmy.ml

170

Firefox 124.0 Release Notes (www.mozilla.org)

submitted 8 months ago by neme@lemm.ee to c/firefox@lemmy.ml

30 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] sugar_in_your_tea@sh.itjust.works 1 points 8 months ago (1 children)

I don't see anything in the OP's comment that defends the status quo.

The OP was focused specifically on technical feedback. Telling the devs you don't like their management process isn't going to change anything. Telling them you think the implementation is substandard because of technical reasons A, B, and C can help change things, because the dev team can respond to that.

If you want to target their management, make an open letter or something and get people talking about it. If you want to influence development decisions, keep the discussion technical.

[–] LWD@lemm.ee 1 points 8 months ago (1 children)

The OP was focused specifically on technical feedback.

Ephera is not the OP. And Ephera decided to talk about business structure for some reason. Maybe you missed that too.

[–] sugar_in_your_tea@sh.itjust.works 2 points 8 months ago (1 children)

Ephera is the OP you responded to, not the OP of the post.

If your feedback is “Don’t roll these out!”, you’re still free to give that feedback

This is the context I'm referring to. Their response highlights that they're not interested in talking about management structure, only the specific technical issues with the feature. They've been incredibly consistent about that.

You went on a tangent about business direction. They responded they're not interested in that, and if that's the way you want to engage, keep the developers out of it because it's completely unhelpful (i.e. don't post stuff like that on their bugzilla, which is unfortunately all to common). I don't think OP is implying that criticizing management decisions isn't worth doing, there's just a more helpful way to do that than including it in a technical discussion.

[–] LWD@lemm.ee 0 points 8 months ago (1 children)

So you have no issue with the validity of my complaint?

Mozilla overpays their CEO
Mozilla has repeatedly screwed over employees
Chasing shiny things isn't helping them
Mozilla is screwing over their users privacy

You just want to argue pedantics? No thank you

[–] sugar_in_your_tea@sh.itjust.works 1 points 8 months ago* (last edited 8 months ago) (1 children)

It's irrelevant to the discussion at hand. Whether I agree with you (I do) has nothing to do with the shopping feature implementation.

If you have technical issues with the shopping feature, bring it up with the developers. If you have policy issues for the management, name and shame with an open letter or similar.

[–] LWD@lemm.ee 1 points 8 months ago (1 children)

Ethos is crucial to code recommendations.

If Mozilla included a virus in Firefox, I wouldn't be suggesting bugfixes to make the virus more user friendly. I would point to the general ethos to not build viruses into their software.

And because Mozilla promises an open Web where you make the choices, hardcoding an addon that promotes the three biggest retailers and a handful of paying advertisers is antithetical to that ethos too.

[–] sugar_in_your_tea@sh.itjust.works 1 points 8 months ago

If Mozilla included a virus in Firefox, I wouldn’t be suggesting bugfixes to make the virus more user friendly. I would point to the general ethos to not build viruses into their software.

The technical problem (i.e. the one relevant to the dev team) is how the virus got into the release product. If it was intentional, it's a management problem and there's no point in talking to the dev team further. If it was due to a breach in their infrastructure, then it absolutely is relevant to discuss w/ the dev team to ensure the breach is contained and fixed.

hardcoding an addon that promotes...

This again can be split into two groups:

technical - opt-in vs opt-out may be a technical decision the devs can make; if it's opt-out, whether it collects information by default may be a dev decision
management - whether it should be hard-coded, opt-in vs opt-out, collect user data or not, etc; there's no point in discussing these with the dev team once it's clear it's not their choice

Target the complains at the right group.