You seemed to be going off on a tangent about their strategic decisions, when I was talking simply about the feature development process.
I have no interest in discussing their strategic decisions, because flaming about it in some random internet forum isn’t going to change anything anyways.
If there was a chance that we worked out a more viable strategy, which Mozilla could tangibly realize, that would be different. But presumably, neither of us work in a full-time managerial position at Mozilla, so to assume so, would be absolute madness.
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.
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.
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.
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
deleted by creator
You seemed to be going off on a tangent about their strategic decisions, when I was talking simply about the feature development process.
I have no interest in discussing their strategic decisions, because flaming about it in some random internet forum isn’t going to change anything anyways.
If there was a chance that we worked out a more viable strategy, which Mozilla could tangibly realize, that would be different. But presumably, neither of us work in a full-time managerial position at Mozilla, so to assume so, would be absolute madness.
deleted by creator
Make a decent tab grouping feature
deleted by creator
Make tabs look like tabs again, and not like huge buttons!
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.
deleted by creator
Ephera is the OP you responded to, not the OP of the post.
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.
deleted by creator
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.
deleted by creator
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.
This again can be split into two groups:
Target the complains at the right group.