When people talk about wanting Firefox to have an open structure that treats Mozilla and non-Mozilla people the same, they are talking about things like https://github.com/gregglind/addon-wr/issues/36 …. There is no good reason why "sideloading an ad to FF" needs to be a thing Mozilla Corp is able to do.
I agree with your empirical statement. I think it's a bad thing. That was the point of my original tweet. I think you're on shaky ground to say that there's no connection between MoCo being the same as Firefox leadership and a MoCo ad being delivered through SHIELD.
-
-
I am not claiming there’s no connection. I don’t think the “ad” was a bad idea in itself (but execution could’ve been better). Being able to arrange co-marketing deals with other companies is a good example of the benefits of MoCo’s influence on Firefox, IMO.
-
You keep expanding the scope of my objection to turn it into a straw man.https://twitter.com/wycats/status/941928685824745472 …
-
I have no objection to comarketing in principle and think things like search deals are healthy. I'm objecting to the fact that it seems MoCo management has full control over the entire technical infrastructure and can bypass the project's leadership to secretly ship things.
-
That is just empirically what happened here, and I think it's not a very extreme position, nor an attack on a healthy role for MoCo, to say it's a problem.
-
I doubt there was anyone in “project leadership” that wasn’t aware and accepting of this.
-
If "leadership" literally means the top echelons of MoCo, that doesn't mean anything. But certainly top technical leaders, even within MoCo, were caught off guard.
-
People are always caught off guard (internal comms are hard), but it’s usually people not directly involved with Firefox product dev (again I speak from experience)
-
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.
- 5 more replies
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.