this post was submitted on 19 Mar 2024
170 points (96.7% liked)

Firefox

20372 readers
142 users here now

/c/firefox

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

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago
MODERATORS
k_o_t@lemmy.ml
golden_zealot@lemmy.ml
170
Firefox 124.0 Release Notes (www.mozilla.org)
submitted 1 year ago by neme@lemm.ee to c/firefox@lemmy.ml
22 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 1 year 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 1 year ago* (last edited 4 weeks ago) (1 children)

deleted by creator

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 year 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.