The initial argument was that Mozilla Corp should not be able to hijack a mechanism designed by the Firefox team to do useful technical (including design etc of course) experiments for marketing without talking to anyone first.
I work on projects with cross-company teams (including Rust, a Mozilla project) and these kinds of project structures are not in conflict with keeping things that need to be kept under wraps under wraps.
-
-
I mean, we can keep abstractly arguing about whether "some MoCo control" is needed to "move forward" but that obscures what happened. Why was this particular mechanism needed to "move forward". Why wasn't a website + opt in addon sufficient?
-
Why is it a threat to Mozilla's ability to "move forward" to structure things in a more opt in way? Did Mr. Robot demand this structure as a condition of doing the deal. Did MoCo leadership determine that deals precisely like this (forced install) are needed strategically?
-
I really doubt it. The "you community zealots don't understand the reality of business" framing is just not really understanding the nature of the critique (btw I'm the CTO of a small business as my day job; I'm not a zealot)
-
I think you’re putting up the strawman now
I dont think you’re a zealot, and I value community and open governance. But as I said upthread, I don’t think this particular case was primarily a failure of governance. Happy to agree to disagree and leave it at that! -
Fair enough on all fronts. And apologies for getting straw-manny on you.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.